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

Normative References #227

Closed
halindrome opened this issue Aug 10, 2016 · 1 comment
Closed

Normative References #227

halindrome opened this issue Aug 10, 2016 · 1 comment
Assignees

Comments

@halindrome
Copy link
Contributor

The spec currently has normative references to two W3C specifications that are not under our control and may not be mature when we want to proceed down the Recommendation track.

[POWERFUL-FEATURES] is a reference to the Secure Contexts spec. I have no concerns about our requiring secure contexts, but we should not have a normative reference to this spec unless we are certain it will be mature. An informative reference may be sufficient.

[WEBIDL] First we are referring to WebIDL level 1... there are features in level 2 that are pretty interesting, but level 2 is far behind on the W3C Rec Track. In any case, we should be certain we are not using any level 2 features. Also, we should be using their recommended text about IDL Fragment Definitions as defined in https://www.w3.org/TR/WebIDL-1/#referencing . Finally, we should be sure that WEBIDL is on pace to be at least a PR when we proceed to Rec or we will potentially be delayed waiting for that spec to mature.

@adrianba
Copy link
Contributor

I've updated the spec to refer to WebIDL-2, since we are actually using some newer WebIDL capabilities. I'm not too worried about this normative reference - we have been moving API specifications with IDL dependencies to Recommendation for a while despite dependencies on WebIDL-1, which is in the process of transitioning to Proposed Rec. I anticipate that we will need to follow the same processes for WebIDL-2.

The spec already used the language for a conforming user agent (the second part of the #referencing) link. I compared this to other API specifications and this seems sufficient. If you want to add more, please propose specific text.

I updated the [POWERFUL-FEATURES] reference to [SECURE-CONTEXTS] now that SpecRef supports this name. I also changed this to an informative reference since the only mention of "secure context" is in a note (except for the [SecureContext] attribute, which is defined in WebIDL.

I hope #259 resolves this issue. If you don't believe so then please reopen and provide concrete text that we can add to close it.

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

3 participants