> So, for example, XEP-0141 page elements could be reordered? 

No. The spec does not know about markup mini languages like XEP-0141, XEP-0071, 
 XEP-0393 and XEP-0394. Markup is validated at the client. Order is maintained 
because the spec just encodes unknown XML into a struct that maintains child 
order. It’s just a pain to bake those into the spec.

> Fields in forms are assumed to be ordered as well,

No. The order of XData fields in a form (“x”) is maintained. It’s a list of 
fields. The order that could change is whether  the list of instructions comes 
after the list of fields.

https://github.com/processone/xmpp/blob/master/specs/xmpp_codec.spec#L2027-L2028

> On Feb 16, 2021, at 4:25 AM, Dave Cridland <[email protected]> wrote:
> 
> 
> 
> On Mon, 15 Feb 2021 at 19:03, Drew Varner <[email protected]> wrote:
> It will affect the stability of child node ordering when forwarding stanzas 
> if the model “knows” those elements.
> 
> 
> So, for example, XEP-0141 page elements could be reordered? That would seem 
> to break things rather badly. Also, of course, any structured text using XML 
> markup.
> 
> Fields in forms are assumed to be ordered as well, I think, so absent 
> XEP-0141 one could argue that the order isn't important I suppose.
> 
> Dave. 
> _______________________________________________
> Standards mailing list
> Info: https://mail.jabber.org/mailman/listinfo/standards
> Unsubscribe: [email protected]
> _______________________________________________

_______________________________________________
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: [email protected]
_______________________________________________

Reply via email to