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.

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

Refer to byte/bit sequences instead of octet/bit strings #397

Merged
merged 7 commits into from
Jan 9, 2025
Merged

Conversation

twiss
Copy link
Member

@twiss twiss commented Jan 7, 2025

Builds on top of #396.

Refer to Infra's byte sequences instead of defining our own octet string concept, and rename bit strings to bit sequences to match. Also, link to Infra's byte sequence/length where appropriate, and properly define the length in bits.


Preview | Diff

@twiss twiss requested a review from annevk January 7, 2025 19:50
Copy link
Member

@annevk annevk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I skimmed through this, but this looks correct to me. Thanks for aligning the language, that'll help future readers.

@@ -612,24 +612,26 @@ <h2>Terminology</h2>
{{BufferSource}} are defined in [[WEBIDL]].
</p>
<p>
An <dfn id="dfn-octet-string">octet string</dfn> is an ordered sequence of zero or more
integers, each in the range 0 to 255 inclusive.
The term [= byte sequence =] is defined in [[Infra]].
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typically you have a line like this:

This specification depends on the Infra Standard. [INFRA]

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I was looking at that for #268, but there's still a few other inconsistencies with the language there, so I'll add that later 😊

@twiss
Copy link
Member Author

twiss commented Jan 9, 2025

Thanks for the reviews!

@twiss twiss merged commit efe2685 into main Jan 9, 2025
2 checks passed
@twiss twiss deleted the byte-sequences branch January 9, 2025 09:10
github-actions bot added a commit that referenced this pull request Jan 9, 2025
SHA: efe2685
Reason: push, by twiss

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants