idnits 2.17.1 draft-steidl-iptc-urn-00.txt: -(140): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == There are 4 instances of lines with non-ascii characters in the document. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Authors' Addresses Section. ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. == There are 1 instance of lines with non-RFC2606-compliant FQDNs in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 232 has weird spacing: '... Schema for t...' -- 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 (November 2003) is 7462 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFC 2141' is mentioned on line 75, but not defined ** Obsolete undefined reference: RFC 2141 (Obsoleted by RFC 8141) == Unused Reference: 'RFC2141' is defined on line 296, but no explicit reference was found in the text == Unused Reference: 'W3CXML' is defined on line 301, but no explicit reference was found in the text == Unused Reference: 'W3CXMLNS' is defined on line 304, but no explicit reference was found in the text == Unused Reference: 'RFC2483' is defined on line 307, but no explicit reference was found in the text == Unused Reference: 'RFC3085' is defined on line 310, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2141 (Obsoleted by RFC 8141) ** Obsolete normative reference: RFC 3406 (Obsoleted by RFC 8141) -- Possible downref: Non-RFC (?) normative reference: ref. 'W3CXML' -- Possible downref: Non-RFC (?) normative reference: ref. 'W3CXMLNS' ** Downref: Normative reference to an Experimental RFC: RFC 2483 ** Downref: Normative reference to an Informational RFC: RFC 3085 Summary: 12 errors (**), 0 flaws (~~), 10 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 URN Namespace for IPTC November 2003 4 Network Working Group 5 Internet Draft M. Steidl 6 Document: draft-steidl-iptc-urn-00.txt IPTC 7 Expires: May 2004 November 2003 9 A Uniform Resource Name(URN)Namespace for 10 the International Press Telecommunications Council (IPTC) 12 Status of this Memo 13 This document is an Internet-Draft and is in full conformance with 14 all provisions of Section 10 of RFC2026 [i]. 15 Internet-Drafts are working documents of the Internet Engineering 16 Task Force (IETF), its areas, and its working groups. Note that 17 other groups may also distribute working documents as Internet- 18 Drafts. 19 Internet-Drafts are draft documents valid for a maximum of six months 20 and may be updated, replaced, or obsoleted by other documents at any 21 time. It is inappropriate to use Internet-Drafts as reference 22 material or to cite them other than as �work in progress.� 23 The list of current Internet-Drafts can be accessed at 24 http://www.ietf.org/ietf/1id-abstracts.txt 25 The list of Internet-Draft Shadow Directories can be accessed at 26 http://www.ietf.org/shadow.html. 28 Abstract 29 This document describes a URN (Uniform Resource Name) namespace for 30 identifying persistent resources published by the International Press 31 Telecommunications Council, IPTC. These resources include XML Data 32 Type Definition files (DTD), XML Schema, Namespaces in XML, XSL 33 stylesheets, other XML based document and documents of other data 34 formats like PDF documents, Microsoft Office documents and others. 36 Table of Contents 37 1. Introduction...................................................2 38 2. IANA URN Specification Template................................2 39 2.1 Namespace ID...............................................2 40 2.2 Registration Information...................................2 41 2.3 Declaration of syntactic structure.........................3 42 2.4 Relevant ancillary documentation...........................4 43 2.5 Identifier uniqueness considerations.......................4 44 2.6 Identifier persistence considerations......................4 45 2.7 Process of identifier assignment...........................5 46 2.8 Process for identifier resolution..........................5 47 2.9 Rules for Lexical Equivalence..............................5 48 2.10 Conformance with URN Syntax...............................5 49 URN Namespace for IPTC November 2003 51 2.11 Validation mechanism......................................5 52 2.12 Scope.....................................................5 53 3. Examples.......................................................5 54 4. Namespace Considerations and Community Considerations..........6 55 5. Security Considerations........................................7 56 6. IANA Considerations............................................7 57 References........................................................7 58 Author�s Addresses................................................7 60 1. Introduction 62 The International Press Telecommunications Council (IPTC) is a non- 63 profit consortium of the world's major news agencies and news 64 industry vendors. It develops and maintains technical standards for 65 the news business that are used by virtually every major news 66 organization in the world. IPTC was established in 1965. 68 Since the 1990's IPTC's standardization work is based on open 69 standards like first SGML, then the XML family of standards, MIME, 70 Unicode etc. 72 As some of these standards require identification of resources IPTC 73 was looking for a technology for globally unique, persistent and 74 location-independent identifiers and decided to implement URNs as 75 described in "URN Syntax" [RFC 2141] for this reason. 77 This namespace specification is for a formal namespace. 79 2. IANA URN Specification Template 81 2.1 Namespace ID 83 "iptc" requested. 85 2.2 Registration Information 87 Registration Version Number: 1 88 Registration Date: 2003-11-11 90 Declared registrant of the namespace: 92 Registering organization: 93 International Press Telecommunications Council IPTC 94 Royal Albert House 95 Sheet Street 96 Windsor, Berkshire SL4 1BE 97 URN Namespace for IPTC November 2003 99 www.iptc.org 101 Designated contact person: 102 Michael Steidl 103 Managing Director 104 mdirector@iptc.org 106 2.3 Declaration of syntactic structure 108 All URNs assigned by IPTC will have a Namespace Specific String (NSS) 109 of the following hierarchical structure: 111 At the top of the hierarchy are three branches: 112 - "std" 113 - "std-draft" 114 - "workdoc" 116 The "std" branch hierarchy: 118 The "std" branch URNs will be assigned to IPTC resources used for 119 specifying and explaining any aspect of an IPTC standard. 121 The NSS in the "std" branch will have this general structure: 123 urn:iptc:std:{std-name}:{std-version}:{res-group} 124 {:res-name}?{:res-version}? 126 where 127 "std-name" is a unique identifier for an IPTC standard. 128 "std-version" reflects the version of this standard. The value 129 'current' will be assigned to point at resources of the current 130 version of a standard. 131 "res-group": this field will take only three values: 132 "spec" for all resources specifying a standard, 133 "doc" for all resources used for additional documentation of 134 and to support the use of a standard. 135 "xmlns" for defining an XML namespace. 136 "res-name" is an identifier for a tangible resource; the name 137 should describe the content or the use of the resource. Since not 138 all resources are tangible this value is optional. 139 "res-version" reflects the version of this resource as long as it 140 takes a physical format � like e.g. a file. Since not all resources 141 are of a physical kind this value is optional. 143 The "std-draft" branch hierarchy: 145 URN Namespace for IPTC November 2003 147 The "std-draft" branch URNs will be assigned to IPTC resources used 148 for specifying and explaining any aspect of an IPTC standard while 149 being in draft status, that is at a time when the resource is not 150 formally approved by the IPTC Standards body. 152 The NSS in the "std" branch will have this general structure: 154 urn:iptc:std-draft:{std-name}:{std-version}:{res-group} 155 {:res-name}?{:res-version}? 157 The substructure of "urn:iptc:std-draft" is identical to that of 158 "urn:iptc:std", find all explanations there. 160 The "workdoc" branch hierarchy: 162 The "workdoc" branch URNs will be assigned to IPTC resources not 163 directly related to IPTC standards but to the work of IPTC. 165 The NSS in the "doc" branch will have this general structure: 167 urn:iptc:workdoc:{group-id}:{doc-id}:{doc-version}{:doc-descr}? 169 where 170 "group-id" is a unique identifier for working groups and working 171 areas of IPTC and constitutes a document group. 172 "doc-id" is a unique identifier for a document within a document 173 group. 174 "doc-version" reflects the version of this work document. 175 "doc-descr" is an optional concise description of the document 176 content. 178 2.4 Relevant ancillary documentation 180 None 182 2.5 Identifier uniqueness considerations 184 Identifier uniqueness will be enforced by the Managing Director of 185 IPTC who will assign unique identifiers to all resources identified 186 by a URN. 188 2.6 Identifier persistence considerations 189 URN Namespace for IPTC November 2003 191 IPTC is committed to maintaining the accessibility and persistence of 192 all resources that are identified by an IPTC URN. 194 2.7 Process of identifier assignment 196 Assignment is limited to the owner of this namespace and its 197 authorities. 199 2.8 Process for identifier resolution 201 IPTC will develop an appropriate mechanism that maps all assigned 202 URNs to Uniform Resource Locators (URL), specifically to enable web 203 based resolution of URNs. 205 2.9 Rules for Lexical Equivalence 207 No special considerations, the rules for lexical equivalence 208 of RFC 2141 apply. 210 2.10 Conformance with URN Syntax 212 No special considerations. 214 2.11 Validation mechanism 216 None specified. IPTC will develop a mechanism for resolving URNs to 217 URLs (see 2.8), this mechanism will also show whether a URN is valid. 219 2.12 Scope 221 Global. 223 3. Examples 225 The following examples are representative for IPTC URNs, but may not 226 refer to actual resources. 228 urn:iptc:std:NewsML:1.1:spec:DTD:1 229 DTD version 1 to specify the IPTC standard "NewsML", version 1.1 231 urn:iptc:std-draft:NITF:3.5:spec:xml-schema:2 232 Second draft XML Schema for the IPTC standard "NITF", version 3.5 233 URN Namespace for IPTC November 2003 235 urn:iptc:std:SportsML:1.0:xmlns 236 URN to identify an XML namespace for the IPTC standard "SportsML", 237 version 1.0. No "res-name" and "res-version" since an XML namespace 238 is of no physical format. 240 urn:iptc:std:NewsML:1.1:doc:news-agency-guidelines:1.2 241 Supporting document named "news-agency-guidelines", version 1, 242 revision 2, based on the IPTC standard "NewsML" version 1.1. 244 urn:iptc:workdoc:NMA:0315:1:srs-terms 245 Work document of IPTC's News Metadata Working Party (NMA), version 246 1, holding terms of the Subject Reference System 248 4. Namespace Considerations and Community Considerations 250 The IPTC acknowledged already the use of URNs during the development 251 of its XML based standard "NewsML". This standard implements the use 252 of URNs as unique identifiers for news items as described in "URN 253 Namespace for NewsML resources"[RFC3085]. 255 While developing additional XML based standards as siblings to 256 NewsML, IPTC soon got aware that URNs have to be assigned to 257 resources that fall beyond the scope of the NewsML namespace. For 258 this reason IPTC developed a new and very general hierarchical 259 namespace structure to cover the needs of the currently developed 260 standards as well as future standards and to be able to assign URNs 261 to resources emanating from them. 263 In addition to resources relating directly to its standards, IPTC 264 also produces and publishes other documents relevant to the news 265 business. As those resources are used by many organizations outside 266 the IPTC membership and therefore could not be considered as internal 267 documents IPTC decided to add a branch to the URN hierarchy to be 268 assigned to these resources. 270 IPTC maintains global activities and its standards as well as 271 resources based on them are used world wide. Since one focus of the 272 activities of IPTC is on global exchange of news any system for 273 unique identification of resources has to be considered under global 274 aspects. 276 For this reason IPTC considers the introduction of a URN namespace 277 for its resources as proper action to maintain globally unique, 278 persistent and location-independent identifiers based on open 279 standards. 281 URN Namespace for IPTC November 2003 283 5. Security Considerations 285 There are no additional security considerations other than those 286 normally associated with the use and resolution of URNs in general. 288 6. IANA Considerations 290 This document includes a URN Namespace registration that conforms to 291 the "Uniform Resources Names (URN) Namespace Definition Mechanism" 292 [RFC3406] and is to be entered into the IANA registry for URN NIDs. 294 References 296 [RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997. 298 [RFC3406] Daigle, L. et al., "Uniform Resource Names (URN) 299 Namespace Definition Mechanisms", RFC 3406, October 2002. 301 [W3CXML] W3C, XML WG, "Extensible Markup Language (XML) 1.0", 302 February 1998, . 304 [W3CXMLNS] W3C, Namespaces WG, "Namespaces in XML", January 1999, 305 . 307 [RFC2483] Mealling, M. and R. Daniel, "URI Resolution Services 308 Necessary for URN Resolution", RFC 2483, January 1999. 310 [RFC3085] Coates, et al., "URN Namespace for NewsML resources", 311 RFC 3085, March 2001. 313 Author�s Addresses 314 Michael Steidl 315 IPTC (International Press Telecommunications Council) 316 Royal Albert House 317 Sheet Street 318 Windsor SL4 1BE 319 United Kingdom 321 Phone: +44 (1753) 705 051 322 Email: mdirector@iptc.org