mirror of https://github.com/moparisthebest/xeps
no presence mentions
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@794 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre
parent
84811e3d18
commit
fd6c0d426c
78
xep-0004.xml
78
xep-0004.xml
|
|
@ -27,101 +27,107 @@
|
|||
&jer;
|
||||
&temas;
|
||||
&stpeter;
|
||||
<revision>
|
||||
<version>2.8pre1</version>
|
||||
<date>in progress, last updated 2007-05-02</date>
|
||||
<initials>psa</initials>
|
||||
<remark><p>Removed mentions of presence stanzas; added section on discovering support; added section on substantive changes in Final state.</p></remark>
|
||||
</revision>
|
||||
<revision>
|
||||
<version>2.7</version>
|
||||
<date>2006-01-25</date>
|
||||
<initials>psa</initials>
|
||||
<remark>Incorporated errata: (1) clarified rules regarding inclusion of option and value elements depending on field type; (2) clarified handling of default values; (3) added value elements to list-multi field in Example 2; (4) harmonized spelling of form-processing entity and form-submitting entity.</remark>
|
||||
<remark><p>Incorporated errata: (1) clarified rules regarding inclusion of option and value elements depending on field type; (2) clarified handling of default values; (3) added value elements to list-multi field in Example 2; (4) harmonized spelling of form-processing entity and form-submitting entity.</p></remark>
|
||||
</revision>
|
||||
<revision>
|
||||
<version>2.6</version>
|
||||
<date>2004-10-13</date>
|
||||
<initials>psa</initials>
|
||||
<remark>Incorporated errata: (1) corrected syntax of <reported/> element (<field/> element should not contain a <value/> child); (2) corrected Example 8.</remark>
|
||||
<remark><p>Incorporated errata: (1) corrected syntax of <reported/> element (<field/> element should not contain a <value/> child); (2) corrected Example 8.</p></remark>
|
||||
</revision>
|
||||
<revision>
|
||||
<version>2.5</version>
|
||||
<date>2004-05-07</date>
|
||||
<initials>psa</initials>
|
||||
<remark>Clarified terminology regarding form-processing entities and form-submitting entities; corrected several small errors in the schema.</remark>
|
||||
<remark><p>Clarified terminology regarding form-processing entities and form-submitting entities; corrected several small errors in the schema.</p></remark>
|
||||
</revision>
|
||||
<revision>
|
||||
<version>2.4</version>
|
||||
<date>2004-05-04</date>
|
||||
<initials>psa</initials>
|
||||
<remark>Per discussion by the authors and Jabber Council, specified that the 'var' attribute is required for all field types except "fixed", for which the 'var' attribute is optional.</remark>
|
||||
<remark><p>Per discussion by the authors and Jabber Council, specified that the 'var' attribute is required for all field types except "fixed", for which the 'var' attribute is optional.</p></remark>
|
||||
</revision>
|
||||
<revision>
|
||||
<version>2.3</version>
|
||||
<date>2004-03-31</date>
|
||||
<initials>psa</initials>
|
||||
<remark>Formalization and further editorial revisions.</remark>
|
||||
<remark><p>Formalization and further editorial revisions.</p></remark>
|
||||
</revision>
|
||||
<revision>
|
||||
<version>2.2</version>
|
||||
<date>2004-01-22</date>
|
||||
<initials>psa</initials>
|
||||
<remark>Editorial revisions.</remark>
|
||||
<remark><p>Editorial revisions.</p></remark>
|
||||
</revision>
|
||||
<revision>
|
||||
<version>2.1</version>
|
||||
<date>2003-02-16</date>
|
||||
<initials>psa</initials>
|
||||
<remark>Added schema.</remark>
|
||||
<remark><p>Added schema.</p></remark>
|
||||
</revision>
|
||||
<revision>
|
||||
<version>2.0</version>
|
||||
<date>2002-12-09</date>
|
||||
<initials>psa</initials>
|
||||
<remark>Per a vote of the Jabber Council, changed status to Final.</remark>
|
||||
<remark><p>Per a vote of the Jabber Council, changed status to Final.</p></remark>
|
||||
</revision>
|
||||
<revision>
|
||||
<version>1.1</version>
|
||||
<date>2002-10-15</date>
|
||||
<initials>rwe</initials>
|
||||
<remark>Call for Experience changes (see <link url="#draft-to-final">Changes Between Draft and Final</link> section). This version voted to Final on 2002-12-09.</remark>
|
||||
<remark><p>Call for Experience changes (see <link url="#draft-changes">Changes in Draft State</link> section). This version voted to Final on 2002-12-09.</p></remark>
|
||||
</revision>
|
||||
<revision>
|
||||
<version>1.0</version>
|
||||
<date>2002-04-24</date>
|
||||
<initials>psa</initials>
|
||||
<remark>Per a vote of the Jabber Council, changed status to Draft.</remark>
|
||||
<remark><p>Per a vote of the Jabber Council, changed status to Draft.</p></remark>
|
||||
</revision>
|
||||
<revision>
|
||||
<version>0.6</version>
|
||||
<date>2002-03-15</date>
|
||||
<initials>rwe</initials>
|
||||
<remark>Protocol tweaks based on Standards list discussion.</remark>
|
||||
<remark><p>Protocol tweaks based on Standards list discussion.</p></remark>
|
||||
</revision>
|
||||
<revision>
|
||||
<version>0.5</version>
|
||||
<date>2002-02-06</date>
|
||||
<initials>rwe</initials>
|
||||
<remark>Protocol tweaks based on implementation and discussion.</remark>
|
||||
<remark><p>Protocol tweaks based on implementation and discussion.</p></remark>
|
||||
</revision>
|
||||
<revision>
|
||||
<version>0.4</version>
|
||||
<date>2001-11-16</date>
|
||||
<initials>rwe</initials>
|
||||
<remark>Major redesign to attempt to clarify the scope of this document and limit what it is trying to solve.</remark>
|
||||
<remark><p>Major redesign to attempt to clarify the scope of this document and limit what it is trying to solve.</p></remark>
|
||||
</revision>
|
||||
<revision>
|
||||
<version>0.3</version>
|
||||
<date>2001-07-23</date>
|
||||
<initials>rwe</initials>
|
||||
<remark>Protocol update</remark>
|
||||
<remark><p>Protocol update</p></remark>
|
||||
</revision>
|
||||
<revision>
|
||||
<version>0.2</version>
|
||||
<date>2001-06-29</date>
|
||||
<initials>rwe</initials>
|
||||
<remark>Protocol update and DocBook version</remark>
|
||||
<remark><p>Protocol update and DocBook version</p></remark>
|
||||
</revision>
|
||||
<revision>
|
||||
<version>0.1</version>
|
||||
<date>2001-01-25</date>
|
||||
<initials>rwe</initials>
|
||||
<remark>Initial release</remark>
|
||||
<remark><p>Initial release</p></remark>
|
||||
</revision>
|
||||
</header>
|
||||
<section1 topic='Introduction' anchor='intro'>
|
||||
|
|
@ -158,7 +164,7 @@
|
|||
</field>
|
||||
</x>
|
||||
]]></code>
|
||||
<p>The &X; element qualified by the 'jabber:x:data' namespace SHOULD be included as a first-level child of an XML stanza; the stanza MAY be of any kind (&IQ;, &MESSAGE;, or &PRESENCE;), although it is RECOMMENDED to use &IQ; or &MESSAGE; (see also the restrictions enumerated below).</p>
|
||||
<p>The &X; element qualified by the 'jabber:x:data' namespace SHOULD be included either directly as a first-level child of a &MESSAGE; stanza or as a second-level child of an &IQ; stanza (where the first-level child is an element qualified by a "wrapper" namespace); see also the restrictions enumerated below.</p>
|
||||
<p>The OPTIONAL <title/> and <instructions/> elements enable the form-processing entity to label the form as a whole and specify natural-language instructions to be followed by the form-submitting entity. The XML character data for these elements SHOULD NOT contain newlines (the \n and \r characters), and any handling of newlines (e.g., presentation in a user interface) is unspecified herein; however, multiple instances of the <instructions/> element MAY be included.</p>
|
||||
<section2 topic='Form Types' anchor='protocol-formtypes'>
|
||||
<p>The data gathered or provided in a 'jabber:x:data' form can be situated in a number of different contexts. Examples include an empty form that needs to be filled out, a completed form, the results of a submission, a search result, or simply a set of data that is encapsulated using the 'jabber:x:data' namespace. The full context for the data is provided by three things:</p>
|
||||
|
|
@ -194,7 +200,6 @@
|
|||
<ul>
|
||||
<li><p>For &IQ; stanzas, the root element qualified by the "wrapper" namespace in a form of type "form" or "submit" MUST be returned in a form of type "result". The &X; element qualified by the 'jabber:x:data' namespace MUST be a child of the "wrapper" namespace's root element. As defined in &xmppcore;, the 'id' attribute MUST be copied in the IQ result. For data forms of type "form" or "result", the &IQ; stanza SHOULD be of type "result". For data forms of type "submit" or "cancel", the &IQ; stanza SHOULD be of type "set".</p></li>
|
||||
<li><p>For &MESSAGE; stanzas, the <thread/> SHOULD be copied in the reply if provided. The &X; element qualified by the 'jabber:x:data' namespace MUST be a child of the &MESSAGE; stanza.</p></li>
|
||||
<li><p>The only data form type allowed for <presence/> stanzas is "result". The &X; element qualified by the 'jabber:x:data' namespace MUST be a child of the &PRESENCE; stanza. In accordance with <cite>XMPP Core</cite>, use of data forms is not recommended unless necessary to provide information that is directly related to an entity's network availability.</p></li>
|
||||
</ul>
|
||||
</section2>
|
||||
<section2 topic='The Field Element' anchor='protocol-field'>
|
||||
|
|
@ -566,6 +571,30 @@
|
|||
]]></example>
|
||||
</section2>
|
||||
</section1>
|
||||
<section1 topic='Service Discovery' anchor='disco'>
|
||||
<p>If an entity supports inclusion of the &X; element qualified by the 'jabber:x:data' namespace as a direct child of the &MESSAGE; stanza type, it MUST report support by including a service discovery feature of "jabber:x:data" &NSNOTE; in response to a Service Discovery information request:</p>
|
||||
<example caption="Service Discovery information request"><![CDATA[
|
||||
<iq type='get'
|
||||
from='romeo@montague.net/orchard'
|
||||
to='juliet@capulet.com/balcony'
|
||||
id='disco1'>
|
||||
<query xmlns='http://jabber.org/protocol/disco#info'/>
|
||||
</iq>
|
||||
]]></example>
|
||||
<example caption="Service Discovery information response"><![CDATA[
|
||||
<iq type='result'
|
||||
from='juliet@capulet.com/balcony'
|
||||
to='romeo@montague.net/orchard'
|
||||
id='disco1'>
|
||||
<query xmlns='http://jabber.org/protocol/disco#info'>
|
||||
...
|
||||
<feature var='jabber:x:data'/>
|
||||
...
|
||||
</query>
|
||||
</iq>
|
||||
]]></example>
|
||||
<p>If an entity supports data forms indirectly through inclusion of data forms in a wrapper namespace (rather than directly within a &MESSAGE; stanza), it MUST NOT advertise support for the 'jabber:x:data' namespace, since support is implicit in support for the wrapper protocol.</p>
|
||||
</section1>
|
||||
<section1 topic='Security Considerations' anchor='security'>
|
||||
<p>There are no security concerns related to this specification above and beyond those described in the relevant section of <cite>XMPP Core</cite>.</p>
|
||||
</section1>
|
||||
|
|
@ -694,10 +723,17 @@
|
|||
</xs:schema>
|
||||
]]></code>
|
||||
</section1>
|
||||
<section1 topic='Changes Between Draft and Final' anchor='draft-to-final'>
|
||||
<p>The following protocol changes were incorporated in the Final specification as a result of experience with the Draft specification (described in version 1.0 of this document):</p>
|
||||
<section1 topic='Changes in Final State' anchor='final-changes'>
|
||||
<p>The following substantive protocol changes have been made while this specification has been in the Final state:</p>
|
||||
<ul>
|
||||
<li>The <x/> element MAY be included in <message/> and <presence/> elements.</li>
|
||||
<li>Specified that the 'var' attribute is required for all field types except "fixed", for which the 'var' attribute is optional.</li>
|
||||
<li>Specified when to advertise support via service discovery.</li>
|
||||
</ul>
|
||||
</section1>
|
||||
<section1 topic='Changes in Draft State' anchor='draft-changes'>
|
||||
<p>The following substantive protocol changes were made while this specification was in the Draft state:</p>
|
||||
<ul>
|
||||
<li>The <x/> element MAY be included directly in <message/> stanzas.</li>
|
||||
<li>The <x/> element MAY contain a <title/> child for forms and results.</li>
|
||||
<li>The <x/> element MUST possess a 'type' attribute.</li>
|
||||
<li>A <field/> element MAY be of type='jid-single'.</li>
|
||||
|
|
|
|||
Loading…
Reference in New Issue