RFC5122
小 (→简介) |
|||
| （未显示1个用户的1个中间版本） | |||
| 第2行： | 第2行： | ||
[[Category:翻译中]] | [[Category:翻译中]] | ||
| − | '''本文的英文原文来自[http://xmpp.org/rfcs/rfc5122.html | + | '''本文的英文原文来自[http://xmpp.org/rfcs/rfc5122.html RFC 5122]''' |
| + | |||
| + | {|border="1" cellspacing="0" width="65%" | ||
| + | |网络工作组 || P. Saint-Andre | ||
| + | |- | ||
| + | |申请讨论: 5122 || XSF | ||
| + | |- | ||
| + | |取代: 4622 || 2008年2月 | ||
| + | |- | ||
| + | |类别: 标准跟踪 || | ||
| + | |} | ||
:::'''用于可扩展的即时消息和出席信息协议(XMPP)的国际化资源标识符(IRIs)和统一资源标识符(URIs)''' | :::'''用于可扩展的即时消息和出席信息协议(XMPP)的国际化资源标识符(IRIs)和统一资源标识符(URIs)''' | ||
'''本文的状态''' | '''本文的状态''' | ||
| + | |||
| + | :本文为互联网社区定义了一个互联网标准跟踪协议, 并请求讨论和改进建议. 关于本协议的标准华情况和状态请参考 “互联网官方协议标准” (STD 1) 的当前版本. 本文不限制分发. | ||
| + | |||
| + | '''摘要''' | ||
:本文定义了使用国际化资源标识符(IRIs)和统一资源标识符(URIs)来对能通过可扩展的即时消息和出席信息协议(XMPP)进行通讯的实体进行标识或与其交互. | :本文定义了使用国际化资源标识符(IRIs)和统一资源标识符(URIs)来对能通过可扩展的即时消息和出席信息协议(XMPP)进行通讯的实体进行标识或与其交互. | ||
| − | 本文取代了 RFC 4622. | + | :本文取代了 RFC 4622. |
==简介== | ==简介== | ||
| − | + | 可扩展的消息和出席信息协议(XMPP)是一个流化XML技术，允许一个网络中的两个实体以准实时的速率交换良好定义但是可扩展的XML元素(称为 "XML 节"). | |
As specified in [XMPP‑CORE], entity addresses as used in communications over an XMPP network must not be prepended with a Uniform Resource Identifier (URI) scheme (as specified in [URI]). However, applications external to an XMPP network may need to identify XMPP entities either as URIs or, in a more modern fashion, as Internationalized Resource Identifiers (IRIs; see [IRI]). Examples of such external applications include databases that need to store XMPP addresses and non-native user agents such as web browsers and calendaring applications that provide interfaces to XMPP services. | As specified in [XMPP‑CORE], entity addresses as used in communications over an XMPP network must not be prepended with a Uniform Resource Identifier (URI) scheme (as specified in [URI]). However, applications external to an XMPP network may need to identify XMPP entities either as URIs or, in a more modern fashion, as Internationalized Resource Identifiers (IRIs; see [IRI]). Examples of such external applications include databases that need to store XMPP addresses and non-native user agents such as web browsers and calendaring applications that provide interfaces to XMPP services. | ||
2015年2月4日 (三) 11:51的最后版本
本文的英文原文来自RFC 5122
| 网络工作组 | P. Saint-Andre |
| 申请讨论: 5122 | XSF |
| 取代: 4622 | 2008年2月 |
| 类别: 标准跟踪 |
- 用于可扩展的即时消息和出席信息协议(XMPP)的国际化资源标识符(IRIs)和统一资源标识符(URIs)
本文的状态
- 本文为互联网社区定义了一个互联网标准跟踪协议, 并请求讨论和改进建议. 关于本协议的标准华情况和状态请参考 “互联网官方协议标准” (STD 1) 的当前版本. 本文不限制分发.
摘要
- 本文定义了使用国际化资源标识符(IRIs)和统一资源标识符(URIs)来对能通过可扩展的即时消息和出席信息协议(XMPP)进行通讯的实体进行标识或与其交互.
- 本文取代了 RFC 4622.
简介
可扩展的消息和出席信息协议(XMPP)是一个流化XML技术，允许一个网络中的两个实体以准实时的速率交换良好定义但是可扩展的XML元素(称为 "XML 节").
As specified in [XMPP‑CORE], entity addresses as used in communications over an XMPP network must not be prepended with a Uniform Resource Identifier (URI) scheme (as specified in [URI]). However, applications external to an XMPP network may need to identify XMPP entities either as URIs or, in a more modern fashion, as Internationalized Resource Identifiers (IRIs; see [IRI]). Examples of such external applications include databases that need to store XMPP addresses and non-native user agents such as web browsers and calendaring applications that provide interfaces to XMPP services.
The format for an XMPP address is defined in [XMPP‑CORE]. Such an address may contain nearly any Unicode character [UNICODE] and must adhere to various profiles of stringprep [STRINGPREP]. The result is that an XMPP address is fully internationalizable and is very close to being an IRI without a scheme. However, given that there is no freestanding registry of IRI schemes, it is necessary to define XMPP identifiers primarily as URIs rather than as IRIs, and to register an XMPP URI scheme instead of an IRI scheme. Therefore, this document does the following:
Specifies how to identify XMPP entities as IRIs or URIs. Specifies how to interact with XMPP entities as IRIs or URIs. Formally defines the syntax for XMPP IRIs and URIs. Specifies how to transform XMPP IRIs into URIs and vice-versa. Registers the xmpp URI scheme.
