idnits 2.17.1 draft-evain-ebu-urn-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 18. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 332. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 339. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 345. ** The document seems to lack an RFC 3978 Section 5.5 (updated by RFC 4748) Disclaimer -- however, there's a paragraph with a matching beginning. Boilerplate error? Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust Copyright Line does not match the current year == Line 200 has weird spacing: '...litated throu...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (February 13, 2008) is 5917 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 2141 (Obsoleted by RFC 8141) Summary: 3 errors (**), 0 flaws (~~), 2 warnings (==), 6 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft J-P. Evain 3 EBU URN Scheme 4 Category: Informational EBU 5 Expires August 2008 February 13, 2008 7 A Uniform Resource Name (URN) Namespace for 8 the European Broadcasting Union (EBU) 9 11 Status of this Memo 13 Distribution of this memo is unlimited. 15 By submitting this Internet-Draft, each author represents that any 16 applicable patent or other IPR claims of which he or she is aware 17 have been or will be disclosed, and any of which he or she becomes 18 aware will be disclosed, in accordance with Section 6 of BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that 22 other groups may also distribute working documents as Internet- 23 Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/1id-abstracts.html 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html. 36 Abstract 38 This document describes a Uniform Resource Name (URN) namespace for 39 the European Broadcasting Union (EBU) for naming persistent 40 resources defined within EBU technical documentation and Internet 41 resources. Example resources include technical documents and 42 specifications, eXtensible Markup Language(XML) Schemas, 43 classification schemes, XML Document Type Definitions (DTDs), 44 namespaces, style sheets, media assets, and other types of resources 45 produced or managed by the EBU. 47 Table of Contents 49 1. Introduction ....................................................2 50 2. Specification Template ..........................................2 51 3. Examples ........................................................6 52 4. Namespace Considerations ........................................6 53 5. Community Considerations ........................................7 54 6. Security Considerations .........................................7 55 7. IANA Considerations .............................................8 56 8. References ......................................................8 57 9. Copyright Notice.................................................9 58 10. Intellectual Property...........................................10 60 1. Introduction 62 The European Broadcasting Union (EBU) is the largest non-for profit 63 professional association of broadcasters worldwide established 64 since 1950. The Union has more than 70 active members in 55 65 countries in Europe, North Africa and the Middle East, and more 66 than 40 associate members in 25 countries further afield. The 67 EBU negotiates broadcasting rights for major sport events, operates 68 the Eurovision and Euroradio networks, organises programme exchanges 69 and co-productions, and provides other operational, and legal 70 support. It provides technical advice to its members and favours the 71 adoption of standardised solutions in broadcast systems from content 72 ingest to end-user delivery. EBU activities cover traditional 73 broadcast and new delivery medias such as the Internet for which a 74 growing number or resources are being developped. 76 The EBU would like to assign unique, permanent, location-independent 77 names based on URNs for some resources it produces or manages. 79 This namespace specification is for a formal namespace. 81 2. Specification Template 83 Namespace ID: 85 "ebu" 87 Registration Information: 89 Version: 1 90 Date: 2007-02-20 92 Declared registrant of the namespace: 94 Name: Jean-Pierre Evain 95 Title: Senior Engineer 96 Affiliation: European Broadcasting Union (EBU) 97 Address: Ancienne Route 17a 98 CH-1218 Geneva 99 SWITZERLAND 100 Phone: +41 22 717 2734 101 Email: evain@ebu.ch 103 Declaration of structure: 105 URNs assigned by the EBU will have the following hierarchical 106 structure based on the organisational structure of the EBU 107 resources: 109 urn:ebu:{category}:{string} 111 where "{category}" is a US-ASCII string that conforms to the 112 syntax of the , and "{string}" is a US-ASCII string that 113 conforms to the syntax of the ([RFC2141]). 115 The individual URNs will be assigned by the EBU through the 116 development process of EBU resources. 118 Relevant ancillary documentation: 120 More information on the EBU and relevant technical activities can 121 be found at ([http://www.ebu.ch/metadata]). 123 Identifier and namespace uniqueness considerations: 125 The EBU understand the vital necessity for uniqueness and will 126 establish unique identifiers and namespaces under the authority of 127 its metadata expert group under the auspices of the EBU Production 128 Management Committee to prevent re-assignation of existing 129 identifiers and namespaces. 131 Identifier and namespace persistence considerations: 133 The European Broadcasting Union (EBU) shall ensure the 134 accessibility and persistence of all resources that are 135 officially assigned URNs by the organization, in particular upon 136 suitable delegation at the level of "{category}"s, and persistence 137 of category assignment. 139 Process of identifier and namespace assignment: 141 The assignment of identifiers and namespaces is fully controlled 142 and managed by the European Broadcasting Union (EBU). 144 Process of identifier resolution: 146 The owner will develop and maintain "URN catalogues" that map all 147 assigned URNs to Uniform Resource Locators (URLs) specifically to 148 enable Web-based resolution of named resources. In the future an 149 interactive online resolution system may be developed to automate 150 this process. 152 The owner will authorize additional resolution services as 153 appropriate. 155 Rules for Lexical Equivalence: 157 The "{category}" is case-insensitive. Thus, the portion of the 158 URN: 160 urn:ebu:{category}: 162 is case-insensitive for matches up to {category}. The remainder 163 of the identifier shall be considered case-sensitive; hence, URNs 164 are only lexically equivalent if they are also lexically 165 identical in the remaining "{string}" field. 167 Conformance with URN Syntax: 169 No special considerations. 171 Validation mechanism: 173 The owner will develop and maintain URN 174 catalogues. The presence of a URN in a catalogue indicates that 175 it is valid. Validation shall more particularly be done by a 176 syntax grammar corresponding to each "{category}". 178 Scope: 180 Global 182 3. Examples 184 The following examples are not guaranteed to be real. They are 185 presented for pedagogical reasons only. 187 urn:ebu:metadata:pmeta_2007 188 urn:ebu:metadata-cs:EscortCS_2007 190 4. Namespace Considerations 192 The EBU develops and maintains metadata schemas and classification 193 schemes, which are made publicly available from 194 http://www.ebu.ch/metadata for integration or cross reference in 195 third party implementations, technical specifications and standards. 196 Reference to the urn:ebu namespace shall be a guarantee of open 197 access and quality. 199 Furthermore, the value of well defined namespaces in fully recognised 200 including for versioning purposes, which will be facilitated through 201 the EBU maintenance of its own namespace dictated by the following 202 rules. 204 URN assignment procedures: 206 The individual URNs shall be assigned through the process of 207 development of EBU resources by the European Broadcasting Union 208 (EBU). 210 URN resolution/delegation: 212 The resolution and delegation shall be determined through the 213 process of development of EBU resources by the European 214 Broadcasting Union (EBU). 216 Type of resources to be identified: 218 Types of resources to be identified include XML schema definition 219 files, classification schemes and identification systems. 221 Type of services to be supported: 223 Types of services supported include controlled term lookup in 224 classification schemes, resolution of ids in identification 225 systems. 227 5. Community Considerations 229 The EBU traditionally addresses the broadcasting community but its 230 resources are made available to all interested parties. 232 Communities involved in offering content over new IP-based delivery 233 medias such as via the Internet and mobile communication networks, or 234 using IP infrastructures and Service Oriented Architectures are 235 welcome to use EBU resources. Metadata and content identifiers, for 236 which the EBU mainly needs the urn:ebu namespace plays a key role in 237 content search and retrieval, end-to-end from content commissoning to 238 user delivery. 240 Web services, search engines, the semantic web are among the core 241 technologies that the EBU is now exploiting to access users in a 242 multi-media multi-platform connected world. 244 Potential beneficiary developing communities include: 246 a) Implementers and users of EBU resources. 248 Resources that comply with EBU specifications 249 (including schemas, instance documents that comply with 250 EBU schemas, and the EBU default Classification Schemes) 251 may, by means of the registered namespace, become exposed to 252 the general Internet and gain from the interoperability 253 benefits of the Internet at large. 255 b) Implementers of other specifications that incorporate part or 256 all of available EBU resources. 258 URNs used to identify EBU resources may be used to enable 259 their inclusion in, and enhancement of, other specifications 260 while maintaining, to a certain degree, interoperability with 261 the EBU (see a) above). 263 c) Implementers of other semantically related specifications that 264 do not directly incorporate part or all of EBU resources. 266 URNs used to identify EBU resources, such as identifiers of 267 terms within default Classification Schemes, may enable 268 interoperation with other semantically determined 269 specifications (including present and future metadata/resource 270 description and ontology specifications) of relevance to EBU 271 implementation communities (see a) and b) above). 273 6. Security Considerations 275 The portion of the URN, urn:ebu:{category}:, is case-insensitive for 276 matches up to {category}. 278 Otherwise, there are no additional security considerations other than 279 those normally associated with the use and resolution of URNs in 280 general. 282 7. IANA Considerations 284 The IANA has registered formal URN namespace 'ebu', to the EBU within 285 the IANA registry of URN NIDs, according to the registration template 286 in Section 2. 288 8. References 290 8.1. Normative References 292 [RFC2141] Moats, R., "URN Syntax", May 1997. 294 Authors' Addresses 296 Jean-Pierre Evain 297 European Broadcasting Union 298 Technical Department 299 L'ancienne route 17A 300 CH-1218 Grand-Saconnex (GE) 301 SWITZERLAND 302 Tel: +41 22 717 2734 303 Fax: +41 22 74 74 734 304 Email: evain@ebu.ch 306 9. Full Copyright Statement 308 Copyright (C) The IETF Trust (2008). 310 This document is subject to the rights, licenses and restrictions 311 contained in BCP 78, and except as set forth therein, the authors 312 retain all their rights. 314 This document and the information contained herein are provided on an 315 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 316 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST, 317 AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, 318 EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT 319 THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY 320 IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR 321 PURPOSE. 323 11. Intellectual Property 325 The IETF takes no position regarding the validity or scope of any 326 Intellectual Property Rights or other rights that might be claimed to 327 pertain to the implementation or use of the technology described in 328 this document or the extent to which any license under such rights 329 might or might not be available; nor does it represent that it has 330 made any independent effort to identify any such rights. Information 331 on the procedures with respect to rights in RFC documents can be 332 found in BCP 78 and BCP 79. 334 Copies of IPR disclosures made to the IETF Secretariat and any 335 assurances of licenses to be made available, or the result of an 336 attempt made to obtain a general license or permission for the use of 337 such proprietary rights by implementers or users of this 338 specification can be obtained from the IETF on-line IPR repository at 339 http://www.ietf.org/ipr. 341 The IETF invites any interested party to bring to its attention any 342 copyrights, patents or patent applications, or other proprietary 343 rights that may cover technology that may be required to implement 344 this standard. Please address the information to the IETF at 345 ietf-ipr@ietf.org.