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

SPARQL DESCRIBE query output format should default to a graph format instead of tabular #212

Open
brianok-aws opened this issue Oct 22, 2021 · 0 comments
Labels
enhancement New feature or request
Projects

Comments

@brianok-aws
Copy link

Is your feature request related to a problem? Please describe.
As described in the SPARQL specification, "the DESCRIBE form takes each of the resources identified in a solution, together with any resources directly named by IRI, and assembles a single RDF graph..." (ref: https://www.w3.org/TR/sparql11-query/#describe). For this reason, it is frustrating that the graph notebook returns this data in a tabular format by default.
When I use most SPARQL toolsets, the output format defaults to a graph format like Turtle when running a DESCRIBE query.

Describe the solution you'd like
I would like the graph notebook to recognize that a DESCRIBE query is being run and return the data in a graph format instead of tabular format.

Describe alternatives you've considered
I likely could write Python code that would send HTTP requests to the Neptune endpoint requesting the specific MIME type, but that would be burdensome on my non-programmer staff.

Additional context
.

@michaelnchin michaelnchin added the enhancement New feature or request label Oct 22, 2021
@michaelnchin michaelnchin added this to New issues/Needs triage or review in Planning via automation Oct 22, 2021
@joywa joywa moved this from New issues/Needs triage or review to In progress in Planning Jan 18, 2023
@joywa joywa moved this from In progress to Medium priority in Planning Mar 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Planning
Medium priority
Development

No branches or pull requests

2 participants