Rich et al,<div><br></div><div>My thinking has been that the Semantic Web only began to take off when pragmatists started to have more influence than the often described "white coated ontologists". In one way, the "white coated ontologists" are right, but their over-engineered solutions really only worked within their specific model of the world. </div>
<div><br></div><div>Now that the pragmatists have more influence, people are marking up huge amounts of data and the issues of how to get these different vocabularies and datasets to work well together is being discussed and worked out on the public-lod email list.</div>
<div><br></div><div>I think the best way to proceed is to get some example data sets online, and then work out how to get them to work together in a useful way.</div><div><br></div><div>An initial step is to connect them using predicates <b>like</b> skos:closeMatch etc.</div>
<div><br></div><div>Then we should work within the larger LOD / Semantic Web community to fix whatever problems we find.</div><div><br></div><div>In some cases this will result in a change in other vocabularies like foaf or skos.</div>
<div><br></div><div>The problems that some of us see in these have been noticed by others and it makes sense that we come to some common solution.</div><div><br></div><div>In other cases it will involve getting the rest of the LOD community to adopt, or at least work well with, those vocabulary terms we propose.</div>
<div><br></div><div>This is to the benefit of our community because it makes the tools and data made available by others usable by us.</div><div><br></div><div>It also might be useful to step back and ask. </div><div><br>
</div><div><i>How successful have taxonomists been in getting the rest of the scientific community to adopt their standards?</i></div><div><br></div><div>My current thinking is that we can deal with DOI's and LSID's if we define predicates that allow consuming applications to recognize that the "object"</div>
<div>is to be interpreted as a DOI-like or LSID-like "thing". And do this in a way that will be widely adopted.</div><div><br></div><div>It is my understanding that Virtuoso is the only triple / quadstore / sparql endpoint that knows how to handle LSIDs.</div>
<div><br></div><div>Also, although I like a lot of what Steve says, I think that most existing crawlers expect that a seeAlso link is to some html, xml, rdf type thing and will</div><div>not be able to handle a multi-megabyte PDF.</div>
<div><br></div><div>This is why I reluctantly minted the predicate "hasPDF"</div><div><br></div><div>Also some services like Sindice seem to be able to interpret predicates that are defined as subproperties of well known predicates.</div>
<div><br></div><div>For instance "txn:hasWikipediaArticle" etc. are subproperties of foaf:page.</div><div><br></div><div>We also need some sort of "playground" knowledge base where related data sets can be loaded and tested to see how well they work together.</div>
<div><br></div><div>It is for this reason that I created the SPARQL endpoint described here: <a href="http://www.taxonconcept.org/sparql-endpoint/">http://www.taxonconcept.org/sparql-endpoint/</a></div><div><br></div><div>
I did a quick look at the apni data and my initial impression is that I like it.</div><div><br></div><div>Two sites I used to check it were: <a href="http://inspector.sindice.com/">http://inspector.sindice.com/</a></div><div>
<br></div><div>and <a href="http://validator.linkeddata.org/vapour">http://validator.linkeddata.org/vapour</a></div><div><br>To get a better idea of how it works etc., I also loaded a small sample of the RDF into my knowledge base.</div>
<div><br></div><div>I had not expected that there would be a related TaxonConcept entity since I have limited myself to mainly US plants, but after checking I found that the example emailed earlier had a related entity in TaxonConcept.</div>
<div><br></div><div>So I made up this page to make it easier for people to browse through the related data.</div><div><br></div><div>Gail K. reminded me that some email clients handle the "#" in some URL's differently. To end users these appear as broken links.</div>
<div><br></div><div>Here is the page with links to the small set of APNI RDF and the related entity in TaxonConcept.</div><div><br></div><div><a href="http://lod.taxonconcept.org/apni_example.html">http://lod.taxonconcept.org/apni_example.html</a><br>
</div><div><br></div><div>Respectfully,</div><div><br></div><div>- Pete</div><div><br><div class="gmail_quote">On Wed, Jan 5, 2011 at 10:43 AM, Richard Pyle <span dir="ltr"><<a href="mailto:deepreef@bishopmuseum.org">deepreef@bishopmuseum.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div lang="EN-US" link="blue" vlink="purple"><div><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">I second Rod’s “V. cool!” proclamation! I think this has the potential to solve a lot of problems with DOIs (particularly for the old literature). It doesn’t solve all the problems (e.g., we still need to define the article-level units within BHL content, and we’ll still need to establish a system of GUIDs that can be applied to sub-article units, such as treatments), but in the vast majority of cases, the DOIs will be the ticket into the services of CrossRef.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">I desperately want to comment on several points made in this thread (which I’ve only read just now), but I’m currently travelling, so I’ll chime in later.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Aloha,</span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Rich</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">P.S. Question for Rod/Chris/anyone else concerning DOIs: Does the annual fee only apply to the ability to mint DOIs within a given year, or does it also apply to resolving them? Put another way, if BHL stops paying its annual fee sometime in the future, will the already-minted DOI’s be resolvable into perpetuity, or will they stop being resolved at that point?</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p><div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div><div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in"><p class="MsoNormal"><b><span style="font-size:10.0pt">From:</span></b><span style="font-size:10.0pt"> <a href="mailto:tdwg-content-bounces@lists.tdwg.org" target="_blank">tdwg-content-bounces@lists.tdwg.org</a> [mailto:<a href="mailto:tdwg-content-bounces@lists.tdwg.org" target="_blank">tdwg-content-bounces@lists.tdwg.org</a>] <b>On Behalf Of </b>Roderic Page<br>
<b>Sent:</b> Wednesday, January 05, 2011 5:42 AM<br><b>To:</b> Chris Freeland<br><b>Cc:</b> <a href="mailto:tdwg-content@lists.tdwg.org" target="_blank">tdwg-content@lists.tdwg.org</a>; Paul Murray</span></p><div class="im">
<br><b>Subject:</b> Re: [tdwg-content] GUIDs for publications (usages and names)</div><p></p></div></div><p class="MsoNormal"> </p><p class="MsoNormal"> </p><div><div><p class="MsoNormal">On 5 Jan 2011, at 15:25, Chris Freeland wrote:</p>
</div><div><div></div><div class="h5"><p class="MsoNormal"><br><br></p><div><p><span style="font-size:10.0pt">And following on re: DOIs, BHL has become a member of CrossRef and starting in February will begin assigning DOIs first to our monographs & then on to journal content. There is an annual fee for membership and then a fee for every DOI assigned. BHL is absorbing these costs for community benefit.<br>
<br>Chris</span></p></div><div><p class="MsoNormal">V. cool! </p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">Regards</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">Rod</p>
</div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal"> </p></div></div></div></div><div><div></div><div class="h5"><div><div><div><div><div><div><div><div><p class="MsoNormal"><span style="font-size:9.0pt;color:black">---------------------------------------------------------</span></p>
</div><div><p class="MsoNormal"><span style="font-size:9.0pt;color:black">Roderic Page</span></p></div><div><p class="MsoNormal"><span style="font-size:9.0pt;color:black">Professor of Taxonomy</span></p></div><div><p class="MsoNormal">
<span style="font-size:9.0pt;color:black">Institute of Biodiversity, Animal Health and Comparative Medicine</span></p></div><div><p class="MsoNormal"><span style="font-size:9.0pt;color:black">College of Medical, Veterinary and Life Sciences</span></p>
</div><div><p class="MsoNormal"><span style="font-size:9.0pt;color:black">Graham Kerr Building</span></p></div><div><p class="MsoNormal"><span style="font-size:9.0pt;color:black">University of Glasgow</span></p></div><div>
<p class="MsoNormal"><span style="font-size:9.0pt;color:black">Glasgow G12 8QQ, UK</span></p></div><div><p class="MsoNormal"><span style="font-size:9.0pt;color:black"> </span></p></div><div><p class="MsoNormal"><span style="font-size:9.0pt;color:black">Email: <a href="mailto:r.page@bio.gla.ac.uk" target="_blank">r.page@bio.gla.ac.uk</a></span></p>
</div><div><p class="MsoNormal"><span style="font-size:9.0pt;color:black">Tel: +44 141 330 4778</span></p></div><div><p class="MsoNormal"><span style="font-size:9.0pt;color:black">Fax: +44 141 330 2792</span></p></div><div>
<p class="MsoNormal"><span style="font-size:9.0pt;color:black">AIM: <a href="mailto:rodpage1962@aim.com" target="_blank">rodpage1962@aim.com</a></span></p></div><div><p class="MsoNormal"><span style="font-size:9.0pt;color:black">Facebook: <a href="http://www.facebook.com/profile.php?id=1112517192" target="_blank">http://www.facebook.com/profile.php?id=1112517192</a></span></p>
</div><div><p class="MsoNormal"><span style="font-size:9.0pt;color:black">Twitter: <a href="http://twitter.com/rdmpage" target="_blank">http://twitter.com/rdmpage</a></span></p></div><div><p class="MsoNormal"><span style="font-size:9.0pt;color:black">Blog: <a href="http://iphylo.blogspot.com" target="_blank">http://iphylo.blogspot.com</a></span></p>
</div><div><p class="MsoNormal"><span style="font-size:9.0pt;color:black">Home page: <a href="http://taxonomy.zoology.gla.ac.uk/rod/rod.html" target="_blank">http://taxonomy.zoology.gla.ac.uk/rod/rod.html</a></span></p></div>
<div><p class="MsoNormal"><span style="font-size:9.0pt;color:black"> </span></p></div><div><p class="MsoNormal"><span style="font-size:9.0pt;color:black"> </span></p></div></div></div></div><p class="MsoNormal"><span style="font-size:9.0pt;color:black"> </span></p>
</div><p class="MsoNormal"><span style="font-size:9.0pt;color:black"> </span></p></div><p class="MsoNormal"><span style="font-size:13.5pt;color:black"> </span></p></div><p class="MsoNormal"> </p></div><p class="MsoNormal">
</p></div></div></div></div></div><br>_______________________________________________<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>