RFC 5174

RFC 5174: A Uniform Resource Name (URN) Namespace for the European Broadcasting Union (EBU) 💖

okay bestie, this one is a URN namespace spec for the European Broadcasting Union (EBU) 📻✨. It's from the Network Working Group and was written by Jean-Pierre Evain of the EBU. It's filed as Category: Informational and dated May 2008 🎀. It doesn't obsolete or update anything (there's no line for that in its header), and it's not an Internet standard, just info for the community 🦋

---

Status of This Memo ✨

this memo is here to provide information for the Internet community 🌸 It does not specify an Internet standard of any kind, and distribution of it is unlimited 💅

Abstract 📝

this doc describes a URN namespace for the EBU so it can give persistent names to resources in its technical docs and on the Internet 🫶 The examples are super varied: technical documents and specifications, eXtensible Markup Language (XML) Schemas, classification schemes, XML Document Type Definitions (DTDs), namespaces, style sheets, media assets, and any other kinds of resources the EBU produces or manages 🎬

Table of Contents 🧚

1. Introduction ....................................................2
2. Specification Template ..........................................2
3. Examples ........................................................4
4. Namespace Considerations ........................................4
5. Community Considerations ........................................5
6. Security Considerations .........................................6
7. IANA Considerations .............................................6
8. Normative References ............................................6

1. Introduction 🌈

okay so the EBU is the largest non-for profit professional association of broadcasters worldwide 👑 and it was founded in 1950 🥹 It has more than 70 active members in 55 countries in Europe, North Africa, and the Middle East, plus more than 40 associate members in 25 countries further afield 🌍 The EBU negotiates broadcasting rights for major sport events, runs the Eurovision and Euroradio networks, organizes program exchanges and co-productions, and gives other operational and legal support 💼 It also gives technical advice to its members and favors standardized solutions in broadcast systems, from content ingest all the way to end-user delivery 📺 Its activities cover traditional broadcast and new delivery medias, like the Internet, and a growing number of resources are being developed for those 🦋

the EBU would like to assign unique, permanent, location-independent names based on URNs for some of the resources it produces or manages 🍓

this namespace specification is for a formal namespace 🎀

2. Specification Template 💅

Namespace ID:

"ebu"

Registration Information:

Version: 1 Date: 2007-02-20

Declared registrant of the namespace:

Name:           Jean-Pierre Evain
Title:          Senior Engineer
Affiliation:    European Broadcasting Union (EBU)
Address:        Ancienne Route 17a
                CH-1218 Geneva
                SWITZERLAND
Phone:          +41 22 717 2734
Email:          evain@ebu.ch

Declaration of structure:

okay, so URNs assigned by the EBU will have this hierarchical structure, based on how the EBU's resources are organized 🧩

urn:ebu:{category}:{string}

where {category} is a US-ASCII string that conforms to the syntax of the <NID>, and {string} is a US-ASCII string that conforms to the syntax of the <NSS> [RFC2141] ✨

the EBU will assign the individual URNs through its development process for EBU resources 🛠️

Relevant ancillary documentation:

if you want more info on the EBU and its relevant technical activities, check out http://www.ebu.ch/metadata 📚

Identifier and namespace uniqueness considerations:

the EBU totally gets how vital uniqueness is 😭 It will set up unique identifiers and namespaces under the authority of its metadata expert group, under the auspices of the EBU Production Management Committee, so that existing identifiers and namespaces don't get re-assigned 🔐

Identifier and namespace persistence considerations:

the European Broadcasting Union (EBU) shall ensure the accessibility and persistence of all resources that are officially assigned URNs by the organization, especially upon suitable delegation at the level of "{category}"s, and the persistence of category assignment 💜

Process of identifier and namespace assignment:

the assignment of identifiers and namespaces is fully controlled and managed by the European Broadcasting Union (EBU) 👑

Process of identifier resolution:

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

the owner will also authorize additional resolution services as appropriate ✨

Rules for Lexical Equivalence:

the "{category}" is case-insensitive 🔤 So the portion of the URN:

urn:ebu:{category}:

is case-insensitive for matches up to {category}. The rest of the identifier shall be considered case-sensitive, so URNs are only lexically equivalent if they're also lexically identical in the remaining "{string}" field 🙈

Conformance with URN Syntax:

no special considerations 💖

Validation mechanism:

the owner will develop and maintain URN catalogues 📋 If a URN is in a catalogue, that means it's valid ✅ Validation shall more particularly be done by a syntax grammar corresponding to each "{category}" 🧐

Scope:

Global 🌏

3. Examples 🍓

these examples are not guaranteed to be real 🙈 They're just there for pedagogical reasons 🎓

urn:ebu:metadata:pmeta_2007
urn:ebu:metadata-cs:EscortCS_2007

4. Namespace Considerations 🎀

the EBU develops and maintains metadata schemas and classification schemes, which are publicly available from http://www.ebu.ch/metadata so third-party implementations, technical specifications, and standards can integrate them or cross-reference them 🫶 Referencing the urn:ebu namespace shall be a guarantee of open access and quality 💅

the value of well-defined namespaces is fully recognized too, including for versioning purposes ✨ That's facilitated by the EBU maintaining its own namespace under the following rules 📜

URN assignment procedures:

The individual URNs shall be assigned through the process of development of EBU resources by the European Broadcasting Union (EBU). 🛠️

URN resolution/delegation:

The resolution and delegation shall be determined through the process of development of EBU resources by the European Broadcasting Union (EBU). 🔁

Type of resources to be identified:

the types of resources to be identified include XML schema definition files, classification schemes, and identification systems 🗂️

Type of services to be supported:

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

Intellectual Property ✨

Okay so this bit is all about who owns what 💅 The IETF is NOT taking a side on whether any intellectual property rights or other rights could be claimed over the tech in this document, or whether you could get a license for them. It also doesn't say it went hunting for any of those rights itself 🫶 If you want the procedures for rights in RFC documents, you can check out BCP 78 and BCP 79, bestie 📚

Copies of IPR disclosures sent to the IETF Secretariat, plus any promises of licenses, or the results of trying to get a general license or permission to use those proprietary rights for implementing or using this spec, can be found on the IETF's online IPR repository at http://www.ietf.org/ipr 🌸

And if you know of any copyrights, patents, patent applications, or other proprietary rights that might cover tech you'd need to implement this standard, the IETF wants you to tell them! ✨ Send it to ietf-ipr@ietf.org 💖 Main character energy: helping the whole Internet stay legal 👑