sparql.md

home #SPARQL Endpoints#

The data of The Gazette can be queried against by using SPARQL against one of the two endpoints provided. The main /sparql endpoint is populated with data from the modern notices which have been placed in the Gazette (starting from 1998). The /longitudinal-dataset/sparql endpoint contains the information derived from indexes of Archive of the Gazette and span a time period from 1900 to 1999.

Useful resources:

• Sample queries
• Flint editor on the gazette website
• Flint SPARQL editor project on github

Resource URL

/sparql

and

/longitudinal-dataset/sparql

Alternative representations

Generic Document URI	Method	Response type
/sparql /longitudinal-dataset/sparql	GET or POST	Various

Content Negotiation

The system utilises content negotiation by default. Content negotiation allows an application to request the format of the results it needs as part of the HTTP request.

The available formats are given in the table below:

Generic Document URI	Method	Accept header​	Response type
/sparql /longitudinal-dataset/sparql	GET or POST	application/sparql-results+xml	SPARQL/XML
		application/rdf+xml	RDF/XML
		application/sparql-results+json	JSON
		application/turtle	Turtle

• Details on SPARQL/XML
• Details on JSON results

Parameters

query	Contains the text of the SPARQL query The text needs to be encoded using application/x-www-form-urlencoded format
	Example Values:
output	desired output format for the response
	Valid Values: text, sparql, json, rdfxml, turtle