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

Add context to <assert> #3010

Open
leo-barnes opened this issue Jan 17, 2025 · 2 comments
Open

Add context to <assert> #3010

leo-barnes opened this issue Jan 17, 2025 · 2 comments

Comments

@leo-barnes
Copy link

We have a case where we have the same SHALL statements that we would like to have <assert> around, but in multiple sections. Currently these generate the same assert ID, but we would ideally want to be able to add a context to the assert so that we get a different ID for each section.

What's the best way of doing this? Can we add some kind of hidden context to the text that does not show up?

AOMediaCodec/av1-avif#299

@leo-barnes
Copy link
Author

We have this:

<h3 id="baseline-profile"><dfn export>AVIF Baseline Profile</dfn></h3>
...
The following shared conditions and requirements from [[!MIAF]] should apply:
    - <assert>[=grid-limit=] (subclause 8.4)</assert>
    - <assert>[=single-track=] (subclause 8.5)</assert>
    - <assert>[=edit-lists=] (subclause 8.6)</assert>
...
<h3 id="advanced-profile"><dfn export>AVIF Advanced Profile</dfn></h3>
...
The following shared conditions and requirements from [[!MIAF]] should apply:
    - <assert>[=grid-limit=] (subclause 8.4)</assert>
    - <assert>[=single-track=] (subclause 8.5)</assert>
    - <assert>[=edit-lists=] (subclause 8.6)</assert>

It would be great if we could do something like <assert for="baseline-profile"> and <assert for="advanced-profile">

@tabatkins
Copy link
Collaborator

Yeah, a for attribute (and an assert-for you can put on an ancestor, which'll carry down into any asserts) that gets included in the hash generation seems like the most straightforward way to handle this.

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

No branches or pull requests

2 participants