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

Add conformance section #363

Merged
merged 7 commits into from
Sep 25, 2017
Merged

Add conformance section #363

merged 7 commits into from
Sep 25, 2017

Conversation

leebyron
Copy link
Collaborator

@leebyron leebyron commented Sep 21, 2017

In anticipation of potentially moving to some license that references "normative", "non-normative", and "conformance" - I think it's helpful to define these concepts relative to the rest of this spec, and clarify some of the details of what technically qualifies as GraphQL, and how to interpret some of the document (like notes and examples) for any future cautious reader.

I'm referencing RFC 2119 since we've already done a good job of using these terms throughout the spec. Most of this conformance definition is highly inspired by W3C and ECMA documents that contain similar language. No need to reinvent the wheel here.

A preview of this content rendered: https://out-amuksthchq.now.sh/

… "normative", "non-normative", and "conformance" - I think it's helpful to define these concepts relative to the rest of this spec, and clarify some of the details of what technically qualifies as GraphQL, and how to interpret some of the document (like notes and examples) for any future cautious reader.

I'm referencing [RFC 2119](https://tools.ietf.org/html/rfc2119) since we've already done a good job of using these terms throughout the spec. Most of this conformance definition is highly inspired by W3C and ECMA documents that contain similar language. No need to reinvent the wheel here.

A preview of this content rendered: https://out-xlhkhmymsm.now.sh/
@leebyron leebyron changed the title In anticipation of potentially moving to some license that references… Add conformance section Sep 21, 2017
In anticipation of potentially moving to some license that references "normative", "non-normative", and "conformance" - I think it's helpful to define these concepts relative to the rest of this spec, and clarify some of the details of what technically qualifies as GraphQL, and how to interpret some of the document (like notes and examples) for any future cautious reader.

I'm referencing [RFC 2119](https://tools.ietf.org/html/rfc2119) since we've already done a good job of using these terms throughout the spec. Most of this conformance definition is highly inspired by W3C and ECMA documents that contain similar language. No need to reinvent the wheel here.

A preview of this content rendered: https://out-xlhkhmymsm.now.sh/
@leebyron leebyron merged commit e29a233 into master Sep 25, 2017
@leebyron leebyron deleted the conformance branch September 25, 2017 18:28
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

Successfully merging this pull request may close these issues.

2 participants