A Uniform Resource Name (URN) Namespace for the Open Geospatial Consortium (OGC)
draft-creed-ogc-urn-03

[Ballot comment]
When I read
      OGC may permit use of experimental type values that will not be
      registered.  As a consequence, multiple users may end up using the
      same value for separate uses.  As experimental usage is only
      intended for testing purposes, this should not be a real issue.

I find the idea of URN that aren't unique sort of disturbing. We have past experience with experiments that become widely successful and then are so embedded in deployed code that the identifier can not be changed.

[Ballot discuss]
I can't review  https://portal.opengeospatial.org/wiki/twiki/bin/view/Member/OGCUrnIntro ? I am happy to clear this discuss if we feel that it is fine to approve this without reviewing the assignment procedures as long as we agree that we will consistently apply that decision to future URN registrations as well as this one.

[Ballot comment]
Issue:
I didn't see a commitment to keep URNs stable in the document.
Specifically, it would be better if they committed not to
unregister items and not to change an item's meaning in an incompatible
way.

Nit:
      and submit new proposals for additional resources. So can any
      individual or organization can make a contribution by submitting
double use of "can"

IANA Last Call comments:

Upon approval of this document, the IANA will make the following assignments in the "URN Namespaces - [RFC2141, RFC3406]" registry located at
http://www.iana.org/assignments/example-foobar-registry

URN Namespaces Value Reference
--------------------- ----- ---------
OGC TDB [RFC-creed-ogc-urn-02]

We understand the above to be the only IANA Action for this document.