[Standards] Re: [jdev] XEP-0115: Entity Capabilities

Peter Saint-Andre stpeter at jabber.org
Tue Jul 3 03:29:41 UTC 2007

Mridul Muralidharan wrote:
> Peter Saint-Andre wrote:
>> Mridul Muralidharan wrote:
>>> Peter Saint-Andre wrote:
>>>> Mridul Muralidharan wrote:
>>>>> Forgot to add, change name from ver & ext to verh and exth ?
>>>> Why?
>>> Conflict with existing clients - too many of them in the wild dont use
>>> these semantics.
>> But introducing new attributes is backward-incompatible, no?
>> Given that both the 'ver' and 'ext' attributes have no semantic meaning
>> in XEP-0115 right now, I don't see why it is a problem to use those
>> attribute names. In fact we're adding semantic meaning with the hashes,
>> but existing clients should work just fine AFAICS.
>> /psa
>   When new clients attempt to interop with existing clients, they will
> not be able to do so - since none of the ver/ext exhibited by existing
> clients will match what gets generated through the md5/sha/etc sum of
> features & capabilities when newer clients attempt to validate this.

Well I read over the proposals on the way home and I realized that the
hash approach is quite different and can't be retrofitted onto caps as
it is today. Hrm. Further thought required...


Peter Saint-Andre
XMPP Standards Foundation

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 7358 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20070702/46cdbe93/attachment.bin>

More information about the Standards mailing list