Construct Query Result Renderer

[BenjaminHofstetter]

Phase: Ideation

Construct Query Results are forced to TTL (accept header). The output is displayed just as Text.

Ideas

• Provide a way to convert RDF from a serialisation to another (nt to ttl)
• Don't depend on TTL (no accept header)
• Sketch (https://sketch.zazuko.com)
• Flux bubbles

To check

• GraphDB
• Stardog
• YasGui
• DBPedia
• Wikidata

[ktk]

These things might be nice to have but we should reflect where they should be done. IMO it would make sense to:

• have a generic RDF converter extension (based on what @tpluscode did for https://converter.zazuko.com/)
• have a generic sketch visualizer (that will work up to a certain size but not for all data)
• have a flux bubble visualizer, which might work for the use-cases where the sketch one explodes

[kvistgaard]

It would be nice to be able to configure the default result format, even now, among the currently available ones.

[BenjaminHofstetter]

• @ktk all good. Just to be clear. Right now CONSTRUCT results use a built in markdown renderer.
• Conversion between RDF serialisations is something we should have a look at it (independent of notebook)
• Sketch is a must for me. But I think we have to check if we can add a renderer to vscode sketch to avoid code duplication or turn it to a web-component.
• Flux was in my mind too. But where is the entry point like what is the starting bubble.
• and btw. ASK queries are handled by the sparql-result+json renderer. And it has to stay like this because it's the same mime-type.