Tupelo Server supports URIQA's "semantic web service" model. In that model, URIQA requests (and Tupelo requests that extend URIQA) are issued as HTTP POSTs against a URL identifying the Tupelo Server instance. Tupelo deviates from the URIQA specification in several important ways:

  1. Tupelo Server does not support the notion of a Concise Bounded Description but instead MGET is extended with a depth parameter that enables arbitrarily-deep subgraphs to be returned regardless of whether the intermediate nodes are blank (at high depths this can be slow depending on the capabilities of the server's backend metadata store.)
  2. Tupelo Server supports RDF serialization formats in addition to RDF/XML (currently N3 and N-Triples).
  3. Tupelo Server allows URIQA semantic web service-style methods to be issued against a resource using GET, PUT, and DELETE in addition to POST.
  4. Tupelo Server provides several additional semantic web service methods including PUT, GET, and DELETE for CRUD on the resource (not its metadata) as well as MQUERY for issuing complex RDF queries against the backing Context.
  • No labels