- From: Gregg Kellogg <gregg@greggkellogg.net>
- Date: Sun, 21 Oct 2012 13:29:39 -0400
- To: Richard Cyganiak <richard@cyganiak.de>
- CC: RDF WG <public-rdf-wg@w3.org>
On Oct 21, 2012, at 1:47 AM, Richard Cyganiak <richard@cyganiak.de> wrote: > On 20 Oct 2012, at 23:19, Gregg Kellogg wrote: >>> From a note in 3.4 [3]: >> >> [[[ >> The null value is processed in a special way in JSON-LD. Unless otherwise specified, a JSON-LD processor must act as if a key-value pair in the body of a JSON-LD document was never declared when the value equals null. If @value, @list, or @set is set to null in expanded form, then the entire JSON object is ignored. If @context is set to null, the active context is reset and when used within a context, it removes any definition associated with the key, unless otherwise specified. >> ]]] > > By the way: Using RFC2119 keywords in Notes is nonsensical. The role of a Note is to provide non-normative explanations within a normative section. Putting conformance statements into a Note is fundamentally wrong. > > Or perhaps MUST in JSON-LD doesn't mean the same as MUST in other W3C specifications? Or unlike in other W3C specifications, Notes are in fact normative in JSON-LD? We will never know, since there is no Conformance section. No, they mean the same things, but the text should be moved out of the Note. Gregg > Bet, > Richard
Received on Sunday, 21 October 2012 17:30:19 UTC