- Network Working Group - Internet-Draft - Expires: March 6, 2004 - I. King - Microsoft Corporation - L. Masinter - Adobe Systems Incorporated - September 6, 2003 [PRE[ The vnd and prs Trees for URI Scheme Names draft-king-vnd-urlscheme-03.txt ]PRE] * Status of this Memo [PRE[ This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. ]PRE] [PRE[ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. ]PRE] [PRE[ Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." ]PRE] [PRE[ The list of current Internet-Drafts can be accessed at http:// www.ietf.org/ietf/1id-abstracts.txt. ]PRE] [PRE[ The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. ]PRE] [PRE[ This Internet-Draft will expire on March 6, 2004. ]PRE] * Copyright Notice [PRE[ Copyright (C) The Internet Society (2003). All Rights Reserved. ]PRE] * Abstract > This document describes a way in which individuals and vendors can define URI schemes in a way that avoids name collisions, but with relaxed registration requirements. This is done by allowing URI schemes that start with "vnd-" or "prs-", analogous to similar mechanism MIME media types. この文書は、名前の衝突を避けられる方法で、 登録要件を緩和しつつ、個人や販売者が URI 方式を定義できる方法を記述します。 これは MIME 媒体型の同様な仕組みと同じように、 [CODE(URI)[vnd-]] や [CODE(URI)[prs-]] から始まる URI 方式を認めることによって行います。 * Note > Discuss this document on uri@w3.org. A HTML version of this document can be found at http://larry.masinter.net/vnduri.html. この文書について で議論して下さい。 この文書の HTML 版は で見つかります。 * 1. Introduction > The registration process for URI schemes, described in RFC 2717 [2], requires IESG review and approval of all proposed scheme names within the "IETF tree", which encompasses simple, short, often descriptive URI scheme names (such as http:, fax:, or mailto:). [[URI]] [[方式]]の登録手続きは、 [[RFC 2717]] に記述されていますが、 単純で短くてしばしば記述的な URI 方式名 (たとえば [SAMP(URI)[http:]], [SAMP(URI)[fax:]], [SAMP(URI)[mailto:]]) を取巻く「[[IETF木]]」内に提案する方式名はすべて [[IESG]] の評価と承認を必要としています。 > However, there are circumstances where it is desirable to allocate a URI scheme name outside of this process. This document establishes alternative trees, "vnd-" and "prs-", corresponding to the similar concept for MIME type registrations[4]. The rules for use and registration of URI schemes with in these trees are intended to be analogous those for the corresponding MIME type trees. しかし、この手続きの外で URI 方式名を割当てることが望ましい場面もあります。 この文書は、 MIME 型登録における同様な概念に対応する代替木 [CODE(URI)[vnd-]] および [CODE(URI)[prs-]] を確立します。 これらの木での URI 方式の使用と登録のための規則は対応する MIME 型木のものと似た物となっているつもりです。 > The "vnd-" tree is used for URI schemes associated with available products or services; "vendor" or "producer" are construed as equivalent and broadly. The registration belongs to the vendor or organization producing software or offering a service that utilizes the URI scheme. Registration in the vendor tree is distinguished by the leading "vnd-", followed, at the discretion of the registration, either by the scheme name or (preferably) by an IANA-approved designation of the producer's name, followed by the specific scheme name. Designations of producers should match those used for media types, and follows the same criteria. [CODE(URI)[vnd-]] 木は利用可能な製品やサービスに関連付けられた URI 方式に使用します。「販売者」や「製造者」は等しく広く構成します。 登録はその URI 方式を利用するソフトウェアを生産したりサービスを提供したりする販売者や組織に属します。 販売者木での登録は、最初に [CODE(URI)[vnd-]] が来た後に、 登録の裁量で、方式名を続けるか、または (できれば) IANA が承認した製造者名称と、それに続けて特定方式名とします。 製造者名称は媒体型に使用するものと一致するべきで、同じ適合基準に従います。 > Similarly, the "prs-" tree is intended for URI schemes used experimentally or as individual contributions. The owner of "personal" registrations and associated specifications is the person or entity making the registration, or one to whom responsibility has been transferred as described below. 同様に、 [CODE(URI)[prs-]] 木は実験的にまたは個人的貢献として使用する URI 方式を意図しています。「個人」登録および関連付けられた仕様書の所有者は登録を行った、または後述の通り責任を移管された個人または団体です。 > Note that earlier drafts of this document suggested using "." as the delimiter between "vnd" and the URI scheme. However, RFC 2717 [2] reserved the "-" character for non-IETF registrations (and not "."), so the delimiter was changed for compatibility. Because these earlier drafts were available for several years, however, there may be some URI schemes with "vnd." still in use. この文書の以前の原案では [CODE(URI)[vnd]] と URI 方式の間の区切子として [CODE(URI)[.]] を使用して提案していたことに注意して下さい。 しかし、 [[RFC 2717]] は非 IETF 登録に ([CODE(URI)[.]] ではなく) [CODE(URI)[-]] を予約しておりますから、 互換性のために区切子を変更しました。しかし、 以前の原案は幾年もの間利用可能でしたから、 [CODE(URI)[vnd.]] のついた URI 方式が依然使用されているかもしれません。 * 2. Syntax > The general syntax for these new trees follows the syntax recommended in RFC 2717 [2]: これらの新しい木の一般的構文は [[RFC 2717]] で推奨されている構文に従います。 > - scheme = ("vnd-" / "prs-") [ vendor-id "-" ] scheme-id - vendor-id = ALPHA *(ALPHA / DIGIT / "+" ) - scheme-id = ALPHA *(ALPHA / DIGIT / "+" / "-" / "." ) ** 2.1 Syntax notes > Note that RFC 2396 [1] limits the characters in URI scheme names to include only letters, digits, plus ("+"), period ("."), or hyphen ("-"); further, that although scheme names are case insensitive, the canonical form is lowercase and documents that specify schemes must do so using lowercase letters. These restrictions apply to and . [[RFC 2396]] は URI 方式名の文字が英数字, 正 ([CODE(URI)[+]]), 句点 ([CODE(URI)[.]]), ハイフン ([CODE(URI)[-]]) だけを含むように制限しています。更に、方式名は大文字・小文字を区別しませんが、正準形は小文字であり、方式名を規定する文書は従って小文字を使用しなければなりません。こうした制限は [CODE(ABNF)[vendor-id]] および [CODE(ABNF)[scheme-id]] に適用します。 > To avoid confusion, a may not contain a hyphen "-" or a period ".". 混乱を避けるため、 [CODE(ABNF)[vendor-id]] はハイフン [CODE(URI)[-]] や句点 [CODE(URI)[.]] を含んではいけません。 ** 2.2 Choosing a vendor-id > The vendor-id is an IANA-approved designation, consisting of a short string of characters that is sufficient to uniquely identify the organization. [CODE(ABNF)[vendor-id]] は IANA が承認した名称で、 組織を一意に識別するために十分な短い文字列とします。 > To avoid exhaustion of the namespace, vendors are encouraged to establish only one vendor-id, although it is recognized that large organizations may actually consist of multiple sub-units. Organizations should use the same vendor-id for MIME types and URI schemes. 大きな組織は実際には複数の小単位で構成されているかもしれないことは分かっていますが、名前空間の枯渇を避けるために、 販売者は一つの [CODE(ABNF)[vendor-id]] だけを確立するようにお勧めします。 > The organization may be a business (whether for-profit or not), governmental unit, educational institution, or any other entity, organization or community which is regularly engaged in producing software. The term "vendor" is used in this document for simplicity. 組織は会社 (営利であれなかれ)、政府組織、教育機関、その他定期的にソフトウェアを生産する団体、組織、社会で構いません。 この文書では用語「販売者」は簡単のために使用しています。 > IANA may choose to reject a request for a particular vendor-id or propose a different vendor-id based on IANA's best judgment as to whether the string proposed is appropriate for the organization requesting it. IANA は、提案された [CODE(ABNF)[vendor-id]] 文字列が要求している組織に適切でないとの IANA の最善の判断に基づき、 特定の [CODE(ABNF)[vendor-id]] の要求を拒絶したり、 異なる [CODE(ABNF)[vendor-id]] を提案することを選べます。 ** 2.3 Syntax for scheme-id > There are no formal restrictions on the scheme-id except that the characters be chosen from those allowed in a URI scheme name (letters, digits, plus, period, hyphen), and be registered using the lowercase form. The registrar is encouraged to select a scheme-id that is short and descriptive of its purpose. [CODE(ABNF)[scheme-id]] には、 URI 方式名で認められている文字 (英数字、正、句点、ハイフン) から選んだ文字群であることと、 小文字形を使って登録することを除いては、 公式な制限はありません。 登記官は短くてその目的の記述的な [CODE(ABNF)[scheme-id]] を選ぶようお勧めします。 * 3. Requirements for Scheme Name Registration ** 3.1 General Requirements > The purpose of registration is to give notice to the Internet community of the existence the scheme. Registration of the vendor-id is required, and serves to partition the namespace (and avoid collision). 登録の目的は方式の存在についてインターネット社会に注意を与えることです。 [CODE(ABNF)[vendor-id]] の登録は必須であり、 名前区間を区画します (し衝突を避けます)。 > Similarly, to avoid collision and misuse, registration of "prs-" and "vnd-" schemes without vendor-id parts is required. 同様に、衝突と誤使用を防ぐため、 [CODE(URI)[prs-]] の登録と [CODE(ABNF)[vendor-id]] 部分なしの [CODE(URI)[vnd-]] 方式の登録は必須です。 > If the vendor-id is registered, registration of a specific scheme-id is optional; if supplied, the registrar may supply whatever information is appropriate. Registration may only consist of the scheme name, or might include a pointer to appropriate documentation of the scheme's syntax and semantics. [CODE(ABNF)[vendor-id]] が登録されていれば、特定 [CODE(ABNF)[scheme-id]] の登録は任意選択です。登録の場合は、登記官は適切な情報をなんでも提供して構いません。登録は方式名のみからなり、方式の構文と意味の適切な文書への指示子を含むかもしれません。 ** 3.2 Registering the vendor-id > The request for vendor-id registration may be sent separately, or may be included in a scheme name registration. The initial request for vendor-id names must contain the proposed vendor-id, the vendor's legal business name, principal business address, telephone number, and contact information for a person or position that will be responsible for the use of the vendor's subtree. The vendor should inform IANA if of changes in this information, and may explicitly transfer ownership of its vendor-id and associated subtree. [CODE(ABNF)[vendor-id]] の登録の要求は別途送信しても構いませんし、 方式名登録に含めても構いません。最初の [CODE(ABNF)[vendor-id]] 名の要求は提案する [CODE(ABNF)[vendor-id]] と販売者の法的商号と本社住所、 電話番号、販売者部分木の使用に責任を持つ担当者または役職の接触情報を含まなければなりません。 販売者はこの情報が変わった時には IANA に知らせるべきであり、 [CODE(ABNF)[vendor-id]] と関連付けられた部分木の所有権を陽に移管しても構いません。 > A given vendor-id can be issued only once, and it does not expire. This is to avoid possible name collisions, since using a registered vendor-id means there may be URI schemes that are not otherwise registered. ある [CODE(ABNF)[vendor-id]] は一度だけ発行することができ、 期限切れはありません。これは名前衝突の虞を避けるためです。 登録 [CODE(ABNF)[vendor-id]] を使用することは別途登録されていない URI 方式があるかもしれないことを意味しますから。 > IANA should maintain a public registry of the vendor-id's, together with contact information for each vendor so registered. A form for submission of this information (together with scheme information as appropriate) is provided in this document. IANA は、 [CODE(ABNF)[vendor-id]] の公開登録簿を、 登録した各販売者の接触情報と共に維持するべきです。 この情報の提出の形式 (と適切な方式情報と共に) この文書で提供しています。 ** 3.3 Publishing Scheme-Specific Information > While public exposure and review of a URI scheme created in the "vnd-" or "prs-" tree is not required, it is encouraged. The 'uri-review@ietf.org' mailing list may be used for review of new URI schemes, even if they are not in the IETF tree. [CODE(URI)[vnd-]] 木や [CODE(URI)[prs-]] 木に作成する URI 方式の公開陳列・評価は必要ではありませんが、推奨します。 新しい URI 方式の評価には、 IETF 木ではない場合でも メイリング・リストを使用して構いません。 > Publication of the scheme description as an Informational RFC may be appropriate for those schemes of sufficient interest to the IETF community; however, this mechanism is usually appropriate only for URI schemes in the IETF tree. IETF 社会に十分関係する方式は情報提供 RFC として方式説明を出版するのが適切かもしれません。 しかし、この仕組みは通常 IETF 木の URI 方式にのみ適切です。 > Note that a separate, explicit request should be made to IANA (at IANA@iana.org) to register schemes; discussion on uri-review@ietf.org is insufficient. The request should follow the form is provided in Appendix A of this document. 方式を登録するためには別途陽な要求を IANA に行うべきです。 での議論は不十分です。要求はこの文書の附属書 A で提供する書式に従うべきです。 > Internet Drafts intended for publication as Informational RFCs describing new URI schemes should also contain an 'IANA Considerations' section with the request for registration included. The registration would occur at the time of publication of the document as an RFC. 新しい URI 方式を説明する情報提供 RFC として出版するつもりの [[Internet Draft]] は「IANA Considerations」の章で登録の要求を含めるべきです。 登録は文書が RFC として出版された時点で行われます。 ** 3.4 Change Control > The vendor is the owner of all schemes within its registered tree, has sole responsibility for management of the sub-tree created by its vendor-id, and owns change control for any URI schemes deployed therein. If a vendor publishes information about a vnd URI scheme by either of the methods described above, changes to the syntax or semantics of that URI scheme must be subsequently published by the same medium as originally employed. 販売者はその登録木中のすべての方式の所有者であり、 その [CODE(ABNF)[vendor-id]] により作成される部分木の完全な維持責任を有し、 その中にある任意の URI 方式の変更権を所有します。 所有者が上述の方式のいずれかによって [CODE(URI)[vnd]] URI 方式についての情報を出版したなら、その URI 方式の構文または意味についての変更はその後元々使用した同じ媒体で出版しなければなりません。 * 4. Security Considerations > The vendor identified by the vendor-id part of the URI scheme name should be consulted for any information regarding the URI scheme and its implementation. To that end, vendors must provide a point of contact that can be reasonably authenticated, for instance, common business contact information (business address, telephone number, etc.). (This is addressed in the registration section above.) URI 方式とその実装に関する情報は URI 方式名の [CODE(ABNF)[vendor-id]] 部分で識別される販売者に問い合わせるべきです。 そのために、販売者はかなり確実な接触点、たとえば代表接触情報 (住所、電話番号など) を提供しなければなりません。 (これは前の登録の章で触れています。) > The registration process encourages vendors to analyze and disclose the security implications of using particular URI schemes. Unregistered schemes or those without appropriate security considerations may be unsafe to use. 登録手続きは販売者に特定 URI 方式を使用することによる安全上の影響を調査し公開するようにお勧めします。 未登録方式や適切な安全上の考察の無い方式は使用すると安全でないかもしれません。 * 5. IANA Considerations > IANA currently maintains a registry of URI scheme names, per the requirements of RFC 2717. Scheme names established under this process should also be entered in that registry, when requested. IANA は現在 URI方式名の登録簿を [[RFC 2717]] の要件によって維持しています。 この手続きの下で確立した方式名も要求された時にその登録簿に入れるべきです。 > IANA should maintain a separate registry of vendor-id strings, relating the vendor-id to the vendor information (business contact information, etc.) provided in the registration. The vendor-id string list should be used also for vendor strings used in media types, as per RFC 2048. IANA should reject a vendor-id registration if it duplicates an existing registration, seems inappropriate, confusing, misleading, or too similar to another registered vendor-id, at IANA's discression. IANA may offer an alternative vendor-id string that IANA considers more appropriate. IANA は別途 [CODE(ABNF)[vendor-id]] 文字列の登録簿を、 登録で提供された販売者情報 (会社接触情報など) を [CODE(ABNF)[vendor-id]] と関連させて維持するべきです。 [CODE(ABNF)[vendor-id]] 文字列一覧は [[RFC 2048]] による媒体型で使用される販売者文字列にも使用するべきです。 IANA は、 IANA の裁量により、既存の登録と重複していたり、 不適切に見えたり、他の登録 [CODE(ABNF)[vendor-id]] と混乱したり誤解したり似すぎたりする [CODE(ABNF)[vendor-id]] を却下するべきです。 IANA は IANA がより適切と考える代替 [CODE(ABNF)[vendor-id]] 文字列を提案しても構いません。 > A party whose vendor-id registration has been rejected or modified may ask for review of the registration by the IESG, in the manner described in RFC 2026, section 6.5. [CODE(ABNF)[vendor-id]] 登録が却下されたり修正されたりした団体は [[RFC 2026]] 6.5 節に記述された方法で IESG に登録の評価を依頼して構いません。 * 6. Registration forms > Form for vendor information: 登録者情報の書式 [PRE[ Vendor-ID: proposed identifier Name: formal name of organization Address: full name of organization Telephone: full telephone number Type: type of organization (corporation, educational institution, etc.) Contact Information: name of contact person and location information ]PRE] > The form for scheme names follows RFC 2717, section 6.0. [[RFC 2717]] 6.0 節に従った方式名の書式 [PRE[ Scheme name: Scheme syntax: Character encoding considerations: Intended usage: Applications and/or protocols which use this URL scheme name: Interoperability considerations: Security considerations: Relevant publications: ]PRE] * Normative References [PRE[ [1] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform Resource Identifiers (URI): Generic Syntax", RFC 2396, August 1998. ]PRE] * Informative References [PRE[ [2] Petke, R. and I. King, "Registration Procedures for URL Scheme Names", RFC 2717, November 1999. ]PRE] [PRE[ [3] Masinter, L., Alvestrand, H., Zigmond, D. and R. Petke, "Guidelines for New URL Schemes", RFC 2718, November 1999. ]PRE] [PRE[ [4] Freed, N., Klensin, J. and J. Postel, "Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures", RFC 2048, November 1996. ]PRE] * Authors' Addresses [PRE[ Ian King Microsoft Corporation One Microsoft Way Redmond, WA 98052-6399 US ]PRE] [PRE[ Phone: +1 425 703 2293 EMail: iking@microsoft.com ]PRE] [PRE[ Larry Masinter Adobe Systems Incorporated 345 Park Ave San Jose, CA 95110 US ]PRE] [PRE[ Phone: +1 408 536 3024 EMail: LMM@acm.org URI: http://larry.masinter.net ]PRE] * Intellectual Property Statement [PRE[ 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. ]PRE] [PRE[ 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. ]PRE] * Full Copyright Statement [PRE[ Copyright (C) The Internet Society (2003). All Rights Reserved. ]PRE] [PRE[ 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. ]PRE] [PRE[ The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assignees. ]PRE] [PRE[ 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. ]PRE] [[RFCのライセンス]]参照。 * Acknowledgment [PRE[ Funding for the RFC Editor function is currently provided by the Internet Society. ]PRE] * memo [1] loan for military personnel, home mortgage loan payment calculator, bank of america auto loan, emergency cash loan houston, va loan program, advance cash check cincinnati, arizona in jumbo loan mortgage, ([[Stanley]] [staleyasmith@hotmail.tw]) [2] Bestrecipesforyou.com just got a new and improved look and we hope that you will like what we’ve done. Our web site was first launched almost ten years ago.... ([[Nick]] [mail@bestrecipesforyou.com]) [3] Bestrecipesforyou.com just got a new and improved look and we hope that you will like what we’ve done. Our web site was first launched almost ten years ago.... ([[Nick]] [mail@bestrecipesforyou.com]) [4] History of the United States of America. ([[Mark]] [mail@usahistorical.com]) [5] History of the United States of America. ([[Mark]] [mail@usahistorical.com]) [6] Enjoy wines from top-rated wine producers around the world from Australia to Germany to South Africa. A great way to sample a variety of wines from major wine regions. A GREAT GIFT for wine lovers. ([[Mark]] [mail@allaboutvine.com]) [7] The (IHR) provides resources for historians. These resources include online articles, free event advertising, MA/PhD study, training courses, an open-access library and more. ([[Ann]] [mail@history-of-uk.com]) [8] good website ([[Herbert]] [mail@rabbitsweb.com]) [9] good website ([[Herbert]] [mail@rabbitsweb.com]) [10] {text1}, {text2} ([[Jack]] [mail@cartodday.com]) [11] goo work ([[Michail]] [mail@webgamesbuilder.com])