Network Working Group                                           J. Snell
Request for Comments: 4946                                     July 2007
Category: Experimental
        
Network Working Group                                           J. Snell
Request for Comments: 4946                                     July 2007
Category: Experimental
        

Atom License Extension

Atom许可证扩展

Status of This Memo

关于下段备忘

This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited.

这份备忘录为互联网社区定义了一个实验性协议。它没有规定任何类型的互联网标准。要求进行讨论并提出改进建议。本备忘录的分发不受限制。

Copyright Notice

版权公告

Copyright (C) The IETF Trust (2007).

版权所有(C)IETF信托基金(2007年)。

Abstract

摘要

This memo defines an extension to the Atom Syndication Format for describing licenses associated with Atom feeds and entries.

此备忘录定义了Atom联合格式的扩展,用于描述与Atom提要和条目关联的许可证。

Table of Contents

目录

   1. Introduction ....................................................2
      1.1. Notational Conventions .....................................2
      1.2. Terminology ................................................2
   2. The "license" Link Relation .....................................3
      2.1. Unspecified License Links ..................................3
      2.2. Comparing License Links ....................................3
      2.3. Example ....................................................3
      2.4. Inherited Licenses .........................................4
      2.5. Relationship with the atom:rights Element ..................4
   3. Security Considerations .........................................5
   4. IANA Considerations .............................................5
   5. Normative References ............................................5
   Appendix A.  Acknowledgements ......................................7
        
   1. Introduction ....................................................2
      1.1. Notational Conventions .....................................2
      1.2. Terminology ................................................2
   2. The "license" Link Relation .....................................3
      2.1. Unspecified License Links ..................................3
      2.2. Comparing License Links ....................................3
      2.3. Example ....................................................3
      2.4. Inherited Licenses .........................................4
      2.5. Relationship with the atom:rights Element ..................4
   3. Security Considerations .........................................5
   4. IANA Considerations .............................................5
   5. Normative References ............................................5
   Appendix A.  Acknowledgements ......................................7
        
1. Introduction
1. 介绍

This document defines an extension to the Atom Syndication Format that can be used to add links to Atom feed or entry documents referencing resources that describe the explicit rights that have been granted to consumers of those documents.

此文档定义了Atom联合格式的扩展,可用于添加指向Atom提要或条目文档的链接,这些文档引用了描述已授予这些文档的使用者的显式权限的资源。

Describing licenses using the mechanisms defined in this specification is currently considered to be largely experimental. While it is a common practice for feed publishers to associate licenses with syndicated content, there are still very few feed consumers that utilize such metadata, and the effectiveness of doing so is still largely unknown. As it is not yet certain how these mechanisms will be used, implementations and feedback are encouraged.

使用本规范中定义的机制描述许可证目前被认为在很大程度上是实验性的。虽然feed发布商将许可证与辛迪加内容相关联是一种常见做法,但利用此类元数据的feed消费者仍然很少,这样做的有效性在很大程度上仍然未知。由于尚不确定这些机制将如何使用,因此鼓励实施和反馈。

1.1. Notational Conventions
1.1. 符号约定

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14, [RFC2119].

本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照BCP 14、[RFC2119]中所述进行解释。

1.2. Terminology
1.2. 术语

The term "link relation" refers to the value of the Atom link elements rel attribute as defined in Section 4.2.7.2 of [RFC4287].

术语“链接关系”是指[RFC4287]第4.2.7.2节中定义的原子链接元素rel属性的值。

The term "license" refers to a potentially machine-readable description of explicit rights that have been granted to consumers of an Atom feed or entry. Rights granted by a license may be associated with obligations that must be assumed by those exercising those rights.

术语“许可证”是指授予Atom提要或条目的使用者的明确权利的潜在机器可读描述。许可授予的权利可能与行使这些权利的人必须承担的义务有关。

Atom allows the use of Internationalized Resource Identifiers (IRIs) [RFC3987]. Every URI [RFC3986] is also an IRI, so a URI may be used wherever below an IRI is named. When an IRI that is not also a URI is given for dereferencing, it MUST be mapped to a URI using the steps in Section 3.1 of [RFC3987].

Atom允许使用国际化资源标识符(IRI)[RFC3987]。每个URI[RFC3986]也是一个IRI,因此可以在IRI下面的任何地方使用URI。当为解引用而给出的IRI不是URI时,必须使用[RFC3987]第3.1节中的步骤将其映射到URI。

Atom allows the use of the xml:base attribute [W3C.REC-xmlbase-20010627] to establish the base URI (or IRI) used to resolve any relative references as described in Section 5.1.1 of [RFC3986].

Atom允许使用xml:base属性[W3C.REC-xmlbase-20010627]来建立用于解析任何相关引用的基本URI(或IRI),如[RFC3986]第5.1.1节所述。

Atom allows the use of the xml:lang attribute to indicate the natural language of an element, its attributes, and its descendents. The language context is only significant for elements and attributes declared to be "Language-Sensitive" as described in [RFC4287]. The title attribute of the atom:link element is defined as being Language-Sensitive.

Atom允许使用xml:lang属性来指示元素的自然语言、属性及其后代。如[RFC4287]所述,语言上下文仅对声明为“语言敏感”的元素和属性有效。atom:link元素的title属性定义为语言敏感。

2. The "license" Link Relation
2. “许可证”链接关系

The "license" link relation can be used to associate licenses with a feed or entry.

“许可证”链接关系可用于将许可证与提要或条目关联。

Feed and entry elements MAY contain any number of "license" link relations but MUST NOT contain more than one with the same combination of href and type attribute values. The IRI specified by the link's href attribute SHOULD be dereferenceable to return a representation of the license. The license representation MAY be machine readable.

提要和条目元素可以包含任意数量的“许可证”链接关系,但不能包含多个具有相同href和type属性值组合的链接关系。链接的href属性指定的IRI应该是可取消引用的,以返回许可证的表示形式。许可证表示可以是机器可读的。

Feeds and entries can be dual-licensed by including multiple "license" link relations specifying different href attribute values. If multiple "license" link relations are specified, each SHOULD contain a title attribute specifying a human-readable label for the license.

提要和条目可以通过包含指定不同href属性值的多个“许可证”链接关系进行双重许可。如果指定了多个“许可证”链接关系,则每个链接关系都应包含一个title属性,用于指定许可证的人类可读标签。

2.1. Unspecified License Links
2.1. 未指定的许可证链接

A publisher can use an "unspecified license link" (a "license" link relation with an href attribute value equal to "http://purl.org/atompub/license#unspecified") to indicate that a feed or license has not been explicitly linked to a license description.

发布者可以使用“未指定的许可证链接”(href属性值等于的“许可证”链接关系)http://purl.org/atompub/license#unspecified)以指示源或许可证未显式链接到许可证说明。

A feed or entry containing an unspecified license link MUST NOT contain any other "license" link relations.

包含未指定许可证链接的提要或条目不得包含任何其他“许可证”链接关系。

2.2. Comparing License Links
2.2. 比较许可证链接

Atom implementations that are capable of supporting "license" links SHOULD use the simple string-comparison method described in [RFC3987], Section 5.3.1, to determine whether multiple "license" links are equivalent. The other comparison methods discussed in Section 5.1 of the IRI specification MAY be used. If the "license" link is specified using a relative reference, it MUST be converted to its fully qualified form before comparison.

能够支持“许可证”链接的Atom实现应使用[RFC3987]第5.3.1节中描述的简单字符串比较方法来确定多个“许可证”链接是否等效。可以使用IRI规范第5.1节中讨论的其他比较方法。如果使用相对引用指定“许可证”链接,则必须在比较之前将其转换为完全限定形式。

2.3. Example
2.3. 实例
     <feed xmlns="http://www.w3.org/2005/Atom">
       <id>http://www.example.com/myfeed</id>
       <title>My Example Feed</title>
       <updated>2005-07-28T12:00:00Z</updated>
       <link href="http://www.example.com/myfeed" />
       <link rel="license" type="application/rdf+xml"
         href="http://creativecommons.org/licenses/by-nc/2.5/rdf" />
        
     <feed xmlns="http://www.w3.org/2005/Atom">
       <id>http://www.example.com/myfeed</id>
       <title>My Example Feed</title>
       <updated>2005-07-28T12:00:00Z</updated>
       <link href="http://www.example.com/myfeed" />
       <link rel="license" type="application/rdf+xml"
         href="http://creativecommons.org/licenses/by-nc/2.5/rdf" />
        
       <rights>
         Copyright (c) 2005.  Some rights reserved.  This feed
         is licensed under a Creative Commons Attribute-NonCommercial
         Use License.  It contains material originally published by
         Jane Smith at http://www.example.com/entries/1 under the
         Creative Commons Attribute License.
       </rights>
       <author><name>James</name></author>
       <entry>
         <id>tag:entries.org,2005:1</id>
         <title>Atom Powered Robots Run Amok</title>
         <updated>2005-06-28T12:00:00Z</updated>
         <link href="http://www.example.org/entries/1" />
         <summary>Atom Powered Robots Run Amok</summary>
         <author><name>Jane Smith</name></author>
         <link rel="license" type="text/html"
           href="http://creativecommons.org/licenses/by/2.5/" />
       </entry>
     </feed>
        
       <rights>
         Copyright (c) 2005.  Some rights reserved.  This feed
         is licensed under a Creative Commons Attribute-NonCommercial
         Use License.  It contains material originally published by
         Jane Smith at http://www.example.com/entries/1 under the
         Creative Commons Attribute License.
       </rights>
       <author><name>James</name></author>
       <entry>
         <id>tag:entries.org,2005:1</id>
         <title>Atom Powered Robots Run Amok</title>
         <updated>2005-06-28T12:00:00Z</updated>
         <link href="http://www.example.org/entries/1" />
         <summary>Atom Powered Robots Run Amok</summary>
         <author><name>Jane Smith</name></author>
         <link rel="license" type="text/html"
           href="http://creativecommons.org/licenses/by/2.5/" />
       </entry>
     </feed>
        
2.4. Inherited Licenses
2.4. 继承的许可证

"License" links specified within atom:feed or atom:source elements are inherited by entries. Generally, a more specific license overrides a less specific license. More specifically, if an atom:entry has any "license" link relations, including the "undefined" license, it does not inherit any license from a containing atom:feed element or contained atom:source element. If an entry has no "license" link relations, and contains an atom:source element, it inherits licenses from the atom:source. If the atom:source element contains no "license" links, or if the entry does not have an atom:source element, the entry inherits licenses from the containing atom:feed.

atom:feed或atom:source元素中指定的“许可证”链接由条目继承。通常,更具体的许可会覆盖不太具体的许可。更具体地说,如果atom:entry具有任何“许可证”链接关系,包括“未定义”许可证,则它不会从包含atom:feed元素或包含atom:source元素继承任何许可证。如果条目没有“许可证”链接关系,并且包含atom:source元素,则它将从atom:source继承许可证。如果atom:source元素不包含“license”链接,或者如果条目没有atom:source元素,则该条目将从包含atom:feed的条目继承许可证。

An entry's license MAY be inherited by media resources associated with the entry. Some media types have ways of including license information, which always overrides the entry's licensing.

条目的许可证可以由与该条目关联的媒体资源继承。某些媒体类型有包含许可证信息的方法,这些信息总是覆盖条目的许可。

An agent searching to find entries that fall under a specific license (e.g. a search for entries containing pictures and the word "knitting" where the entry is under any Creative Commons license) MUST check the most granular license definition available, rather than assume license inheritance without checking.

代理搜索特定许可证下的条目(例如,搜索包含图片和单词“kniting”的条目,其中条目属于任何Creative Commons许可证)必须检查可用的最精细的许可证定义,而不是在不检查的情况下假设许可证继承。

2.5. Relationship with the atom:rights Element
2.5. 与atom的关系:rights元素

"License" link relations are related to the atom:rights element in that both are intended to communicate information about the rights

“许可证”链接关系与atom:rights元素相关,因为两者都旨在传递有关权限的信息

associated with an Atom document. Where the two differ, however, is in the fact that atom:rights is intended strictly as a human-readable assertion of rights held over a work while the "license" link relation is intended to provide a potentially machine-readable description of what rights have been granted to others. The two constructs may overlap one another and conflicts could arise if they are contradictory. It is important that publishers of Atom documents ensure that the atom:rights and "license" link relations are consistent with one another.

与Atom文档关联。然而,两者的不同之处在于,atom:rights的目的是严格地作为一种人类可读的作品权利主张,而“许可”链接关系的目的是提供一种潜在的机器可读描述,说明授予他人的权利。这两种结构可能相互重叠,如果它们相互矛盾,则可能发生冲突。Atom文档的发布者必须确保Atom:rights和“license”链接关系彼此一致。

