Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Avoid "we" except in the acknowledgements. #15

Merged
merged 2 commits into from
Jun 22, 2024
Merged

Avoid "we" except in the acknowledgements. #15

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ad3d8fa
Avoid "we" except in the acknowledgements.
cabo Jun 19, 2024
2230436
Update draft-ietf-cbor-update-8610-grammar.md
cabo Jun 20, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions draft-ietf-cbor-update-8610-grammar.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -145,13 +145,13 @@ This allows almost any non-C0 character to be escaped by a backslash,
but critically misses out on the `\uXXXX` and `\uHHHH\uLLLL` forms
that JSON allows to specify characters in hex (which should be
applying here according to Bullet 6 of {{Section 3.1 of -cddl}}).
(Note that we import from JSON the unwieldy `\uHHHH\uLLLL` syntax,
(Note that CDDL imports from JSON the unwieldy `\uHHHH\uLLLL` syntax,
which represents Unicode code points beyond U+FFFF by making them look
like UTF-16 surrogate pairs; CDDL text strings are not using UTF-16 or
surrogates.)

Both can be solved by updating the SESC production.
We use the opportunity to add a popular form of directly specifying
This document uses the opportunity to add a popular form of directly specifying
characters in strings using hexadecimal escape sequences of the form
`\u{hex}`, where `hex` is the hexadecimal representation of the
Unicode scalar value.
Expand All @@ -178,7 +178,7 @@ sourcecode-name="cddl-new-sesc.abnf"}
(Notes:
In ABNF, strings such as `"A"`, `"B"` etc. are case-insensitive, as is
intended here.
We could have written `%x62` as `%s"b"`, but didn't, in order to
The rules above could, instead of `%x62`, also have used `%s"b"` etc., but didn't, in order to
maximize ABNF tool compatibility.)

Now that SESC is more restrictively formulated, this also requires an
Expand All @@ -203,7 +203,7 @@ As U+007F is not printable, including it in a byte string literal is
as confusing as for a text string literal, and it should therefore be
excluded from BCHAR as it is from SCHAR.
The same reasoning also applies to the C1 control characters,
so we actually exclude the entire range from U+007F to U+009F.
so the updated ABNF actually excludes the entire range from U+007F to U+009F.
The same reasoning then also applies to text in comments (PCHAR).
For completeness, all these should also explicitly exclude the code
points that have been set aside for UTF-16's surrogates.
Expand Down Expand Up @@ -394,8 +394,8 @@ ultimately make up the module created by the file.
Any other rule content in the file has to be available for directive
processing, making the requirement for at least one rule cumbersome.

Therefore, we extend the grammar as in {{empty-new}}
and make the existence of at least one rule a semantic constraint, to
Therefore, the present update extends the grammar as in {{empty-new}}
and turns the existence of at least one rule into a semantic constraint, to
be fulfilled after processing of all directives.

~~~ abnf
Expand Down
Loading