RFC 3688 (rfc3688) - Page 2 of 8
The IETF XML Registry
Alternative Format: Original Text Document
RFC 3688 The IETF XML Registry January 2004
authoritative location for their XML elements. As part of this
standard, the IANA will maintain:
o the public representation of the document,
o the URI for the elements if one is provided at the time of
registration,
o a registry of Public Identifiers as URIs.
In the case where the registrant does not request a particular URI,
the IANA will assign it a Uniform Resource Name (URN) that follows
[RFC 3553].
2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in BCP 14, RFC 2119
[RFC 2119].
3. Registerable Documents
3.1. The Assigned/Registered URI
All elements (except PUBLIC identifiers) in this registry will
require a URI in order to be registered. If the registrant wishes to
have a URI assigned, then a URN of the form
urn:ietf:params:xml::
will be assigned where is the type of the document being
registered (see below). is a unique id generated by the IANA
based on any means the IANA deems necessary to maintain uniqueness
and persistence. NOTE: in order for a URN of this type to be
assigned, the item being registered MUST have been through the IETF
consensus process. Basically, this means that it must be documented
in a RFC. The RFC 3553 [RFC 3553] URN registration template is found
in Section 6.
The IANA will also maintain a file server available via at least HTTP
and FTP that contains all of the registered elements in some publicly
accessible file space in the same way that all of the IANA's
registered elements are available via
http://www.iana.org/assignments/. While the directory structure of
this server is up to the IANA, it is suggested that the files be
organized by the and the individual files have the as
their filename.
Mealling Best Current Practice