Re: @direction in json ld 1.0

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:
https://github.com/w3c/json-ld-syntax/issues/259

Which resulted in reopening this one:
https://github.com/w3c/json-ld-syntax/issues/16

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

Cheers,
Benjamin

--

http://bigbluehat.com/

http://linkedin.com/in/benjaminyoung

________________________________
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:


{
  "@context":"https://schema.org",
  "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