Sesame 2.x HTTP Protocol Interface

The “HTTP communication protocol for Sesame 2” as described in detail in the rdf4j documentation, comprises three principle cabilities:

repository administration

The standard adminstration operations are available at the respective relative resources

  • contexts
  • size
  • namespaces

content management

Content management requests apply to the resource

http://dydra.com/<account-name>/repositories/<repository-name>/statements

The supported methods include those specified for Sesame as well as the PATCH method. For those requests, the Sesame protocol for a given resource location is extended to accept content as desribed for the Graph Store PATCH method.

repository queries

Queries are adressed to a repository as the resource

http://dydra.com/<account-name>/repositories/<repository-name>/statements

This is a current implementation limitation, as it is planned to align the name with the Sesame protocol in a future release. Of the standard parameters, the following are not supported - queryLn : SPARQL1.1 query and update are supported. SeRQL is not supported. - infer : No inference is performed. - $<timeout> is ignored

In addition to the standard parameters, a Dydra SPARQL endpoint permits the following - revision : A revision designator sets constructs the query dataset from the respective revision - provenance : A repository identifier enables provenance record generation to be saved in the respective repository upon completion of a SPARQL update request.

graph store requests

Graph store requests are adressed to a direct graph which comprises the repository as the resource

http://dydra.com/<account-name>/repositories/<repository-name>/rdf/direct/graph

or the standard graph store end point

http://dydra.com/<account-name>/repositories/<repository-name>/service

in which case, the graph may be specified indirectly.

Table Of Contents

Previous topic

Library Functions

Next topic

Native RPC Interface