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

DESCRIBE quad result #2980

Open
namedgraph opened this issue Jan 28, 2025 · 5 comments
Open

DESCRIBE quad result #2980

namedgraph opened this issue Jan 28, 2025 · 5 comments
Labels
enhancement Incrementally add new feature

Comments

@namedgraph
Copy link
Contributor

Version

4.7.0

Feature

IMO when quads are requested in Fuseki, DESCRIBE queries should return a quad result (just like CONSTRUCT GRAPH does) instead of stripping the graph URIs and returning the remaining triples in the default graph, as they currently do.

More context: https://lists.apache.org/thread/49spskzf3or2ty743yz9p08twzv9p5cj

Are you interested in contributing a solution yourself?

Perhaps?

@namedgraph namedgraph added the enhancement Incrementally add new feature label Jan 28, 2025
@afs
Copy link
Member

afs commented Jan 28, 2025

This is different to the CONSTRUCT case.

CONSTRUCT { GRAPH ... } is different, extension syntax. The only way to get quads is to ask for quads.

DESCRIBE with no syntax indication breaks compatibility as a network protocol.

Turtle is a subset of TriG (N-triples is a subset of N-Quads). So asking for TriG in a standards compliant DESCRIBE query can return TriG.

@namedgraph
Copy link
Contributor Author

So are you saying that a new query form would be required in order to describe as quads? Something like DESCRIBE GRAPH?

I can make an issue on https://github.com/w3c/sparql-dev

@afs
Copy link
Member

afs commented Jan 29, 2025

If you do, it needs a proper description.

It's not a Jena issue.

DESCRIBE supports data introspection in the client. That style of working has not taken root.

@namedgraph
Copy link
Contributor Author

If you do, it needs a proper description.

Can you point to an example?

DESCRIBE supports data introspection in the client. That style of working has not taken root.

Not sure I understand :)

@afs
Copy link
Member

afs commented Jan 30, 2025

DESCRIBE is "get data about a thing - look to see what comes back".

If that client knows the shape of the data, it can use SELECT or CONSTRUCT to get what it is looking for.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Incrementally add new feature
Projects
None yet
Development

No branches or pull requests

2 participants