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

range attribute vs restriction element #410

Open
robUx4 opened this issue May 30, 2021 · 1 comment
Open

range attribute vs restriction element #410

robUx4 opened this issue May 30, 2021 · 1 comment
Labels
bug errata-rfc8794 Errors found in RFC 8794
Milestone

Comments

@robUx4
Copy link
Contributor

robUx4 commented May 30, 2021

Following the 2021-05-25 IETF meeting, we discussed the issue of elements that have a range attribute but also have a restriction element.

In Matroska there are elements like TrackEntry\TrackType TrackEntry\Video\FieldOrder that have both elements and some missing values in the possible range. It seems when there is a restriction element set, the range value is redundant and confusing. We should make them mutually exclusive.

@hubblec4
Copy link

Yes, if a restriction is present then is no reason to have a range attribute, because the restriction is more precise.

@robUx4 robUx4 added this to the new-rfc milestone Jul 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug errata-rfc8794 Errors found in RFC 8794
Projects
None yet
Development

No branches or pull requests

2 participants