RFC 3614

RFC 3614: A Uniform Resource Name (URN) Namespace for the Motion Picture Experts Group (MPEG) ✨

• Network Working Group 🎀
• Request for Comments: 3614
• Author: J. Smith (John R. Smith), IBM T. J. Watson Research Center 🧠
• Category: Informational 📚
• Date: September 2003 🗓️
• Obsoletes / Updates: none listed in the title block 🙅‍♀️

---

Status of This Memo

okay so this memo is informational 💅 It's for the Internet community, and it does not specify an Internet standard of any kind. Distribution is unlimited, so share it with everyone 🌈

Copyright Notice

Copyright (C) The Internet Society (2003). All Rights Reserved. 🔒

Abstract

This doc describes a Uniform Resource Name (URN) namespace for the Motion Picture Experts Group (MPEG) 🎬 It's for naming persistent resources that are part of the MPEG standards. Think technical documents and specifications, eXtensible Markup Language (XML) Schemas, classification schemes, XML Document Type Definitions (DTDs), namespaces, style sheets, media assets, and other types of resources made or managed by MPEG. It's giving organized 📁✨

1. Introduction 🌸

MPEG is a working group of the International Organization for Standardization (ISO) and International Engineering Consortium (IEC). Their whole thing is developing standards for coded representation of digital audio and video 🎧📺 They've made MPEG-1, which is the standard that Video CD and MP3 are based on. Then there's MPEG-2, the one behind Digital Television set top boxes and DVD. MPEG-4 is the standard for multimedia for the fixed and mobile web, and MPEG-7, "Multimedia Content Description Interface", is the standard for describing and searching audio and visual content. Work on MPEG-21, "Multimedia Framework" is currently underway 🔥

MPEG wants to assign unique, permanent, location-independent names based on URNs for some of the resources it produces or manages. Main character energy 👑

This namespace specification is for a formal namespace 💖

2. Specification Template 💅

Namespace ID:

"mpeg"

Registration Information:

Version: 1
Date: 2001-11-20

Declared registrant of the namespace:

Name:           John R. Smith
Title:          Chair, MPEG MDS Subgroup
Affiliation:    IBM T. J. Watson Research Center
Address:        30 Saw Mill River Road
                Hawthorne, NY 10532 USA
Phone:          +1 (914) 784-7320
Email:          jrsmith@watson.ibm.com

Declaration of structure:

URNs assigned by MPEG will have the following hierarchical structure, based on the organizational structure of the MPEG standards 🧩

urn:mpeg:{standard name}:{assigned US-ASCII string}

where "{standard name}" is a US-ASCII string that conforms to URN Syntax requirements ([RFC2141]) and corresponds to the name of an MPEG standard (such as "mpeg1", "mpeg2", "mpeg4", "mpeg7", "mpeg21", and

and "{assigned US-ASCII string}" is a US-ASCII string that conforms to URN Syntax requirements ([RFC2141]).

The individual URNs SHALL be assigned by MPEG through the process of developing MPEG standards. Non-negotiable 🫶

Relevant ancillary documentation:

None 🤷‍♀️

Identifier uniqueness considerations:

MPEG SHALL establish unique identifiers as appropriate. 🔑

Uniqueness is guaranteed as long as the assigned string is never reassigned for a given standard name, and the standard name is never reassigned either. Iconic behaviour ✨

Identifier persistence considerations:

MPEG is committed to maintaining the accessibility and persistence of all resources that are officially assigned URNs by the organization 🫡

Persistence of identifiers depends on suitable delegation of resolution at the level of "standard name"(s), and on persistence of standard name assignment 🧷

Process of identifier assignment:

Assignment is limited to the owner and to those authorities that are specifically designated by the owner. MPEG MAY designate portions of its namespace for assignment by other parties. 🎀

Process of identifier resolution:

The owner will develop and maintain "URN catalogs" that map all assigned URNs to Uniform Resource Locators (URLs), specifically to enable Web-based resolution of named resources 🌐 In the future, an interactive online resolution system may be developed to automate this process 🤖

The owner will authorize additional resolution services as appropriate 💜

Rules for Lexical Equivalence:

The "standard name" is case-insensitive. So the portion of the URN:

urn:mpeg:{standard name}:

is case-insensitive for matches. The remainder of the identifier MUST be considered case-sensitive. Pay attention to this one bestie 👀

Conformance with URN Syntax:

No special considerations. 🙌

Validation mechanism:

None specified. The owner will develop and maintain URN catalogs.

The presence of a URN in a catalog indicates that it is valid ✅

Scope:

Global 🌍

3. Examples 🧚

The following examples are not guaranteed to be real. They are presented for pedagogical reasons only 🙈

urn:mpeg:mpeg7:schema:2001
urn:mpeg:mpeg7:cs:VideoDomainCS:2001
urn:mpeg:mpeg7:cs:GenreCS:2001
urn:mpeg:mpeg7:cs:ContentCS:2001

4. Namespace Considerations 🔮

URN assignment procedures:

The individual URNs SHALL be assigned through the process of developing MPEG standards, by the Moving Picture Experts Group (MPEG), which is a working group of ISO/IEC 🎞️

URN resolution/delegation:

The resolution and delegation SHALL be determined through the process of developing MPEG standards, by the Moving Picture Experts Group (MPEG). MPEG has developed requests for registration authority for MPEG-7 classification schemes and MPEG-21 identification systems. These registration authorities SHALL be responsible for corresponding parts of the MPEG namespace 🗂️

Type of resources to be identified:

Types of resources to be identified include XML schema definition files, classification schemes, and identification systems 🏷️

Type of services to be supported:

Types of services supported include controlled term lookup in classification schemes, and resolution of IDs in identification systems 🔍

5. Community Considerations 🫂

Open assignment and use of identifiers within the namespace:

With ongoing development of MPEG standards, MPEG SHALL establish requirements for assignment and use of identifiers within the MPEG namespace. MPEG has already established requirements for assignment and use of MPEG-7 classification schemes under the MPEG namespace. A registration authority SHALL have the responsibility for processing third-party requests for registering classification schemes 📝

Open operation of resolution servers for the namespace (server):

With ongoing development of MPEG standards, MPEG SHALL establish requirements and seek candidates for operating resolution servers as appropriate 🖥️

Creation of software that can meaningfully resolve and access services for the namespace (client):

With ongoing development of MPEG standards, MPEG SHALL develop reference software implementations of its standards 💻

6. Security Considerations 💀

⚠️ Okay bestie, this part is serious. There are no additional security considerations beyond those normally associated with the use and resolution of URNs in general. Treat it with the same care you'd give any URN, no exceptions 🚨

7. IANA Considerations 🦋

The IANA has registered formal URN namespace 12 to MPEG, within the IANA registry of URN NIDs 🎉

8. Normative References 📖

[RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997.

9. Author's Address 💌

John R. Smith
IBM T. J. Watson Research Center
30 Saw Mill River Road
Hawthorne, NY 10532 USA

Phone: 1 (914) 784-7320
EMail: jrsmith@watson.ibm.com

10. Full Copyright Statement ⭐

The legal wording below is kept verbatim, because it's a license and not something to paraphrase 🫶

Copyright (C) The Internet Society (2003). 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 assignees.

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 💖