> AM> "neogeography"
>
> It isn't. Apparently, there're a lot of geoscientific data sets
> (SRTM- and ASTER-derived digital elevation models, some of the
> MODIS datasets, Landsat imagery is what comes to mind) which are
> referenced to UTM, sinusoidal or other projections. To me, it
> looks like that the only field where WGS-84 is predominant in
> geoscience is climatology.
Well, the SRTM and ASTER datasets that i found and use are in WGS-84.
And i think of "neogeography" as people with no GIS knowledge at all
handling such data (and who most likely know coordinates only from their
GPS, and the numbers above the wikipedia articles), not of those people
who are well aware of the implications of using a certain CRS.
Anyway, for the purpose of the document we had reached consensus in the
group to go for WGS-84 as the default, and "keep the door open" for
other CRSes. I'd very much not like to re-open that discussion again.
> Just to clarify: while the stated purpose of the proposal is to
> ``provide a protocol independent, compact and generic way to
> refer to a physical geographic location'', don't you assume a
> rather specific protocol here? Namely, one with a user seeing
> an URI within his or her WWW browser window?
No, i do not. The purpose for my include what you describe, but
essentially it's purpose is to be used in anyplace where a whatever
protocol allows the inclusion of an arbitrary URI.
Where the information contained in the URI originates, and what a user
agent (if it ever reaches one) does with that information is a
completely different story.
> AM> - most internet users are not even aware that there's something
> AM> like CRSes.
>
> I don't think that most of the Internet users of today seen an
> RCPT command, either. Nevertheless, SMTP keeps going.
RCPT is a an element of a protocol command, not an identification
scheme. "mailto:" is the corresponding identification scheme - and
people know very well what it means and how to use it, even if it's
printed on a business card - and for that, they don't need to speak
SMTP.
Anyway: Let's get the document done, so that we have a stable basis for
whatever things may bloom based on that :-)
Alex
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv
