[poe] Issue: Error in the ODRL JSON-LD context resource marked as JSON-LD

nitmws has just labeled an issue for https://github.com/w3c/poe as "JSON-LD":

== Error in the ODRL JSON-LD context resource ==
@vroddon and I have been working on the transformation of Turtle RDF used on the [Validation page](https://www.w3.org/2016/poe/wiki/Validation) into JSON-LD RDF - and ran into errors, even when using the  jsonld.js Node.js module created by the JSON-LD people. 
I raised a Github issue there https://github.com/digitalbazaar/jsonld.js/issues/201# and got this response:

The problem is the following constructs in ODRL22.jsonld:

> "uid":     {"@type": "@id", "@id": "@id"},
> "type":    {"@type": "@id", "@id": "@type"},

uid isn't even being used but those constructs are apparently not handled well with any recent jsonld.js (recent 0.4.x or dev 0.5.x). Are you just trying to setup aliases for @id and @type? The following change will do that:

> -    "uid":     {"@type": "@id", "@id": "@id"},
> -    "type":    {"@type": "@id", "@id": "@type"},
> +    "uid":     "@id",
> +    "type":    "@type",

@dlongley @gkellogg: Does the above have defined behavior or should implementations error on it? If it's defined then we should add some test suite tests for it. If not, should this be defined in 1.1 or what should implementations do? Clearly jsonld.js shouldn't be spitting out "undefined" nonsense when this happens. Would be better to just have an error.

(see https://github.com/digitalbazaar/jsonld.js/issues/201#issuecomment-334816999)

**Result: the ODRL context file/resource - http://www.w3.org/ns/odrl.jsonld - should be fixed**

(This change to the ODRL context shows correct in the results of a test software for this transformation:  https://github.com/nitmws/rdf-jsonld-transformation-test1)

See https://github.com/w3c/poe/issues/277

Received on Friday, 6 October 2017 18:51:26 UTC