From a03513bddc40917d2f95727fc4677f303d5d0159 Mon Sep 17 00:00:00 2001 From: Mark Larah Date: Thu, 7 Jan 2021 11:11:46 -0800 Subject: [PATCH] Update Section 3 -- Type System.md --- spec/Section 3 -- Type System.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/spec/Section 3 -- Type System.md b/spec/Section 3 -- Type System.md index d105c3d06..60c8ae167 100644 --- a/spec/Section 3 -- Type System.md +++ b/spec/Section 3 -- Type System.md @@ -404,10 +404,10 @@ For example, the following is *not* a valid Schema Coordinate: Entity.Business ``` -In this counter example, both `Entity.Business` and `Business` would refer to -the `Business` type. Since it would be ambiguous what the "primary key" should -be in an application that uses Schema Coordinates to reference types, this is -not allowed. +In this counter example, `Entity.Business` is redundant since `Business` already +uniquely identifies the Business type. Such redundancy is disallowed by this +spec - every type, field, field argument, enum value, directive, and directive +argument has exactly one canonical Schema Coordinate. ## Types