moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-12-21 23:28:51 -05:00
Code Issues Releases Wiki Activity

1.13rc11

Browse Source 
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@3679 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2009-12-03 18:35:29 +00:00
parent a4f3be37f7
commit 84a6d463b5
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
xep-0060.xml
View File

@ -51,8 +51,8 @@
&ralphm;
<revision>
<version>1.13rc10</version>
<date>in progress, 2009-12-02</date>
<version>1.13rc11</version>
<date>in progress, 2009-12-03</date>
<initials>psa</initials>
<remark>
<ul>
@ -77,7 +77,7 @@
<li>Removed the notion of batch publishing because it makes information coherence and atom handling excessively difficult.</li>
<li>Added error handling for too-many-subscriptions to help prevent a certain denial of service attack.</li>
<li>Added process for retrieving default subscription configuration options for leaf nodes, by omitting the 'node' attribute on the &lt;default/&gt; element (also added the &lt;default/&gt; element to the schema for the http://jabber.org/protocol/pubsub namespace, since it was missing).</li>
<li>Added optional data versioning via the 'ver' attribute on the &lt;item/&gt; and &lt;items/&gt; elements, along with associated pubsub#versioning configuration field.</li>
<li>Added optional data versioning via the 'ver' attribute on the &lt;item/&gt; element (item-level versioning) and &lt;items/&gt; element (node-level versioning), along with associated pubsub#versioning configuration field.</li>
</ul>
</remark>
</revision>
@ -4757,8 +4757,8 @@ And by opposing end them?
</section1>
<section1 topic='Data Versioning' anchor='versioning'>
<p>A service MAY track the "version" of data published at a node, in the form of the version across all published items, the version of each particular item, or both. The version is tracked using the 'ver' attribute, which can be included on the &lt;items/&gt; element or the &lt;item/&gt; element.</p>
<p class='def'><strong>Definition:</strong> The <strong>'ver' attribute</strong> is a string that identifies a particular version of the items published at a node or of a particular item. The value MUST be generated only by the server, MUST NOT be accepted by the service from the publisher, and MUST be treated by the client as opaque. The server can use any appropriate method for generating the version ID, such as a hash of the published data or a strictly-increasing sequence number.</p>
<p>A service MAY track the "version" of data published at a node, in the form of the version across all published items ("node-level versioning"), the version of each particular item ("item-level versioning"), or both. The version is tracked using the 'ver' attribute, which is included on the &lt;items/&gt; element for node-level versioning and on the &lt;item/&gt; element for item-level versioning.</p>
<p class='def'><strong>Definition:</strong> The <strong>'ver' attribute</strong> is a string that identifies a given version of the collective items published at a node, or of a particular item. The value of a node-level version identifier MUST be generated only by the service, MUST NOT be accepted by the service from a publisher. The value of an item-level version identifier MAY be accepted by a service from a publisher, but if not included SHOULD be generated by the service. Version identifiers MUST be treated by subscribers as opaque, but MAY have meaning to publishers. Any appropriate method can be used for generating version identifiers, such as a hash of the published data or a strictly-increasing sequence number.</p>
<p>Note: The value of the 'ver' attribute is conceptually equivalent to the 'ver' attribute from &xep0237;.</p>
<p>If a service supports data versioning, it MUST advertise a feature of "http://jabber.org/protocol/pubsub#versioning".</p>
<section2 topic='Versioning of All Items' anchor='versioning-items'>