I agree. there are a number of tools that can interpret the geo: standard and it is not as if the alternatives are more accurate.<div><br></div><div>I never understood why this issue is any different that having people standardize on meters.</div>
<div><br></div><div>The issue of error can be dealt with with the addition of another field.</div><div><br></div><div>I think a better solution might be easy-to-use tools that let groups convert their records to geo:lat and geo:long before submitting them.</div>
<div><br></div><div>- Pete<br><br><div class="gmail_quote">On Fri, Aug 6, 2010 at 10:01 AM, joel sachs <span dir="ltr"><<a href="mailto:jsachs@csee.umbc.edu">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;">
All,<br>
<br>
When representing observation records in RDF, there are advantages to using Dublin Core and Geo (<a href="http://www.w3.org/2003/01/geo/wgs84_pos#" target="_blank">http://www.w3.org/2003/01/geo/wgs84_pos#</a>)<br>
namespaces where possible. For example, if we use DC:date, and geo:lat, geo:long, instead of DwC:eventDate, DwC:lat, and DwC:long, then Linked Data browsers can automatically map the records, plot them on a timeline, etc.<br>
<br>
My question is: What are the disadvantages to doing this? (For example, is this going to break someone's DwC validator?)<br>
<br>
Thanks -<br><font color="#888888">
Joel.<br>
<br>
</font></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>GeoSpecies Knowledge Base <br>About the GeoSpecies Knowledge Base<br>------------------------------------------------------------<br>
</div>