Uploaded image for project: 'Apache Jena'
  1. Apache Jena
  2. JENA-1512

SPARQL Service Description?

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: Jena 3.6.0
    • Fix Version/s: None
    • Component/s: Fuseki
    • Labels:
      None

      Description

      From a completely fresh Fuseki download, I executed:

      ./fuseki-server --mem /test

      Then I get:

        ~ curl -v http://localhost:3030/test/query
      *   Trying ::1...
      * TCP_NODELAY set
      * Connected to localhost (::1) port 3030 (#0)
      > GET /test/query HTTP/1.1
      > Host: localhost:3030
      > User-Agent: curl/7.54.0
      > Accept: /
      >
      < HTTP/1.1 404 Service Description: /test/query
      < Date: Fri, 23 Mar 2018 16:58:18 GMT
      < Fuseki-Request-ID: 11
      < Vary: Accept,Accept-Encoding,Accept-Charset
      < Content-Type: text/plain;charset=utf-8
      < Cache-Control: must-revalidate,no-cache,no-store
      < Pragma: no-cache
      < Content-Length: 108
      <
      Error 404: Service Description: /test/query

      And the log shows only:

       [2018-03-23 12:58:18] Fuseki     INFO  [11] GET http://localhost:3030/test/query
      [2018-03-23 12:58:18] Fuseki     INFO  [11] GET /test :: 'query' :: <none> ?
      [2018-03-23 12:58:18] Fuseki     WARN  Service Description / SPARQL Query / /test/query
      [2018-03-23 12:58:18] Fuseki     INFO  [11] 404 Service Description: /test/query (0 ms)

       

      On the one hand, Fuseki seems to be aware that it should be supplying a Service Description there, but on the other, it ain't doing that. So this ticket could go two ways: if we don't claim to have implemented Service Description, it's a ticket for doing that (in some of our copious free time). If we do claim to implement it, it seems like it's not working quite right. (Unless, as is more than possible, I don't understand how Service Description is supposed to work. I'm going on "SPARQL 1.1 Service Description" section 2, which says,

      SPARQL services made available via the SPARQL Protocol SHOULD return a service description document at the service endpoint when dereferenced using the HTTP GET operation without any query parameter strings provided. This service description MUST be made available in an RDF serialization, MAY be embedded in (X)HTML by way of RDFa [RDFA, and SHOULD use content negotiation [CONNEG if available in other RDF representations.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              ajs6f Adam Soroka
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: