W3C home > Mailing lists > Public > public-json-ld-wg@w3.org > June 2019

Question about JSON-LD: @type in expanded term definitions in @context

From: Graham Klyne <gk@ninebynine.org>
Date: Mon, 10 Jun 2019 11:54:06 +0100
Message-ID: <5CFE36CE.2020001@ninebynine.org>
To: public-json-ld-wg@w3.org
(I've just noticed that this mailing list is open to public comments, so I'm 
resending a question previously sent to semantic-web@w3.org)

I'm working from the 1.0 version of the JSON-LD spec:
https://www.w3.org/TR/json-ld/

My question is this: does the inclusion of a "@type" value in an "expanded term
definition" [1] in a JSON-LD context automatically mean that the defined term is 
a datatype property URI, and hence that the value of the "@type" key must be a 
datatype URI?

[1] https://www.w3.org/TR/json-ld/#dfn-expanded-term-definition

I think the answer is "yes" (it's the usage illustrated for Typed Values [2]),
but I'm struggling to find anything in the spec that definitively states this is 
the case).

[2] https://www.w3.org/TR/json-ld/#typed-values

...

In hindsight, I think the use of the same "@type" keyword for node types and
value types maybe unfortunate, and what is leading to this uncertainty.  If I'm
correct in my interpretation, the spec has clearly been misinterpreted by others 
(see below), and may benefit from some clarification in the 1.1 round.

More background on my question is at:
https://github.com/LinkedPasts/linked-places/issues/11

#g
--
Received on Monday, 10 June 2019 10:54:37 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:15:26 UTC