NOTE: The galeon mailing list is no longer active. The list archives are made available for historical reasons.
Hi All, At the Ocenas IE report we had discussions about this issue: http://www.oostethys.org/ogcae-ocean-science-ie-report-has-been-submitted-to-ogc see: - section 9.4.1 which is a summary if how to use OGC urns - section 9.6 about Vertical Datum Coordinate reference system and the EPSG registry where you can search for codes is here: http://www.epsg-registry.org/ -luis ___ Luis Bermudez Ph.D. Coastal Research Technical Manager Southeastern Universities Research Association (SURA) bermudez@xxxxxxxx - Office: (202) 408-8211 Mobile: (267) 481-4939 1201 New York Ave. NW Suite 430, Washington DC 20005 On Oct 9, 2008, at 6:58 AM, Dominic Lowe wrote:
Hi Jon, all,My understanding of this issue is that the CRS should be identified by a URN but not necessarily a 'code' so your suggestion of resolving to a machinereadable document is perfectly valid as long as that document has an identifier.But one of the big problems with referencing other things in this way is that a URN can effectively refer to anything and there may not even be a resolverservice at the other end (there might be a hard copy document!) - so ultimately I think your application needs to agree upon and understandthe 'type' of URNs it is going to handle and deal with those. The benefits ofusing URNs of course are that somebody else does the work of defining 'things'. OGC are investing time in URN development: http://www.opengeospatial.org/ogcnaBut that's not to say the CF community shouldn't also invest time in definingresolvable coordinate reference systems specific for our needs.This does bring up the whole interoperability argument again though... :)I agree it is one of the main challenges for CF when it comes to OGC. Cheers, Dom
galeon archives: