On 11/19/09 3:21 AM, Fabio Forno wrote: > On Thu, Nov 19, 2009 at 12:20 AM, Peter Saint-Andre <[email protected]> > wrote: > >> ###### >> >> 7.1.2.4 Item Versioning >> > [...] >> The combination of the ItemID and 'ver' MUST be unique, such that a >> subsequent publish with the same ItemID MUST have a different value of >> the 'ver' attribute than the earlier published item. >> > > This part for my understanding is not clear. First of all I think the > uniqueness of 'ver' and 'ItemId' refers to the node only, moreover I > wouldn't say that a publish must have a new 'ver' , since the > publisher shouldn't add any 'ver' attribute at all. Imho we should say > something like for any subsequent publish the service MUST produce a > new 'ver' attribute.
If 'ver' for pubsub nodes is conceptually equivalent to 'ver' for rosters, then 'ver' refers to the "state" of the node itself (i.e., all the items ever published at the node). Therefore it does not exist at the item level but at the node level, so 'ver' + ItemID is not a unique combination (as you say). However, anytime a new item is published to the node then then 'ver' needs to change. Correct? Peter -- Peter Saint-Andre https://stpeter.im/
smime.p7s
Description: S/MIME Cryptographic Signature
