Tuesday, June 2, 2009

Re: [Geopriv] The "geo" URI draft

Gee I like design-by-committee.

This thread seems to have lost sight of the original design goals of this work: cheap and simple.

Now we could worry about the impact of a new coordinate reference systems, but whatever we choose, two things happen: we start paying a price now; we probably get it wrong.

The only think that I am certain we can get right now is a version tag (which it seems that we've started to use datum/CRS tags for recently). So maybe that's the way to go--an optional version tag that forces the receiver to drop the whole payload if it isn't the expected value. There's a little cost involved, but at least we know how to do that part right.

Even then, I'm not convinced that we need to do this given the relative ease with which we are able to convert between different systems. Of course, to do that with the utmost precision, we'd need to include a time parameter to allow for continental drift adjustments... And then we can add location type parameters, maybe mood.

As for extraplanetary locations, these aren't really compatible with the idea of "simple". If we want to go off planet, maybe we wont be able to take our geo: URIs with us. I can live with that.

Furthermore, <http://microformats.org/wiki/index.php?title=mars-examples&oldid=32233> was used to support an argument for the addition of extraterrestrial positions. Strange, because it uses a completely different tag to identify the microformat describing a position on Mars; 'mars' instead of 'geo'. That suggests that if I wanted to identify the Spirit landing site I would use 'mars:-14.5718,175.4785'. All in all, an elegant solution (thanks Peter :).

--Martin
------------------------------------------------------------------------------------------------
This message is for the designated recipient only and may
contain privileged, proprietary, or otherwise private information.
If you have received it in error, please notify the sender
immediately and delete the original. Any unauthorized use of
this email is prohibited.
------------------------------------------------------------------------------------------------
[mf2]
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv