This is a little bit of a hack but it should work.<div><br></div><div><span style="border-collapse:collapse;color:rgb(51, 51, 51);font-family:arial, sans-serif;font-size:13px">dwc:vernacularName</span></div>
<div><font color="#333333" face="arial, sans-serif"><span style="border-collapse:collapse"> <span style="font-size:13px">dwc:vernacularName_en</span><br>
</span></font><span style="border-collapse:collapse;color:rgb(51, 51, 51);font-family:arial, sans-serif"> <span style="font-size:13px">dwc:vernacularName_fr</span><br>
</span></div><div><br></div><div><span style="border-collapse:collapse;color:rgb(51, 51, 51);font-family:arial, sans-serif;font-size:13px">The language variants are subproperties of the dwc:</span><span style="border-collapse:collapse;color:rgb(51, 51, 51);font-family:arial, sans-serif;font-size:13px">vernacularName</span></div>
<div><span style="border-collapse:collapse;color:rgb(51, 51, 51);font-family:arial, sans-serif;font-size:13px"><br></span></div><div><span style="border-collapse:collapse;color:rgb(51, 51, 51);font-family:arial, sans-serif;font-size:13px">This would also avoid the somewhat awkward SPARQL queries needed when you want to query for "Name"@en and not "Name"@es</span></div>
<div><span style="border-collapse:collapse;color:rgb(51, 51, 51);font-family:arial, sans-serif;font-size:13px"><br></span></div><div><span style="border-collapse:collapse;color:rgb(51, 51, 51);font-family:arial, sans-serif;font-size:13px">* For a more semantic web friendly version I was thinking of the following predicate hierarchy.</span></div>
<div><span style="border-collapse:collapse;color:rgb(51, 51, 51);font-family:arial, sans-serif;font-size:13px"><br></span></div><div><span style="border-collapse:collapse;color:rgb(51, 51, 51);font-family:arial, sans-serif;font-size:13px">hasTaxonName</span></div>
<div><span style="border-collapse:collapse;color:rgb(51, 51, 51);font-family:arial, sans-serif;font-size:13px"> hasAcceptedName</span></div><div><span style="border-collapse:collapse;color:rgb(51, 51, 51);font-family:arial, sans-serif;font-size:13px"> hasOriginalName</span></div>
<div><span style="border-collapse:collapse;color:rgb(51, 51, 51);font-family:arial, sans-serif;font-size:13px"> hasVernacularName = hasCommonName</span></div><div><span style="border-collapse:collapse;color:rgb(51, 51, 51);font-family:arial, sans-serif;font-size:13px"><br>
</span></div><div><span style="border-collapse:collapse;color:rgb(51, 51, 51);font-family:arial, sans-serif;font-size:13px">The GNI URI forms would be</span></div><div><font class="Apple-style-span" color="#333333" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><meta charset="utf-8"><span class="Apple-style-span" style="font-size: 13px; "><div>
<br></div><div><div>hasTaxonNameID</div><div> hasAcceptedNameID</div><div> hasOriginalNameID</div><div> hasHeterochresonymID</div><div> hasHeterotypicNameID</div><div> hasHomotypicNameID</div><div> hasOrthochresonymID</div>
</div></span></span></font></div><div><span style="border-collapse:collapse;color:rgb(51, 51, 51);font-family:arial, sans-serif;font-size:13px"><br></span></div><div><span style="border-collapse:collapse;color:rgb(51, 51, 51);font-family:arial, sans-serif;font-size:13px">I have an example of this in the Knowledge Base. </span></div>
<div><span style="border-collapse:collapse;color:rgb(51, 51, 51);font-family:arial, sans-serif;font-size:13px"><br></span></div><div><span style="border-collapse:collapse;color:rgb(51, 51, 51);font-family:arial, sans-serif;font-size:13px">It still has a bug in that the GNI URI's should have been replaced with their human readable </span><span style="border-collapse: collapse; color: rgb(51, 51, 51); font-size: 13px; "><font class="Apple-style-span" face="'courier new', monospace">skos:prefLabels</font></span><span style="border-collapse:collapse;color:rgb(51, 51, 51);font-family:arial, sans-serif;font-size:13px"> as they are in URIburner and Sig.ma.</span></div>
<div><span style="border-collapse:collapse;color:rgb(51, 51, 51);font-family:arial, sans-serif;font-size:13px"><br></span></div><div><div><font class="Apple-style-span" color="#333333" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse; ">You can click through the related things in this KB view. <a href="http://bit.ly">bit.ly</a> </span><span class="Apple-style-span" style="border-collapse: collapse; "><a href="http://bit.ly/oz9pJC">http://bit.ly/oz9pJC</a></span></font></div>
<div><font class="Apple-style-span" color="#333333" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br></span></font></div><div><font class="Apple-style-span" color="#333333" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><a href="http://lsd.taxonconcept.org/describe/?url=http%3A%2F%2Fgni.globalnames.org%2Frgs%2F12341234">http://lsd.taxonconcept.org/describe/?url=http%3A%2F%2Fgni.globalnames.org%2Frgs%2F12341234</a></span></font></div>
<div><font class="Apple-style-span" color="#333333" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br></span></font></div><div><font class="Apple-style-span" color="#333333" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">Note how you can click between the links to the taxonomic authors etc, and the links to <a href="http://citebank.org">citebank.org</a> web pages (not LOD RDF resources)</span></font></div>
</div><div><span style="border-collapse:collapse;color:rgb(51, 51, 51);font-family:arial, sans-serif;font-size:13px"><br></span></div><div><span style="border-collapse:collapse;color:rgb(51, 51, 51);font-family:arial, sans-serif;font-size:13px">- Pete</span></div>
<div><br><div class="gmail_quote">On Tue, Jul 26, 2011 at 10:47 AM, joel sachs <span dir="ltr"><<a href="mailto:jsachs@csee.umbc.edu" target="_blank">jsachs@csee.umbc.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Darwin Core is one of my favourite things. It's simple, elegant, and<br>
flexible. I wasn't there at design time, so I don't know if it was<br>
designed with the semantic web in mind, but it looks like it. It is, as<br>
John put it, primarily a collection of terms [and their definitions]. So<br>
if two people/agents use the same terms, they will share the same<br>
semantics. (This is why I think that a "more semantic Darwin Core" is not<br>
the appropriate goal for a Darwin Core/rdf working group.)<br>
<br>
I'm concerned that there's so much confusion concerning DwC, since<br>
confusion is (typically) a barrier to adoption.<br>
<br>
One source of confusion is Simple Darwin Core. A huge fraction of DwC<br>
records can be expressed as spreadsheets. Since *all* Simple DwC records<br>
can be expressed as spreadsheets, many people think<br>
<br>
Simple Darwin Core = spreadsheet-expressible Darwin Core<br>
<br>
(which isn't true). This means that if they want to express their data as<br>
a spreadsheet, they think they need to conform to Simple Darwin Core.<br>
<br>
The requirement of Simple Darwin Core is that there be no repeated<br>
elements. But the requirement for spreadsheet-expressible Darwin Core is<br>
that there be no repeated nested elements. I previously argued<br>
(<a href="http://lists.tdwg.org/pipermail/tdwg-content/2011-January/002220.html" target="_blank">http://lists.tdwg.org/pipermail/tdwg-content/2011-January/002220.html</a>) in<br>
favour of using subscripts to represent elements in repeated nests<br>
(thereby permitting their use in spreadsheets). Even if we don't permit<br>
that, I'm not sure that the benefits of maintaing a separate Simple Darwin<br>
Core standard, in addition to the regular Darwin Core standard, are<br>
greater than the costs in terms of giving people wrong ideas. (I prefer<br>
the presentation at <a href="http://rs.tdwg.org/dwc/terms/guides/xml/index.htm" target="_blank">http://rs.tdwg.org/dwc/terms/guides/xml/index.htm</a>,<br>
where Simple DwC is presented as simply one of several XML schemas for<br>
Darwin Core.)<br>
<br>
I *think* I see the motivation for Simple DwC. Suppose X wants to use<br>
Darwin Core, but doesn't know much about databases, and just wants to put<br>
all his data in a spreadsheet. He might not know what a repeated, nested<br>
data structure is. So it's easiest to just say to him "don't repeat any<br>
elements, and you'll be fine - your records will be<br>
spreadsheet-expressible". I agree that that's a benefit. Are there others?<br>
<br>
Thanks -<br>
Joel.<br>
<br>
<br>
<br>
_______________________________________________<br>
tdwg-content mailing list<br>
<a href="mailto:tdwg-content@lists.tdwg.org" target="_blank">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>
</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>
Email: <a href="mailto:pdevries@wisc.edu" target="_blank">pdevries@wisc.edu</a><br><a href="http://www.taxonconcept.org/" target="_blank">TaxonConcept</a> & <a href="http://about.geospecies.org/" target="_blank">GeoSpecies</a> Knowledge Bases<br>
A Semantic Web, <a href="http://linkeddata.org/" target="_blank">Linked Open Data</a> Project<br>--------------------------------------------------------------------------------------<br>
</div>