The IETF XML Registry / IETF XML 登録簿
This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Distribution of this memo is unlimited.
Copyright (C) The Internet Society (2004). All Rights Reserved.
This document describes an IANA maintained registry for IETF standards which use Extensible Markup Language (XML) related items such as Namespaces, Document Type Declarations (DTDs), Schemas, and Resource Description Framework (RDF) Schemas.
この文書は、拡張可能マーク付け言語 (XML) 関連項目、 例えば名前空間, 文書型宣言 (DTD), Schema, 資源記述枠組 (RDF) Schema などを使用する IETF 規格についての IANA が維持する登録簿を説明します。
Over the past few years, the Extensible Markup Language (XML) [W3C.REC-xml] has become a widely used method for data markup. There have already been several IETF Working Groups that have produced standards that define XML Document Type Definitions (DTDs), XML Namespaces [W3C.REC-xml-names], and XML Schemas [W3C.REC-xmlschema-1]. Each one of these technologies uses Uniform Resource Identifiers (URIs) [RFC2396] and other standardized identifiers to identify various components.
ここ何年か、拡張可能マーク付け言語 (XML) がデータのマーク付けの方法として広く使われるようになっています。 XML 文書型定義 (DTD)、 XML名前空間、XMLSchema を定義する規格を制作した IETF 作業部会も既に幾つかあります。 これらの技術はそれぞれ統一資源識別子 (URI) や他の標準化識別子を種々の構成部品を識別するために使っています。
For example, while it has been the practice within some standards that use Document Type Definitions (DTDs) to forego the use of the PUBLIC identifiers in favor of 'well known' SYSTEM identifiers, it has proven to be more trouble than its worth to attempt to standardize SYSTEM identifiers. The result is that several IETF standards that have simply created non-resolvable URIs in order to simply identify but not resolve the DTD for some given XML document.
たとえば、文書型定義 (DTD) を使う幾つかの規格では「よくしられている」
SYSTEM 識別子ではなく [PUBLIC]]
識別子を使用することをしないのが習慣になっていますが、
これは SYSTEM 識別子を標準化しようと試みるよりも問題があることが分かっています。
結果として、幾つかの IETF 規格はある XML について解決可能な DTD
ではなく単に識別するための解決不能な URI を単に作っています。
This document seeks to standardize and improve these practices by creating an IANA maintained registry of XML element identifiers so that document authors and implementors have a well maintained and authoritative location for their XML elements. As part of this standard, the IANA will maintain:
この文書は、 IANA が維持する XML 要素識別子の登録簿を作ることでこれらの慣習を標準化・改善しようとするものであり、 文書著者および実装者は、 XML 要素のよく維持された模範的な位置を持つこととなります。 この規格の一部として、 IANA は
- o the public representation of the document,
- o the URI for the elements if one is provided at the time of registration,
- o a registry of Public Identifiers as URIs.
In the case where the registrant does not request a particular URI, the IANA will assign it a Uniform Resource Name (URN) that follows [RFC3553].
登録者が特定の URI を要求しない場合には、 IANA は RFC 3553 にしたがって統一資源名 (URN) を割り当てます。
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, RFC 2119 [RFC2119].
All elements (except PUBLIC identifiers) in this registry will require a URI in order to be registered. If the registrant wishes to have a URI assigned, then a URN of the form
この登録簿の全ての要素 (PUBLIC 識別子を除く。)
は、登録のために URI を必要とします。登録者が URI
を割り当てられたいと思うなら、
- urn:ietf:params:xml:<class>:<id>
will be assigned where <class> is the type of the document being registered (see below). <id> is a unique id generated by the IANA based on any means the IANA deems necessary to maintain uniqueness and persistence. NOTE: in order for a URN of this type to be assigned, the item being registered MUST have been through the IETF consensus process. Basically, this means that it must be documented in a RFC. The RFC 3553 [RFC3553] URN registration template is found in Section 6.
という形式の URN を割り当てます。 ここで、 class は登録される文書の型 (後述) です。 id は IANA が生成する唯一識別子で、唯一性と持続性を維持するために必要な手段により決定します。 注意: この型の URN を登録するためには、その登録される項目が IETF 合意過程を通じていなければなりません。基本的に、 このことは RFC で文書化されていなければならないことを意味します。 RFC 3553 URN 登録雛形は6章にあります。
The IANA will also maintain a file server available via at least HTTP and FTP that contains all of the registered elements in some publicly accessible file space in the same way that all of the IANA's registered elements are available via http://www.iana.org/assignments/. While the directory structure of this server is up to the IANA, it is suggested that the files be organized by the <class> and the individual files have the <id> as their filename.
IANA は少なくても HTTP と FTP で利用可能なファイル鯖も維持します。 この鯖は公衆接続可能ファイル空間にすべての登録された要素を http://www.iana.org/assignments/ で利用可能なすべての IANA の登録された要素と同じ方法で含みます。 この鯖のディレクトリ構造は IANA が決めることですが、ファイルは class で組織化し、個々のファイルで id をファイル名とすることを提案します。
Implementors are warned that they should not programatically rely on those resources being available or the directory structure remaining static for any reason. It is explicitly recognized that some software tools attempt to download DTDs, schema, etc., 'on the fly' and that developers should understand when this is done and when to not reference IANA network resources as a 'schema download repository'. This is the reason that the IANA will not register or provide SYSTEM identifiers.
実装者には、これらの資源が利用可能であることやディレクトリ構造が静的でありつづけることにいかなる理由でもプログラム的に依存しないよう警告します。
「その場で」 DTD, スキーマその他を入手しようとするソフトウェア工具があること、
および開発者はいつこれを行い、いつ IANA ネットワーク資源に
「スキーマ入手倉庫」として参照しないのかを理解すrべきであることが陽に認識されます。
これは、 IANA が SYSTEM 識別子を登録するのでも提供するのでもないという理由です。
The list of types of XML elements that can be registered with the IANA are:
IANA で登録できる XML 要素の型の一覧:
publicid -- An XML document that contains a DOCTYPE declaration or any other external reference can identify that reference via both a PUBLIC identifier and a SYSTEM identifier. The SYSTEM identifier is system-specific information that enables the entity manager of an XML system to locate the file, memory location, or pointer within a file where the entity can be found. It should also be noted that a system identifier could be an invocation of a program that controls access to an entity that is being identified. Thus, they are not registered items. In many cases, SYSTEM identifiers are also URIs. However, in these cases, the URI is still only used for system-specific information. In the case where a PUBLIC Identifier is also a URI, it is possible for the SYSTEM Identifier to contain the same URI but this behavior is not recommended unless its side effects are well known and understood to not cause any unacceptable harm.
publicid — DOCTYPE 宣言や他の外部参照を含んでいる
XML文書は、 PUBLIC 識別子と SYSTEM
識別子の両者によってその参照を識別することが出来ます。
SYSTEM 識別子は、 XML システムの実体管理器がファイル、
記憶位置、実体が見つかるファイル中の指示子を位置づけることを可能にするシステム依存の情報です。
システム識別子は識別されている実体への接続を制御するプログラムを呼び出すこともある点にも注意しておくべきです。
従って、これは登録項目ではありません。
多くの場合、 SYSTEM 識別子は URI でもあります。
しかし、そのような場合、 URI は依然システム依存情報のために使われるだけです。
PUBLIC 識別子も URI である場合には、 SYSTEM
識別子も同じ URI を含むことが可能ですが、そのことの副作用がよく分かっており、
受け入れられない害を起こすことが無いと理解されている場合を除いて推奨しません。
A PUBLIC identifier is a name that is intended to be meaningful across systems and different user environments. Typically, it will be a name that has a registered owner associated with it, so that public identifiers will be guaranteed unique and no two entities will have the same public identifier. In practice, PUBLIC identifiers are typically Formal Public Identifiers [ISO.8879.1986] but they are not restricted to just that set. As said in [RFC3151]:
PUBLIC 識別子は、システムや異なる利用者環境の間に渡って意味があることを想定した名前です。典型的には、それに関連付けられた登録所有者を持つ名前で、従って公開識別子は固有性が保証され、二つの実体が同じ公開識別子を持つことはありません。
実際上、 PUBLIC 識別子は典型的に公式公開識別子ですが、
この集合だけに限定されているわけではありません。 RFC3151
が述べている通りです。
"Any string which consists only of the public identifier characters (defined by Production 13 of Extensible Markup Language (XML) 1.0 Second Edition) is a legal public identifier."
公開識別子文字 (拡張可能マーク付け言語 (XML) 1.0 第2版の生成規則13 で定義されている。) だけで構成される任意の文字列は合法的な公開識別子です。
Therefore, it is legal for a PUBLIC identifier to be a URN if it adheres to the character set restrictions.
従って、文字集合制限を守るなら PUBLIC 識別子を URN
とすることも合法です。
Thus, the identifier registered along with a DTD is its PUBLIC identifier. The only restriction being that it must adhere to the character set restrictions. In the case where the registrant does not provide one, the IANA will assign one of the form 'urn:ietf:params:xml:pi:<id>'. Registrants are encouraged to investigate RFC 3151 [RFC3151] as a recommended method for minting a URN that can also be represented as an FPI.
従って、 DTD と共に登録される識別子はその PUBLIC
識別子です。結ういつの制限は、文字集合制限を守らなければならないことです。
登録者がそうしていない場合には、 IANA
は urn:ietf:params:xml:pi:<id> の形式でこれを割り当てます。
登録者は FPI としても表現可能な URN を鋳造する推奨される方法について
RFC 3151 も調査することをすすめます。
ns -- XML Namespaces [W3C.REC-xml-names] are named by a URI. They
have no real, machine-parseable representation. Thus, the
registered document will be either the specification or a
reference to it. In the case where a URI is not provided by the
registrant, the IANA will assign a URN of the form
'urn:ietf:params:xml:ns:<id> which will be the XML Namespace's
name.nsurn:ietf:params:xml:ns:id の書式で URN
を割り当て、これが XML 名前空間の名前となります。 schema -- XML Schemas [W3C.REC-xmlschema-1] are also identified by a
URI but their contents are machine parseable. The IANA registered
document will be the XML Schema file. The URN the IANA assigns
can be used as the URI for the schema and is of the form
'urn:ietf:params:xml:schema:<id>'.schemaurn:ietf:params:xml:schema:id の書式となります。 rdfschema -- The Resource Description Format (RDF)
[W3C.CR-rdf-schema] is an XML serialization of a connected graph
based data model used for metadata expression. RDF makes use of
schemas for RDF that express grammars about relationships between
URIs. These grammars are identified by URIs. The URN assigned by
the IANA can be used as the identifying URI and is of the form
'urn:ietf:params:xml:rdfschema:<id>'.rdfschemaurn:ietf:params:xml:rdfschema:id
の書式となります。Until the IANA requests or implements an automated process for the registration of these elements, any specifications must make that request part of the IANA considerations section of their respective documents. That request must be in the form of the following template:
IANA がこれらの要素の登録の自動化過程を要求または実装するまで、 各仕様書はそれぞれの文書の IANA に関しての章の要求部分を用意しなければなりません。 その要求は、次の雛形の書式でなければなりません。
URI
The URI or PUBLIC identifier that identifies the XML component. If
the registrant is requesting that the IANA assign a URI then this
field should be specified as "please assign".PUBLIC 識別子。
登録者が IANA に URI 割り当てを要求する時は、
この欄は「登録して下さい」と指定するべきです。 Registrant Contact
The individual/organization that is the registration contact for
the component being registered. Ideally, this will be the name
and pertinent physical and network contact information. In the
case of IETF developed standards, the Registrant will be the IESG. XML
The exact XML to be stored in the registry. Unless the beginning
and end of the file is obvious, the document should use the text
"BEGIN" to mark the beginning of the file and "END" to mark the
end of the file. The IANA will insert any text between those two
strings (minus any page breaks and RFC formatting inserted by the
RFC Editor) into the file kept in the repository.The information maintained by the IANA will be authoritative and will be a target for attack. In some cases, such as XML Schema and DTDs, the content maintained by the IANA may be directly input into software. Thus, extra care should be taken by the IANA to maintain the security precautions required for an important reference location for the Internet.
IANA が維持する情報は規定的な物でしょうから、攻撃の対象となります。 場合によっては、たとえば XML Schema や DTD なら、 IANA が維持している内容は直接ソフトウェアの入力となるかもしれません。 従って、 IANA がインターネットの重要な参照位置に必要な安全上の注意を余分に払うべきです。
Beyond this concern, there are no other security considerations not already found with any other IANA registry.
これ以外には、他の IANA 登録簿には他の安全状の問題点は見つかっていません。
This document seeks to create a rather large registry for which the IANA (at the direction of the IESG) will be primarily responsible. The amount of effort required to maintain this registry is not insignificant and the policies and procedures surrounding any approval process are non-trivial. The registry is on a First Come First Served basis, but a Specification is Required. Once the IETF has some experience with this registry, these policies may change.
この文書は、IANA が (IESG の指示で) 主として責を持つ大きな登録簿を作ろうとする物です。 この登録簿を維持するのに必要な作業の量は小さな物ではなく、 認められた処理を取り巻く方針と手続きは自明ではありません。 登録簿は先来先給の基本に基づきますが、仕様書が必要です。 一度 IETF がこの登録簿についての経験を得たら、 この方針は変更するかも知れません。
RFC 3553 [RFC3553] specifies that any new registry requiring a name, to be assigned below the 'urn:ietf:params' namespace and must specify the structure of that space in template form. The IANA has created and will maintain this new sub-namespace:
RFC3553 は、新しい登録簿は urn:ietf:params
名前空間下に登録するための名前が必要で、
その空間の構造を雛形の書式で規定しなければならないと規定しています。
IANA はこの新しい部分名前空間を作成・維持します。
Registry-name: xml
Specification: This document contains the registry specification.
The namespace is organized with one sub-namespace which is the
<id>.この文書は登録簿仕様を含んでいます。名前空間は id である部分名前空間により組織化します。
Repository: To be assigned according to the guidelines found above.
上述の指針にしたがって割り当てます。
Index value: The class name
[ISO.8879.1986] International Organization for Standardization,
"Information processing - Text and office
systems - Standard generalized markup language
(SGML)", ISO Standard 8879, 1986. [RFC2119] Bradner, S., "Key words for use in RFCs to
Indicate Requirement Levels", BCP 14, RFC 2119,
March 1997. [RFC2396] Berners-Lee, T., Fielding, R. and L. Masinter,
"Uniform Resource Identifiers (URI): Generic
Syntax", RFC 2396, August 1998. [RFC3151] Walsh, N., Cowan, J. and P. Grosso, "A URN
Namespace for Public Identifiers", RFC 3151,
August 2001. [RFC3553] Mealling, M., Masinter, L., Hardie, T. and G.
Klyne, "An IETF URN Sub-namespace for
Registered Protocol Parameters", BCP 73, RFC
3553, June 2003. [W3C.CR-rdf-schema] Brickley, D. and R. Guha, "Resource Description
Framework (RDF) Schema Specification 1.0", W3C
CR-rdf-schema, March 2000,
http://www.w3.org/TR/2000/CR-rdf-schema-
20000327>. [W3C.REC-xml] Bray, T., Paoli, J., Sperberg-McQueen, C. and
E. Maler, "Extensible Markup Language (XML) 1.0
(2nd ed)", W3C REC-xml, October 2000,
http://www.w3.org/TR/REC-xml. [W3C.REC-xml-names] Bray, T., Hollander, D. and A. Layman,
"Namespaces in XML", W3C REC-xml-names, January
1999, http://www.w3.org/TR/REC-xml-names. [W3C.REC-xmlschema-1] Thompson, H., Beech, D., Maloney, M. and N.
Mendelsohn, "XML Schema Part 1: Structures",
W3C REC-xmlschema-1, May 2001,
http://www.w3.org/TR/xmlschema-1/.The IETF takes no position regarding the validity or scope of any intellectual property 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; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication 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 implementors or users of this specification can be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director.
Michael Mealling VeriSign, Inc. Mountain View, CA USA
EMail: michael@verisignlabs.com URI: http://www.research.verisignlabs.com
Copyright (C) The Internet Society (2004). All Rights Reserved.
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assignees.
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS 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.
Funding for the RFC Editor function is currently provided by the Internet Society.
[1] 大急ぎで訳したので少々雑ですけど、気になるところがあったら直して下さい。