Examples are either introduced explicitly in prose (e.g. See Appendix A for more details about the definition of algorithms and other notational conventions used in this document.Īll contents of this document are normative except portions explicitly declared as non‐normative.Įxamples in this document are non‐normative, and are presented to aid understanding of introduced concepts and the behavior of normative portions of the specification. Implementers are encouraged to include equivalent but optimized implementations. Algorithms described in this document are written to be easy to understand. “Let completedResult be the result of calling CompleteValue()”) is to be interpreted as having at least the same level of requirement as the algorithm containing that step.Ĭonformance requirements expressed as algorithms can be fulfilled by an implementation of this specification in any way as long as the perceived result is equivalent. Any algorithm referenced within an algorithm step (e.g. “Return the result of calling resolver”) are to be interpreted with the same level of requirement as the algorithm it is contained within. These key words may appear in lowercase and still retain their meaning unless explicitly declared as non‐normative.Ī conforming implementation of GraphQL may provide additional functionality, but must not where explicitly disallowed or would otherwise result in non‐conformance.Īlgorithm steps phrased in imperative grammar (e.g. The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in the normative portions of this document are to be interpreted as described in IETF RFC 2119. Conformance requirements are described in this document via both descriptive assertions and key words with clearly defined meanings. IN NO EVENT WILL ANY PARTY BE LIABLE TO ANY OTHER PARTY FOR LOST PROFITS OR ANY FORM OF INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER FROM ANY CAUSES OF ACTION OF ANY KIND WITH RESPECT TO THIS SPECIFICATION OR ITS GOVERNING AGREEMENT, WHETHER BASED ON BREACH OF CONTRACT, TORT (INCLUDING NEGLIGENCE), OR OTHERWISE, AND WHETHER OR NOT THE OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.Ī conforming implementation of GraphQL must fulfill all normative requirements. The entire risk as to implementing or otherwise using the Specification is assumed by the Specification implementer and user. THIS SPECIFICATION IS PROVIDED “AS IS.” The contributors expressly disclaim any warranties (express, implied, or otherwise), including implied warranties of merchantability, non‐infringement, fitness for a particular purpose, or title, related to the Specification. Your use of this Specification may be subject to other third party rights. You can review the signed copies of the Open Web Foundation Final Specification Agreement Version 1.0 for this specification at /facebook/graphql, which may also include additional parties to those listed above. The latest working draft release can be found at /graphql/draft/.Īs of September 26, 2017, the following persons or entities have made this Specification available under the Open Web Foundation Final Specification Agreement (OWFa 1.0), which is available at.

Previous editions of the GraphQL specification can be found at s that match their release tag. GraphQL has evolved and may continue to evolve in future editions of this specification. The development of this open standard started in 2015. This is the specification for GraphQL, a query language and execution engine originally created at Facebook in 2012 for describing the capabilities and requirements of data models for client‐server applications.

Graphql fragments