Yes, skos:prefLabel and skos:altLabel I believe are also subproperties of rdfs:Label.<div><br></div><div>So you could do any of these but if you want it to have the name scientificName and be interpreted as</div><div>a rdfs:Label one way is to have it be either a subproperty of rdfs:Label or the skos:Label. In the end,</div>
<div>they are all interpreted as a kind of rdfs:Label.</div><div><br></div><div>> <span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; ">I don't really see why this is so different from DC.</span></div>
<div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br></span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">Yes, people using DC also have the problem in that they can't figure out do I put a URI here or a string?</span></font></div>
<div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br></span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">If you look at the expected states in this example you will see the names for the states, that is because Sindice</span></font></div>
<div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">knows to put in the label associated with the geoname URI. Otherwise you would see a geoname URI. The</span></font></div>
<div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">same is true for the GNI names. The geonames label is from the GeoNames RDF, I simply mark these up</span></font></div>
<div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">using the Geonames URI's. In a sense you use the URI and you get the label for "free"</span></font></div>
<div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br></span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">< <a href="http://sig.ma/search?pid=e95218de8a57e4cda099116caa25c5ac">http://sig.ma/search?pid=e95218de8a57e4cda099116caa25c5ac</a> ></span></font></div>
<div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br></span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">The use of hasScientificName vs scientificName is simply to make the triples read more naturally.</span></font></div>
<div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">It is not required.</span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br>
</span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><concept> dwc:hasScientificName "Puma concolor"</span></font></div>
<div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br></span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">I think part of the problem we are having is that people are not recognizing how different RDF is from straight XML.</span></font></div>
<div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br></span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">You really just have to add some variant of rdfs:Label in one of the files and all the other things that reference that</span></font></div>
<div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">URI will get the label for free.</span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br>
</span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">So as long as the GNI or Geonames RDF contains the label in it's RDF, I don't need include that in my RDF.</span></font></div>
<div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br></span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">At the level of the cloud or the contents of the triple store the label only has to be associated with a particular URI</span></font></div>
<div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">once.</span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br>
</span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">- Pete</span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br>
</span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br></span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br>
</span></font><br><div class="gmail_quote">On Wed, Oct 6, 2010 at 3:01 AM, Rutger Vos <span dir="ltr"><<a href="mailto:rutgeraldo@gmail.com">rutgeraldo@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
For labels, would it perhaps make sense to use skos:prefLabel and skos:altLabel?<br>
<div><div></div><div class="h5"><br>
On Wed, Oct 6, 2010 at 8:02 AM, Peter DeVries <<a href="mailto:pete.devries@gmail.com">pete.devries@gmail.com</a>> wrote:<br>
> Hi Steve,<br>
> You are probably right that it might be best to use rdfs:Label, but I am<br>
> thinking we might be able to get the same<br>
> result my defining the string variants as subproperties of rdfs:Label.<br>
> This would make them an rdfs:Label but a special kind of rdfs:Label.<br>
> This is one of those things that I would test with Sindice and URIburner to<br>
> see if they interpret these correctly.<br>
> This would require a live vocabulary that Sindice could look at to determine<br>
> that hasScientificName is to be<br>
> treated as a rdfs:Label.<br>
> - Pete<br>
><br>
> On Mon, Oct 4, 2010 at 10:41 AM, Steve Baskauf<br>
> <<a href="mailto:steve.baskauf@vanderbilt.edu">steve.baskauf@vanderbilt.edu</a>> wrote:<br>
>><br>
>> Although this specific example deals with taxonomic name identifiers, it<br>
>> is related to a previous discussion on this list about how we should use the<br>
>> dwc:xxxxxID terms and other terms (such as recordedBy and identifiedBy) that<br>
>> could have either a string (literal) or URI form. Although I don't really<br>
>> want to see an unnecessary proliferation of Darwin Core terms, I think that<br>
>> in the interest of clarity (particularly where RDF is involved) there either<br>
>> should be multiple terms that make it clear what form of identifier is<br>
>> expected, or else there should be an understanding that in RDF the default<br>
>> for such a term is a URI which would then have an rdfs:Label property which<br>
>> was the string form. I think the former would be preferable to the latter.<br>
>><br>
>> I came to this opinion when trying to write RDF describing an herbarium<br>
>> specimen. The collector should be the dwc:recordedBy property of the<br>
>> specimen. Optimally, there would be a database in which known collectors<br>
>> were assigned URIs so that "Glen N. Montz", "Glen Montz", "G. N. Montz",<br>
>> etc. would all be different labels for the same resource. However,<br>
>> realistically, I'm not going to drop what I'm doing to set up such a<br>
>> database (even if I were capable of doing it, which I'm not). So I ended up<br>
>> just writing it as <dwc:recordedBy>Glen N. Montz</dwc:recordedBy> even<br>
>> though I knew it wasn't probably the best thing. In a large Occurrence<br>
>> database that was compiled from the RDF created by a lot of people, there<br>
>> might end up being a mixture of strings and URIs for dwc:recordedBy<br>
>> properties of the specimens. It seems to me like it would be better to have<br>
>> properties like dwc:recordedBy for strings and dwc:recordedByURI for a<br>
>> corresponding URI (and I suppose dwc:recordedByLSID if anyone wants to use<br>
>> it). Of course, this would require a number of term additions to DwC and<br>
>> clarification in the DwC documentation that the generic version was intended<br>
>> for strings.<br>
>><br>
>> With respect to the example<br>
>> <dwc:hasScientificNameLSID<br>
>> rdf:resource="urn:lsid:catalogueoflife.org:taxon:24e7d624-60a7-102d-be47-00304854f810:ac2010"/><br>
>> I think you are right that (with the possible exception of rdfs:seeAlso)<br>
>> there is an expectation that an rdf:resource attribute will be a resolvable<br>
>> URI that produces RDF. So<br>
>><br>
>> <dwc:hasScientificNameLSID>urn:lsid:catalogueoflife.org:taxon:24e7d624-60a7-102d-be47-00304854f810:ac2010</dwc:hasScientificNameLSID><br>
>> is probably better.<br>
>><br>
>> Steve<br>
>><br>
>> Peter DeVries wrote:<br>
>><br>
>> I have been thinking about the following pattern. In part after looking at<br>
>> the GBIF vocabulary.<br>
>> I am not sure if it is even a good idea but might be worth some<br>
>> discussion.<br>
>> For those fields that have both a string and "ID" form maybe the following<br>
>> pattern might be useful<br>
>> hasScientificName = string form<br>
>> hasScientificNameURI = Resolvable LOD compliant identifier<br>
>> hasScientificNameLSID = LSID identifier which could be resolvable once you<br>
>> add the "http:proxy" etc.<br>
>> This allows all three forms to be included if desired, it also provides a<br>
>> hint as to how the field should be interpreted or resolved.<br>
>> One group could also provide a mapping service so that each record does<br>
>> not need to include all three forms, but would allow systems<br>
>> to find the matching LSID for a given URI or vs. versa.<br>
>> My concern was that it would be difficult to infer how a scientificNameID<br>
>> should be interpreted by other systems.<br>
>> Is this an LSD, is it a URI, is it a UUID etc. ?<br>
>> This impacts the structure of the RDF.<br>
>> * Note that the actual identifiers might not be correct, the example below<br>
>> is more about the form of the RDF<br>
>> * For instance, I don't think it is probably correct to see the COL LSID<br>
>> as just a namestring<br>
>> * Also in this example the GNI name does not exactly match the string name<br>
>> <dwc:hasScientificName>Puma concolor (Linnaeus<br>
>> 1771)</dwc:hasScientificName><br>
>> <dwc:hasScientificNameURI<br>
>> rdf:resource="<a href="http://gni.globalnames.org/name_strings/6c3dc35f-d901-5cc5-b9c8-ad241069b9f8" target="_blank">http://gni.globalnames.org/name_strings/6c3dc35f-d901-5cc5-b9c8-ad241069b9f8</a>"/><br>
>> <dwc:hasScientificNameLSID<br>
>> rdf:resource="urn:lsid:catalogueoflife.org:taxon:24e7d624-60a7-102d-be47-00304854f810:ac2010"/><br>
>> Some system may choke on the LSID form assuming that it uses a standard<br>
>> resolution mechanism<br>
>> So it might be best to use this form<br>
>><br>
>> <dwc:hasScientificNameLSID>urn:lsid:catalogueoflife.org:taxon:24e7d624-60a7-102d-be47-00304854f810:ac2010</dwc:hasScientificNameLSID><br>
>> - Pete<br>
>> ----------------------------------------------------------------<br>
>> Pete DeVries<br>
>> Department of Entomology<br>
>> University of Wisconsin - Madison<br>
>> 445 Russell Laboratories<br>
>> 1630 Linden Drive<br>
>> Madison, WI 53706<br>
>> TaxonConcept Knowledge Base / GeoSpecies Knowledge Base<br>
>> About the GeoSpecies Knowledge Base<br>
>> ------------------------------------------------------------<br>
>><br>
>> --<br>
>> Steven J. Baskauf, Ph.D., Senior Lecturer<br>
>> Vanderbilt University Dept. of Biological Sciences<br>
>><br>
>> postal mail address:<br>
>> VU Station B 351634<br>
>> Nashville, TN 37235-1634, U.S.A.<br>
>><br>
>> delivery address:<br>
>> 2125 Stevenson Center<br>
>> 1161 21st Ave., S.<br>
>> Nashville, TN 37235<br>
>><br>
>> office: 2128 Stevenson Center<br>
>> phone: (615) 343-4582, fax: (615) 343-6707<br>
>> <a href="http://bioimages.vanderbilt.edu" target="_blank">http://bioimages.vanderbilt.edu</a><br>
><br>
><br>
><br>
> --<br>
> ----------------------------------------------------------------<br>
> Pete DeVries<br>
> Department of Entomology<br>
> University of Wisconsin - Madison<br>
> 445 Russell Laboratories<br>
> 1630 Linden Drive<br>
> Madison, WI 53706<br>
> TaxonConcept Knowledge Base / GeoSpecies Knowledge Base<br>
> About the GeoSpecies Knowledge Base<br>
> ------------------------------------------------------------<br>
><br>
</div></div>> _______________________________________________<br>
> tdwg-content mailing list<br>
<div class="im">> <a href="mailto:tdwg-content@lists.tdwg.org">tdwg-content@lists.tdwg.org</a><br>
</div><div class="im">> <a href="http://lists.tdwg.org/mailman/listinfo/tdwg-content" target="_blank">http://lists.tdwg.org/mailman/listinfo/tdwg-content</a><br>
><br>
><br>
<br>
<br>
<br>
</div>--<br>
Dr. Rutger A. Vos<br>
School of Biological Sciences<br>
Philip Lyle Building, Level 4<br>
University of Reading<br>
Reading<br>
RG6 6BX<br>
United Kingdom<br>
Tel: +44 (0) 118 378 7535<br>
<a href="http://www.nexml.org" target="_blank">http://www.nexml.org</a><br>
<a href="http://rutgervos.blogspot.com" target="_blank">http://rutgervos.blogspot.com</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>----------------------------------------------------------------<br>Pete DeVries<br>Department of Entomology<br>University of Wisconsin - Madison<br>445 Russell Laboratories<br>
1630 Linden Drive<br>Madison, WI 53706<br><a href="http://www.taxonconcept.org/" target="_blank">TaxonConcept Knowledge Base</a> / <a href="http://lod.geospecies.org/" target="_blank">GeoSpecies Knowledge Base</a><br><a href="http://about.geospecies.org/" target="_blank">About the GeoSpecies Knowledge Base</a><br>
------------------------------------------------------------<br>
</div>