On 29.09.2017 16:18, Sam Whited wrote: > On Fri, Sep 29, 2017, at 05:38, Florian Schmaus wrote: >> But this leads to a very ugly protocol design where an additional extension >> element carrying the mapping information from item ID to item "version" >> is required. I think this is good case very namespaced attributes would >> really shine. > > Presumably if you were using the namespaced > attributes you would put them on the item, like so: > > <item id='4e30f35051b7b8b42abe083742187228' > caps:value='67f7f792-f2ee-4918-8894-36a3c4a6dd5f'> > … > </item>
Yes, exactly. > However, you could equally make it an element in the item: > > <item id='4e30f35051b7b8b42abe083742187228''> > <caps > > xmlns='urn:xmpp:pubsub:cap:0'>67f7f792-f2ee-4918-8894-36a3c4a6dd5f</caps> > … > </item> I don't think we should (or even could) inject stuff into the item's payload. - Florian
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
