Improve examples and apply consistent formatting:
* Replace wrong recipient in example by 'alice@example.org'
* Use recipient 'bob@example.com' in examples consistently
* Apply consistent formatting for revision history
Update to XEP-0420 version 0.4.0 and XEP-0434 version 0.5.0:
* Replace SCE's old 'content' element by its new 'envelope' element
* Replace SCE's old 'payload' element by its new 'content' element
* Update SCE's namespace to 'urn:xmpp:sce:1'
* Update TM's namespace to 'urn:xmpp:tm:0'
* Update namespace to 'urn:xmpp:atm:1'
Update to XEP-0420 version 0.4.0 and adapt namespace to shortname:
* Replace SCE's old 'content' element by its new 'envelope' element
* Replace SCE's old 'payload' element by its new 'content' element
* Update SCE's namespace to 'urn:xmpp:sce:1'
* Change namespace to 'urn:xmpp:tm:0'
In case the XEP has not yet a shortname assigned, the transformation
would add a superfluous line break in the postfix due a missing
<xsl:text> element.
Add usage of Trust Message URIs, use more precise sentences, apply consistent formatting:
* Add usage of Trust Message URIs for initial authentications
* Use 'that' instead of 'which' for restrictive clauses
* Apply consistent formatting for paragraphs and revision history
Add new section, use more precise sentences, apply consistent formatting:
* Add new section for Trust Message URIs
* Use 'that' instead of 'which' for restrictive clauses
* Apply consistent formatting for paragraphs and revision history
I am tired of seeing all those badly or misreferenced XEPs out
there. This produces a high-quality BibLaTeX entry that follows the
recommendations of the biblatex Package and
draft-carpenter-rfc-citation-recs-01 § 5.2 [1].
It also uses proper 'date' attribution, from the first date in the XEP
history to the date of the latest revision entry.
1: https://tools.ietf.org/html/draft-carpenter-rfc-citation-recs-01#section-5.2
Don't remember why it did this here. There's another spot where it
removes longer stretches of whitespace. Doesn't trim leading or trailing
whitespace tho, but that's what breaks it here.
Further reading and some rationale for these changes can be found at:
https://tools.ietf.org/html/draft-knodel-terminology-04
All changes are intended to be editorial in nature, not break existing
wire protocols, and not alter the meanings of any text.
