Skip to content

Commit 8be29ca

Browse files
committed
Update Section 3 -- Type System.md
1 parent 4905977 commit 8be29ca

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

spec/Section 3 -- Type System.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -435,10 +435,10 @@ For example, the following is *not* a valid Schema Coordinate:
435435
Entity.Business
436436
```
437437

438-
In this counter example, both `Entity.Business` and `Business` would refer to
439-
the `Business` type. Since it would be ambiguous what the "primary key" should
440-
be in an application that uses Schema Coordinates to reference types, this is
441-
not allowed.
438+
In this counter example, `Entity.Business` is redundant since `Business` already
439+
uniquely identifies the Business type. Such redundancy is disallowed by this
440+
spec - every type, field, field argument, enum value, directive, and directive
441+
argument has exactly one canonical Schema Coordinate.
442442

443443
## Types
444444

0 commit comments

Comments
 (0)