W3C home > Mailing lists > Public > public-linked-json@w3.org > August 2014

RE: @value/@type/@language combination

From: Markus Lanthaler <markus.lanthaler@gmx.net>
Date: Thu, 14 Aug 2014 12:29:40 +0200
To: "'Linked JSON'" <public-linked-json@w3.org>
Message-ID: <002901cfb7aa$a8d490a0$fa7db1e0$@gmx.net>
On Thursday, August 14, 2014 2:06 AM, Gregg Kellogg wrote:
> On Aug 13, 2014, at 4:31 PM, Robert Sanderson wrote:
>> We have a use case that would require all three of @value, @type and
>> @language for a single resource, which is not allowed according to the
>> specification (eg section 8.3)
> Note that the RDF data model allows literals to have either a datatype or
> language, but not both. JSON-LD is just being consistent here.

Unfortunately that's true. For a bit more background, I raised that in the
RDF WG back in 2012:


According to that thread, the best approach would be to use something like

    "description": {
      "rdf:value": {
        "@value": "<p>Some <b>description</b></p>",
        "@type": "rdf:XMLLiteral"
      "schema:language": "en"

if you don't want to parse the XMLLiteral (which I completely agree is an
insane requirement).

Markus Lanthaler
Received on Thursday, 14 August 2014 10:30:10 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:18:42 UTC