[tdwg-tag] DwC change review: geo terms
hlapp at nescent.org
Wed Sep 7 01:08:12 CEST 2011
Where is adopting these terms now going to put us with respect to OGC
standards, which, I think, will ultimately be more authoritative than
an informal W3C vocabulary.
I don't have enough insight into OGC standards for vocabularies for
describing geolocations, but I have also learned earlier this year
from Flip Dibner (copied here) that there are efforts underway within
OGC to create RDF vocabularies (presumably corresponding to OGC's XML
On Sep 6, 2011, at 6:33 PM, Javier de la Torre wrote:
> Hi John,
> As you mention from previous discussion I would still adopt option
> number 1 as I believe there is enough tools out there to handle
> transformations. The current situation I think is much worst on the
> consumer part and I think is time to think more on data use than on
> data mobilization.
> On 07/09/2011, at 00:00, John Wieczorek <tuco at berkeley.edu> wrote:
>> Perhaps my message was too long for easy digestion and action, as
>> received no responses. I will take the initiative to initiate option
>> 3. No further action from the TAG on this at this point. Be prepared
>> though, VOTES by the TAG on publicly resolved issues are forthcoming
>> very soon.
>> On Sat, Sep 3, 2011 at 9:34 AM, John Wieczorek <tuco at berkeley.edu>
>>> Hi TAGers,
>>> I am deep in the review process for the proposed changes to Darwin
>>> Core, trying to do due diligence. Some of the change requests are
>>> challenging to summarize to determine if there is consensus, in
>>> of, or because of the discussions. One of the requests on which I’d
>>> like some TAG help before proposing a solution is the request for
>>> inclusion of the terms from the geo: namespace
>>> Support in tdwg-content for this request comes from multiple
>>> independent sources. There has been a long history of discussion
>>> beginning in anticipation of the 2010 TDWG BioBlitz. The proposal
>>> gone through the minimum 30-day public review and discussion on the
>>> forum tdwg-content at lists.tdwg.org:
>>> There seems to be general support for the additions, however, after
>>> reviewing the discussions and the references. I have the following
>>> 1) The discussions presented geo:lat and geo:lng as W3C standards.
>>> This is not actually the case. These terms were created by the W3C
>>> Semantic Web Interest Group in 2003. The documentation for these
>>> (http://www.w3.org/2003/01/geo/) states:
>>> "This document was created as an informal collaboration within W3C's
>>> Semantic Web Interest Group. This work is not currently on the W3C
>>> recommendation track for standardization, and has not been subject
>>> the associated review process, quality assurance, etc. If there is
>>> interest amongst the W3C membership in standards work on a
>>> location/mapping RDF vocabulary, this current work may inform any
>>> formal efforts to follow."
>>> These terms do seem to have widespread usage in the semantic web.
>>> Should we be concerned that they are not part of a standard?
>>> 2) geo:lat and geo:lng are not semantically equivalent to the
>>> Darwin Core terms decimalLatitude and decimalLongitude, which have
>>> been a part of the Darwin Core since it 2003 (or before, if we
>>> the missing Datum term in earlier versions). The addition of the
>>> terms as a third set of geolocation terms for Darwin Core raised
>>> concerns about confusion. I share this concern. An option would be
>>> adopt these terms and deprecate dwc:decimalLatitude, dwc:Longitude,
>>> and dwc:geodeticDatum. Data that would have occupied these terms
>>> go instead to dwc:verbatimLatitude dwc:verbatimLongitude, and
>>> dwc:verbatimSRS. I see a couple of problems with this. First, most
>>> the time the data in the decimal coordinate fields are not the
>>> verbatim originals, so this would be a misuse of the Darwin Core
>>> terms. Second, this change would make it more difficult for data
>>> consumer’s to use existing georeferences. Here’s how. Right now the
>>> verbatim fields are meant to hold the original coordinate
>>> which means they have a wide variety of content - everything from
>>> to custom-encoded coordinates, in any conceivable format. Meanwhile,
>>> the data in the decimal coordinates fields can be much more readily
>>> transformed into the desired standardized spatial reference system
>>> afforded by the geo: terms, because the values are at least
>>> standardized on decimal degrees and only a datum transformation
>>> has to
>>> be done on them.
>>> Do we abandon the dwc: terms decimalLatitude, decimalLongitude, and
>>> geodeticDatum? Do we abandon them now? Do we build the simplest
>>> possible tools necessary for anyone to do the transformations so
>>> these terms are no longer needed? If so, do we wait until those
>>> 3) Additional concern was expressed that the term geo:alt should
>>> be added. No one has made a formal request for this. However, if the
>>> other geo: terms were adopted, it might be silly not to adopt this
>>> as well. Doing so would raise a host of issues similar to those
>>> for lat and lng.
>>> I don’t have a good solution. The best short-term one, in my
>>> is to leave Darwin Core as it is, and to recommend that if
>>> applications (or aggregators) want to share “cleansed” point-based
>>> georeferences, that they do so with the geo: tags, the values for
>>> which they derive through transformations to WGS84 of the DwC
>>> coordinates and geodeticDatum.
>>> 1) Accept the proposal, adding geo:lat, geo:lng, and geo:alt to the
>>> list of recommended terms for DwC.
>>> 2) Reject the proposal pending further directed research into a
>>> comprehensive solution that considers all geospatial terms in Darwin
>>> Core (including footprintWKT, for example).
>>> 3) Reject the proposal for now, reopening the public discussion with
>>> these concerns.
>> tdwg-tag mailing list
>> tdwg-tag at lists.tdwg.org
> tdwg-tag mailing list
> tdwg-tag at lists.tdwg.org
: Hilmar Lapp -:- Durham, NC -:- informatics.nescent.org :
More information about the tdwg-tag