Internet DRAFT - draft-stockhammer-msf-urn
draft-stockhammer-msf-urn
Internet Engineering Task Force T. Stockhammer, Ed.
Internet-Draft Qualcomm Germany GmbH
Intended status: Informational 19 December 2023
Expires: 21 June 2024
URN Namespace for Metaverse Standards Forum Resources
draft-stockhammer-msf-urn-00
Abstract
This document describes the Namespace IDentifier (NID) 'metaverse-
standards-org' for Uniform Resource Names (URNs) used to identify
resources published by Metaverse Standards Forum. The forum
specifies and manages resources that utilize this URN identification
model. Example resources include ressources, eXtensible Markup
Language (XML) Schemas, classification schemes, XML Document Type
Definitions (DTDs), namespaces, style sheets, and other types of
resources produced or managed by the Metaverse Standards Forum.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on 21 June 2024.
Copyright Notice
Copyright (c) 2023 IETF Trust and the persons identified as the
document authors. All rights reserved.
Stockhammer Expires 21 June 2024 [Page 1]
Internet-Draft URN Namespace for MSF December 2023
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. Code Components
extracted from this document must include Revised BSD License text as
described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Revised BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2. URN Specification for Metaverse Standards Forum . . . . . . . 3
3. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Namespace Considerations . . . . . . . . . . . . . . . . . . 5
5. Community Considerations . . . . . . . . . . . . . . . . . . 5
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
7. Security Considerations . . . . . . . . . . . . . . . . . . . 6
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
8.1. Normative References . . . . . . . . . . . . . . . . . . 6
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 6
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction
The Metaverse Standards Forum is a non-profit, member-funded
consortium of standards-related organizations, companies, and
institutions that are cooperating to foster interoperability for an
open and inclusive metaverse. Originally founded in June 2022, the
Forum was incorporated in April 2023 to accelerate its mission to
enable and promote broad cooperation and coordination over metaverse-
related standards activities. The Forum does not itself create
standards but instead generates domain and technical reports, use
case and requirements recommendations, pilots, testbeds and
plugfests, open source tooling, best practices and guidelines, and
other data, insights, and visibility to enable standards
organizations to accelerate the development and evolution of
standards that will be essential to building the metaverse. As part
of these efforts, there is a need to specify identifiers in a managed
namespace that are unique and persistent. To ensure that this
namespace's uniqueness is absolute, the registration of a specific
Uniform Resource Name (URN) [RFC8141] Namespace Identifier (NID) for
use by Metaverse Standards Forum is specified in this document, in
full conformance with the NID registration process specified in
[RFC8141].
This namespace specification is for a formal namespace.
Stockhammer Expires 21 June 2024 [Page 2]
Internet-Draft URN Namespace for MSF December 2023
1.1. Terminology
+=========+=================================+
| Acronym | Meaning |
+=========+=================================+
| MSF | Metaverse Standards Forum |
+---------+---------------------------------+
| NID | Namespace IDentifier |
+---------+---------------------------------+
| URN | Uniform Resource Name |
+---------+---------------------------------+
| SRDG | Standards Register Domain Group |
+---------+---------------------------------+
Table 1
2. URN Specification for Metaverse Standards Forum
Namespace ID:
metaverse-standards-org
Registration Information:
registration version number: 1
registration date: 2023-12-25
Declared registrant of the namespace:
Registering organization:
Name: Metaverse Standards Forum
Address: 9450 SW Gemini Drive #16821, Beaverton, OR 97008 USA
Designated Contact:
Namespace Manager, standards_registry-feedback@lists.metaverse-
standards.org
Declaration of syntactic structure:
The Namespace Specific String (NSS) of all URNs that use the
Metaverse Standards NID will have the following structure:
urn:metaverse-standards-org:{MSFresource}:{ResourceSpecificString}
Stockhammer Expires 21 June 2024 [Page 3]
Internet-Draft URN Namespace for MSF December 2023
where "MSFresource" is a US-ASCII string that conforms to the URN
syntax requirements [RFC8141] and defines a specific class of
resource type. Each resource type has a specific labeling scheme
that is covered by "ResourceSpecificString", which also conforms
to the naming requirements [RFC8141].
The Metaverse Standards Forum maintains a registration procedure
within the Standards Register Domain Group (SRDG) that will manage
the assignment of "MSFresource" and the specific registration
values assigned foreach resource class.
Relevant ancillary documentation:
none
Identifier uniqueness considerations:
The SRDG of the MSF manages resources using the "metaverse-
standards-org" NID and will be the authority for managing the
resources and subsequent strings associated. In the associated
procedures, SRDG will ensure the uniqueness of the strings
themselves or shall permit secondary responsibility for the
management of well-defined sub-trees.
The MSF may permit the 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.
Identifier persistence considerations:
The MSF provides clear documentation on a number of the registered
uses of the "metaverse-standards-org" NID. Additional uses
developed by the MSF membership in the future will be first
approved by the SRDG and then by the entire MSF voting membership.
This is the normal process for all MSF permanent resources for use
by the community.
The SRDG maintains a permanent registry of approved uses. This
resource is structured such that each "MSFresource" has a separate
description and registration table.
The registration tables and information are published and
maintained by the SRDG on the MSF web site.
Process of identifier assignment:
The SRDG uses the approved MSF policies and procedures for
discussion, approval, and registration of each type of resource
maintained.
Stockhammer Expires 21 June 2024 [Page 4]
Internet-Draft URN Namespace for MSF December 2023
Process for identifier resolution:
The namespace is not listed with an RDS; this is not relevant.
Rules for lexical equivalence:
No special considerations; the rules for lexical equivalence of
[RFC8141] apply.
Conformance with URN syntax:
No special considerations.
Validation mechanism:
None specified. URN assignment will be handled by procedures
implemented in support of Metaverse Standards Forum activities.
Scope:
Global
3. Example
The following example represents a hypothetical URN that could be
assigned by Metaverse Standards Forum:
urn:metaverse-standards-org:use-case:ar-white-board:2023
This example defines the URN to be used for a usecase defined in the
Metaverse Standards Forum. An associated description of the use case
is published.
4. Namespace Considerations
Metaverse Standards Forum develops ressources that may require the
use of data models. URN Namespaces are key constructs to manage the
definitions of those data models reliably with persistence and
uniqueness.
The use of URNs should also help specification authors to maintain
different versions of URNs and dependencies between URNs across
different versions of Metaverse Standards Forum ressources if they so
wish.
5. Community Considerations
Participants involved in the development and usage of Metaverse
Standards Forum ressources and Metaverse industry deployments will
benefit from the publication of this namespace by providing
consistent and reliable names for the XML namespaces, schema
locations, and similar identifiers of physical data models published
within Metaverse Standards Forum ressources
Stockhammer Expires 21 June 2024 [Page 5]
Internet-Draft URN Namespace for MSF December 2023
6. IANA Considerations
This document adds a new entry ("metaverse-standards-org") in the
urn-namespaces registry. This is the defining document. The entry
can be found in the "Uniform Resource Names (URN) Namespaces"
registry available from the IANA site (http://www.iana.org) and any
associated mirrors.
7. Security Considerations
There are no additional security considerations other than those
normally associated with the use and resolution of URNs in general,
which are described in [RFC1737], and [RFC8141].
8. References
8.1. Normative References
[RFC1737] Sollins, K. and L. Masinter, "Functional Requirements for
Uniform Resource Names", RFC 1737, DOI 10.17487/RFC1737,
December 1994, <https://www.rfc-editor.org/info/rfc1737>.
[RFC8141] Saint-Andre, P. and J. Klensin, "Uniform Resource Names
(URNs)", RFC 8141, DOI 10.17487/RFC8141, April 2017,
<https://www.rfc-editor.org/info/rfc8141>.
Acknowledgements
The authors wish to thank XXX for their useful comments and
suggestions. The authors also acknowledge that the text from RFC6289
formed the basis for the initial version of this document.
Author's Address
Thomas Stockhammer (editor)
Qualcomm Germany GmbH
Anzingerstrasse 17
81671 Munich
Germany
Phone: +491725702667
Email: tsto@qti.qualcomm.com
URI: URI [REPLACE/DELETE]
Stockhammer Expires 21 June 2024 [Page 6]
