mirror of
https://github.com/moparisthebest/xeps
synced 2024-11-05 00:45:05 -05:00
177 lines
8.7 KiB
XML
177 lines
8.7 KiB
XML
<?xml version='1.0' encoding='UTF-8'?>
|
|
<!DOCTYPE xep SYSTEM 'xep.dtd' [
|
|
<!ENTITY % ents SYSTEM 'xep.ent'>
|
|
%ents;
|
|
]>
|
|
<?xml-stylesheet type='text/xsl' href='xep.xsl'?>
|
|
<xep>
|
|
<header>
|
|
<title>Service Discovery Extensions</title>
|
|
<abstract>This document specifies best practices for including extended information in Service Discovery results.</abstract>
|
|
&LEGALNOTICE;
|
|
<number>0128</number>
|
|
<status>Active</status>
|
|
<type>Informational</type>
|
|
<sig>Standards</sig>
|
|
<dependencies>
|
|
<spec>XMPP Core</spec>
|
|
<spec>XEP-0004</spec>
|
|
<spec>XEP-0030</spec>
|
|
<spec>XEP-0068</spec>
|
|
</dependencies>
|
|
<supersedes/>
|
|
<supersededby/>
|
|
<shortname>N/A</shortname>
|
|
&stpeter;
|
|
<revision>
|
|
<version>1.0.1</version>
|
|
<date>2019-07-30</date>
|
|
<initials>gdk</initials>
|
|
<remark>Remove now-incorrect informational statement about the likelihood of multiple forms in a single disco#info reply.</remark>
|
|
</revision>
|
|
<revision>
|
|
<version>1.0</version>
|
|
<date>2004-10-20</date>
|
|
<initials>psa</initials>
|
|
<remark>Per a vote of the Jabber Council, advanced status to Active; also added implementation notes.</remark>
|
|
</revision>
|
|
<revision>
|
|
<version>0.2</version>
|
|
<date>2004-03-15</date>
|
|
<initials>psa</initials>
|
|
<remark>Clarified syntax and corrected several errors; added IM server example.</remark>
|
|
</revision>
|
|
<revision>
|
|
<version>0.1</version>
|
|
<date>2004-03-05</date>
|
|
<initials>psa</initials>
|
|
<remark>Initial version.</remark>
|
|
</revision>
|
|
</header>
|
|
<section1 topic='Introduction' anchor='intro'>
|
|
<p>Developers periodically wonder why &xep0030; does not include more bits of information. For example, why does the <identity/> element not include a 'description' attribute, and can we add one now? The answer is: well, it just doesn't, and at this point it's too late to make further changes (since XEP-0030 is Final). So the best approach is to specify a well-defined extension mechanism.</p>
|
|
<p>Let us consider an example. A &xep0045; room might want to include additional information in its service discovery results, such as the full room description, the current discussion topic (room subject), the number of occupants in the room, and the JID of the room owner.</p>
|
|
<p>Adding one new attribute to the service discovery schema (even if that were an option) would not solve the problem, since a MUC service might want to provide certain bits of information, whereas a &xep0060; service might want to provide other bits.</p>
|
|
<p>A better solution would be to include extended information qualified by a namespace that provides a way to flexibly define structured data formats. Thankfully, we already possess such a protocol: &xep0004;. In addition, we possess a way to define common fields used in data forms: &xep0068;. Using these building blocks, we can define some best practices for extending service discovery results.</p>
|
|
</section1>
|
|
<section1 topic='Recommendations' anchor='recommendations'>
|
|
<p>If an entity desires to provide extended information about itself in an IQ results stanza within the context of the <cite>Service Discovery</cite> protocol, it SHOULD do so by including each bit of information as the XML character data of the <value/> child of a distinct <field/> element, with the entire set of fields contained within an <x/> element of type "result" qualified by the 'jabber:x:data' namespace; this <x/> element SHOULD be a child of the <query/> element qualified by the 'http://jabber.org/protocol/disco#info' namespace. Thus the IQ result SHOULD be of the following form:</p>
|
|
<code><![CDATA[
|
|
<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>]]></code>
|
|
<p>Note: A <field/> element MAY contain more than one <value/> child if appropriate.</p>
|
|
<p>If the data fields are to be used in the context of a protocol approved by the XMPP Standards Foundation, they SHOULD be described in the relevant XMPP Extension Protocol specification and registered in accordance with the rules defined in XEP-0068, resulting in the inclusion of a <field/> element whose 'var' attribute has a value of "FORM_TYPE" and whose 'type' attribute has a value of "hidden".</p>
|
|
<p>An entity MUST NOT supply extended information about associated children communicated via the 'http://jabber.org/protocol/disco#items' namespace, since a core principle of <cite>Service Discovery</cite> is that an entity must define its own identity only and must not define the identity of any children associated with the entity.</p>
|
|
</section1>
|
|
<section1 topic='Examples' anchor='examples'>
|
|
<section2 topic='IM Server' anchor='examples-server'>
|
|
<p>The following is an example of including a disco extension in the IQ result sent by a standard instant messaging server.</p>
|
|
<example caption='Entity Queries Server for Information'><![CDATA[
|
|
<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>
|
|
]]></example>
|
|
</section2>
|
|
<section2 topic='Multi-User Chat Room' anchor='examples-muc'>
|
|
<p>The following is an example of including a disco extension in the IQ result sent by a Multi-User Chat room.</p>
|
|
<example caption='User Queries Room for Information'><![CDATA[
|
|
<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>
|
|
]]></example>
|
|
</section2>
|
|
</section1>
|
|
<section1 topic='Implementation Notes' anchor='impl'>
|
|
<p>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).</p>
|
|
</section1>
|
|
<section1 topic='Security Considerations' anchor='security'>
|
|
<p>Applications SHOULD ensure that information disclosed in a disco extension is appropriate for discovery by any entity on the network.</p>
|
|
</section1>
|
|
<section1 topic='IANA Considerations' anchor='iana'>
|
|
<p>This document requires no interaction with &IANA;.</p>
|
|
</section1>
|
|
<section1 topic='XMPP Registrar Considerations' anchor='registrar'>
|
|
<p>This document requires no interaction with the ®ISTRAR;; however, specifications following the best practices defined herein may register FORM_TYPEs and field values with the XMPP Registrar.</p>
|
|
</section1>
|
|
</xep>
|