Skip to content

Emphasize the bounds can be dymanically adjusted by implements#53

Merged
tunetheweb merged 4 commits intow3c:mainfrom
guohuideng2024:main
Jan 19, 2026
Merged

Emphasize the bounds can be dymanically adjusted by implements#53
tunetheweb merged 4 commits intow3c:mainfrom
guohuideng2024:main

Conversation

@guohuideng2024
Copy link
Copy Markdown
Member

@guohuideng2024 guohuideng2024 commented Jan 9, 2026

And remove the recommend bounds that are out of date.

Also add "Guohui Deng" to the spec editor list.

Bug:#50

And remove the recommend bounds that are out of date.

Bug:w3c#50
@guohuideng2024
Copy link
Copy Markdown
Member Author

quote from the current README file:
The upper and lower bounds are not explicit, as they are subject to change over time.

quote from the current index.bs file (official spec):
NOTE: While implementations may choose different values, the recommended upper bound is 8GiB and the recommended lower bound is 0.25GiB (or 256MiB).

It appears to me the original consensus is that the spec doesn't specify concrete bound values but let the implementations to decide and the values can be adjusted over time.

However, the documents also recommend explicit values that inevitably would become dated and causes confusing.

This PR removes the explicit values and emphasizes that the implementations can adjust the bound values. It makes it clear that adjusting the bounds to values different from the old recommend values is not a violation of the spec.

@tunetheweb
Copy link
Copy Markdown
Member

@guohuideng2024 as discussed can we add an explicit mention that implementors may also choose different max/min boundaries per device? Then we're good to merge!

@guohuideng2024
Copy link
Copy Markdown
Member Author

@guohuideng2024 as discussed can we add an explicit mention that implementors may also choose different max/min boundaries per device? Then we're good to merge!

Now the text mentions the boundaries can differ on different device types without mentioning "geographic regions".

@guohuideng2024 guohuideng2024 marked this pull request as ready for review January 16, 2026 17:44
Copy link
Copy Markdown
Member

@tunetheweb tunetheweb left a comment

Choose a reason for hiding this comment

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

I updated the examples as well.

Good to merge now.

@tunetheweb tunetheweb merged commit 8eebca0 into w3c:main Jan 19, 2026
2 checks passed
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