As per Relevance of the word document, we have this rfc below:
Network Working Group K.
Request for Comments: 3120 OASIS, Inc
Category: Informational N.
Sun Microsystems, Inc
June 2001
A URN Namespace for XML.
Status of this
This memo provides information for the Internet community. It
not specify an Internet standard of any kind. Distribution of
memo is unlimited
Copyright
Copyright (C) The Internet Society (2001). All Rights Reserved
This document describes a URN (Uniform Resource Name) namespace
is engineered by the Organization for the Advancement of
Information Standards (OASIS) for naming persistent resources
in the XML.org repository (such as XML (Extensible Markup Language
Document Type Definitions, XML Schemas, Namespaces, Stylesheets,
other documents).
1.
The XML.org Registry is provided by XML.org as a public service
XML schemas, DTDs, stylesheets, and other documents can be shared
Documents are submitted to a repository then retrieved by others
may want to use them. These documents require unique identifiers
Motivated by these observations, XML.org would like to assign URNs
some resources in order to retain unique, permanent location
independent names for them
This namespace specification is for a formal namespace
2. Specification
Namespace ID
"xmlorg" requested
Best & Walsh Informational [Page 1]
RFC 3120 A URN Namespace for XML.org June 2001
Registration Information
Registration Version Number: 3
Registration Date: 2001-02-05
Declared registrant of the namespace
Karl
OASIS - Organization for the Advancement of
Information
Post Office Box 455
Billerica, MA USA 01821
Phone: +1 (978) 667 5115
Declaration of structure
The Namespace Specific String (NSS) of all URNs assigned
XML.org will have the following hierarchical structure
There is one branch at the top of the hierarchy: "objects".
The Objects
The general structure of the NSS in the names hierarchy has
form
urn:xmlorg:objects:{type}{:subtype}?:{object-id
where "type" identifies the document type (document, schema
stylesheet, entity, xmlns, etc.), the optional "subtype
provides additional information about the document type (
example, stylesheet or schema language), and "object-id" is
unique identifier for the document
The Director of Technical Operations at OASIS assigns
types, subtypes, and all unique identifiers
Relevant ancillary documentation
Identifier uniqueness considerations
Identifier uniqueness will be enforced by the Director
Technical Operations who assigns unique identifiers to
documents identified by URN
Best & Walsh Informational [Page 2]
RFC 3120 A URN Namespace for XML.org June 2001
Identifier persistence considerations
OASIS is committed to maintaining the accessibility
persistence of all the resources that are assigned URNs
Process of identifier assignment
Assignment is limited to the owner and those authorities that
specifically designated by the owner. OASIS may assign
of its namespace for assignment by other parties
Process of identifier resolution
The owner will distribute catalogs (OASIS TR9401 Catalogs)
map the assigned URNs to resource identifiers (e.g., URLs).
more interactive, online resolution system will also be
in the near future
The owner will authorize additional resolution services
appropriate
Rules for Lexical Equivalence
URNs are lexically equivalent if they are lexically identical
Conformance with URN Syntax
No special considerations
Validation mechanism
None specified. The owner will publish OASIS TR9401 Catalogs
The presence of a URN in a catalog indicates that it is valid
Scope
3.
The following examples are not guaranteed to be real. They
listed for pedagogical reasons only
urn:xmlorg:objects:schema:xmlschema:
urn:xmlorg:objects:dtd:xml:docbook:v4.1.2
Best & Walsh Informational [Page 3]
RFC 3120 A URN Namespace for XML.org June 2001
4. Security
There are no additional security considerations other than
normally associated with the use and resolution of URNs in general
[1] Goldfarb, C. F., "ISO (International Organization
Standardization) ISO 8879:1986(E) Information Processing --
and Office Systems -- Standard Generalized Markup
(SGML)", 1986.
[2] W3C, XML WG, "Extensible Markup Language (XML) 1.0",
1998, .
[3] W3C, Namespaces WG, "Namespaces in XML", January 1999,
.
[4] OASIS, Entity Mgmt. TC, "Entity Management: OASIS
Resolution 9401:1997 (Amendment 2 to TR 9401)", January 1994,
.
[5] Moats, R., "URN Syntax", RFC 2141, May 1997.
[6] Mealling, M. and R. Daniel, "URI Resolution Services
for URN Resolution", RFC 2483, January 1999.
Authors'
Karl
OASIS, Inc
P.O. Box 455
Billerica, MA 01821
EMail: karl.best@oasis-open.
Norman
Sun Microsystems, Inc
One Network
MS UBUR02-201
Burlington, MA 01803-0902
EMail: Norman.Walsh@East.Sun.
Best & Walsh Informational [Page 4]
RFC 3120 A URN Namespace for XML.org June 2001
Full Copyright
Copyright (C) The Internet Society (2001). All Rights Reserved
This document and translations of it may be copied and furnished
others, and derivative works that comment on or otherwise explain
or assist in its implementation may be prepared, copied,
and distributed, in whole or in part, without restriction of
kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However,
document itself may not be modified in any way, such as by
the copyright notice or references to the Internet Society or
Internet organizations, except as needed for the purpose
developing Internet standards in which case the procedures
copyrights defined in the Internet Standards process must
followed, or as required to translate it into languages other
English
The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns
This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Funding for the RFC Editor function is currently provided by
Internet Society
Best & Walsh Informational [Page 5]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
