Skip to content

Commit a03513b

Browse files
magicmarkleebyron
authored andcommitted
Update Section 3 -- Type System.md
1 parent 50ae66a commit a03513b

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
@@ -404,10 +404,10 @@ For example, the following is *not* a valid Schema Coordinate:
404404
Entity.Business
405405
```
406406

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

412412
## Types
413413

0 commit comments

Comments
 (0)