On 2/10/21 6:54 PM, Dave Cridland wrote:> There's a few options.

1) We ignore the problem.
2) We note that there may exist implementations which rely on the ordering, but say receivers MUST NOT rely on ordering. 3) We note that there may exist implementations which rely on the ordering, and say sender SHOULD order.
4) A combination of both 2 and 3.

The safest for interoperability is probably (4), but I am easy to please, I just need some idea of whether any implementations (still) exist which rely on the ordering.

I don't care about SHOULD/MUST here, hence I would also be fine with 3).

Since you asked: Smack relies on the ordering (in case a non-default form field type is used), since Smack needs to see the <reported/> first to assign types to the field while parsing the following <item/>s.

- Florian

Attachment: OpenPGP_signature
Description: OpenPGP digital signature

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

Reply via email to