2feb49bc-6755-11dc-8314-0800200c9a66
Seen in rfc5138

Seen in rfc5138

Seen in RFC 5138
Counts : rfc5138:2
RFC 5138              A URN Namespace for the CGI          February 2008


   urn:cgi:feature:USGS:2feb49bc-6755-11dc-8314-0800200c9a66

      - identifies a feature instance given the designation
        2feb49bc-6755-11dc-8314-0800200c9a66 by the US Geological
        Survey.

   urn:cgi:object:SGU:552cb080-6755-11dc-8314-0800200c9a66

      - identifies an object given the designation
        552cb080-6755-11dc-8314-0800200c9a66 by the Geological Survey of
        Sweden.

4.  Namespace Considerations

   There is currently no available namespace that will allow the CGI to
   uniquely specify and access resources, such as schemas and
   registries, that are required by organizations implementing CGI
   standards.  There is also a need for other standards organizations,
   such as the Open Geospatial Consortium (OGC) to be able to access
   CGI-specific resources.

   The CGI members considered use of other existing NIDs, such as those
   for OGC.  However, these do not support the semantics required and in
   particular do not allow for the delegation of identifier assignment
   within the CGI community that is demonstrated here.

5.  Community Considerations

   CGI standards require access to resources, such as schemas,
   registries, catalogues, documents, and services.  In order for the
   larger IT community to be able to implement applications that access
   CGI resources effectively, a unique namespace is required.  We desire
   these resources to be freely and openly available as a set of
   community resources.

   The design of the CGI namespace builds on the experience of the Open
   Geospatial Consortium (OGC) which has defined the framework of
   geospatial services within which CGI standards have been developed.
   The OGC membership has expertise in using the OGC URN [OGC-URN]
   [OGC-DEF], gained through implementation experiments and a variety of
   operational testbeds.  The CGI namespace is compatible with this
   experience.

6.  Security Considerations

   There are no additional security considerations other than those
   normally associated with the use and resolution of URNs in general.




Cox                          Informational                      [Page 6]
-1 RFC regex push