One of the goals of my work is to create data structures that allow me to do useful queries.<div><br></div><div>For example:</div><div><br></div><div>1) I would like to be able to query for occurrences of a species, not simply occurrences of a particular name string.</div>
<div>2) I would like to be able to query for a list of possible candidate species based on a particular latitude and longitude.</div><div>3) I would like to make related, but not identical entities, "findable" by linking to them using skos:closeMatch or some future non-entailing version of owl:sameAs</div>
<div>4) The data structure should leverage existing, widely used LOD vocabularies, to take advantage of those systems and tools that understand them.</div><div>5) To minimize ambiguity and increase triple store efficiency, controlled vocabularies should be represented using URI's rather than literals</div>
<div><br></div><div>It is these kinds of goals and use cases that determine the best way to organize and structure the data.</div><div><br></div><div>What I still don't understand is why some think that we can arrive at a standard that can be all things to all people without a set of use cases and example data sets.</div>
<div><br></div><div>I would also like examples of why using things like SKOS will result in an unusable standard.</div><div><br></div><div>There are issues with SKOS and FOAF which are being worked out on the public-lod list.</div>
<div><br></div><div>There are also a number of ways to work around some of the potential problems with SKOS and FOAF.</div><div><br></div><div>In my experience it seems as if the TDWG standards process is broken.</div><div>
<br></div><div>At various times I have tried to help, but at the end of the day I need something that works.</div><div><br></div><div>Respectfully,</div><div><br></div><div>- Pete</div><div><br></div><div><br><br><div class="gmail_quote">
On Sun, Nov 14, 2010 at 7:29 AM, Roger Hyam <span dir="ltr"><<a href="mailto:rogerhyam@mac.com">rogerhyam@mac.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi Lee,<br>
<br>
Harmonizing TDWG standards is a technical intervention but what is it a solution to? We must do this in order to . . . . . .<br>
<br>
All the best,<br>
<font color="#888888"><br>
Roger<br>
</font><div><div></div><div class="h5"><br>
<br>
<br>
<br>
<br>
On 13 Nov 2010, at 23:47, Lee Belbin <<a href="mailto:leebelbin@gmail.com">leebelbin@gmail.com</a>> wrote:<br>
<br>
> Re (0) - fair point Roger, but as I said (implied maybe) in my last post, surely<br>
> the most significant use case is the harmonization of old and new TDWG<br>
> standards?! Your 'stool' analogy is currently missing at least one leg.<br>
><br>
> Lee<br>
><br>
> Lee Belbin<br>
> Geospatial Team Leader<br>
> Atlas of Living Australia<br>
><br>
><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>
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>
</div></div></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>