<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I am not sure I understand why we can not set DWC fields to conform to WGS84 and then use what everybody else is using.<div><br></div><div>For example in eventDate DWC conforms to ISO 8601, why dont we do the same for location... it would allow to simplify it quite a lot and be more compliant with other standards-existing apps, etc.</div><div><br></div><div>Just an idea.</div><div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><span class="Apple-style-span" style="font-size: medium; "><div><b><font class="Apple-style-span" color="#515151"><font class="Apple-style-span" size="3"><span class="Apple-style-span" style="font-size: 11px; ">Javier de la Torre</span></font></font></b></div><div><font class="Apple-style-span" color="#8FC500"><b><font class="Apple-style-span" size="3"><span class="Apple-style-span" style="font-size: 11px; "><a href="http://www.vizzuality.com/">www.vizzuality.com</a></span></font></b></font></div></span></div></div></span></div></span></div></span></div></span></span>
</div>
<br><div><div>On Aug 9, 2010, at 4:13 PM, John Wieczorek wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta charset="utf-8">The partially good news is that if enough information (dwc:geodeticDatum) is given in a Darwin Core-based record, geo:lat/lon can be determined from it. More disturbing to me is that anyone would think geo:lat/lon alone is sufficient for any application, as it carries no notion of uncertainty and therefore fitness for use. Add dwc:coordinateUncertaintyInMeters (or even dwc:coordinatePrecision if you must) to the mix and I would be much happier.<div>
<br><br><div class="gmail_quote">On Sun, Aug 8, 2010 at 11:26 PM, <span dir="ltr"><<a href="mailto:Garry.Jolley-Rogers@csiro.au">Garry.Jolley-Rogers@csiro.au</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi Jim,<br>
Thanks. Had this aside to read in detail later. I think John is right... As same value with different constraints mean different interpretations are possible and seems to be the key thing. How are the values to be interpreted.<br>
<br>
G<br>
<div class="im"><br>
-----Original Message-----<br>
From: Jim Croft [mailto:<a href="mailto:jim.croft@gmail.com">jim.croft@gmail.com</a>]<br>
</div><div class="im">Sent: Monday, 9 August 2010 4:12 PM<br>
To: Alexander, Paul (PI, Black Mountain); Harvey, Paul.W (PI, Black Mountain); Jolley-Rogers, Garry (PI, Black Mountain); Cawsey, Margaret (CES, Crace); Greg Whitbread<br>
Cc: <a href="mailto:tuco@berkeley.edu">tuco@berkeley.edu</a><br>
</div><div><div></div><div class="h5">Subject: Fwd: [tdwg-tag] time and space namespaces in Darwin Core<br>
<br>
Did you catch this thread on tdwg-tag? It is an almost exact mirror<br>
of the conversations we have be having in the taxon profile space, but<br>
involving the specimen locational data.<br>
<br>
>From John's comments it would appear he is not prepared to accept the<br>
geo: and dwc: lat/long as 'exact match' because, although they are the<br>
same values, they have different constraints (or more precisely one<br>
one has a constraint and one doesn't).<br>
<br>
I wouldn't have picked it but this looks like a case for 'closematch'.<br>
<br>
jim<br>
<br>
<br>
---------- Forwarded message ----------<br>
From: John Wieczorek <<a href="mailto:tuco@berkeley.edu">tuco@berkeley.edu</a>><br>
Date: Mon, Aug 9, 2010 at 3:56 AM<br>
Subject: Re: [tdwg-tag] time and space namespaces in Darwin Core<br>
To: joel sachs <<a href="mailto:jsachs@csee.umbc.edu">jsachs@csee.umbc.edu</a>><br>
Cc: <a href="mailto:tdwg-bioblitz@googlegroups.com">tdwg-bioblitz@googlegroups.com</a>, <a href="mailto:tdwg-tag@lists.tdwg.org">tdwg-tag@lists.tdwg.org</a><br>
<br>
<br>
There is actually no equivalency between dwc:decimalLatitude and<br>
geo:lat because geo:lat is specified to represent the latitude in the<br>
WGS84 spatial reference system and dwc:decimalLatitude has no such<br>
such restriction.<br>
<br>
On Fri, Aug 6, 2010 at 10:08 AM, joel sachs <<a href="mailto:jsachs@csee.umbc.edu">jsachs@csee.umbc.edu</a>> wrote:<br>
><br>
> On Fri, 6 Aug 2010, Hilmar Lapp wrote:<br>
><br>
> > Shouldn't the RDF for DwC link DwC:lat to geo:lat (using some subtype<br>
> > or better yet equivalency relation)? And shouldn't hence Linked Data<br>
> > browsers be able to use DwC:lat in the same way as geo:lat?<br>
> ><br>
><br>
> Yes. But no Linked Data browser I'm aware of applies<br>
> owl:equivalentProperty assetions before rendering the data. (In fact, most<br>
> do no reasoning at all.) I agree that, whatever our default display,<br>
> it should include the appropriate mapping statements, either via an<br>
> rdfs:seeAlso or similar link, or directly in the document.<br>
><br>
><br>
> Joel.<br>
><br>
><br>
> > -hilmar<br>
> ><br>
> > On Aug 6, 2010, at 11:01 AM, joel sachs wrote:<br>
> ><br>
> >> All,<br>
> >><br>
> >> When representing observation records in RDF, there are advantages<br>
> >> to using Dublin Core and Geo (<a href="http://www.w3.org/2003/01/geo/" target="_blank">http://www.w3.org/2003/01/geo/</a><br>
> >> wgs84_pos#)<br>
> >> namespaces where possible. For example, if we use DC:date, and<br>
> >> geo:lat, geo:long, instead of DwC:eventDate, DwC:lat, and DwC:long,<br>
> >> then Linked Data browsers can automatically map the records, plot<br>
> >> them on a timeline, etc.<br>
> >><br>
> >> My question is: What are the disadvantages to doing this? (For<br>
> >> example, is this going to break someone's DwC validator?)<br>
> >><br>
> >> Thanks -<br>
> >> Joel.<br>
> >><br>
> ><br>
> > --<br>
> > ===========================================================<br>
> > : Hilmar Lapp -:- Durham, NC -:- <a href="http://informatics.nescent.org/" target="_blank">informatics.nescent.org</a> :<br>
> > ===========================================================<br>
> ><br>
<br>
_________________<br>
Jim Croft ~ <a href="mailto:jim.croft@gmail.com">jim.croft@gmail.com</a> ~ +61-2-62509499 ~<br>
<a href="http://www.google.com/profiles/jim.croft" target="_blank">http://www.google.com/profiles/jim.croft</a><br>
'A civilized society is one which tolerates eccentricity to the point<br>
of doubtful sanity.'<br>
- Robert Frost, poet (1874-1963)<br>
<br>
Please send URIs, not attachments:<br>
<a href="http://www.gnu.org/philosophy/no-word-attachments.html" target="_blank">http://www.gnu.org/philosophy/no-word-attachments.html</a><br>
</div></div></blockquote></div><br></div>
_______________________________________________<br>tdwg-tag mailing list<br><a href="mailto:tdwg-tag@lists.tdwg.org">tdwg-tag@lists.tdwg.org</a><br>http://lists.tdwg.org/mailman/listinfo/tdwg-tag<br></blockquote></div><br></div></body></html>