Am Sa., 8. Aug. 2020 um 07:07 Uhr schrieb Ruslan N. Marchenko <[email protected]>: > > Hi Standards, > > I'm trying to extend PEP server implementation to support OMEMO and > stumbled upon following issue: the OMEMO 5.3.2 stipulates the max_items > should be specified in the publish-options form, however neither form > registry nor XEP-0060 allow anything but access-model in the publishing > options. > > Is it my mis-interpretation of the form registry enforcement or OMEMO > needs to add a statement that it is going to extend the registery with > additional fields? > > I.e. I know the form can contain any arbitrary data just wonder if any > implementation applies some additional validation of the publish > options which may lead to iq errors. Or if such options would simply be > ignored and needs to be done via additional node configration > roundtrip? >
Quoting XEP-0060 here: > A pub-sub service advertising support for publishing options MUST check each > precondition field against the node configuration of the same name, and it > MUST reject the publication upon encountering unknown fields. *of the same name*. This means the publish option doesn’t need to be registered. Just the node configuration field. cheers Daniel _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
