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

“these APIs” is ambiguous #283

Closed
ddorwin opened this issue Jul 22, 2016 · 3 comments
Closed

“these APIs” is ambiguous #283

ddorwin opened this issue Jul 22, 2016 · 3 comments
Assignees
Milestone

Comments

@ddorwin
Copy link
Contributor

ddorwin commented Jul 22, 2016

The spec refers to the APIs defined in the EME specification as these APIs 22 times. While longer, we may want to say “the APIs [defined] in this specification” instead.

As an example, in the following statement from https://w3c.github.io/encrypted-media/#direct-individualization, a section outside any of the objects, it might not be clear which APIs we are referring to. (We’re mostly referring to “message” events and similar.)

MUST NOT be passed to or through the application via these APIs.

@ddorwin ddorwin added this to the V1Editorial milestone Jul 22, 2016
@ddorwin
Copy link
Contributor Author

ddorwin commented Aug 2, 2016

Unless there are comments or suggestions, I'll plan to replace "these APIs" with "the APIs defined in this specification" tomorrow.

@ddorwin ddorwin self-assigned this Aug 2, 2016
@mwatson2
Copy link
Contributor

mwatson2 commented Aug 2, 2016

Sounds good to me.

ddorwin added a commit to ddorwin/encrypted-media that referenced this issue Aug 3, 2016
@ddorwin
Copy link
Contributor Author

ddorwin commented Aug 3, 2016

PR #291.

@ddorwin ddorwin closed this as completed in 8fbdab6 Aug 8, 2016
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