Define Data Collections used in the spec

At a glance

• Identifier: #1102
• Stage: RFC3: Accepted
• Champion: @benjie
• PR: Define Data Collections used in the spec
• Related:
  • #1063 (Type system ordering of: object interfaces, directive arguments, input object fields, enum values)
  • #1092 (Recommend that order of unordered collections is maintained where possible)

Timeline

• Added to 2025-06-26 WG agenda
• Added to 2025-06-05 WG agenda
• Commit pushed: Merge branch 'main' into data-collections on 2025-05-22 by @benjie
• Added to 2025-05-01 WG agenda
• Added to 2025-04-03 WG agenda
• Commit pushed: Define what a collection is and integrate feedback on 2025-04-01 by @benjie
• Added to 2024-07-18 WG agenda
• Spec PR created on 2024-07-01 by benjie
• Mentioned in 2024-07 WG notes
• Commit pushed: Define Data Collections used in the spec on 2024-04-05 by @benjie

---

The spec uses the terms "set", "list" and "map" in many places. This PR defines these terms and their conformance requirements.

This is a change extracted from #1063 as discussed at last night's WG meeting

This is PR 1 of 3 in the "data collections" trilogy stack; next are:

2. https://github.com/graphql/graphql-spec/pull/1092
3. https://github.com/graphql/graphql-spec/pull/1063

cc @graphql/tsc

(Replacement of #1091; to do PR stack with #1092 and #1063)