Skip to content

Commit 766e902

Browse files
committed
Merge branch 'main' into fragment-args-2024-amendments
2 parents 0d7bc1a + 43ae7ba commit 766e902

20 files changed

+1380
-562
lines changed

LICENSE.md

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
# Appendix: Copyright and Licensing
2+
3+
The GraphQL Specification Project is made available by the
4+
[Joint Development Foundation](https://www.jointdevelopment.org/) Projects, LLC,
5+
GraphQL Series. The current
6+
[Working Group](https://github.com/graphql/graphql-wg) charter, which includes
7+
the IP policy governing all working group deliverables (including
8+
specifications, source code, and datasets) may be found at
9+
[https://technical-charter.graphql.org](https://technical-charter.graphql.org).
10+
11+
**Copyright Notice**
12+
13+
Copyright © 2015-2018, Facebook, Inc.
14+
15+
Copyright © 2019-present, GraphQL contributors
16+
17+
THESE MATERIALS ARE PROVIDED “AS IS”. The parties expressly disclaim any
18+
warranties (express, implied, or otherwise), including implied warranties of
19+
merchantability, non-infringement, fitness for a particular purpose, or title,
20+
related to the materials. The entire risk as to implementing or otherwise using
21+
the materials is assumed by the implementer and user. IN NO EVENT WILL THE
22+
PARTIES BE LIABLE TO ANY OTHER PARTY FOR LOST PROFITS OR ANY FORM OF INDIRECT,
23+
SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER FROM ANY CAUSES
24+
OF ACTION OF ANY KIND WITH RESPECT TO THIS DELIVERABLE OR ITS GOVERNING
25+
AGREEMENT, WHETHER BASED ON BREACH OF CONTRACT, TORT (INCLUDING NEGLIGENCE), OR
26+
OTHERWISE, AND WHETHER OR NOT THE OTHER MEMBER HAS BEEN ADVISED OF THE
27+
POSSIBILITY OF SUCH DAMAGE.
28+
29+
**Licensing**
30+
31+
The licenses for the GraphQL Specification Project are:
32+
33+
| Deliverable | License |
34+
| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
35+
| Specifications | [Open Web Foundation Agreement 1.0 (Patent and Copyright Grants)](https://www.openwebfoundation.org/the-agreements/the-owf-1-0-agreements-granted-claims/owfa-1-0) |
36+
| Source code | [MIT License](https://opensource.org/licenses/MIT) |
37+
| Data sets | [CC0 1.0](https://creativecommons.org/publicdomain/zero/1.0/) |

STYLE_GUIDE.md

Lines changed: 33 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -92,7 +92,7 @@ Definition paragraphs start with `::` and add the matching italicized term to
9292
the [specification index](https://spec.graphql.org/draft/#index), making it easy
9393
to reference them.
9494

95-
## Tone of voice
95+
## Tone of Voice
9696

9797
The GraphQL specification is a reference document and should use neutral and
9898
descriptive tone of voice.
@@ -104,3 +104,35 @@ The present tense is usually clearer and shorter:
104104
✅ Present: The client then sends a request to the server.
105105

106106
❌ Future: The client will then send a request to the server.
107+
108+
**Write in the third person**
109+
110+
The specification should avoid the first person (“we,” “our”) and instead use
111+
the third person or passive constructions when necessary. For example:
112+
113+
✅ “The server validates the request against the schema.”
114+
115+
❌ “We validate the request against the schema.”
116+
117+
**Use RFC 2119 keywords**
118+
119+
The specification should use the normative keywords defined in
120+
[RFC 2119](https://www.rfc-editor.org/rfc/rfc2119) (**MUST**, **MUST NOT**,
121+
**SHOULD**, **SHOULD NOT**, **MAY**). However, in the context of a sentence
122+
these words should be lower-cased (e.g., “must,” “should,” “may”) in context of
123+
a sentence. This avoids unnecessary visual emphasis while preserving normative
124+
meaning.
125+
126+
✅ “A query must contain a single root operation type.”
127+
128+
❌ “A query MUST contain a single root operation type.”
129+
130+
**Avoid unnecessary hyphenation**
131+
132+
Only use hypenated compound words when either commonly used elsewhere in english
133+
or technical writing. Otherwise prefer separate words or a non-hyphenated
134+
compound word, whichever is most commonly accepted.
135+
136+
✅ User defined shorthand words are separated by whitespace
137+
138+
❌ User-defined short-hand words are separated by white-space

changelogs/September2025.md

Lines changed: 215 additions & 0 deletions
Large diffs are not rendered by default.

cspell.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,8 @@ words:
2121
- tatooine
2222
- zuck
2323
- zuckerberg
24+
- brontie
25+
- oneOf
2426
# Forbid Alternative spellings
2527
flagWords:
2628
- implementor

package.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@
1414
},
1515
"scripts": {
1616
"test": "npm run test:spelling && npm run test:format && npm run test:build",
17-
"test:spelling": "cspell \"spec/**/*.md\" README.md",
17+
"test:spelling": "cspell \"spec/**/*.md\" README.md LICENSE.md",
1818
"format": "prettier --write \"**/*.{md,yml,yaml,json}\"",
1919
"test:format": "prettier --check \"**/*.{md,yml,yaml,json}\" || npm run suggest:format",
2020
"test:algorithm-format": "node .github/algorithm-format-check.mjs",

0 commit comments

Comments
 (0)