Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add note about unsupported conneg in Fuseki #142

Merged
merged 1 commit into from
Sep 9, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions docs/docs/getting-started-plugins.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,13 @@ You can simply add Jelly format support to [Apache Jena](https://jena.apache.org
- For other applications, consult the manual of the application.
- You can now use Jelly format for parsing, serialization, and streaming serialization in your Jena application.

!!! bug "Content negotiation in Fuseki"

Currently Apache Jena Fuseki will not properly handle content negotiation for the Jelly format, due to the supported content types being hardcoded in Fuseki (see [upstream issue](https://github.com/apache/jena/issues/2700)).

Until that is fixed, you can use Jelly with Fuseki endpoints by specifying the `output=application/x-jelly-rdf` parameter (either in the URL or in the URL-encoded form body) when querying the endpoint.


### Eclipse RDF4J

You can simply add Jelly format support to an application based on RDF4J with Jelly's plugin JAR.
Expand Down