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

Review of Compliance Warden Architecture #72

Open
dukesook opened this issue Nov 3, 2023 · 3 comments
Open

Review of Compliance Warden Architecture #72

dukesook opened this issue Nov 3, 2023 · 3 comments

Comments

@dukesook
Copy link
Contributor

dukesook commented Nov 3, 2023

#67 No, the effort is not abandoned. But I wanted to review a plan of implementation with fresh eyes.

Originally, I envisioned having an uncompressed specification that the user could select from. I also want to eventually add JPEG 2000 & HT-J2K. Following this pattern, the user would have to know which specification to select in order to test their file.

It would be nice is the Compliance Warden determine compliance without this spec parameter. Could this be done by parsing the ftyp box and then running the appropriate specs?

I still haven't studied the code very much yet, but these are some of my initial thoughts. Just thinking out loud.

@rbouqueau
Copy link
Member

Could this be done by parsing the ftyp box and then running the appropriate specs?

We could introduce an "auto" mode based on some probing.

@dukesook
Copy link
Contributor Author

dukesook commented Nov 3, 2023

I think an "auto" mode would be great. Hopefully that wouldn't be too difficult to implement.

@rbouqueau
Copy link
Member

Don't hesitate to open specific issues. That would allow to trigger specific discussions if other people are also interested.

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