Issue with using the document base for the default vocabulary in JSON-LD 1.1 about jena HOT 4 CLOSED

Fixed in trunk (1.4.0-SNAPSHOT). Titanium v1.4.0 will be released during February, hopefully.

from jena.

I confirm it's expansion bug. An input is expanded before serialization into RDF so the bug propagates down the stream. Will be fixed.

from jena.

just heads up, v1.4.0 has been released https://github.com/filip26/titanium-json-ld/releases/tag/v1.4.0

from jena.

Hi @Tomvbe,

I tried with the development codebase and get the same results.

Jena uses Titanium JSON-LD for parsing JSON-LD, The Jena5 dependency is on version Titanium 1.3.3 and Jena 4.10.0 depends on 1.3.2.

Tracing the example, Jena calls Titanium with

    private void read(Document document, String baseURI, StreamRDF output, Context context) throws JsonLdError {
        // JSON-LD to RDF
        JsonLdOptions opts = getJsonLdOptions(baseURI, context);
        RdfDataset dataset = JsonLd.toRdf(document).options(opts).base(baseURI).get();
        extractPrefixes(document, output::prefix);
        JenaTitanium.convert(dataset, profile, output);
    }

opts is new JsonLdOptions(), baseURI is null.

It seems the URI coming back from Titanium in RdfDataset is "http://example/documentRestaurant" so it looks like an issue within Titanium.

cc: @filip26

from jena.