From e497cf4f41125bc6b156310fdfcaab78b6597f7c Mon Sep 17 00:00:00 2001 From: Ashi Krishnan Date: Sat, 23 Apr 2022 06:43:08 -0400 Subject: [PATCH] add wording for implicit bindings, tk maybe a note --- link/v1.0/link-v1.0.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/link/v1.0/link-v1.0.md b/link/v1.0/link-v1.0.md index 1db863f..010dba6 100644 --- a/link/v1.0/link-v1.0.md +++ b/link/v1.0/link-v1.0.md @@ -160,7 +160,7 @@ Elements are the same as in [global graph references](#sec-Global-Graph-Referenc A {Binding} contains: - {gref}: GRef — the [global graph reference](#sec-Global-Graph-References) which is the target of the binding -- {implicit}: Bool — indicating whether the binding was explicitly imported or created implicitly. Implicit bindings may be overwritten by explicit bindings and will not be formed if an explicit binding for the item alreaady exists +- {implicit}: Bool — indicating whether the binding was explicitly imported or created implicitly. Implicit bindings are "soft"—they may be overwritten by explicit bindings and will not be formed if an explicit binding for the item alreaady exists. Similar to a [gref](#sec-Global-Graph-References)'s elements, different types of scoped items can have the same name without conflict. For example, a scope can contain both a type and schema named "User", although this should generally be avoided if possible.