Re: @direction in json ld 1.0

That's because of the context using `@vocab`. If they didn't, then a JSON-LD 1.0 processor wouldn't choke. For example: (maps `name` directly in `@context`).

Sadly, the most widely used context files (presumably 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 <>
Sent: Monday, September 30, 2019 4:29 AM
To: W3C JSON-LD Working Group <>
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:-)


Ivan Herman, W3C
mobile: +31-641044153

Received on Monday, 30 September 2019 13:59:51 UTC