Hi Markus,<div><br></div><div>I expect them to copy and paste the URI in, or import the list as a field in their database.</div><div><br></div><div>Current Name Mapped to Concept</div><div>Puma concolor <a href="http://lod.taxonconcept.org/ses/v6n7p.html">se:v6n7p</a></div>
<div><br></div><div>That way in the future if the name changes without a change in the concept.</div><div>Eupuma concolor <a href="http://lod.taxonconcept.org/ses/v6n7p.html">se:v6n7p</a></div><meta charset="utf-8"><div><br>
</div><div>The data says linked.</div><div><br></div><div>Eventually <a href="http://lod.taxonconcept.org/ses/v6n7p.html">se:v6n7p</a> will be linked to the name variants in the GNI (it is to some extent already)</div><div>
<br></div><div>We have not done this yet except for the TDWG meeting example (<a href="http://lod.taxonconcept.org/tdwg_nomina.rd">http://lod.taxonconcept.org/tdwg_nomina.rd</a>f) but eventually these will have something like</div>
<div><br></div><div><meta charset="utf-8"><a href="http://lod.taxonconcept.org/ses/v6n7p.html">se:v6n7p</a> hasAcceptedScientificNameURI <<a href="http://gni.globalnames.org/name_strings/772d5162-f5aa-596c-98e0-a1c6c5a29bb9">http://gni.globalnames.org/name_strings/772d5162-f5aa-596c-98e0-a1c6c5a29bb9</a>></div>
<div><meta charset="utf-8"><a href="http://lod.taxonconcept.org/ses/v6n7p.html">se:v6n7p</a> hasSynonymNameURI <<a href="http://gni.globalnames.org/name_strings/35da7f30-25ff-5111-ab29-1a4f9988ef51">http://gni.globalnames.org/name_strings/35da7f30-25ff-5111-ab29-1a4f9988ef51</a>></div>
<div><meta charset="utf-8"><a href="http://lod.taxonconcept.org/ses/v6n7p.html">se:v6n7p</a> hhasBasionymNameURI <<a href="http://gni.globalnames.org/name_strings/35da7f30-25ff-5111-ab29-1a4f9988ef51">http://gni.globalnames.org/name_strings/35da7f30-25ff-5111-ab29-1a4f9988ef51</a>></div>
<div><br></div><div>etc.</div><div><br></div><div>And the following relations can be made from these to Rich's "Name Uses"</div><div><br></div><div><<a href="http://lod.taxonconcept.org/ses/v6n7p.html">se:v6n7p</a>> hasRelatedGNUB <GNUB ID> - basically ties the concept to a particular name use without stating the nature of the relationship.</div>
<div><br></div><div>With something like this to show the nature of the relationships (the literal below would be replaced with resolvable GNUB ID's)</div><div><br></div><div><meta charset="utf-8"><<a href="http://lod.taxonconcept.org/ses/v6n7p.html">se:v6n7p</a>> equivalentGNUB <"Puma concolor (Linnaeus 1771) sec. Brown" ></div>
<div><meta charset="utf-8"><<a href="http://lod.taxonconcept.org/ses/v6n7p.html">se:v6n7p</a>> narrowerGNUB <"Puma concolor (Linnaeus 1771)" ></div><div><br></div><div>* Probably one of Rich Pyle's fish might make a better example.</div>
<div><br></div><div>In a sense you are not only linking your occurrence record to a particular concept you are also linking it to other data in a number of other related data sets.</div><div><br></div><div>Since each data set, in fact each triple, can be assigned to it's own graph you can choose to ignore triples or datasets that you don't think are appropriate.</div>
<div><br></div><div>I have limited set of related data on my endpoint for this species with the various data sets assigned to different graphs.</div><div><br></div><div>For example the species Puma concolor <a href="http://lod.taxonconcept.org/ses/v6n7p.html">http://lod.taxonconcept.org/ses/v6n7p.html</a><br>
</div><div><br></div><div>Browsable Endpoint View <a href="http://lsd.taxonconcept.org/describe/?url=http://lod.taxonconcept.org/ses/v6n7p%23Species">http://lsd.taxonconcept.org/describe/?url=http://lod.taxonconcept.org/ses/v6n7p%23Species</a> <a href="http://bit.ly">bit.ly</a> <a href="http://bit.ly/gMFqR1">http://bit.ly/gMFqR1</a><br>
</div><div>Similar to what is in the Sig.ma example <a href="http://sig.ma/search?pid=f986676a3b575b165e1498fd25927eaf">http://sig.ma/search?pid=f986676a3b575b165e1498fd25927eaf</a></div><div><br></div><div>The SPARQL endpoints are described here: <a href="http://www.taxonconcept.org/sparql-endpoint/">http://www.taxonconcept.org/sparql-endpoint/</a></div>
<div><br></div><div>THis is in contrast to all the info in the LOD about Puma concolor via Sig.ma</div><div><br></div><div><a href="http://sig.ma/search?pid=a8365fad23aa42aff4c8f3078f30028c">http://sig.ma/search?pid=a8365fad23aa42aff4c8f3078f30028c</a><br>
</div><div><br></div><div>I guess one of the differences is that you are giving the data suppliers a choice as to what if any species concept they think is most appropriate for their data vs. having an algorithm assign one for them. A side effect is that their data would then be linked to other data and more easily findable by potential users.</div>
<div><br></div><div>Respectfully,</div><div><br></div><div>- Pete</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><meta charset="utf-8"><meta charset="utf-8"><div><br></div><div>I guess my point is that higher classifications also vary so you need to have some smarts behind the disambiguation.</div>
<div><br></div><div>The also allows groups to link there data even between potentially contentious names like Aedes triseriatus ?= Ochlerotatus triseriatus<br><br><div class="gmail_quote">On Thu, Nov 25, 2010 at 7:42 AM, "Markus Döring (GBIF)" <span dir="ltr"><<a href="mailto:mdoering@gbif.org">mdoering@gbif.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Peter,<br>
if people misspell scientific names and get authorships wrong, would you expect them to use URLs more carefully?<br>
<br>
Whatever terms we define, there will always be wrong data to deal with. The best guess we currently have for understanding the meaning of weird, often wrongly spelled names in occurrence records is to take the higher classification into the picture. Of course there are also synonyms, homonyms, misspellings and some names with authorships but most without.<br>
<br>
Markus<br>
<br>
<br>
PS: if anyone is interested in a rich variety of names we maintain a test file of scientific names for our parser here:<br>
<a href="http://gbif-ecat.googlecode.com/svn/trunk/ecat-common/src/test/resources/scientific_names.txt" target="_blank">http://gbif-ecat.googlecode.com/svn/trunk/ecat-common/src/test/resources/scientific_names.txt</a><br>
All names have been spotted in the wild...<br>
<div><div></div><div class="h5"><br>
<br>
On Nov 25, 2010, at 14:21, Peter DeVries wrote:<br>
<br>
> This is in response to David's example here; <a href="http://code.google.com/p/gbif-ecat/wiki/Nom5ExampleMytilusedulis" target="_blank">http://code.google.com/p/gbif-ecat/wiki/Nom5ExampleMytilusedulis</a><br>
><br>
> It demonstrates a number of issues, the main one being it is not clear what the intent of the GBIF submitter was.<br>
><br>
> Mytilus edulis Linnaeus 1758 <= Appears to be the correct name<br>
> Mytilus edulis Linné 1758 <= Appears to be a lexical variant of the correct name<br>
> Mytilus edulis d' Orbigny <= Is this an error, a different description or a different species?<br>
> Mytilus edulis Pennant <= Is this an error, a different description or a different species?<br>
> Mytilus edulis <= Is this an ommission, an error, a different description or a different species?<br>
><br>
><br>
> The intent of the GBIF contributor is in some cases not clear from the list above.<br>
><br>
> It is unclear what species they actually mean, and it is unclear if intend on entailing a specific classification or not.<br>
><br>
> Was it clear that they thought Mytilus edulis Linnaeus 1758 = Mytilus edulis Linné 1758 or not?<br>
><br>
> How do you determine their intent from the simple name string?<br>
><br>
> I think the intent be clearer if the submitter included a species concept URI with their submission.<br>
><br>
> A URI that showed that a species has multiple often dynamic classifications, some of which are linkable via semantic web URI's.<br>
><br>
> For example:<br>
><br>
> Wikipedia (<a href="http://en.wikipedia.org/wiki/Blue_mussel" target="_blank">http://en.wikipedia.org/wiki/Blue_mussel</a>) => <a href="http://dbpedia.org/resource/Blue_mussel" target="_blank">http://dbpedia.org/resource/Blue_mussel</a><br>
> Kingdom Animalia<br>
> Phylum Mollusca<br>
> Class Bivalvia<br>
> Subclass Heterodonta<br>
> Order Mytiloida<br>
> Family Mytilidae<br>
> Subfamily Mytilinae<br>
> Genus Mytilus<br>
> Species Mytilus edulis<br>
><br>
> ITIS (79454)<br>
> Kingdom Animalia<br>
> Phylum Mollusca<br>
> Class Bivalvia<br>
> Subclass Pteriomorphia<br>
> Order Mytiloida<br>
> Family Mytilidae<br>
> Genus Mytilus<br>
> Species Mytilus edulis<br>
><br>
> WORMS (140480)<br>
> Biota<br>
> Kingdom Animalia<br>
> Phylum Mollusca<br>
> Class Bivalvia<br>
> Subclass Pteriomorphia<br>
> Order Mytiloida<br>
> Family Mytilidae<br>
> Genus Mytilus<br>
> Species Mytilus edulis<br>
><br>
> CoL (6979242)<br>
> Kingdom Animalia<br>
> Phylum Mollusca<br>
> Class Bivalvia<br>
> Order Mytiloida<br>
> Family Mytilidae<br>
> Genus Mytilus<br>
> Species Mytilus edulis<br>
><br>
> NCBI (6550) => "<a href="http://purl.uniprot.org/taxonomy/6550" target="_blank">http://purl.uniprot.org/taxonomy/6550</a>"/<br>
> cellular organisms<br>
> Eukaryota<br>
> Fungi/Metazoa group<br>
> Metazoa<br>
> Eumetazoa<br>
> Bilateria<br>
> Coelomata<br>
> Protostomia<br>
> Mollusca<br>
> Bivalvia<br>
> Pteriomorphia<br>
> Mytiloida<br>
> Mytiloidea<br>
> Mytilidae<br>
> Mytilinae<br>
> Mytilus<br>
> Mytilus edulis<br>
><br>
> EUNIS<br>
> Kingdom Animalia<br>
> Phylum MOLLUSCA<br>
> Class Bivalvia<br>
> Order Anisomyaria<br>
> Family Mytilidae<br>
> Genus Mytilus<br>
> Mytilus edulis Linné, 1758<br>
><br>
><br>
> The example below is not the same species as above but it shows how the intent might be made clearer.<br>
><br>
> Urosalpinx cinerea (Say 1822) => "by this I mean the same species concept as se:Zom2X" => <a href="http://lod.taxonconcept.org/ses/Zom2X.html" target="_blank">http://lod.taxonconcept.org/ses/Zom2X.html</a><br>
><br>
> * This would be better if the concept description had more data like photo's, type specimens etc, but it does link to them and DNA barcodes.<br>
> The next version will also link to GBIF => <a href="http://data.gbif.org/species/13750666/" target="_blank">http://data.gbif.org/species/13750666/</a><br>
><br>
> HTML <a href="http://lod.taxonconcept.org/ses/Zom2X.html" target="_blank">http://lod.taxonconcept.org/ses/Zom2X.html</a><br>
> RDF <a href="http://lod.taxonconcept.org/ses/Zom2X.rdf" target="_blank">http://lod.taxonconcept.org/ses/Zom2X.rdf</a><br>
> TXNburner* (<a href="http://lsd.taxonconcept.org/describe/?url=http%3A%2F%2Flod.taxonconcept.org%2Fses%2FZom2X%23Species" target="_blank">http://lsd.taxonconcept.org/describe/?url=http%3A%2F%2Flod.taxonconcept.org%2Fses%2FZom2X%23Species</a>)<br>
> Sindice <a href="http://sig.ma/search?pid=7a8281129fa5ae55af919c7b90e97544" target="_blank">http://sig.ma/search?pid=7a8281129fa5ae55af919c7b90e97544</a><br>
><br>
> * If this did not go through your email correctly you can get to it from the <a href="http://lod.taxonconcept.org/ses/Zom2X.html" target="_blank">http://lod.taxonconcept.org/ses/Zom2X.html</a> or <a href="http://bit.ly/hyTnXf" target="_blank">http://bit.ly/hyTnXf</a><br>
><br>
> These are not perfect but they already make it more clear what data sets relate to the same species and what data sets relate to different species.<br>
> By linking to one of these, you are accepting that a species can have multiple classifications and there can be multiple names for the your intended concept.<br>
><br>
> Respectfully,<br>
><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>
</div></div>> _______________________________________________<br>
> tdwg-content mailing list<br>
> <a href="mailto:tdwg-content@lists.tdwg.org">tdwg-content@lists.tdwg.org</a><br>
> <a href="http://lists.tdwg.org/mailman/listinfo/tdwg-content" target="_blank">http://lists.tdwg.org/mailman/listinfo/tdwg-content</a><br>
<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>