<div>I thought I would explain how I have been marking up occurrence records in RDF in this blog post.</div><div><br></div><div><a href="http://www.taxonconcept.org/taxonconcept-blog/2011/2/21/species-occurrence-records-represented-in-rdf.html">http://www.taxonconcept.org/taxonconcept-blog/2011/2/21/species-occurrence-records-represented-in-rdf.html</a></div>
<div><br></div><div>The quad store view of the different RDF entities mentioned in the blog can be seen here:</div><div><br></div><div>Via this <a href="http://bit.ly">bit.ly</a> bundle <a href="http://bit.ly/fnlTZd">http://bit.ly/fnlTZd</a></div>
<div><br></div><div>* Note that some of these links get change in email so you might want to use the <a href="http://bit.ly">bit.ly</a> bundle above</div><div><br></div><div>The RDF page: <a href="http://lsd.taxonconcept.org/describe/?url=http://ocs.taxonconcept.org/ocs/f522444a-2dd9-400e-be59-47213ef38cb9.rdf">http://lsd.taxonconcept.org/describe/?url=http://ocs.taxonconcept.org/ocs/f522444a-2dd9-400e-be59-47213ef38cb9.rdf</a></div>
<div><br></div><div>The Occurrence: <a href="http://lsd.taxonconcept.org/describe/?url=http://ocs.taxonconcept.org/ocs/f522444a-2dd9-400e-be59-47213ef38cb9%23Occurrence">http://lsd.taxonconcept.org/describe/?url=http://ocs.taxonconcept.org/ocs/f522444a-2dd9-400e-be59-47213ef38cb9%23Occurrence</a></div>
<div><br></div><div>The Area: <a href="http://lsd.taxonconcept.org/describe/?url=geo:44.86528100,-87.23147800;u=10">http://lsd.taxonconcept.org/describe/?url=geo:44.86528100,-87.23147800;u=10</a></div><div><br></div><div>
The Species Concept: <a href="http://lsd.taxonconcept.org/describe/?url=http://lod.taxonconcept.org/ses/ICmLC%23Species">http://lsd.taxonconcept.org/describe/?url=http://lod.taxonconcept.org/ses/ICmLC%23Species</a></div><div>
<br></div><div>The Individual: <a href="http://lsd.taxonconcept.org/describe/?url=http://ocs.taxonconcept.org/ocs/f522444a-2dd9-400e-be59-47213ef38cb9%23Individual">http://lsd.taxonconcept.org/describe/?url=http://ocs.taxonconcept.org/ocs/f522444a-2dd9-400e-be59-47213ef38cb9%23Individual</a></div>
<div><br></div><div>The Identification: <a href="http://lsd.taxonconcept.org/describe/?url=http://ocs.taxonconcept.org/ocs/f522444a-2dd9-400e-be59-47213ef38cb9%23Identification_0001">http://lsd.taxonconcept.org/describe/?url=http://ocs.taxonconcept.org/ocs/f522444a-2dd9-400e-be59-47213ef38cb9%23Identification_0001</a></div>
<div><br></div><div>The Continent: <a href="http://lsd.taxonconcept.org/describe/?url=http://sws.geonames.org/6255149/">http://lsd.taxonconcept.org/describe/?url=http://sws.geonames.org/6255149/</a></div><div><br></div><div>
The County: <a href="http://lsd.taxonconcept.org/describe/?url=http://sws.geonames.org/5250768/">http://lsd.taxonconcept.org/describe/?url=http://sws.geonames.org/5250768/</a></div><div><br></div><div><br></div><div>Although the exact format of these could be changed there are several existing advantages and some possible future advantages.</div>
<div><br></div><div>1) Each data provider could expose their own data to the web without a central authority.</div><div> This could be in the form of RDF, RDFa, or as gzipped RDF dump files. (records.rdf.gz)</div><div>
They would be automatically discoverable on the LOD cloud.</div><div> A third party service could add value by pointing to the various repositories, perhaps with an annotation system like or as part of CKAN. (<a href="http://ckan.net/">http://ckan.net/</a>)</div>
<div><br></div><div>2) Data validation in terms of being "well-formed" could be checked with the existing RDF and RDFa validators.</div><div><br></div><div> <a href="http://www.w3.org/RDF/Validator/">http://www.w3.org/RDF/Validator/</a></div>
<div><br></div><div> <a href="http://validator.w3.org/">http://validator.w3.org/</a></div><div><br></div><div>3) The next level of validation e.g:</div><div> Is this a valid geographic coordinate?</div><div> Does the coordinate match the geographical names listed *(You could even have a service that takes the geo area and determines the correct geographic names etc.)</div>
<div> Does the scientific name match a known species?</div><div> Are the other required fields present and well formed.</div><div> Is this a new record for that species in that specific geographic area</div>
<div><br></div><div> Would have to be done by a validator created for the community, but it would benefit from the existing tools.</div><div><br></div><div>4) All the third party LOD tools and services would be able to use these records.</div>
<div><br></div><div>Respectfully,</div><div><br></div><div>- Pete</div><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>