RFC 4195

RFC 4195: A Uniform Resource Name (URN) Namespace for the TV-Anytime Forum ✨

okay so this is RFC 4195 🎀. It's written by W. Kameyama from GITS, Waseda University, it's Category: Informational, and the date is October 2005. The title block doesn't list anything it obsoletes or updates, so it's just vibing on its own 💅

---

Status of This Memo 📜

This memo gives information to the Internet community 🫶 It is not an Internet standard of any kind, and you can distribute it as much as you want.

Copyright Notice ©️

Copyright (C) The Internet Society (2005).

Abstract ✨

okay so this doc defines a Uniform Resource Name (URN) namespace that the TV-Anytime Forum set up for naming persistent resources it publishes 🦋 That includes the TV-Anytime Forum Standards, XML (Extensible Markup Language) Document Type Definitions, XML Schemas, Namespaces, and other documents, all with names that stick around.

1. Introduction 🌸

The TV-Anytime Forum makes a LOT of documents (specifications, working documents, and schemas) 📚 Lots of standards bodies are thinking about adopting them, like ETSI (European Telecommunication Standardization Institute), DVB (Digital Video Broadcasting), ARIB (Association of Radio Industries and Businesses), and ATSC (Advance Television Systems Committee). Iconic lineup, honestly.

The TV-Anytime Forum wants global, distributed, persistent, location-independent names for all of these resources 🌈

2. Specification Template 🎀

Here's the whole template, bestie 💖

Namespace ID

The namespace ID is "tva".

Registration information

The registration version number is 1, and the registration date is 2005-1-6.

Declared registrant of the namespace

• Name: Wataru KAMEYAMA
• Title: Vice Chairman and Secretary, The TV-Anytime Forum
• Affiliation: Graduate School of Global Information and Telecommunication Studies, Waseda University
• Address: 1011 Okuboyama, Nishi-tomida, Honjo-shi, Saitama 367-0035, JAPAN
• Phone: +81 495 24 6052
• Email: wataru@waseda.jp

Declaration of structure

Every Namespace Specific String (NSS) for URNs the TV-Anytime Forum assigns is going to have this hierarchical structure 🧚

urn:tva:{category}:{string}

The "category" is a US-ASCII string that follows URN syntax requirements ([RFC2141]). "{string}" is also a string that follows URN syntax requirements ([RFC2141]) 💜

Relevant ancillary documentation

The TV-Anytime Forum specs have been publicly available the whole time they were being developed, from "ftp://tva:tva@ftp.bbc.co.uk/Specifications/" 📂 The final specs are also published as formal ETSI technical specification documents in the ETSI TS 102 822 series. ✨

Identifier uniqueness considerations

The TV-Anytime Forum shall establish unique identifiers as appropriate.

Uniqueness is guaranteed as long as the assigned "{category}" is never reassigned for other categories. The TV-Anytime Forum is responsible for that 🫶

Identifier persistence considerations

The TV-Anytime Forum is committed to keeping accessible and persistent every resource that the organization officially assigns a URN to 💅 Persistence of identifiers depends on suitable delegation at the level of "category"s, and on the category assignments staying persistent too.

Process of identifier assignment

All identifier assignments are fully controlled and managed by the TV-Anytime Forum 👑

Process of identifier resolution

The namespace isn't listed with an RDS, so this one isn't relevant 🙈

Rules for Lexical Equivalence

The "{category}" part is case-insensitive. So the portion of the URN:

urn:tva:{category}:

is case-insensitive when matching. The rest of the identifier shall be treated as case-sensitive, so URNs are only lexically equivalent if the remaining {string} field is lexically identical too 🔥

Conformance with URN Syntax

No special considerations. Easy.

Validation mechanism

Validation shall be done with a syntax grammar for each "{category}" 🎀

Scope

Global. 🌍

3. Examples 🧚

These examples aren't guaranteed to be real. They're only here for teaching purposes 🍓

urn:tva:metadata:2002
urn:tva:metadata:cs:IntentionCS:2002
urn:tva:metadata:cs:ActionTypeCS:2002
urn:tva:rmp:tvax

4. Community Considerations 🫶

The names in this namespace are meant to be used in any public implementations of the TV-Anytime Forum specs, so that anybody can benefit from the officially assigned namespace ✨

Here are the potential beneficiary communities:

• a) Implementers of the TV-Anytime specifications. Resources that follow the TV-Anytime Forum specs (including TV-Anytime schemas, instance documents that comply with TV-Anytime schemas, and TV-Anytime default Classification Schemes) may, through the registered namespace, become exposed to the general Internet and get the interoperability perks of the Internet at large 🌐
• b) Implementers of other specifications that incorporate components of the TV-Anytime specifications. URNs used to identify TV-Anytime components can help them get included in, and enhance, other specs, while keeping, to a certain degree, interoperability with the TV-Anytime community (see a) above) 💜
• c) Implementers of other semantically related specifications that do not directly incorporate components of the TV-Anytime specifications. URNs that identify components of the TV-Anytime specs, like identifiers for terms in default Classification Schemes, may enable interoperation with other semantically determined specs (including present and future metadata/resource description and ontology specifications) that matter to TV-Anytime implementation communities (see a) and b) above) 🦋

5. Namespace Considerations 🏷️

This application needs a unique namespace because its assignment mechanism requires delegation to the TV-Anytime Forum. Since this namespace identifies components of the TV-Anytime specifications, the TV-Anytime Forum will manage how the components relate to each other and keep the identifiers unique 👑

6. Security Considerations 🔐

There are no additional security considerations beyond the ones normally associated with using and resolving URNs in general. Stay safe out there, bestie 🫶

Informative References 📚

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

Author's Address 🖋️

Wataru KAMEYAMA
GITS, Waseda University
1011 Okuboyama, Nishi-tomida
Honjo-shi, Saitama, 367-0035
JAPAN

Phone: +81 495 24 6052
EMail: wataru@waseda.jp

Full Copyright Statement ©️

Copyright (C) The Internet Society (2005).

This document is subject to the rights, licenses and restrictions in BCP 78. Except as stated there, the authors keep all their rights 💖

This document and the information in it are provided on an "AS IS" basis. THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT USING THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS, OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE 🙈

Intellectual Property 💡

The IETF takes no position on the validity or scope of any Intellectual Property Rights or other rights that might be claimed to apply to the implementation or use of the technology described here. It also doesn't say whether any license under those rights might or might not be available, and it hasn't made any independent effort to find those rights. Info on how RFC documents handle rights is in BCP 78 and BCP 79 📜

Copies of IPR disclosures made to the IETF Secretariat, any assurances of licenses to be made available, or the result of an attempt to get a general license or permission to use such proprietary rights by implementers or users of this spec can be found in the IETF on-line IPR repository at http://www.ietf.org/ipr.

The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology needed to implement this standard. Send that info to the IETF at ietf-ipr@ietf.org 🫶

Acknowledgement 🌷

Funding for the RFC Editor function is currently provided by the Internet Society. 💜