The post content itself can be either text (content element without "type" attribute or with "type" attribute with "text" value) or XHTML ("content" element "type" attribute with "xhtml" value). If Romeo publishes XHTML content, his client MUST publish two "content" elements: a text one, and a XHTML one. For XHTML publishing, see Publish-Subscribe (XEP-0060).https://xmpp.org/extensions/xep-0277.xml#publish
While there is a fairly obvious interpretation here if the type attributes differ, I agree with your reading of the RFC that it is invalid to have multiple content. Thus we should fix the XEP and also any software currently following the XEP example.
I will send a request to modify that paragraph in favour of element "atom:link".
I doubt there is any benefit to bending over backward to include such a link, though of course someone could if they want to in pracise I doubt they will and I don't think we need to mention it specifically in the XEP.
Realistically, no one is using the "fallback" content much anyway and it's clear from the RFC that they didn't consider this a reasonable use case which I mostly agree with in hindsight.
signature.asc
Description: PGP signature
_______________________________________________ Standards mailing list -- [email protected] To unsubscribe send an email to [email protected]
