Network Working Group M. Steidl
Request for Comments: 3937 IPTC
Category: Informational October 2004
Network Working Group M. Steidl
Request for Comments: 3937 IPTC
Category: Informational October 2004
A Uniform Resource Name (URN) Namespace for the International Press Telecommunications Council (IPTC)
国际新闻电信委员会（IPTC）的统一资源名称（URN）命名空间
Status of this Memo
本备忘录的状况
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2004).
版权所有（C）互联网协会（2004年）。
Abstract
摘要
This document describes a URN (Uniform Resource Name) namespace for identifying persistent resources published by the International Press Telecommunications Council (IPTC). These resources include XML Data Type Definition files (DTD), XML Schema, Namespaces in XML, XSL stylesheets, other XML based document and documents of other data formats like PDF documents, Microsoft Office documents and others.
本文档描述了一个URN（统一资源名称）名称空间，用于标识由国际新闻电信委员会（IPTC）发布的持久资源。这些资源包括XML数据类型定义文件（DTD）、XML模式、XML名称空间、XSL样式表、其他基于XML的文档以及其他数据格式的文档，如PDF文档、Microsoft Office文档等。
Table of Contents
目录
1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . 2
2. IANA URN Specification Template . . . . . . . . . . . . . . . 3
2.1. Namespace ID. . . . . . . . . . . . . . . . . . . . . . 3
2.2. Registration Information. . . . . . . . . . . . . . . . 3
2.3. Declaration of syntactic structure. . . . . . . . . . . 3
2.4. Relevant ancillary documentation. . . . . . . . . . . . 5
2.5. Identifier uniqueness considerations. . . . . . . . . . 5
2.6. Identifier persistence considerations . . . . . . . . . 5
2.7. Process of identifier assignment. . . . . . . . . . . . 5
2.8. Process for identifier resolution . . . . . . . . . . . 5
2.9. Rules for Lexical Equivalence . . . . . . . . . . . . . 5
2.10. Conformance with URN Syntax . . . . . . . . . . . . . . 5
2.11. Validation mechanism. . . . . . . . . . . . . . . . . . 5
2.12. Scope . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . 6
4. Namespace Considerations and Community Considerations . . . . 6
5. Security Considerations . . . . . . . . . . . . . . . . . . . 7
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
7. References. . . . . . . . . . . . . . . . . . . . . . . . . . 7
7.1. Normative References. . . . . . . . . . . . . . . . . . 7
7.2. Informative References. . . . . . . . . . . . . . . . . 7
Author's Address. . . . . . . . . . . . . . . . . . . . . . . . . 8
Full Copyright Statement. . . . . . . . . . . . . . . . . . . . . 9
1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . 2
2. IANA URN Specification Template . . . . . . . . . . . . . . . 3
2.1. Namespace ID. . . . . . . . . . . . . . . . . . . . . . 3
2.2. Registration Information. . . . . . . . . . . . . . . . 3
2.3. Declaration of syntactic structure. . . . . . . . . . . 3
2.4. Relevant ancillary documentation. . . . . . . . . . . . 5
2.5. Identifier uniqueness considerations. . . . . . . . . . 5
2.6. Identifier persistence considerations . . . . . . . . . 5
2.7. Process of identifier assignment. . . . . . . . . . . . 5
2.8. Process for identifier resolution . . . . . . . . . . . 5
2.9. Rules for Lexical Equivalence . . . . . . . . . . . . . 5
2.10. Conformance with URN Syntax . . . . . . . . . . . . . . 5
2.11. Validation mechanism. . . . . . . . . . . . . . . . . . 5
2.12. Scope . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . 6
4. Namespace Considerations and Community Considerations . . . . 6
5. Security Considerations . . . . . . . . . . . . . . . . . . . 7
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
7. References. . . . . . . . . . . . . . . . . . . . . . . . . . 7
7.1. Normative References. . . . . . . . . . . . . . . . . . 7
7.2. Informative References. . . . . . . . . . . . . . . . . 7
Author's Address. . . . . . . . . . . . . . . . . . . . . . . . . 8
Full Copyright Statement. . . . . . . . . . . . . . . . . . . . . 9
The International Press Telecommunications Council (IPTC) is a non-profit consortium of the world's major news agencies and news industry vendors. It develops and maintains technical standards for the news business that are used by virtually every major news organization in the world. IPTC was established in 1965.
国际新闻电信理事会（IPTC）是一个由世界主要新闻机构和新闻行业供应商组成的非盈利财团。它为新闻业务制定和维护技术标准，世界上几乎所有主要新闻机构都在使用这些标准。IPTC成立于1965年。
Since the 1990's IPTC's standardization work is based on open standards like first SGML, then the XML [W3CXML] family of standards, MIME, Unicode, and so on.
自20世纪90年代以来，IPTC的标准化工作是基于开放标准的，比如首先是SGML，然后是XML[W3CXML]系列标准、MIME、Unicode等等。
As some of these standards require identification of resources IPTC was looking for a technology for globally unique, persistent and location-independent identifiers and decided to implement URNs as described in "URN Syntax" [RFC2141] for this reason.
由于其中一些标准要求识别资源，IPTC正在寻找一种用于全球唯一、持久和位置独立标识符的技术，因此决定按照“URN语法”[RFC2141]中的描述实现URN。
This namespace specification is for a formal namespace.
此名称空间规范适用于正式名称空间。
"iptc" requested.
请求“iptc”。
Registration Version Number: 1 Registration Date: 2003-11-11
注册版本号：1注册日期：2003-11-11
Declared registrant of the namespace:
已声明命名空间的注册人：
Registering organization: International Press Telecommunications Council IPTC Royal Albert House Sheet Street Windsor, Berkshire SL4 1BE www.iptc.org
注册机构：国际新闻电信委员会IPTC皇家艾伯特大厦Sheet Street伯克希尔温莎SL4 1BE www.IPTC.org
Designated contact person: Michael Steidl Managing Director mdirector@iptc.org
指定联系人：Michael Steidl常务董事mdirector@iptc.org
All URNs assigned by IPTC will have a Namespace Specific String (NSS) of the following hierarchical structure:
IPTC分配的所有URN将具有以下层次结构的命名空间特定字符串（NSS）：
At the top of the hierarchy are three branches: - "std" - "std-draft" - "workdoc"
在层次结构的顶部有三个分支：-“std”-“std草稿”-“workdoc”
The "std" branch hierarchy:
“std”分支层次结构：
The "std" branch URNs will be assigned to IPTC resources used for specifying and explaining any aspect of an IPTC standard.
“std”分支URN将分配给IPTC资源，用于指定和解释IPTC标准的任何方面。
The NSS in the "std" branch will have this general structure:
“std”分支机构中的NSS将具有以下一般结构：
urn:iptc:std:{std-name}:{std-version}:{res-group}
{:res-name}?{:res-version}?
urn:iptc:std:{std-name}:{std-version}:{res-group}
{:res-name}?{:res-version}?
where "std-name" is a unique identifier for an IPTC standard. "std-version" reflects the version of this standard. The value 'current' will be assigned to point at resources of the current version of a standard. "res-group": this field will take only three values: "spec" for all resources specifying a standard, "doc" for all resources used for additional documentation of and to support the use of a standard. "xmlns" for defining an XML namespace [W3CXMLNS]. "res-name" is an identifier for a tangible resource; the name should describe the content or the use of the resource. Since not all resources are tangible this value is optional. "res-version" reflects the version of this resource as long as it takes a physical format - like e.g., a file. Since not all resources are of a physical kind this value is optional.
其中，“std名称”是IPTC标准的唯一标识符。“标准版本”反映了本标准的版本。“当前”值将分配给标准当前版本的资源点。“res group”：此字段仅取三个值：“spec”表示指定标准的所有资源，“doc”表示用于标准附加文档和支持标准使用的所有资源。“xmlns”用于定义XML命名空间[W3CXMLNS]。“资源名称”是有形资源的标识符；名称应描述资源的内容或使用。由于并非所有资源都是有形的，因此该值是可选的。“res version”反映此资源的版本，只要它采用物理格式，例如文件。由于并非所有资源都是物理类型，因此此值是可选的。
The "std-draft" branch hierarchy:
“标准草案”分支层次结构：
The "std-draft" branch URNs will be assigned to IPTC resources used for specifying and explaining any aspect of an IPTC standard while being in draft status, that is at a time when the resource is not formally approved by the IPTC Standards body.
“std草稿”分支URN将分配给IPTC资源，用于在处于草稿状态时（即资源未经IPTC标准机构正式批准时）指定和解释IPTC标准的任何方面。
The NSS in the "std" branch will have this general structure:
“std”分支机构中的NSS将具有以下一般结构：
urn:iptc:std-draft:{std-name}:{std-version}:{res-group}
{:res-name}?{:res-version}?
urn:iptc:std-draft:{std-name}:{std-version}:{res-group}
{:res-name}?{:res-version}?
The substructure of "urn:iptc:std-draft" is identical to that of "urn:iptc:std", find all explanations there.
“urn:iptc:std草稿”的子结构与“urn:iptc:std草稿”的子结构相同，请在此处找到所有解释。
The "workdoc" branch hierarchy:
“workdoc”分支层次结构：
The "workdoc" branch URNs will be assigned to IPTC resources not directly related to IPTC standards but to the work of IPTC.
“workdoc”分支URN将分配给IPTC资源，这些资源与IPTC标准无关，但与IPTC的工作相关。
The NSS in the "doc" branch will have this general structure:
“doc”分支机构中的NSS将具有以下一般结构：
urn:iptc:workdoc:{group-id}:{doc-id}:{doc-version}{:doc-descr}?
urn:iptc:workdoc:{group-id}:{doc-id}:{doc-version}{:doc-descr}?
where "group-id" is a unique identifier for working groups and working areas of IPTC and constitutes a document group. "doc-id" is a unique identifier for a document within a document group.
其中，“组id”是IPTC工作组和工作区域的唯一标识符，构成文件组。“文档id”是文档组中文档的唯一标识符。
"doc-version" reflects the version of this work document. "doc-descr" is an optional concise description of the document content.
“文档版本”反映了本工作文档的版本。“文档描述”是对文档内容的可选简明描述。
None
没有一个
Identifier uniqueness will be enforced by the Managing Director of IPTC who will assign unique identifiers to all resources identified by a URN.
标识符唯一性将由IPTC总经理执行，他将为URN标识的所有资源分配唯一标识符。
IPTC is committed to maintaining the accessibility and persistence of all resources that are identified by an IPTC URN.
IPTC致力于维护IPTC URN标识的所有资源的可访问性和持久性。
Assignment is limited to the owner of this namespace and its authorities.
分配仅限于此命名空间的所有者及其权限。
IPTC will develop an appropriate mechanism that maps all assigned URNs to Uniform Resource Locators (URL), specifically to enable web based resolution of URNs.
IPTC将开发一种适当的机制，将所有分配的URN映射到统一资源定位器（URL），特别是支持基于web的URN解析。
No special considerations, the rules for lexical equivalence of RFC 2141 apply.
没有特殊考虑，RFC 2141的词汇等效规则适用。
No special considerations.
没有特别考虑。
None specified. IPTC will develop a mechanism for resolving URNs to URLs (see 2.8), this mechanism will also show whether a URN is valid.
没有具体说明。IPTC将开发一种将URN解析为URL的机制（见2.8），该机制还将显示URN是否有效。
Global.
全球的
The following examples are representative for IPTC URNs, but may not refer to actual resources.
以下示例代表IPTC URN，但可能未提及实际资源。
urn:iptc:std:NewsML:1.1:spec:DTD:1
DTD version 1 to specify the IPTC standard "NewsML", version 1.1
urn:iptc:std:NewsML:1.1:spec:DTD:1
DTD version 1 to specify the IPTC standard "NewsML", version 1.1
urn:iptc:std-draft:NITF:3.5:spec:xml-schema:2
Second draft XML Schema for the IPTC standard "NITF", version 3.5
urn:iptc:std-draft:NITF:3.5:spec:xml-schema:2
Second draft XML Schema for the IPTC standard "NITF", version 3.5
urn:iptc:std:SportsML:1.0:xmlns URN to identify an XML namespace for the IPTC standard "SportsML", version 1.0. No "res-name" and "res-version" since an XML namespace is of no physical format.
urn:iptc:std:SportsML:1.0:xmlns urn用于标识iptc标准“SportsML”1.0版的XML命名空间。没有“res name”和“res version”，因为XML命名空间没有物理格式。
urn:iptc:std:NewsML:1.1:doc:news-agency-guidelines:1.2 Supporting document named "news-agency-guidelines", version 1, revision 2, based on the IPTC standard "NewsML" version 1.1.
urn:iptc:std:NewsML:1.1:doc:news agency guidelines:1.2名为“新闻机构指南”的支持文件，第1版，第2版，基于iptc标准“NewsML”第1.1版。
urn:iptc:workdoc:NMA:0315:1:srs-terms
Work document of IPTC's News Metadata Working Party (NMA), version
1, holding terms of the Subject Reference System
urn:iptc:workdoc:NMA:0315:1:srs-terms
Work document of IPTC's News Metadata Working Party (NMA), version
1, holding terms of the Subject Reference System
The IPTC acknowledged already the use of URNs during the development of its XML based standard "NewsML". This standard implements the use of URNs as unique identifiers for news items as described in "URN Namespace for NewsML resources" [RFC3085].
IPTC在其基于XML的标准“NewsML”的开发过程中已经承认了URN的使用。本标准实现了将URN用作新闻项的唯一标识符，如“新闻ML资源的URN命名空间”[RFC3085]中所述。
While developing additional XML based standards as siblings to NewsML, IPTC soon got aware that URNs have to be assigned to resources that fall beyond the scope of the NewsML namespace. For this reason IPTC developed a new and very general hierarchical namespace structure to cover the needs of the currently developed standards as well as future standards and to be able to assign URNs to resources emanating from them.
在开发其他基于XML的标准作为NewsML的同级标准时，IPTC很快意识到必须将URN分配给超出NewsML命名空间范围的资源。因此，IPTC开发了一种新的非常通用的分层命名空间结构，以满足当前开发的标准以及未来标准的需要，并能够将URN分配给源于这些标准的资源。
In addition to resources relating directly to its standards, IPTC also produces and publishes other documents relevant to the news business. As those resources are used by many organizations outside the IPTC membership and therefore could not be considered as internal documents IPTC decided to add a branch to the URN hierarchy to be assigned to these resources.
除了与其标准直接相关的资源外，IPTC还制作和发布与新闻业务相关的其他文档。由于这些资源被IPTC成员之外的许多组织使用，因此不能被视为内部文件，IPTC决定在URN层次结构中添加一个分支以分配给这些资源。
IPTC maintains global activities and its standards as well as resources based on them are used world wide. Since one focus of the activities of IPTC is on global exchange of news any system for unique identification of resources has to be considered under global aspects.
IPTC维持全球活动，其标准以及基于这些活动的资源在全球范围内使用。由于IPTC活动的一个重点是全球新闻交流，因此必须在全球层面下考虑任何资源独特识别系统。
For this reason IPTC considers the introduction of a URN namespace for its resources as proper action to maintain globally unique, persistent and location-independent identifiers based on open standards.
因此，IPTC认为为其资源引入URN名称空间是基于开放标准维护全局唯一、持久和位置独立标识符的适当行动。
There are no additional security considerations other than those normally associated with the use and resolution of URNs in general.
除了通常与使用和解决骨灰盒相关的安全注意事项外，没有其他安全注意事项。
This document includes a URN Namespace registration that conforms to the "Uniform Resources Names (URN) Namespace Definition Mechanism" [RFC3406] and has been entered into the IANA registry for URN NIDs.
本文档包括符合“统一资源名称（URN）命名空间定义机制”[RFC3406]的URN命名空间注册，并已输入URN NID的IANA注册表。
[RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997.
[RFC2141]Moats，R.，“瓮语法”，RFC 21411997年5月。
[RFC3406] Daigle, L., van Gulik, D., Iannella, R. and P. Faltstrom, "Uniform Resource Names (URN) Namespace Definition Mechanisms", BCP 66, RFC 3406, October 2002.
[RFC3406]Daigle，L.，van Gulik，D.，Iannella，R.和P.Faltstrom，“统一资源名称（URN）命名空间定义机制”，BCP 66，RFC 3406，2002年10月。
[W3CXML] W3C, XML WG, "Extensible Markup Language (XML) 1.0" (Third Edition), February 2004, <http://www.w3.org/TR/REC-xml>.
[W3CXML]W3C，XML工作组，“可扩展标记语言（XML）1.0”（第三版），2004年2月<http://www.w3.org/TR/REC-xml>.
[W3CXMLNS] W3C, Namespaces WG, "Namespaces in XML", January 1999, <http://www.w3.org/TR/REC-xml-names>.
[W3CXMLNS]W3C，名称空间工作组，“XML中的名称空间”，1999年1月<http://www.w3.org/TR/REC-xml-names>.
[RFC3085] Coates, A., Allen, D. and D. Rivers-Moore, "URN Namespace for NewsML Resources", RFC 3085, March 2001.
[RFC3085]Coates，A.，Allen，D.和D.Rivers Moore，“新闻ML资源的URN名称空间”，RFC 30852001年3月。
Author's Address
作者地址
Michael Steidl IPTC (International Press Telecommunications Council) Royal Albert House Sheet Street Windsor SL4 1BE United Kingdom
Michael Steidl IPTC（国际新闻电信委员会）英国温莎皇家艾伯特大厦床单街SL4 1BE
Phone: +44 (1753) 705 051
EMail: mdirector@iptc.org
Phone: +44 (1753) 705 051
EMail: mdirector@iptc.org
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2004).
版权所有（C）互联网协会（2004年）。
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and 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 THE USE OF 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 regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the IETF's procedures with respect to rights in IETF Documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关IETF文件中权利的IETF程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为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 that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。