查看源代码

[[Category:XMPP扩展]]
[[Category:已翻译]]

'''本文的英文原文来自[http://xmpp.org/extensions/xep-0128.html XEP-0128]'''

'''XEP-0128: 发现服务扩展协议'''

摘要: 这个文件规定了发现服务的扩展信息的最佳做法。

作者: Peter Saint-Andre 

版权: © 1999 - 2010 XMPP标准化基金会(XSF). 参见[[XEP-0030#附录C:法律通告|法律通告]].

现状: 活跃 

类型: 信息 

版本: 1.0 

最后更新: 2004-10-20 


注意：注意：此信息规范定义了一个最佳实践或协议配置文件已被批准的XMPP理事会和/或董事XSF局。实现是鼓励和最佳做法或协议配置文件是在生产系统中部署适当的。


==简介==
开发人员觉得发现服务不能包含更多的信息. 例如, <identity/> 元素不包含'description'属性, 我们可以增加这个属性吗? 答案是可以,但现在不行,太迟了(因为XEP-0030是最终版). 因此,最好的办法是制定一个扩充机制.

让我们参考一个示例. 一个多用户聊天室[2] 可能想要获取更多的信息, 包括房间描述信息,房间主题,房间在线人数和房间所有者的JID.

增加一个新属性的服务发现架构(即使真的是一个选项)不能解决的问题,因为一MUC的服务可能需要提供某些信息，而发布，订阅 [ 3 ]服务可能需要提供其信息。 

一个更好的解决办法是通过一个扩展的信息包括命名空间，提供了一种灵活的结构化数据格式定义合格。 谢天谢地，我们已经拥有了这样一个协议： 数据表格 [ 4 ]。 此外，我们拥有一个共同的方式来定义字段形式用于数据： 数据表格现场标准化 [ 5 ]。 使用这些构建模块，我们可以定义为扩展服务发现结果的一些最佳做法。

==建议==
如果一个实体的希望提供服务发现协议的扩展信息,出现在回复信息内,它应该这样做:每个独立的<field/>元素包含<value/>点数据信息子节点,所有<field/>元素包含在一个类型为"result"命名空间值为'jabber:x:data'的<x/>元素里.

<iq type='result'> 
  <query xmlns='http://jabber.org/protocol/disco#info'> 
    ... 
    <x type='result' xmlns='jabber:x:data'> 
      <field var='[var-name]' label='[optional]'> 
        <value>[var-value]</value> 
      </field> 
      ... 
    </x> 
  </query> 
</iq>Note: A <field/> element MAY contain more than one <value/> child if appropriate.

如果数据字段被用来在由XMPP标准基金会核准的议定书时，他们应该符合相关的XMPP扩展协议规范并按照XEP - 0068定义的规则注册，返回信息中包含一个<field/>元素,其'var'属性为"FORM_TYPE"，其'type'属性的值为"hidden"。

一个实体不能提供'http://jabber.org/protocol/disco#items' 命名空间相关子信息,因为服务发现的核心原则是：一个实体必须确定其身份,不界定的身份与子节点的实体.

==示例==
===IM服务器===
The following is an example of including a disco extension in the IQ result sent by a standard instant messaging server.

Example 1. Entity Queries Server for Information

<iq type='get' 
    from='capulet.com' 
    to='shakespeare.lit' 
    id='disco1'> 
  <query xmlns='http://jabber.org/protocol/disco#info'/> 
</iq> 
 
<iq type='result' 
    from='shakespeare.lit' 
    to='capulet.com' 
    id='disco1'> 
  <query xmlns='http://jabber.org/protocol/disco#info'> 
    <identity 
        category='server' 
        type='im' 
        name='shakespeare.lit jabber server'/> 
    <feature var='jabber:iq:register'/> 
    <x xmlns='jabber:x:data' type='result'> 
      <field var='FORM_TYPE' type='hidden'> 
        <value>http://jabber.org/network/serverinfo</value> 
      </field> 
      <field var='c2s_port'> 
        <value>5222</value> 
      </field> 
      <field var='c2s_port_ssl'> 
        <value>5223</value> 
      </field> 
      <field var='http_access'> 
        <value>http://shakespeare.lit/jabber</value> 
      </field> 
      <field var='ip_version'> 
        <value>ipv4</value> 
        <value>ipv6</value> 
      </field> 
      <field var='info_url'> 
        <value>http://shakespeare.lit/support.php</value> 
      </field> 
    </x> 
  </query> 
</iq> 
===群===
The following is an example of including a disco extension in the IQ result sent by a Multi-User Chat room.

Example 2. User Queries Room for Information

<iq type='get' 
    from='hag66@shakespeare.lit/pda' 
    to='darkcave@macbeth.shakespeare.lit' 
    id='disco1'> 
  <query xmlns='http://jabber.org/protocol/disco#info'/> 
</iq> 
 
<iq type='result' 
    from='darkcave@macbeth.shakespeare.lit' 
    to='hag66@shakespeare.lit/pda' 
    id='disco1'> 
  <query xmlns='http://jabber.org/protocol/disco#info'> 
    <identity 
        category='conference' 
        type='text' 
        name='A Dark Cave'/> 
    <feature var='http://jabber.org/protocol/muc'/> 
    <feature var='jabber:iq:register'/> 
    <x xmlns='jabber:x:data' type='result'> 
      <field var='FORM_TYPE' type='hidden'> 
        <value>http://jabber.org/protocol/muc#roominfo</value> 
      </field> 
      <field var='muc#roominfo_description' label='Description'> 
        <value>The place for all good witches!</value> 
      </field> 
      <field var='muc#roominfo_subject' label='Subject'> 
        <value>Spells</value> 
      </field> 
      <field var='muc#roominfo_occupants' label='Number of occupants'> 
        <value>3</value> 
      </field> 
      <field var='muc#roominfo_lang' label='Language of discussion'> 
        <value>en</value> 
      </field> 
    </x> 
  </query> 
</iq> 

==实现说明==
In general, the XMPP Standards Foundation may choose to define at most one FORM_TYPE for each service discovery identity (category+type) registered with the XMPP Registrar. In addition, particular applications may define application-specific FORM_TYPEs as well, and one entity may have multiple service discovery identities (e.g., an XMPP server might also function as a publish-subscribe service). Therefore, it is possible (and allowed) for a single service discovery result to contain multiple service discovery extension elements (potentially up to two elements for each identity). However, in practice it is unlikely that any given service discovery result will contain more than one service discovery extension element.

==安全注意事项==
Applications SHOULD ensure that information disclosed in a disco extension is appropriate for discovery by any entity on the network.

==IANA注意事项==
This document requires no interaction with the Internet Assigned Numbers Authority (IANA) [6].

==XMPP协议注册事项==
This document requires no interaction with the XMPP Registrar [7]; however, specifications following the best practices defined herein may register FORM_TYPEs and field values with the XMPP Registrar.


==附录==

===附录A:文档信息===

系列：[http://xmpp.org/extensions/ XEP]

序号：0128

发布者：[http://xmpp.org/xsf/ XMPP标准基金会]

状态：[http://www.xmpp.org/extensions/xep-0001.html#states-Final 终结版]

类型：[http://www.xmpp.org/extensions/xep-0001.html#types-Standards%20Track 标准跟踪]

版本：1.0

最后更新：2004-10-20

批准机构：[http://xmpp.org/council/ XMPP理事会]

依赖标准：[[XEP-0004|XEP-0030|XEP-0068|XMPP Core]]

取代: 无

被替代标准：无

缩略名：N/A

原文控制： [http://svn.xmpp.org:18080/browse/XMPP/trunk/extensions/xep-0128.xml HTML] [http://svn.xmpp.org:18080//changelog/~rss/XMPP/trunk/extensions/xep-0128.xml/rss.xml RSS]

本文的其它格式： [http://xmpp.org/extensions/xep-0030.xml XML] [http://xmpp.org/extensions/xep-0128.pdf PDF]


--------------------------------------------------------------------------------
===附录B:作者信息===
Peter Saint-Andre
Email: stpeter@jabber.org
JabberID: stpeter@jabber.org
URI: https://stpeter.im/



{{Template:XEP附录CDEF}}

===附录G:备注===
1. XEP-0030: Service Discovery <http://xmpp.org/extensions/xep-0030.html>.

2. XEP-0045: Multi-User Chat <http://xmpp.org/extensions/xep-0045.html>.

3. XEP-0060: Publish-Subscribe <http://xmpp.org/extensions/xep-0060.html>.

4. XEP-0004: Data Forms <http://xmpp.org/extensions/xep-0004.html>.

5. XEP-0068: Field Data Standardization for Data Forms <http://xmpp.org/extensions/xep-0068.html>.

6. The Internet Assigned Numbers Authority (IANA) is the central coordinator for the assignment of unique parameter values for Internet protocols, such as port numbers and URI schemes. For further information, see <http://www.iana.org/>.

7. The XMPP Registrar maintains a list of reserved protocol namespaces as well as registries of parameters used in the context of XMPP extension protocols approved by the XMPP Standards Foundation. For further information, see <http://xmpp.org/registrar/>.


--------------------------------------------------------------------------------
===附录H:修订历史===
Note: Older versions of this specification might be available at http://xmpp.org/extensions/attic/

Version 1.0 (2004-10-20)
Per a vote of the Jabber Council, advanced status to Active; also added implementation notes. (psa) 
Version 0.2 (2004-03-15)
Clarified syntax and corrected several errors; added IM server example. (psa) 
Version 0.1 (2004-03-05)
Initial version. (psa) 

--------------------------------------------------------------------------------

END