Uploaded image for project: 'Rya'
  1. Rya
  2. RYA-477 SPARQLEndpoint overhaul
  3. RYA-478

SPARQLEndpoint => content-negotiation

    XMLWordPrintableJSON

    Details

    • Type: Sub-task
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 3.2.12
    • Fix Version/s: 3.2.12
    • Component/s: clients
    • Labels:
      None

      Description

      currently it's only possible to get SPARQL results in application/rdf+xml (with content-type header: text/xml) for graph query results and application/sparql-results+json (with content-type header: application/json) for tuple query results. this should be improved to expose all available official mimetypes with proper content-negotiation (accept headers). it should be possible to override accept headers by URL params, so that all mimetypes are also available within a browser for testing. the implementation should make use of sesame's (later rdf4j's) writer registries (rdfwriter + tuplequeryresultwriter) so that additional writers (mimetypes) are available without touching the endpoint's code: for example: there's a json-ld writer for sesame (rdf4j) which just needs to be dropped into the server's lib folder to be available..

        Attachments

          Activity

            People

            • Assignee:
              turnguard Jakobitsch Jürgen
              Reporter:
              turnguard Jakobitsch Jürgen
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Due:
                Created:
                Updated: