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

Commits on Sep 21, 2017

  1. 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 committed Sep 21, 2017
    Configuration menu
    Copy the full SHA
    cfb6729 View commit details
    Browse the repository at this point in the history
  2. Add conformance section

    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 committed Sep 21, 2017
    Configuration menu
    Copy the full SHA
    3f8b14e View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    b24ef6b View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    2015091 View commit details
    Browse the repository at this point in the history
  5. Configuration menu
    Copy the full SHA
    693b4a0 View commit details
    Browse the repository at this point in the history

Commits on Sep 22, 2017

  1. remove confusing phrase

    leebyron committed Sep 22, 2017
    Configuration menu
    Copy the full SHA
    089ef5c View commit details
    Browse the repository at this point in the history

Commits on Sep 25, 2017

  1. Minor phrasing

    leebyron authored Sep 25, 2017
    Configuration menu
    Copy the full SHA
    030471b View commit details
    Browse the repository at this point in the history