On 31.05.2017 11:56, Daniel Gultsch wrote: > 2017-05-31 11:46 GMT+02:00 Florian Schmaus <[email protected]>: >> On 31.05.2017 11:25, Daniel Gultsch wrote: >>> 1) Add wording to XEP-0203 that the delay element MAY contain either >>> character data that provide a natural language description OR an >>> element of a different namespace describing the reason for the delay. >> >> I think a cleaner approach would be to extend <delay/> with an optional >> <reason/> element, which has an attribute whose value is defined by an >> registry established in xep203. > > Fair enough. But at this point we probably wouldn't get around bumping > XEP-0203 or would we? > But we could use the chance to get rid of the XML character content of > the delay element which is - if not wrapped in a text or something > like that - pretty ugly anway. (Since it can not be translated and > all)
I totally forgot that <delay/> has textual content defined. That is why it is good practice to wrap such content into an extra element. So we either A) bump the namespace and do it right this time B) make 'reason' an attribute of <delay/>, which doesn't require a namespace bump - Florian
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
