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

Glossary: add 'implementation' #1593

Open
wants to merge 6 commits into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 15 additions & 2 deletions rfcs/glossary/Appendix C -- Glossary.md
Original file line number Diff line number Diff line change
Expand Up @@ -187,9 +187,22 @@ Example:

### (GraphQL) service

**Definition**: a software capable of executing a GraphQL request and returning
a GraphQL response according to this specification.
**Definition**: A GraphQL service generates a [response](https://spec.graphql.org/draft/#sec-Response) from a [request](https://spec.graphql.org/draft/#request) via [execution](https://spec.graphql.org/draft/#sec-Execution).

How the conformance is implemented is irrelevant. A cache in front of another
GraphQL service can itself be seen as a conforming service, assuming it does not
break any conformance requirements (e.g. on cache failure).

Examples: GitHub GraphQL API, Shopify GraphQL API, etc...

Note: The specification has no concept of client and server. While most
services are implemented as servers, this is not a requirement and execution
can happen anywhere as long as it conforms to the specification.

### (GraphQL) implementation

**Definition**: software that implements the algorithms and behaviours described
in the GraphQL specification.

Examples: graphql-js, Hot Chocolate, graphql-java, etc...