moparisthebest
/
xeps
mirror of https://github.com/moparisthebest/xeps
1
0
Fork 0
Code Issues Releases Wiki Activity

feedback from ralphm 

git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1103 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2007-07-31 22:25:03 +00:00
parent 5bf334fef4
commit b002951d6b
1 changed files with 10 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
xep-0060.xml
View File

@ -1502,7 +1502,7 @@ And by opposing end them?
</pubsub>
</iq>
]]></example>
<p>Note: The foregoing example shows some (but by no means all) of the possible configuration options that MAY be provided. If an implementation provides these options using the <strong>Data Forms</strong> protocol, it MUST use the field variables that are registered with the XMPP Registrar in association with the 'http://jabber.org/protocol/pubsub' namespace (a preliminary representation of those field variables is shown above and in the <link url='#registrar-formtypes-options'>pubsub#subscribe_options FORM_TYPE</link> section of this document, but MUST NOT be construed as canonical since the XMPP Registrar may standardize additional fields at a later date without changes to this document).</p>
<p>Note: The foregoing example shows some (but by no means all) of the possible configuration options that MAY be provided. If an implementation provides these options using the <strong>Data Forms</strong> protocol, it MUST use the field variables that are registered with the XMPP Registrar in association with the 'http://jabber.org/protocol/pubsub' namespace (a preliminary representation of those field variables is shown above and in the <link url='#registrar-formtypes-subscribe'>pubsub#subscribe_options FORM_TYPE</link> section of this document, but MUST NOT be construed as canonical since the XMPP Registrar may standardize additional fields at a later date without changes to this document).</p>
<p>Note: Many of the relevant data form fields are of type "boolean" and MUST be handled accordingly. &BOOLEANNOTE;</p>
<p>There are several reasons why the options request might fail:</p>
<ol>
@ -2505,7 +2505,7 @@ And by opposing end them?
<p>A pubsub service MAY automatically create a node when it receives a publish request sent to a node that does not exist (instead of returning an &notfound; error). When doing so, the service SHOULD apply the default node configuration. If a service supports this functionality, it MUST advertise that fact by including a feature of "http://jabber.org/protocol/pubsub#auto-create" in its disco#info responses.</p>
</section3>
<section3 topic='Publishing Options' anchor='publisher-publish-options'>
<p>A pubsub service MAY support the ability to specify options along with a publish request. Here is an example:</p>
<p>A pubsub service MAY support the ability to specify options along with a publish request (if so, it MUST advertise support for the "http://jabber.org/protocol/pubsub#publish-options" feature). Here is an example:</p>
<example caption='Publishing with options'><![CDATA[
<iq type='set'
from='hamlet@denmark.lit/blogbot'
@ -2546,8 +2546,8 @@ And by opposing end them?
]]></example>
<p>The following rules apply:</p>
<ol>
<li>The &lt;publish-options/&gt; element MUST contain a data form (see <cite>XEP-0004</cite>).</li>
<li>The FORM_TYPE of the data form MUST be "http://jabber.org/protocol/pubsub#publish-options" (see <cite>XEP-0068</cite>).</li>
<li>The &lt;publish-options/&gt; element SHOULD contain a data form (see <cite>XEP-0004</cite>).</li>
<li>If a data form is included, the FORM_TYPE SHOULD be "http://jabber.org/protocol/pubsub#publish-options" (see <cite>XEP-0068</cite>).</li>
<li>Fields registered with the XMPP Registrar for that FORM_TYPE MUST specify how they are to be handled by the form-processing entity.</li>
</ol>
<p>Specifically, the following field handling methods are defined:</p>
@ -4993,6 +4993,12 @@ And by opposing end them?
<td>REQUIRED</td>
<td><link url='#publisher-publish'>Publish an Item to a Node</link></td>
</tr>
<tr>
<td>publish-options</td>
<td>Publishing an item with options is supported.</td>
<td>OPTIONAL</td>
<td><link url='#publisher-publish-options'>Publishing Options</link></td>
</tr>
<tr>
<td>publisher-affiliation</td>
<td>The publisher affiliation is supported.</td>