[Standards] Field Standardization for http://jabber.org/protocol/pubsub#publish-options
christian.schudt at gmx.de
Sat Nov 1 20:21:26 UTC 2014
XEP-0060 specifies Field Standardization for publish-options with only one field ("pubsub#access_model“):
However, XEP-0222 and XEP-0223 uses more fields for the "http://jabber.org/protocol/pubsub#publish-options“ form type:
What does it mean? Is XEP-0060 lacking some fields or are those configuration forms just very liberal and/or service dependant?
E.g. if I include "pubsub#persist_items“ in the publish options, I am using a non-standardized field (as per XEP-0060) and theoretically can’t be sure, that the server interprets it right.
On the other hand I am encouraged to do so as per XEP-0222.
Can configuration forms be "extended" at will?
Some clarification is appreciated.
And btw: <publish-options> is missing in the XML schema in XEP-0060.
More information about the Standards