RFC 3120

A URN Namespace for XML.org

📅 published June 2001, from ietf

RFC 3120: A URN Namespace for XML.org 🎀

okay bestie, here's the vibe check ✨ this RFC was written by Karl Best (OASIS, Inc.) and Norman Walsh (Sun Microsystems, Inc.) in June 2001. It's marked as Informational 📚, so it's giving "here's some info" rather than "you must do this." The title block doesn't list anything it obsoletes or updates 🦋

Status of This Memo 📝

this memo is just providing info for the Internet community 💅 it doesn't specify an Internet standard of any kind. distribution is unlimited, so share it with everyone 🌸

copyright (C) The Internet Society (2001). all rights reserved 🔒

Abstract 💌

this doc describes a URN (Uniform Resource Name) namespace that the Organization for the Advancement of Structured Information Standards (OASIS) engineered for naming persistent resources in the XML.org repository 🌈 that includes stuff like XML (Extensible Markup Language) Document Type Definitions, XML Schemas, Namespaces, Stylesheets, and other docs 🧚

1. Introduction ✨

so the XML.org Registry is a public service where people share XML schemas, DTDs, stylesheets, and other docs 💖 people submit stuff to the repository, and then others grab it to use. all these docs need unique identifiers, obviously 🙈

because of all that, XML.org wants to give URNs to some resources so they get unique, permanent, location-independent names 🫶

this namespace spec is for a formal namespace 👑

2. Specification Template 🎀

Namespace ID

the requested namespace ID is xmlorg 💜

Registration Information

  • Registration Version Number: 3
  • Registration Date: 2001-02-05

Declared registrant of the namespace

the registrant is:

Karl Best
OASIS - Organization for the Advancement of Structured
Information Standards
Post Office Box 455
Billerica, MA USA 01821

Phone: +1 (978) 667 5115

Declaration of structure

the Namespace Specific String (NSS) of every URN that XML.org assigns has a hierarchical structure 🌳 there's one branch at the top, and it's called objects 🦋

The Objects Hierarchy

the general NSS structure in the names hierarchy looks like this:

urn:xmlorg:objects:{type}{:subtype}?:{object-id}

where:

  • type tells you the document type (document, schema, stylesheet, entity, xmlns, etc.) 📄
  • the optional subtype gives extra info about the document type, like the stylesheet or schema language 🧁
  • object-id is a unique identifier for the document 🔑

the Director of Technical Operations at OASIS assigns document types, subtypes, and all unique identifiers 👑

Relevant ancillary documentation

None 🌙

Identifier uniqueness considerations

uniqueness gets enforced by the Director of Technical Operations, who gives unique identifiers to every document identified by a URN 💅

Identifier persistence considerations

OASIS is committed to keeping all the URN-assigned resources accessible and persistent 🫶 iconic behaviour, honestly ✨

Process of identifier assignment

assignment is limited to the owner and any authorities the owner specifically designates 🔐 OASIS may also assign portions of its namespace to other parties 🌸

Process of identifier resolution

the owner will distribute catalogs (OASIS TR9401 Catalogs) that map the assigned URNs to resource identifiers (like URLs) 🗺️ a more interactive, online resolution system will also be deployed in the near future 🚀

the owner will also authorize additional resolution services as appropriate 💖

Rules for Lexical Equivalence

URNs are lexically equivalent if they are lexically identical 🪞 no plot twists here 💀

Conformance with URN Syntax

no special considerations 🌈

Validation mechanism

none specified. the owner will publish OASIS TR9401 Catalogs, and if a URN is in a catalog, that means it's valid ✅

Scope

global 🌍

3. Examples 🍓

these examples are not guaranteed to be real 🙈 they're just here for pedagogical reasons, bestie 📚

urn:xmlorg:objects:schema:xmlschema:xcatalog
urn:xmlorg:objects:dtd:xml:docbook:v4.1.2

4. Security Considerations 🔒

there are no extra security considerations beyond the ones that normally come with using and resolving URNs in general 🛡️ so keep your usual guard up, okay? 💀

References 📚

  • [1] Goldfarb, C. F., "ISO (International Organization for Standardization) ISO 8879:1986(E) Information Processing -- Text and Office Systems -- Standard Generalized Markup Language (SGML)", 1986.
  • [2] W3C, XML WG, "Extensible Markup Language (XML) 1.0", February 1998, <http://www.w3.org/TR/REC-xml>.
  • [3] W3C, Namespaces WG, "Namespaces in XML", January 1999, <http://www.w3.org/TR/REC-xml-names>.
  • [4] OASIS, Entity Mgmt. TC, "Entity Management: OASIS Technical Resolution 9401:1997 (Amendment 2 to TR 9401)", January 1994, <http://www.oasis-open.org/html/a401.htm>.
  • [5] Moats, R., "URN Syntax", RFC 2141, May 1997.
  • [6] Mealling, M. and R. Daniel, "URI Resolution Services Necessary for URN Resolution", RFC 2483, January 1999.

Authors' Addresses 💌

Karl Best OASIS, Inc. P.O. Box 455 Billerica, MA 01821 US

EMail: karl.best@oasis-open.org

Norman Walsh Sun Microsystems, Inc. One Network Drive MS UBUR02-201 Burlington, MA 01803-0902 US

EMail: Norman.Walsh@East.Sun.COM

this part is legal boilerplate, so I'm keeping it word-for-word 🫶

Copyright (C) The Internet Society (2001). All Rights Reserved.

This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.

The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.

This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Acknowledgement 🌷

funding for the RFC Editor function is currently provided by the Internet Society 💖

📦 where this page comes from