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

Validate CDDL extracts during curation step #1417

Open
tidoust opened this issue Dec 17, 2024 · 0 comments
Open

Validate CDDL extracts during curation step #1417

tidoust opened this issue Dec 17, 2024 · 0 comments

Comments

@tidoust
Copy link
Member

tidoust commented Dec 17, 2024

Reffy now produces CDDL extracts (see #1353). These CDDL extracts are provided as-is with no guarantee whatsoever. Ideally, we'd be able to provide additional guarantees:

  1. Syntax-wise, the CDDL extracts should be valid. This requires making sure that the CDDL can be parsed. cddlparser could perhaps be used but then it's in Python. The main other alternatives are cddl written in Rust and cddlc written in Ruby.
  2. Semantic-wise, the CDDL should "make sense". Additional checks could be done directly by the CDDL parser (e.g. no duplicate rules) and we probably don't need to go much deeper than that. Ideally though, the semantic checks would also consider the combination of CDDL extracts that share the same namespace. This requires a mechanism to tell how CDDL extracts need to be combined. For example, the CDDL defined in WebDriver BiDi is extended by Permissions and Web Bluetooth but these extensions are only noted informatively in WebDriver BiDi. The extension mechanism could perhaps leverage CDDL Module Structure.
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

1 participant