Hierarchical view is not supported by this JSON-LD processor

[naturzukunft]

My code is not working any more. Maybe because of upgrading to 5.0.2 ?

		WriterConfig config = getWriterConfig();
		StringWriter stringWriter = new StringWriter();
		Rio.write(input, stringWriter, RDFFormat.JSONLD, config);
		String string = stringWriter.toString();

private WriterConfig getWriterConfig() {
		WriterConfig config = new WriterConfig();
		config.set(JSONLDSettings.HIERARCHICAL_VIEW, true);
		config.set(JSONLDSettings.COMPACT_ARRAYS, true);
		config.set(JSONLDSettings.OPTIMIZE, true);
		return config;
	}

Does that mean, i canntot use Rio.write any more ?

stacktrace: java.lang.UnsupportedOperationException: Hierarchical view is not supported by this JSON-LD processor. Use org.eclipse.rdf4j.rio.jsonld.legacy.JSONLDWriter instead.
	at org.eclipse.rdf4j.rio.jsonld.JSONLDWriter.endRDF(JSONLDWriter.java:154)
	at org.eclipse.rdf4j.rio.Rio.write(Rio.java:653)
	at org.eclipse.rdf4j.rio.Rio.write(Rio.java:608)

[hmottestad]

You'll have to use the legacy one.

[naturzukunft]

Ok, looks good. The project has been built, no tests are failed.
I'm using now

• spring-boot: 3.3.5
• rdf4j: 5.0.2 (model api and repository)

but without the sparql endpoint (rdf4j-spring-boot-sparql-web).

[hmottestad]

I would recommend looking into framing with JSON-LD 1.1 instead. We should have an example or two in the unit tests.

Framing is a great way of making json-ld more accessible for developers who are used to json. It's not as generic as the hierarchical jsond-ld, but it's a lot more supported and standardised. Also a lot more powerful.

[naturzukunft]

is framing the right solution for generic results? i didn't know the structure, that i have to format.

[hmottestad]

Not for a generic result no.

What is your use case for hierarchical json-ld?

[naturzukunft]

Presenting rdf in a way that is understood by as many activity-pub implementierungen as possible.

I may have to make certain individual translations, depending on which implementation I am communicating with. That remains to be seen. From what I've already learnt, interoperability is not that great.

With individual translations, framing per implementation and possibly type may become interesting.

[naturzukunft]

at the moment i stumble over this error

java.lang.NoSuchMethodError: 'java.lang.Object com.github.jsonldjava.utils.JsonUtils.fromJsonParser(com.fasterxml.jackson.core.JsonParser)'
	at org.eclipse.rdf4j.rio.jsonld.legacy.JSONLDParser.getJSONObject(JSONLDParser.java:153) ~[rdf4j-rio-jsonld-legacy-5.0.2.jar:5.0.2]
	at org.eclipse.rdf4j.rio.jsonld.legacy.JSONLDParser.parse(JSONLDParser.java:133) ~[rdf4j-rio-jsonld-legacy-5.0.2.jar:5.0.2]
	at org.eclipse.rdf4j.rio.jsonld.legacy.JSONLDParser.parse(JSONLDParser.java:103) ~[rdf4j-rio-jsonld-legacy-5.0.2.jar:5.0.2]

[naturzukunft]

probably maven decided to use the wrong version o

			<groupId>com.github.jsonld-java</groupId>
			<artifactId>jsonld-java</artifactId>

[hmottestad]

Probably a version conflict yes. IntelliJ has a nice diagram tool to show version conflicts in maven.