[2021-01-07] Open an issue to discuss expansions we might take atop Schema Coordinates

[benjie]

The Schema Coordinates RFC has a very narrow goal, deliberately. This is great; but we can build upon this syntax to standardize a lot more of how we reference things in GraphQL which will enable even more powerful tooling. Benjie recently discussed this with @daniman from Apollo and shared this with the WG; it was suggested that having this discussion in a closed issue/merged PR could lose important attention so Benjie is to open an issue with a summary of the current discussions around this topic and to gather feedback from others.

Benjie: explains discussion with Danielle and summarises: graphql/graphql-spec/pull/746#issuecomment-740914167
Benjie: if there are other use cases for this, now would be the time to say
Mike: where should we discuss that
Mark: in the RFC
Lee: it's fine for that to happen there; it's hard to follow discussions on closed PRs. Maybe we should open an new issue about how Schema Coordinates can be evolved.
Mike: I'd like to surface how we might use this; we track usage of deprecations and this would have been fantastic for that.
Lee: that's great; I think Evan has opinions on this too.
Evan: yeah we use paths internally and as part of our public deprecated API usage docs.
ACTION - Benjie - open this issue?

• assignee(s): @benjie
• source: https://github.com/graphql/graphql-wg/blob/master/notes/2021-01-07.md#discuss-schema-coordinates-spec-10m-mark

---

Note: Action Item issues are reviewed and closed during Working Group
meetings.

[benjie]

Have gathered together and written up various thoughts on this here: https://github.com/benjie/graphql-spec/blob/operation-expressions/rfcs/OperationExpressions.md - definitely encourage others to get involved.