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.
It is important for form consuming entities which validate the form
field types that the <reported/> element appears before any <item/>
element in result forms. This is because the <reported/> element
contains the information about the field type of the fields. So if a
form has any <item/> before <reported/>, valididating entites would
need two passes to parse the form: the first pass to parse <reported/>
and the second one to parse the fields in <item/>s.
I consider this a non-breaking change, and just a clarification of the
XEP authors intention.
