Independent Submission M. Lanthaler
Request for Comments: 7284
Category: Informational June 2014
ISSN: 2070-1721
Independent Submission M. Lanthaler
Request for Comments: 7284
Category: Informational June 2014
ISSN: 2070-1721
The Profile URI Registry
配置文件URI注册表
Abstract
摘要
This document defines a registry for profile URIs to be used in specifications standardizing profiles.
本文档定义了用于规范标准化配置文件的配置文件URI的注册表。
Status of This Memo
关于下段备忘
This document is not an Internet Standards Track specification; it is published for informational purposes.
本文件不是互联网标准跟踪规范；它是为了提供信息而发布的。
This is a contribution to the RFC Series, independently of any other RFC stream. The RFC Editor has chosen to publish this document at its discretion and makes no statement about its value for implementation or deployment. Documents approved for publication by the RFC Editor are not a candidate for any level of Internet Standard; see Section 2 of RFC 5741.
这是对RFC系列的贡献，独立于任何其他RFC流。RFC编辑器已选择自行发布此文档，并且未声明其对实现或部署的价值。RFC编辑批准发布的文件不适用于任何级别的互联网标准；见RFC 5741第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7284.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc7284.
Copyright Notice
版权公告
Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2014 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。
Table of Contents
目录
1. Introduction ....................................................2
2. Registration Process ............................................2
3. Example Registration Request ....................................2
4. IANA Considerations .............................................3
4.1. Initial Registry Contents ..................................4
5. Security Considerations .........................................4
6. Acknowledgements ................................................4
7. Normative References ............................................5
1. Introduction ....................................................2
2. Registration Process ............................................2
3. Example Registration Request ....................................2
4. IANA Considerations .............................................3
4.1. Initial Registry Contents ..................................4
5. Security Considerations .........................................4
6. Acknowledgements ................................................4
7. Normative References ............................................5
Profiles, as defined by [RFC6906], can be used to signal support for additional semantics, such as constraints, conventions, extensions, or any other aspects that do not alter the basic media type semantics. Profiles are identified by a URI and can thus be created without central coordination.
[RFC6906]定义的配置文件可用于表示对附加语义的支持，如约束、约定、扩展或不改变基本媒体类型语义的任何其他方面。配置文件由URI标识，因此可以在没有中心协调的情况下创建。
Similar to media types and link relation types, it is, in some cases, beneficial to centrally manage profile URIs to ensure interoperability and decrease the coupling between clients and servers. This allows the independent evolution of clients and servers as both are coupled to these central contracts instead of being coupled to each other. Therefore, this document establishes an IANA registry for profile URIs.
与媒体类型和链接关系类型类似，在某些情况下，集中管理配置文件URI有助于确保互操作性并减少客户端和服务器之间的耦合。这允许客户机和服务器的独立演化，因为两者都耦合到这些中央契约，而不是彼此耦合。因此，本文为概要文件URI建立了IANA注册表。
All elements in this registry require a URI in order to be registered. The meaning of the profile URI should be documented in a permanent and readily available public specification in sufficient detail so that interoperability between independent implementations is possible (see the registration template in Section 4).
此注册表中的所有元素都需要URI才能注册。概要文件URI的含义应记录在一个永久的、随时可用的公共规范中，并提供足够的详细信息，以便独立实现之间的互操作性成为可能（参见第4节中的注册模板）。
An example registration request can be found in Section 3.
在第3节中可以找到注册请求的示例。
The following is an example registration request for the profile URI http://example.com/profiles/example.
下面是配置文件URI的注册请求示例http://example.com/profiles/example.
This is a request to IANA to please register the profile URI "http://example.com/profiles/example" in the "Profile URIs" registry according [RFC7284].
这是对IANA的请求，请注册配置文件URI“http://example.com/profiles/example在“配置文件URI”注册表中，根据[RFC7284]。
o Profile URI: http://example.com/profiles/example
o 配置文件URI：http://example.com/profiles/example
o Common Name: My Profile
o 通用名称：我的个人资料
o Description: An exemplary profile URI registration.
o 描述：示例性配置文件URI注册。
o Reference: [the relevant specification]
o 参考：[相关规范]
This document establishes the "Profile URIs" registry. The registration procedure for new entries requires a request in the form of the following template and is "First Come First Served" per [RFC5226]. Instructions for a registrant to request the registration of a profile URI are in Section 2.
本文档建立了“配置文件URI”注册表。新条目的登记程序要求以以下模板的形式提出申请，并按照[RFC5226]的规定“先到先得”。注册人请求注册配置文件URI的说明见第2节。
The underlying registry data (e.g., the XML file) must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions [TRUST].
基础注册表数据（如XML文件）必须包括简化的BSD许可证文本，如信托法律条款[Trust]第4.e节所述。
The registration template is:
注册模板为：
o Profile URI: The URI that identifies the registered profile.
o 配置文件URI：标识已注册配置文件的URI。
o Common Name: The name by which the profile being registered is generally known.
o 通用名称：注册配置文件时通常使用的名称。
o Description: A relatively short description of the profile. For simple profiles, this might be all the documentation that is required and there might be no reference document. In those cases, be sure this description adequately documents the profile and is suitable for interoperable implementation.
o 描述：对概要文件的相对简短的描述。对于简单概要文件，这可能是所需的所有文档，并且可能没有参考文档。在这些情况下，请确保此描述充分记录了概要文件，并且适合于可互操作的实现。
o Reference: Reference to the document that specifies the URI, preferably including a URI that can be used to retrieve a copy of the document. An indication of the relevant sections may also be included. This is recommended but can be left blank if the "Description" field provides sufficient documentation.
o 引用：对指定URI的文档的引用，最好包括可用于检索文档副本的URI。也可包括相关章节的说明。建议这样做，但如果“说明”字段提供了足够的文档，则可以将其留空。
o Notes: [optional]
o 注：[可选]
The "Profile URIs" registry's initial contents are:
“配置文件URI”注册表的初始内容是：
o Profile URI: urn:example:profile-uri o Common Name: Exemplary Profile o Description: A profile to be used in examples, in accordance with [RFC6963]. o Reference: [RFC7284]
o 配置文件URI:urn：示例：配置文件URI o通用名称：示例性配置文件o说明：根据[RFC6963]在示例中使用的配置文件。o参考文献：[RFC7284]
o Profile URI: http://dublincore.org/documents/2008/08/04/dc-html/ o Common Name: Dublin Core HTML metadata profile o Description: A set of conventions by which a Dublin Core metadata description set can be can be represented within an (X)HTML web page using (X)HTML elements and attributes. o Reference: [DC-HTML]
o 配置文件URI：http://dublincore.org/documents/2008/08/04/dc-html/ o通用名称：都柏林核心HTML元数据配置文件o描述：都柏林核心元数据描述集可以使用（X）HTML元素和属性在（X）HTML网页中表示的一组约定。o参考文献：[DC-HTML]
o Profile URI: http://www.w3.org/ns/json-ld#expanded o Common Name: Expanded JSON-LD o Description: A profile URI to request or signal expanded JSON-LD document form. o Reference: [JSON-LD]
o 配置文件URI：http://www.w3.org/ns/json-ld#expanded o公共名称：扩展JSON-LD o描述：请求或发送扩展JSON-LD文档表单的配置文件URI。o参考：[JSON-LD]
o Profile URI: http://www.w3.org/ns/json-ld#compacted o Common Name: Compacted JSON-LD o Description: A profile URI to request or signal compacted JSON-LD document form. o Reference: [JSON-LD]
o 配置文件URI：http://www.w3.org/ns/json-ld#compacted o通用名称：压缩的JSON-LD o描述：请求或发送压缩的JSON-LD文档表单的配置文件URI。o参考：[JSON-LD]
o Profile URI: http://www.w3.org/ns/json-ld#flattened o Common Name: Flattened JSON-LD o Description: A profile URI to request or signal flattened JSON-LD document form. o Reference: [JSON-LD]
o 配置文件URI：http://www.w3.org/ns/json-ld#flattened o通用名称：扁平化JSON-LD o描述：请求或发送扁平化JSON-LD文档表单的配置文件URI。o参考：[JSON-LD]
There are no additional security considerations beyond those already inherent to using URIs. Security considerations for URIs in general can be found in [RFC3986].
除了使用URI已经固有的安全考虑之外，没有其他安全考虑。URI的一般安全注意事项可在[RFC3986]中找到。
Thanks to Dave Cridland, Barry Leiba, Nevil Brownlee, and Peter Saint-Andre for valuable comments and suggestions.
感谢戴夫·克里德兰、巴里·莱巴、纳维尔·布朗利和彼得·圣安德烈，为他们提供了宝贵的评论和建议。
[DC-HTML] Johnston, P. and A. Powell, "Expressing Dublin Core metadata using HTML/XHTML meta and link elements", Dublin Core Metadata Initiative Recommendation, August 2008, <http://dublincore.org/documents/2008/08/04/dc-html/>.
[DC-HTML]Johnston，P.和A.Powell，“使用HTML/XHTML元数据和链接元素表达都柏林核心元数据”，都柏林核心元数据倡议建议，2008年8月<http://dublincore.org/documents/2008/08/04/dc-html/>.
[JSON-LD] Sporny, M., Kellogg, G., and M. Lanthaler, "JSON-LD 1.0", World Wide Web Consortium Recommendation, January 2014, <http://www.w3.org/TR/json-ld/>.
[JSON-LD]Sporny，M.，Kellogg，G.和M.Lanthaler，“JSON-LD 1.0”，万维网联盟建议，2014年1月<http://www.w3.org/TR/json-ld/>.
[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月。
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008.
[RFC5226]Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 5226，2008年5月。
[RFC6906] Wilde, E., "The 'profile' Link Relation Type", RFC 6906, March 2013.
[RFC6906]王尔德，E.“配置文件”链接关系类型，RFC 69062013年3月。
[RFC6963] Saint-Andre, P., "A Uniform Resource Name (URN) Namespace for Examples", BCP 183, RFC 6963, May 2013.
[RFC6963]Saint Andre，P.，“统一资源名（URN）名称空间示例”，BCP 183，RFC 6963，2013年5月。
[TRUST] IETF, "Trust Legal Provisions (TLP)", <http://trustee.ietf.org/license-info>.
[信托]IETF，“信托法律条款（TLP）”<http://trustee.ietf.org/license-info>.
Author's Address
作者地址
Markus Lanthaler
马库斯兰塔勒
EMail: mail@markus-lanthaler.com
URI: http://www.markus-lanthaler.com/
EMail: mail@markus-lanthaler.com
URI: http://www.markus-lanthaler.com/