Update to XEP-0434 version 0.6.0 and XEP-0384 version 0.8.0:
* Use Base64-encoded key identifiers in examples
* Update TM's namespace to 'urn:xmpp:tm:1'
* Update OMEMO's namespace to 'urn:xmpp:omemo:2'
The requirement to strip `<private/>` by the sending server was in the
XEP from day 1. It was later changed from "MUST" to "SHOULD" and from
"sending server" to "receiving server", so that the latter could also
prevent normal message routing.
As this behavior only ever affected the `<private/>` element and not the
`<no-copy/>` hint (introduced in 2017), which should be treated in a
similar but not equal way, and there is a security benefit in letting
the receiving client know that message routing was manipulated, it makes
sense to remove this requirement.
As there is no negative effect of keeping another element in delivered
messages, nobody complained about `<no-copy/>` not being stripped, and
bumping Carbons today would be rather unfortunate, this is done without
a namespace bump, despite "breaking" the specification.
Currently this only explains the difference between the before/after
parameters of RSM and the before-id/after-id parameters of mam#extended.
Signed-off-by: Sam Whited <sam@samwhited.com>
- Add a way to discover on which protocols Order-By applies
- Remove references to SQL (except in implementation notes)
- Specify that order-by operate on the whole item set and inside a RSM result set
- Explicitly says that creation and modification dates are set by Pubsub service itself
- Specify that Clark notation should be used for extensions
- Add a full example with Pubsub and RSM
- Add hint for SQL based implementations
- removed XEP-0060 and XEP-0313 as dependencies, they are mentioned as use cases, but are not mandatory
- better wording following feedback
- Namespace bump
