Consistent HTML formatting #315
Conversation
index.html
Outdated
| with JSON Object Signing and Encryption | ||
| (<a href="https://datatracker.ietf.org/wg/jose/about/">JOSE</a>), | ||
| Selective Disclosure for JWTs [[SD-JWT]], and CBOR Object Signing and | ||
| Encryption (COSE) [[RFC9052]]. This enables the Verifiable Credential |
There was a problem hiding this comment.
"CBOR Object Signing and Encryption" is broken across lines, when it's a term that should be searchable and so needs to be on a single line.
index.html
Outdated
| // ReSpec | ||
| var respecConfig = { | ||
| group: "vc", | ||
|
|
There was a problem hiding this comment.
It's better not to have any whitespace at the end of lines.
There was a problem hiding this comment.
If we're going to change the line breaks in the source, we should be employing Semantic Line Breaks, so that the source can easily be searched for terms because the terms are never broken across lines.
The simple form of these rules is that:
- Line breaks should never occur within a sentence, except after punctuation marks, such as commas.
- There should always be a line break after periods ending sentences (but not those indicating abbreviations).
Before we merge this, I'd also like to understand how we are going to verify that no changes to the output occurred. (When doing changes like this, it's easy for stray characters to creep in or be deleted due to manual errors.)
Thanks.
|
I've applied (most of) the feedback. I believe the html is more readable now. I've removed trailing whitespaces and checked for any lost content (could not find anything). |
|
only formatting changes. merging. |
No normative changes. Purely editorial for consistency.
Preview | Diff