JSON-LD to Turtle serialization eats up @id with no value

[csarven]

re: #496 (comment)

http://example.org/resourceA contains:
{"@id": "http://example.net/note#foo", "http://schema.org/citation":{"@id": "http://example.org/article#results" } }

$ curl -H'Accept: text/turtle' http://example.org/resourceA
@prefix note: <http://example.net/note#>.
@prefix schem: <http://schema.org/>.
@prefix n0: <http://example.org/article#>.

 note:foo schem:citation n0:results .

Looks good to me.

http://example.org/resourceB contains:
{"@id": "", "http://schema.org/citation":{"@id": "http://example.org/article#results" } }

$ curl -H'Accept: text/turtle' http://example.org/resourceB

No body.

[dmitrizagidulin]

I think I see what you're saying. There's a problem with translation code in the get handler. (The base uri is somehow getting lost for translation)

[dmitrizagidulin]

Filed upstream issue linkeddata/rdflib.js#177

[RubenVerborgh]

This is an rdflib bug related to JSON-LD and base IRIs, which is fixed in linkeddata/rdflib.js#195. I'll wait for a new rdflib.js version to be released, and will then update package.json to fix this.

[RubenVerborgh]

Fixed by #548.