Exp. term definitions SHOULD NOT contain any other keys (instead of MUST NOT)
authorMarkus Lanthaler <mark_lanthaler@gmx.net>
Wed, 19 Sep 2012 11:09:31 +0200
changeset 866 71c43eb1eeb8
parent 865 06065aa9cd65
child 867 72f6b506265f
Exp. term definitions SHOULD NOT contain any other keys (instead of MUST NOT)

This was discussed in 72d098d2183aa8d33dac0c15edee47eeeaa598f1.
spec/latest/json-ld-syntax/index.html
--- a/spec/latest/json-ld-syntax/index.html	Tue Sep 11 15:03:20 2012 -0700
+++ b/spec/latest/json-ld-syntax/index.html	Wed Sep 19 11:09:31 2012 +0200
@@ -2928,7 +2928,7 @@
   definition</tref> (see <a href="#expanded-term-definition"></a>).</p>
 <p>An <tdef>expanded term definition</tdef> is composed of zero or more keys from <code>@id</code>,
   <code>@type</code>, <code>@language</code> or <code>@container</code>. An
-  <tref>expanded term definition</tref> MUST NOT contain any other keys.
+  <tref>expanded term definition</tref> SHOULD NOT contain any other keys.
   All values associated with <code>@id</code> MUST expand to an <tref>absolute IRI</tref>.</p>
 <p>If the <tref>term</tref> definition is not a <tref>compact IRI</tref> or <tref>absolute IRI</tref>,
   the <tref>expanded term