[Standards] XEP-0372 references pointing to different elements in same stanza

JC Brand lists at opkode.com
Fri Sep 10 06:34:39 UTC 2021

On 09.09.21 19:22, Sam Whited wrote:
> Seems like we might as well use the element name since that has to be
> unique; one less unique ID to store.
Element names are not unique. For example, you can have multiple <text> 
elements in a PEP message.

This is why my request is for the "anchor" attribute of the <reference> 
to use a URI fragment to point to the "id" attribute of the element 
being referenced.

> Also if you have a schema, structs,
> etc. in your language of choice you now don't have to go update them for
> every possible element to add an id attribute, there aren't conflicts
> with anything that already has an id attribute that we inevitably will
> want to reference in the future, etc.
> That being said, my concern is that some libraries would treat
> <subject/> as "{}subject" and some would treat it as
> "{jabber:client}subject".
> —Sam
> On Thu, Sep 9, 2021, at 13:15, Kevin Smith wrote:
>> It’s not the element name, it’s just (possibly unfortunately) the same
>> in that example. It’s the id.
> _______________________________________________
> Standards mailing list
> Info: https://mail.jabber.org/mailman/listinfo/standards
> Unsubscribe: Standards-unsubscribe at xmpp.org
> _______________________________________________

More information about the Standards mailing list