I have been thinking about the following pattern. In part after looking at the GBIF vocabulary.<div><br></div><div>I am not sure if it is even a good idea but might be worth some discussion.</div><div><br></div><div>For those fields that have both a string and "ID" form maybe the following pattern might be useful</div>
<div><br></div><div>hasScientificName = string form</div><div>hasScientificNameURI = Resolvable LOD compliant identifier</div><div>hasScientificNameLSID = LSID identifier which could be resolvable once you add the "http:proxy" etc.</div>
<div><br></div><div>This allows all three forms to be included if desired, it also provides a hint as to how the field should be interpreted or resolved.</div><div><br></div><div>One group could also provide a mapping service so that each record does not need to include all three forms, but would allow systems</div>
<div>to find the matching LSID for a given URI or vs. versa.</div><div><br></div><div>My concern was that it would be difficult to infer how a scientificNameID should be interpreted by other systems.</div><div><br></div><div>
Is this an LSD, is it a URI, is it a UUID etc. ?</div><div><br></div><div>This impacts the structure of the RDF.</div><div><br></div><div><div>* Note that the actual identifiers might not be correct, the example below is more about the form of the RDF</div>
<div>* For instance, I don't think it is probably correct to see the COL LSID as just a namestring</div><div>* Also in this example the GNI name does not exactly match the string name</div><div><br></div><div><dwc:hasScientificName>Puma concolor (Linnaeus 1771)</dwc:hasScientificName></div>
<div><dwc:hasScientificNameURI rdf:resource="<a href="http://gni.globalnames.org/name_strings/6c3dc35f-d901-5cc5-b9c8-ad241069b9f8">http://gni.globalnames.org/name_strings/6c3dc35f-d901-5cc5-b9c8-ad241069b9f8</a>"/></div>
<div><dwc:hasScientificNameLSID rdf:resource="urn:lsid:catalogueoflife.org:taxon:24e7d624-60a7-102d-be47-00304854f810:ac2010"/></div><div><br></div><div>Some system may choke on the LSID form assuming that it uses a standard resolution mechanism</div>
<div><br></div><div>So it might be best to use this form</div><div><br></div><div><dwc:hasScientificNameLSID>urn:lsid:catalogueoflife.org:taxon:24e7d624-60a7-102d-be47-00304854f810:ac2010</dwc:hasScientificNameLSID></div>
<div><br></div>- Pete</div><div><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>