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

Re: @direction in json ld 1.0

From: Benjamin Young <byoung@bigbluehat.com>
Date: Mon, 30 Sep 2019 13:59:22 +0000
To: Ivan Herman <ivan@w3.org>, W3C JSON-LD Working Group <public-json-ld-wg@w3.org>
Message-ID: <DM5PR06MB3401CBF6D231A0125A0CD858B2820@DM5PR06MB3401.namprd06.prod.outlook.com>
That's because of the schema.org context using `@vocab`. If they didn't, then a JSON-LD 1.0 processor wouldn't choke. For example: https://tinyurl.com/y3vzjegw (maps `name` directly in `@context`).

Sadly, the most widely used context files (presumably Schema.org and ActivityStreams) use `@vocab`.

We did discuss this for a long while at TPAC...but I don't think we ever found a solution for old processors + `@vocab` containing context files...

It's best expressed in this issue:

Which resulted in reopening this one:

We can make sure getting us all in sync around this status is on the agenda for this Friday.





From: Ivan Herman <ivan@w3.org>
Sent: Monday, September 30, 2019 4:29 AM
To: W3C JSON-LD Working Group <public-json-ld-wg@w3.org>
Subject: @direction in json ld 1.0

Maybe I did not remember right, but we thought that "@direction" should be absorbed by a JSON-LD 1.0 processor, ie, we can deploy it safely. However, the construction:

  "name" : {
    "@value": "na mi van",
    "@language": "hu",
    "@direction": "ltr"

will not work either; there will be an error message due to the presence of value and direction in one object (see [1]).

I guess we cannot do anything about it, but it is a bit of a pain:-)

[1]  https://tinyurl.com/y6goh76p

Ivan Herman, W3C
Home: http://www.w3.org/People/Ivan/
mobile: +31-641044153
ORCID ID: https://orcid.org/0000-0003-0782-2704
Received on Monday, 30 September 2019 13:59:51 UTC

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