PNNSbreadcrumb separatorGeneric Allocationbreadcrumb separatorETSI XML URI Namespace

ETSI XML URI Namespace

XML uses URIs, or Uniform Resource Identifiers, in order to clearly identify an XML module, or an object defined within an XML file.  A number of
different URI schemes exist.  W3C uses URIs for XML which are from the http: scheme.  IETF and some other bodies make use of the urn: scheme.

ETSI has reserved a URI namespace in the http: scheme, for use specifically as identifiers within XML code which is published as part of an ETSI
 specification.  The root namespace is:  The ETSI namespace is structured into 3 domains: Deliverable-based Domain,
Common Domain and ETSI Identified Organisation Domain.

URIs in the http: scheme used in XML files look like HTTP URLs, but they are unique Identifiers, not Locators, i.e. the URI does not necessarily
point to any specific location or page accessible with the HTTP protocol.

Further information

RFC 3986:   Uniform Resource Identifier (URI): Generic Syntax
RFC 3406:   Uniform Resource Names (URN) Namespace Definition Mechanisms
RFC 2616:   Hypertext Transfer Protocol -- HTTP/1.1
W3C Namespaces in XML 1.0
W3C Namespaces in XML 1.1

Deliverable Based Domain

This Domain is used for URIs which are assigned in one ETSI specification and are unrelated to other URIs assigned in other specifications. Every
ETSI specification has a URI root which can be associated with it, whether or not it is actually used in the specification.  This URI root is defined as

where nnnnn is the five digit number obtained by removing the first digit of the ETSI Document number, and any part or sub-part numbers.  Leading
 zeros are NOT removed.  The  resulting number is independent of ETSI deliverable type.

Example 1: The value obtained for TS 101 123 is "01123".  The value obtained for ES 201 123 is also "01123", since the assignment of ETSI
document numbers is independent of ETSI document type.  Technically, TS 101 123 and ES 201 123 are just two different versions of the same
document.  Both will result in the following URI root:

Example 2: The value obtained for ES 201 915-4 is “01915”.  The URI root obtained is:

Example 3: The value obtained for EN 300 822 is 00822.  The URI root obtained is:

There is no need to register either the ETSI Deliverable Based URI root, or any sub-structure or individual URIs based on this URI root, with the ETSI
 Secretariat.  The ETSI document number, uniquely assigned by the ETSI Secretariat, is sufficient to guarantee uniqueness and to identify the
location of a URI defintion.

The ETSI technical body which drafts the specification, is responsible for assignment and management of any URIs in its specification. 

Common Domain

The Common Domain URIs are assigned by the ETSI Secretariat, on request, to an ETSI Technical Body, for use in more than one ETSI

The ETSI Technical Body is fully responsible for creation and management of the sub-structure under the assigned URI root, and shall maintain an
ETSI deliverable describing this sub-structure.  This specification shall be identified in their request for a Common Domain URI.

The format for a common domain URI is the ETSI URI root ( followed by a name which identifies the common domain.  Technical
Bodies requesting the assignment of a common domain URI root should suggest this name. The ETSI Secretariat maintains a register of assigned
Common Domain URIs.

Requests for a common domain URI should be addressed to the ETSI CTI:

ETSI Identified Organization Domain

ETSI will assign a URI root to any organization which requests it, whether or not that organization is an ETSI member. 

The ETSI Secretariat maintains a register of assigned URI roots in the ETSI Identified Organization domain, but does not maintain the sub-structure
under these assigned URIs. 

The format of an ETSI Identified Organization URI root is:

followed by a name which identifies the organization.  The requesting organization should suggest this name when they make their request.

Requests for an ETSI Identified Organization URI should be addressed to the ETSI CTI: