Skip to content

endpoint not working outside of squebi interface #16

@bobdc

Description

@bobdc

The HTML interface to the endpoint at http://data.carnegiehall.org/sparql/ works fine but attempts to query the endpoint itself make it look like the endpoint is not supporting the SPARQL protocol.

The following URL is shown in the browser's address bar as the default query when using the squebi interface, and it works fine in the browser:

http://data.carnegiehall.org/sparql/#?query=SELECT%20*%20WHERE%20%7B%0A%20%20%3Fs%20%3Fp%20%3Fo%20%0A%7D%20LIMIT%209&writer=browse

Using curl to talk directly to the SPARQL endpoint, like this, just retrieves the HTML of the squebi form when it should retrieve XML or JSON of the answer set (I tried both "http:" as shown and "https:"):

curl "http://data.carnegiehall.org/sparql/#?query=SELECT%20*%20WHERE%20%7B%0A%20%20%3Fs%20%3Fp%20%3Fo%20%0A%7D%20LIMIT%209"

As an example of how it should work, the same query sent to the Smithsonian's SPARQL endpoint works fine:

curl "https://edan.si.edu/saam/sparql?query=SELECT%20*%20WHERE%20%7B%0A%20%20%3Fs%20%3Fp%20%3Fo%20%0A%7D%20LIMIT%209"

It also works when sent to Wikidata's SPARQL endpoint:

curl "https://query.wikidata.org/sparql?query=SELECT%20*%20WHERE%20%7B%0A%20%20%3Fs%20%3Fp%20%3Fo%20%0A%7D%20LIMIT%209"

Because of the wonderful data in the Carnegie Hall linked data dataset, I was going to use it in a demo of SPARQL in a Jupyter notebook on http://bobdc.com/blog/ , but the notebook plugin talks to endpoints using the SPARQL protocol, so I can only use endpoints that support that.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions