跳到主要内容

6. IANA 考虑事项

本规范更新了 HTTP [RFC3864] 中 "Link" 的消息头注册表条目, 使其引用本文档.

Header field: Link
Applicable protocol: http
Status: standard
Author/change controller:
    IETF  ([email protected])
    Internet Engineering Task Force
Specification document(s):
    [RFC5988]

6.2. 链接关系类型注册表​

本规范建立了链接关系类型 (Link Relation Type) 注册表, 并更新 Atom [RFC4287], 使其引用该注册表以取代 "Registry of Link Relations".

底层注册表数据 (例如该 XML 文件) 必须包含 Trust Legal Provisions 第 4.e 节所述的 Simplified BSD License 文本 (http://trustee.ietf.org/license-info).

6.2.1. 注册新的链接关系类型​

关系类型在指定专家 (Designated Expert, 由 IESG 或其代表任命) 的建议下注册, 采用 Specification Required 方式 (使用 [RFC5226] 中的术语).

已注册关系类型的要求见第 4.1 节.

注册请求由下方填写完整的注册模板构成, 通常发布在 RFC 或开放标准中 (按 [RFC2026] 第 7 节所述的含义). 然而, 为允许在发布之前分配取值, 指定专家在确信某一规范将会发布之后, 可以先行批准注册.

注意, 第三方也可以注册关系类型, 前提是指定专家认定某个未注册的关系类型已被广泛部署, 且不太可能及时完成注册.

注册模板为:

Relation Name:

Description:

Reference:

Notes: [optional]

Application Data: [optional]

注册请求应发送至 [email protected] 邮件列表, 并在主题行中清晰标明 (例如 "NEW RELATION - example" 表示注册一个 "example" 关系类型).

在收到请求后最多 14 天内, 指定专家将批准或拒绝该注册请求, 并把该决定告知评审列表和 IANA. 拒绝应当包含解释, 并在适用时给出如何使请求获得成功的建议.

指定专家所作的决定 (或未作决定) 可以首先向应用领域主管 (Application Area Directors) 申诉 (可通过 [email protected] 电子邮件地址联系, 或直接在 http://www.iesg.org/ 网站上查找其电子邮件地址); 如果申诉人对答复不满意, 可以向整个 IESG 申诉 (使用 [email protected] 邮件列表). IANA 只应接受来自指定专家的注册表更新, 并应把所有注册请求转给评审邮件列表.

6.2.2. 初始注册表内容​

链接关系类型注册表的初始内容为:

Relation Name: alternate
Description: Designates a substitute for the link's context.
Reference: [W3C.REC-html401-19991224]

Relation Name: appendix
Description: Refers to an appendix.
Reference: [W3C.REC-html401-19991224]

Relation Name: bookmark
Description: Refers to a bookmark or entry point.
Reference: [W3C.REC-html401-19991224]

Relation Name: chapter
Description: Refers to a chapter in a collection of resources.
Reference: [W3C.REC-html401-19991224]

Relation Name: contents
Description: Refers to a table of contents.
Reference: [W3C.REC-html401-19991224]

Relation Name: copyright
Description: Refers to a copyright statement that applies to the
   link's context.
Reference: [W3C.REC-html401-19991224]

Relation Name: current
Description: Refers to a resource containing the most recent
   item(s) in a collection of resources.
Reference: [RFC5005]

Relation Name: describedby
Description: Refers to a resource providing information about the
   link's context.
Documentation: <http://www.w3.org/TR/powder-dr/#assoc-linking>

Relation Name: edit
Description: Refers to a resource that can be used to edit the
   link's context.
Reference: [RFC5023]

Relation Name: edit-media
Description: Refers to a resource that can be used to edit media
   associated with the link's context.
Reference: [RFC5023]

Relation Name: enclosure
Description: Identifies a related resource that is potentially
   large and might require special handling.
Reference: [RFC4287]

Relation Name: first
Description: An IRI that refers to the furthest preceding resource
   in a series of resources.
Reference: [RFC5988]
Notes: this relation type registration did not indicate a
   reference.  Originally requested by Mark Nottingham in December
   2004.

Relation Name: glossary
Description: Refers to a glossary of terms.
Reference: [W3C.REC-html401-19991224]

Relation Name: help
Description: Refers to a resource offering help (more information,
   links to other sources information, etc.)
Reference: [W3C.REC-html401-19991224]

Relation Name: hub
Description: Refers to a hub that enables registration for
   notification of updates to the context.
Reference: <http://pubsubhubbub.googlecode.com/> <http://
   pubsubhubbub.googlecode.com/svn/trunk/pubsubhubbub-core-0.3.html>
Notes: this relation type was requested by Brett Slatkin.

Relation Name: index
Description: Refers to an index.
Reference: [W3C.REC-html401-19991224]

Relation Name: last
Description: An IRI that refers to the furthest following resource
   in a series of resources.
Reference: [RFC5988]
Notes: this relation type registration did not indicate a
   reference.  Originally requested by Mark Nottingham in December
   2004.

Relation Name: latest-version
Description: Points to a resource containing the latest (e.g.,
   current) version of the context.
Reference: [RFC5829]

Relation Name: license
Description: Refers to a license associated with the link's
   context.
Reference: [RFC4946]

Relation Name: next
Description: Refers to the next resource in a ordered series of
   resources.
Reference: [W3C.REC-html401-19991224]

Relation Name: next-archive
Description: Refers to the immediately following archive resource.
Reference: [RFC5005]

Relation Name: payment
Description: indicates a resource where payment is accepted.
Reference: [RFC5988]
Notes: this relation type registration did not indicate a
   reference.  Requested by Joshua Kinberg and Robert Sayre.  It is
   meant as a general way to facilitate acts of payment, and thus
   this specification makes no assumptions on the type of payment or
   transaction protocol.  Examples may include a Web page where
   donations are accepted or where goods and services are available
   for purchase. rel="payment" is not intended to initiate an
   automated transaction.  In Atom documents, a link element with a
   rel="payment" attribute may exist at the feed/channel level and/or
   the entry/item level.  For example, a rel="payment" link at the
   feed/channel level may point to a "tip jar" URI, whereas an entry/
   item containing a book review may include a rel="payment" link
   that points to the location where the book may be purchased
   through an online retailer.

Relation Name: prev
Description: Refers to the previous resource in an ordered series
   of resources.  Synonym for "previous".
Reference: [W3C.REC-html401-19991224]

Relation Name: predecessor-version
Description: Points to a resource containing the predecessor
   version in the version history.
Reference: [RFC5829]

Relation Name: previous
Description: Refers to the previous resource in an ordered series
   of resources.  Synonym for "prev".
Reference: [W3C.REC-html401-19991224]

Relation Name: prev-archive
Description: Refers to the immediately preceding archive resource.
Reference: [RFC5005]

Relation Name: related
Description: Identifies a related resource.
Reference: [RFC4287]

Relation Name: replies
Description: Identifies a resource that is a reply to the context
   of the link.
Reference: [RFC4685]

Relation Name: section
Description: Refers to a section in a collection of resources.
Reference: [W3C.REC-html401-19991224]

Relation Name: self
Description: Conveys an identifier for the link's context.
Reference: [RFC4287]

Relation Name: service
Description: Indicates a URI that can be used to retrieve a
   service document.
Reference: [RFC5023]
Notes: When used in an Atom document, this relation type specifies
   Atom Publishing Protocol service documents by default.  Requested
   by James Snell.

Relation Name: start
Description: Refers to the first resource in a collection of
   resources.
Reference: [W3C.REC-html401-19991224]

Relation Name: stylesheet
Description: Refers to an external style sheet.
Reference: [W3C.REC-html401-19991224]

Relation Name: subsection
Description: Refers to a resource serving as a subsection in a
   collection of resources.
Reference: [W3C.REC-html401-19991224]

Relation Name: successor-version
Description: Points to a resource containing the successor version
   in the version history.
Reference: [RFC5829]

Relation Name: up
Description: Refers to a parent document in a hierarchy of
   documents.
Reference: [RFC5988]
Notes: this relation type registration did not indicate a
   reference.  Requested by Noah Slater.

Relation Name: version-history
Description: points to a resource containing the version history
   for the context.
Reference: [RFC5829]

Relation Name: via
Description: Identifies a resource that is the source of the
   information in the link's context.
Reference: [RFC4287]

Relation Name: working-copy
Description: Points to a working copy for this resource.
Reference: [RFC5829]

Relation Name: working-copy-of
Description: Points to the versioned resource from which this
   working copy was obtained.
Reference: [RFC5829]

6.3. 链接关系应用数据注册表​

本规范还建立了链接关系应用字段 (Link Relation Application Field) 注册表, 以允许向链接关系类型注册表中的条目扩展应用特定的数据 (以下称 "应用数据" / "app data"), 这些数据特定于某个给定链接关系类型的所有实例.

应用数据在指定专家 (由 IESG 或其代表任命) 的建议下注册, 采用 Specification Required 方式 (使用 [RFC5226] 中的术语). 注册请求由下方填写完整的注册模板构成:

Application Name:

Description:

Default Value:

Notes: [optional]

Description SHOULD 标识应用数据的取值空间. Default Value MUST 适用于那些不适用该应用数据的条目.

早于应用数据被添加之前就已存在的条目, 将自动被视为具有该应用数据的默认值; 如果有例外情况, 对此类条目的修改应由指定专家协调, 并与拟议应用数据的作者以及现有条目的注册者 (如有可能) 协商进行.

注册请求应发送至 [email protected] 邮件列表, 并在主题行中清晰标明 (例如 "NEW APP DATA - example" 表示注册 "example" 应用数据).

在收到请求后最多 14 天内, 指定专家将批准或拒绝该注册请求, 并把该决定告知评审列表. 拒绝应当包含解释, 并在适用时给出如何使请求获得成功的建议. 超过 21 天仍未有结果的注册请求, 可以提请 IESG 注意 (使用 [email protected] 邮件列表) 以求解决.

当注册请求获得成功后, 指定专家将把它转交 IANA 以便发布. IANA 只应接受来自指定专家的注册表更新, 并应把所有注册请求转给评审邮件列表.