If an atom:entry that does not contain an atom:source is copied from one feed into another feed, then if the feed into which it is copied contains a license, an atom:source element SHOULD be added to the copied entry. If a source feed contains a license, that license SHOULD be preserved in an atom:source element added to any entries copied from the source feed that do not already contain atom:source elements.

如果将不包含atom:source的atom:entry从一个提要复制到另一个提要,则如果复制到的提要包含许可证,则应将atom:source元素添加到复制的条目中。如果源提要包含许可证,则应将该许可证保留在atom:source元素中,该元素添加到从源提要复制的、尚未包含atom:source元素的任何条目中。

3. Security Considerations
3. 安全考虑

When "license" link relations are used in Atom documents, the security considerations specified in [RFC4287] Section 8 apply.

当在Atom文档中使用“许可”链接关系时,[RFC4287]第8节中规定的安全注意事项适用。

4. IANA Considerations
4. IANA考虑

This specification defines one new Atom link relation type to be registered in the IANA Registry of Link Relations as defined by [RFC4287].

本规范定义了一种新的Atom链接关系类型,该类型将在[RFC4287]定义的链接关系IANA注册表中注册。

Attribute Value: license Description: Specifies the IRI of a license associated with the containing feed, entry, or source element. Expected display characteristics: None Security considerations: When "license" link relations are used in Atom documents, the security considerations for handling links in Atom documents apply.

属性值:许可证描述:指定与包含提要、条目或源元素关联的许可证的IRI。预期显示特征:无安全注意事项:当在Atom文档中使用“许可证”链接关系时,处理Atom文档中链接的安全注意事项适用。

5. Normative References
5. 规范性引用文件

[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.

[RFC2119]Bradner,S.,“RFC中用于表示需求水平的关键词”,BCP 14,RFC 2119,1997年3月。

[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, January 2005.

[RFC3986]Berners Lee,T.,Fielding,R.,和L.Masinter,“统一资源标识符(URI):通用语法”,STD 66,RFC 3986,2005年1月。

[RFC3987] Duerst, M. and M. Suignard, "Internationalized Resource Identifiers (IRIs)", RFC 3987, January 2005.

[RFC3987]Duerst,M.和M.Suignard,“国际化资源标识符(IRIs)”,RFC 3987,2005年1月。

[RFC4287] Nottingham, M., Ed., and R. Sayre, Ed., "The Atom Syndication Format", RFC 4287, December 2005.

[RFC4287]诺丁汉,M.,Ed.,和R.Sayre,Ed.,“原子联合格式”,RFC 4287,2005年12月。

[W3C.REC-xmlbase-20010627] Marsh, J., "XML Base", World Wide Web Consortium Recommendation REC-xmlbase-20010627, June 2001, <http://www.w3.org/TR/2001/REC-xmlbase-20010627>.

[W3C.REC-xmlbase-20010627]Marsh,J.,“XML库”,万维网联盟建议REC-xmlbase-20010627,2001年6月<http://www.w3.org/TR/2001/REC-xmlbase-20010627>.

Appendix A. Acknowledgements
附录A.确认书

The author gratefully acknowledges the feedback from Mike Linksvayer, Robin Cover, Lisa Dusseault, Bjorn Hohrmann, Frank Ellermann, and the members of Atom Publishing Format and Protocol working group during the development of this specification.

作者非常感谢Mike Linksvayer、Robin Cover、Lisa Dusseault、Bjorn Hohrmann、Frank Ellermann以及Atom出版格式和协议工作组成员在本规范制定过程中提供的反馈。

Author's Address

作者地址

James M Snell

詹姆斯·姆斯内尔

   EMail: jasnell@gmail.com
   URI:   http://www.snellspace.com
        
   EMail: jasnell@gmail.com
   URI:   http://www.snellspace.com
        

Full Copyright Statement

完整版权声明

Copyright (C) The IETF Trust (2007).

版权所有(C)IETF信托基金(2007年)。

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, THE IETF TRUST 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.

本文件及其包含的信息以“原样”为基础提供,贡献者、他/她所代表或赞助的组织(如有)、互联网协会、IETF信托基金和互联网工程任务组不承担任何明示或暗示的担保,包括但不限于任何保证,即使用本文中的信息不会侵犯任何权利,或对适销性或特定用途适用性的任何默示保证。

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 procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.

IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围,或此类权利下的任何许可可能或可能不可用的程度,不采取任何立场;它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息,请参见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编辑功能的资金目前由互联网协会提供。