Internet Engineering Task Force (IETF) A. Tamas
Request for Comments: 8589 B. Phister, Ed.
Category: Informational J-E. Rodriguez
ISSN: 2070-1721 OP3FT
May 2019
Internet Engineering Task Force (IETF) A. Tamas
Request for Comments: 8589 B. Phister, Ed.
Category: Informational J-E. Rodriguez
ISSN: 2070-1721 OP3FT
May 2019
The 'leaptofrogans' URI Scheme
“leaptofrogans”URI方案
Abstract
摘要
This document describes the 'leaptofrogans' Uniform Resource Identifier (URI) scheme, which enables applications to launch Frogans Player on a given Frogans site. Frogans is a medium for publishing content and services on the Internet, defined as a generic software layer on the Internet. Frogans Player is software that enables end users to browse Frogans sites.
本文档描述了“leaptofrogans”统一资源标识符（URI）方案，该方案使应用程序能够在给定的Frogans站点上启动Frogans Player。Frogans是一种在Internet上发布内容和服务的媒介，定义为Internet上的通用软件层。Frogans Player是一款允许最终用户浏览Frogans网站的软件。
Status of This Memo
关于下段备忘
This document is not an Internet Standards Track specification; it is published for informational purposes.
本文件不是互联网标准跟踪规范；它是为了提供信息而发布的。
This document is a product of the Internet Engineering Task Force (IETF). It has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are candidates for any level of Internet Standard; see Section 2 of RFC 7841.
本文件是互联网工程任务组（IETF）的产品。互联网工程指导小组（IESG）已批准将其出版。并非IESG批准的所有文件都适用于任何级别的互联网标准；见RFC 7841第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc8589.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问https://www.rfc-editor.org/info/rfc8589.
Copyright Notice
版权公告
Copyright (c) 2019 IETF Trust and the persons identified as the document authors. All rights reserved.
版权（c）2019 IETF信托基金和被确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://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. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(https://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Background Information . . . . . . . . . . . . . . . . . . . 2
1.1. About Frogans . . . . . . . . . . . . . . . . . . . . . . 2
1.2. About the OP3FT . . . . . . . . . . . . . . . . . . . . . 3
2. The Need for a New URI Scheme and Its Purpose . . . . . . . . 3
3. Choice of the Scheme Name . . . . . . . . . . . . . . . . . . 4
4. Scheme Syntax . . . . . . . . . . . . . . . . . . . . . . . . 5
4.1. URI Scheme . . . . . . . . . . . . . . . . . . . . . . . 5
4.2. IRI Usage and Encoding . . . . . . . . . . . . . . . . . 6
5. Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . 6
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
7. Security Considerations . . . . . . . . . . . . . . . . . . . 7
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
8.1. Normative References . . . . . . . . . . . . . . . . . . 8
8.2. Informative References . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
1. Background Information . . . . . . . . . . . . . . . . . . . 2
1.1. About Frogans . . . . . . . . . . . . . . . . . . . . . . 2
1.2. About the OP3FT . . . . . . . . . . . . . . . . . . . . . 3
2. The Need for a New URI Scheme and Its Purpose . . . . . . . . 3
3. Choice of the Scheme Name . . . . . . . . . . . . . . . . . . 4
4. Scheme Syntax . . . . . . . . . . . . . . . . . . . . . . . . 5
4.1. URI Scheme . . . . . . . . . . . . . . . . . . . . . . . 5
4.2. IRI Usage and Encoding . . . . . . . . . . . . . . . . . 6
5. Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . 6
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
7. Security Considerations . . . . . . . . . . . . . . . . . . . 7
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
8.1. Normative References . . . . . . . . . . . . . . . . . . 8
8.2. Informative References . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
Frogans is a medium for publishing content and services on the Internet. From its inception in 1999, the medium was designed as a generic software layer running on top of the original Internet infrastructure (i.e., the TCP and IP protocols and the Domain Name System (DNS)), alongside other existing layers such as E-mail or the World Wide Web.
Frogans是一种在互联网上发布内容和服务的媒介。自1999年成立以来，该媒体被设计为一个通用软件层，运行在原始互联网基础设施（即TCP和IP协议以及域名系统（DNS））之上，与其他现有层（如电子邮件或万维网）一起。
As a medium, Frogans is not meant for publishing Web sites, but Frogans sites, a kind of site founded upon a different format, enabling a different kind of communication between end users and publishers of content and services.
作为一种媒介，Frogans并非用于发布网站，而是用于发布Frogans网站，这是一种基于不同格式的网站，能够在最终用户和内容和服务发布者之间实现不同类型的通信。
Frogans is intended to be complementary to the World Wide Web; it is not intended to be a replacement. This is analogous to instant messaging, which was not intended to and did not replace E-mail.
Frogans旨在补充万维网；它不打算作为替代品。这与即时消息类似，即时消息本来不打算也没有取代电子邮件。
Compared to the World Wide Web, Frogans suggests publishing content and services that involve visual rather than text-based communication, focused content rather than long pages, and natural interaction rather than complex user interfaces. For further information on the reasons for introducing Frogans on the Internet, and for an in-depth discussion of the similarities and differences between Frogans sites and Web sites, see [FSDL], Section 1.4 ("Frogans sites and Web sites").
与万维网相比，Frogans建议发布的内容和服务涉及视觉交流而不是基于文本的交流，关注内容而不是长页面，自然交互而不是复杂的用户界面。有关在互联网上引入Frogans的原因的更多信息，以及Frogans网站和网站之间的相似性和差异的深入讨论，请参见[FSDL]，第1.4节（“Frogans网站和网站”）。
The technology making up the medium, i.e., the Frogans technology, includes multiple components such as:
构成介质的技术，即Frogans技术，包括多个组件，例如：
o An XML-based language, called Frogans Slide Description Language [FSDL], used to develop Frogans sites.
o 一种基于XML的语言，称为Frogans幻灯片描述语言[FSDL]，用于开发Frogans网站。
o International identifiers, called Frogans addresses [IFAP], used to access Frogans sites. Each Frogans site has its own Frogans address.
o 国际标识符，称为Frogans地址[IFAP]，用于访问Frogans站点。每个Frogans站点都有自己的Frogans地址。
o Browsing software, called Frogans Player, enabling end users to browse Frogans sites. An end user opens a Frogans site by entering its Frogans address in Frogans Player.
o 浏览软件，称为Frogans Player，允许最终用户浏览Frogans网站。最终用户通过在Frogans Player中输入Frogans地址打开Frogans站点。
o A registry, called the Frogans Core Registry (FCR), that contains all Frogans addresses registered by Frogans site publishers. The registry operator, called the FCR Operator, ensures the resolution of Frogans addresses when end users enter them in Frogans Player.
o 一个名为Frogans核心注册表（FCR）的注册表，包含Frogans站点发布者注册的所有Frogans地址。当最终用户在Frogans Player中输入Frogans地址时，注册表操作符（称为FCR操作符）确保Frogans地址的解析。
Created in 2012, the Organization for the Promotion, Protection, and Progress of Frogans Technology [OP3FT] is a dedicated, non-profit organization whose purpose is to hold, promote, protect, and ensure the progress of the Frogans technology, in the form of an open standard, available to all, free of charge.
Frogans技术促进、保护和进步组织（OP3FT）成立于2012年，是一个专门的非营利组织，其宗旨是以开放标准的形式，免费向所有人提供Frogans技术，以保持、促进、保护和确保Frogans技术的进步。
As part of its mission, the OP3FT develops and releases technical specifications, reference implementations (including Frogans Player), and various policies, which define the rights and responsibilities of all stakeholders involved in the technology worldwide.
作为其使命的一部分，OP3FT制定并发布了技术规范、参考实施（包括Frogans Player）和各种政策，这些政策定义了全球技术相关的所有利益相关者的权利和责任。
Generic software layers running on top of the original Internet infrastructure offer mechanisms that enable end users to easily go from one layer to another, in both directions. For example, end users can easily launch their usual Web browser on a given Web page from a message in their usual E-mail client; in the other direction, end users can easily launch their usual E-mail client with a given E-mail address from a Web page in their usual Web browser. This is commonly achieved using URIs [RFC3986].
运行在原始互联网基础设施之上的通用软件层提供了一些机制，使最终用户能够在两个方向上轻松地从一层转到另一层。例如，最终用户可以轻松地从其常用电子邮件客户端中的消息启动给定网页上的常用Web浏览器；在另一个方向上，最终用户可以使用给定的电子邮件地址从其常用Web浏览器中的网页轻松启动其常用的电子邮件客户端。这通常是通过使用URI[RFC3986]实现的。
As regards Frogans as a medium, in the outgoing direction, FSDL enables Frogans site publishers to include way-out buttons in their Frogans sites. These buttons enable end users to launch their usual Web browser on a given Web page, or to launch their usual E-mail
至于Frogans作为媒介，在外向的方向上，FSDL使Frogans站点发布者能够在他们的Frogans站点中包含退出按钮。这些按钮使最终用户能够在给定网页上启动其常用的Web浏览器，或启动其常用的电子邮件
client with a given E-mail address. This is achieved by associating a URI with each of those way-out buttons (the scheme of the URI can be any of 'http', 'https', or 'mailto').
具有给定电子邮件地址的客户端。这是通过将URI与每一个“退出”按钮相关联来实现的（URI的模式可以是“http”、“https”或“mailto”中的任意一个）。
Conversely, in the incoming direction, Web-site publishers should have a means to include in their Web pages links that enable end users to launch Frogans Player on a given Frogans site. Likewise, people writing E-mail messages should have a means to include in their messages links that enable recipients to launch Frogans Player on a given Frogans site. More generally, any end-user application should be able to launch Frogans Player on a given Frogans site.
相反，在即将到来的方向上，网站发布者应该有一种方法在其网页中包含链接，使最终用户能够在给定的Frogans网站上启动Frogans Player。同样，写电子邮件的人应该有一种方法，在他们的邮件中包含链接，使收件人能够在给定的Frogans站点上启动Frogans Player。更一般地说，任何最终用户应用程序都应该能够在给定的Frogans站点上启动Frogans Player。
To achieve this, a new URI scheme, containing a Frogans address, is needed.
为了实现这一点，需要一个包含Frogans地址的新URI方案。
Given that Frogans, as a medium, does not enable deep linking for Frogans sites, there is no need for additional information in the new URI scheme other than the Frogans address.
考虑到Frogans作为一种媒介，不支持Frogans站点的深度链接，因此除了Frogans地址之外，在新的URI方案中不需要其他信息。
The use of a media type as a means to include on a Web page a link that enables end users to launch Frogans Player on a given Frogans site was tested in 2006 with the registration of the 'vnd.frogans.ltf' media type with IANA [LTF]. But use of a media type was determined to be unsatisfactory for several reasons. First, for any such link included on a Web page, the author of the Web page had to create and host a .ltf file on the Web server hosting that Web page, which was cumbersome. Furthermore, prior to creating such links, the author had to ask the server administrator to associate the .ltf files with the 'vnd.frogans.ltf' media type on the server. Alternatively, the author could create a link via a redirection service that would generate a .ltf file on the fly while associating it with the 'vnd.frogans.ltf' media type. But that alternative raised privacy concerns and potentially added latency for end users. Finally, on the Web browser side, it appeared that using a media type from a Web page to launch another application did not always work, especially on mobile devices.
2006年，通过向IANA[ltf]注册“vnd.Frogans.ltf”媒体类型，测试了将媒体类型用作在网页上包含链接的方法，该链接允许最终用户在给定的Frogans网站上启动Frogans Player。但由于几个原因，媒体类型的使用被确定为不令人满意。首先，对于网页上包含的任何此类链接，网页作者必须在托管该网页的Web服务器上创建并托管一个.ltf文件，这很麻烦。此外，在创建此类链接之前，作者必须要求服务器管理员将.ltf文件与服务器上的“vnd.frogans.ltf”媒体类型相关联。或者，作者可以通过重定向服务创建链接，该服务将动态生成.ltf文件，同时将其与“vnd.frogans.ltf”媒体类型关联。但这一替代方案引发了隐私问题，并可能增加最终用户的延迟。最后，在Web浏览器方面，使用网页中的媒体类型启动另一个应用程序似乎并不总是有效，尤其是在移动设备上。
The name chosen for the new URI scheme is 'leaptofrogans'.
为新URI方案选择的名称是“leaptofrogans”。
This scheme name was chosen in compliance with [RFC7595], Section 3.8 ("Scheme Name Considerations").
该方案名称是根据[RFC7595]第3.8节（“方案名称注意事项”）选择的。
The following shorter names were discussed, but they were not chosen:
讨论了以下较短的名称，但未选择：
o 'ltf': this name, an acronym for "leap to Frogans", was considered insufficiently descriptive, especially for typical end users who have little technical knowledge.
o “ltf”：这个名字是“leap to Frogans”的首字母缩略词，被认为描述不充分，特别是对于缺乏技术知识的典型终端用户。
o 'leapto': this name was considered overly general, and it is not specifically associated with Frogans.
o “leapto”：这个名字被认为过于笼统，与弗罗根没有特别的联系。
o 'frogans': this name was rejected because it could create confusion between URIs based on this scheme and those Frogans addresses that start with "frogans".
o “frogans”：此名称被拒绝，因为它可能会在基于此方案的URI和那些以“frogans”开头的frogans地址之间造成混淆。
Frogans addresses [IFAP] are international identifiers made up of Unicode characters. Thus, a method for encoding non-US-ASCII characters is necessary when the new scheme is used as a URI. The new scheme can also be useful as an IRI [RFC3987] in contexts where IRIs are allowed.
Frogans地址[IFAP]是由Unicode字符组成的国际标识符。因此，当新方案用作URI时，需要一种编码非US ASCII字符的方法。在允许IRI的上下文中，新方案也可以用作IRI[RFC3987]。
The syntax for the 'leaptofrogans' URI scheme is:
“leaptofrogans”URI方案的语法为：
leaptofrogans-uri = "leaptofrogans:" pct-encoded-frogans-address
leaptofrogans uri=“leaptofrogans:”pct编码的frogans地址
where pct-encoded-frogans-address is a Frogans address compliant with [IFAP] and whose Unicode characters are each encoded as follows:
其中，pct编码的frogans地址是符合[IFAP]的frogans地址，其Unicode字符编码如下：
o If the character is a US-ASCII character, do not replace it and skip to the next character. Note that according to [IFAP], the US-ASCII character cannot be the U+0025 PERCENT SIGN character.
o 如果字符是US-ASCII字符，请不要替换它并跳到下一个字符。请注意，根据[IFAP]，US-ASCII字符不能是U+0025%符号字符。
o Otherwise, apply steps 1 through 3 below:
o 否则，应用以下步骤1至3：
1. Convert the character to a sequence of one or more octets using UTF-8 [UTF-8]
1. 使用UTF-8[UTF-8]将字符转换为一个或多个八位字节的序列
2. Convert each octet to %HH, where HH is the hexadecimal notation of the octet value. Note that this is identical to the percent-encoding mechanism in Section 2.1 of [RFC3986].
2. 将每个八位字节转换为%HH，其中HH是八位字节值的十六进制表示法。注意，这与[RFC3986]第2.1节中的百分比编码机制相同。
3. Replace the original character with the resulting character sequence (i.e., a sequence of %HH triplets).
3. 将原始字符替换为生成的字符序列（即%HH三元组的序列）。
Examples of 'leaptofrogans' URIs:
“leaptofrogans”URI的示例：
- if the Frogans address is the string of US-ASCII characters "Network-Name*Site-Name", the URI is as follows:
- 如果Frogans地址是US-ASCII字符“网络名称*站点名称”的字符串，则URI如下所示：
leaptofrogans:Network-Name*Site-Name
leaptofrogans：网络名称*站点名称
- if the Frogans address is the string of Unicode characters U+7F51, U+7EDC, U+540D, U+002A, U+7AD9, U+540D (which is a Chinese translation of the Frogans address in the previous example), the URI is as follows:
- 如果Frogans地址是Unicode字符U+7F51、U+7EDC、U+540D、U+002A、U+7AD9、U+540D组成的字符串（在上例中是Frogans地址的中文翻译），则URI如下所示：
leaptofrogans:%E7%BD%91%E7%BB%9C%E5%90%8D*%E7%AB%99%E5%90%8D
跳跃程序：%E7%BD%91%E7%BB%9C%E5%90%8D*%E7%AB%99%E5%90%8D
The syntax for an IRI corresponding to the 'leaptofrogans' URI scheme is:
与“leaptofrogans”URI方案对应的IRI语法为：
leaptofrogans-iri = "leaptofrogans:" frogans-address
leaptofrogans iri=“leaptofrogans:”弗罗根地址
where frogans-address is a Frogans address compliant with [IFAP] and encoded in UTF-8 [UTF-8].
其中，frogans address是符合[IFAP]的frogans地址，编码为UTF-8[UTF-8]。
In contexts where both URIs and IRIs are allowed, end-user applications can use either a URI or an IRI based on the 'leaptofrogans' URI scheme when launching Frogans Player on a given Frogans site. This is because Frogans Player must interpret both URIs and IRIs based on the 'leaptofrogans' URI scheme. If the U+0025 PERCENT SIGN character is found in the string, then the string will be interpreted by Frogans Player as a URI; otherwise, it will be interpreted as an IRI.
在同时允许URI和IRI的环境中，最终用户应用程序在给定的Frogans站点上启动Frogans Player时，可以使用URI或基于“leaptofrogans”URI方案的IRI。这是因为Frogans播放器必须根据“leaptofrogans”URI方案解释URI和IRIs。如果在字符串中找到U+0025%符号字符，则该字符串将被Frogans Player解释为URI；否则，它将被解释为IRI。
In order to enable all users worldwide to use the Frogans technology in a clearly defined, secure, and perpetual environment, the OP3FT Bylaws [BYLAWS] provide for the implementation of an intellectual property policy.
为了使全世界的所有用户都能在一个明确定义、安全和永久的环境中使用Frogans技术，OP3FT章程[章程]规定了知识产权政策的实施。
In this context, the OP3FT is the holder of the "Frogans" trademark that is registered in France, the United States, and other countries around the world. The right to use the "Frogans" trademark in references or as part of initiatives in connection with the Frogans technology is granted in the OP3FT Trademark Usage Policy [OTUP].
在这种情况下，OP3FT是在法国、美国和世界其他国家注册的“Frogans”商标的持有人。OP3FT商标使用政策[OTUP]授予在参考资料中使用“Frogans”商标的权利，或作为与Frogans技术相关的倡议的一部分使用“Frogans”商标的权利。
In accordance with the guidelines and registration procedures for new URI schemes [RFC7595], IANA has registered 'leaptofrogans' URI scheme as follows:
根据新URI方案的指南和注册程序[RFC7595]，IANA已注册“leaptofrogans”URI方案，如下所示：
Scheme name: 'leaptofrogans'
方案名称：“leaptofrogans”
Status: Permanent
地位：永久
Scheme syntax: See Section 4 of RFC 8589.
方案语法：见RFC 8589第4节。
Scheme semantics: See Section 2 of RFC 8589.
方案语义：参见RFC 8589第2节。
Encoding considerations: See Section 4 of RFC 8589.
编码注意事项：参见RFC 8589第4节。
Applications/protocols that use this scheme name: Frogans Player as well as any end-user application (such as a Web browser or an E-mail client) wishing to launch Frogans Player on a given Frogans site.
使用此方案名称的应用程序/协议：Frogans Player以及希望在给定Frogans站点上启动Frogans Player的任何最终用户应用程序（如Web浏览器或电子邮件客户端）。
Interoperability considerations: There are no known interoperability concerns related to use of the 'leaptofrogans' URI scheme.
互操作性注意事项：使用“leaptofrogans”URI方案没有已知的互操作性问题。
Security considerations: See Section 7 of RFC 8589.
安全注意事项：见RFC 8589第7节。
Contact: Alexis Tamas <mailto:alexis.tamas@op3ft.org>
Contact: Alexis Tamas <mailto:alexis.tamas@op3ft.org>
Change controller: OP3FT <mailto:contact-standards@op3ft.org>
Change controller: OP3FT <mailto:contact-standards@op3ft.org>
References: RFC 8589
参考文献：RFC 8589
The author of a Web page can create a link where the true nature of the URI is hidden in the link text that is visible to end users. The same applies for an E-mail message and other end-user applications.
网页作者可以创建一个链接，在该链接中，URI的真实性质隐藏在最终用户可见的链接文本中。这同样适用于电子邮件和其他最终用户应用程序。
For URIs based on the 'leaptofrogans' URI scheme, the risk of confusion is mitigated because Frogans Player must always display the real Frogans address contained in the URI, and it must always require confirmation by the end user before opening the corresponding Frogans site.
对于基于“leaptofrogans”URI方案的URI，混淆的风险得到了缓解，因为Frogans Player必须始终显示URI中包含的真实Frogans地址，并且在打开相应的Frogans站点之前，必须始终需要最终用户的确认。
Also, an end-user application may provide a URI containing a Frogans address that is not valid. This does not represent a risk because, before asking for confirmation by the end user, Frogans Player must
此外，最终用户应用程序可能提供包含无效Frogans地址的URI。这并不代表风险，因为在请求最终用户确认之前，Frogans玩家必须
always verify that the Frogans address contained in the URI is compliant with [IFAP], and it must always raise an error if the Frogans address is not compliant.
始终验证URI中包含的Frogans地址是否符合[IFAP]，如果Frogans地址不符合，则必须始终引发错误。
[IFAP] OP3FT, "International Frogans Address Pattern", Version 1.1, ISBN 978-2-37313-000-3, November 2014, <https://www.frogans.org/en/resources/ifap/access.html>.
[IFAP]OP3FT，“国际蛙人地址模式”，版本1.1，ISBN 978-2-37313-000-3，2014年11月<https://www.frogans.org/en/resources/ifap/access.html>.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, DOI 10.17487/RFC3986, January 2005, <https://www.rfc-editor.org/info/rfc3986>.
[RFC3986]Berners Lee，T.，Fielding，R.，和L.Masinter，“统一资源标识符（URI）：通用语法”，STD 66，RFC 3986，DOI 10.17487/RFC3986，2005年1月<https://www.rfc-editor.org/info/rfc3986>.
[RFC3987] Duerst, M. and M. Suignard, "Internationalized Resource Identifiers (IRIs)", RFC 3987, DOI 10.17487/RFC3987, January 2005, <https://www.rfc-editor.org/info/rfc3987>.
[RFC3987]Duerst，M.和M.Suignard，“国际化资源标识符（IRIs）”，RFC 3987，DOI 10.17487/RFC3987，2005年1月<https://www.rfc-editor.org/info/rfc3987>.
[RFC7595] Thaler, D., Ed., Hansen, T., and T. Hardie, "Guidelines and Registration Procedures for URI Schemes", BCP 35, RFC 7595, DOI 10.17487/RFC7595, June 2015, <https://www.rfc-editor.org/info/rfc7595>.
[RFC7595]Thaler，D.，Ed.，Hansen，T.和T.Hardie，“URI方案的指南和注册程序”，BCP 35，RFC 7595，DOI 10.17487/RFC7595，2015年6月<https://www.rfc-editor.org/info/rfc7595>.
[UTF-8] Yergeau, F., "UTF-8, a transformation format of ISO 10646", STD 63, RFC 3629, DOI 10.17487/RFC3629, November 2003, <https://www.rfc-editor.org/info/rfc3629>.
[UTF-8]Yergeau，F.，“UTF-8，ISO 10646的转换格式”，STD 63，RFC 3629，DOI 10.17487/RFC3629，2003年11月<https://www.rfc-editor.org/info/rfc3629>.
[BYLAWS] OP3FT, "Bylaws of the French Fonds de Dotation OP3FT, Organization for the Promotion, Protection and Progress of Frogans Technology", July 2016, <https://www.op3ft.org/en/resources/bylaws/access.html>.
【章程】OP3FT，“法国点滴基金会OP3FT章程，促进、保护和进步弗罗根技术组织”，2016年7月<https://www.op3ft.org/en/resources/bylaws/access.html>.
[FSDL] OP3FT, "Frogans Slide Description Language", Version 3.0, Preliminary Draft 7, September 2018, <https://www.frogans.org/en/resources/fsdl/access.html>.
[FSDL]OP3FT，“Frogans幻灯片描述语言”，版本3.0，初稿7，2018年9月<https://www.frogans.org/en/resources/fsdl/access.html>.
[LTF] IANA, "Media Types", <https://www.iana.org/assignments/media-types>.
[LTF]IANA，“媒体类型”<https://www.iana.org/assignments/media-types>.
[OP3FT] OP3FT, "Organization for the Promotion, Protection and Progress of Frogans Technology", <https://www.op3ft.org/>.
[OP3FT]OP3FT，“促进、保护和进步佛罗根技术组织”<https://www.op3ft.org/>.
[OTUP] OP3FT, "OP3FT Trademark Usage Policy", March 2017, <https://www.frogans.org/en/resources/otup/access.html>.
[OTUP]OP3FT，“OP3FT商标使用政策”，2017年3月<https://www.frogans.org/en/resources/otup/access.html>.
Authors' Addresses
作者地址
Alexis Tamas OP3FT 6, Square Mozart 75016 Paris France
亚历克西斯·塔马斯OP3英尺6，法国巴黎莫扎特广场75016号
Phone: +33 1 53 92 00 40
Email: alexis.tamas@op3ft.org
Phone: +33 1 53 92 00 40
Email: alexis.tamas@op3ft.org
Benjamin Phister (editor) OP3FT 6, Square Mozart 75016 Paris France
本杰明·菲斯特（编辑）OP3英尺6，法国巴黎莫扎特广场75016号
Phone: +33 1 53 92 00 40
Email: benjamin.phister@op3ft.org
Phone: +33 1 53 92 00 40
Email: benjamin.phister@op3ft.org
Jean-Emmanuel Rodriguez OP3FT 6, Square Mozart 75016 Paris France
Jean Emmanuel Rodriguez OP3英尺6，法国巴黎莫扎特广场75016
Phone: +33 1 53 92 00 40
Email: jean-emmanuel.rodriguez@contrib.op3ft.org
Phone: +33 1 53 92 00 40
Email: jean-emmanuel.rodriguez@contrib.op3ft.org