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

Address Apple's FO #85

Closed
nigelmegitt opened this issue Mar 8, 2023 · 1 comment · Fixed by #86
Closed

Address Apple's FO #85

nigelmegitt opened this issue Mar 8, 2023 · 1 comment · Fixed by #86
Labels

Comments

@nigelmegitt
Copy link
Contributor

@gkatsev @hober @dwsinger and @nigelmegitt met to discuss Apple's FO and potential resolutions to it. We determined that changing the success criteria factors of verification 2nd bullet from "content implementation" to "content-producing implementation" would allow Apple to remove their objection.

One of the clarifications in understanding that I had during that discussion was that in the case of a private implementation, say one created and used by a broadcaster or content provider, an assertion that the implementation exists plus a significant corpus of content from that implementation, would be enough to satisfy the criterion that a "content-producing implementation" exists.

Another is that a content-producing implementation that is asserted to meet any validation requirements in the specification in question does not necessarily have to be a validating implementation: for example, the implementer could arrange for tighter authoring constraints to be in place than are strictly needed, with the intention that the output cannot be invalid, without running a validator on the implementation's output.

On this basis I will propose a pull request that implements this proposal.

@palemieux
Copy link
Contributor

On this basis I will propose a pull request that implements this proposal.

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants