IIRC, JSON-LD is supported via an external API only, thus, issues can only be handled therein.
Regarding your issue, see [1] which is supposed to lead to the same error message according to the JSON-LD test case definition here [2] [1] https://github.com/json-ld/tests/blob/master/error-0010-in.jsonld [2] https://github.com/json-ld/tests/blob/master/error-manifest.jsonld#L72-L79 On 28.02.2018 13:57, Laura Morales wrote: > I was looking at this draft [1] about standardizing a "graph" URI. A > suggested format would be > > <graph:name:ec654ec1-7f8f-11e3-ae96-b385f4bc450c> > > I tried to define a prefix like this > > PREFIX graph: <graph:name:> > > such that I could use > > graph:ec654ec1-7f8f-11e3-ae96-b385f4bc450c > > but this is causing problems with JSON-LD. The error is > > ERROR riot :: cyclic IRI mapping: graph > > A simple way to reproduce the error is with this JSON-LD file: > > { > "@graph" : [ ], > "@context" : { > "graph" : "graph:name:" > } > } > > $ riot --syntax jsonld --validate test.json > ERROR riot :: cyclic IRI mapping: graph > > Shouldn't the parser recognize that "graph:name:" is an absolute URI? I don't > understand why this would be ambiguous. Looks like it's treating "graph:" as > a prefix but it's actually a URI scheme. > > > > > > [1] > https://s3.amazonaws.com/artifacts.opencypher.org/website/ocig3/oCIG3+-+Draft+graph+URI+Scheme+Specification+0.3.pdf
