View Materialization

Dydra extends the W3C SPARQL HTTP Protocol to permit access to repositories which constitute materialized views. The facility permits to materialize the results for any query defined in a repository’s web interface under

http://dydra.com/<account-name>/<repository-name>/@query

A materialized request is a GET request to the repository which stores the materialized cache. As a convention, these repositories carry a name which combines the name of the base repository with that of the view and an indicator for the view form. Each view form interprets the requst argument values and yields results respective its index. (See Materialized Repository Management .)

GET

A GET request to a view endpoint returns the results from materialized form which correspond to the query argument values

http://dydra.com/<account-name>/<source-repository-name>__<view-name>__view/sparql?parameterName=argumentValue

The accept type should correspond to the form of the source query, which may be either a SELECT or and CONSTRUCT.

The index and result generation process varies respective the view repository type

repository class

processing

internal-view-repository

  • parameters are established by the associated query

  • request argument values permit any term type

  • the solution set or graph reflects the projection or construct template of the associated query

internal-text-repository

  • the string pattern is the one parameter

  • the request argument values permits a string only

internal-text-view-repository

  • parameters are established by the associated query

  • request argument values permit strings only

  • the solution set or graph reflects the projection or construct template of the associated query

Headers

Accept: specifies the SPARQL response document media type.

Query Arguments

$<parameterName>="<argumentValue>"

nb. the URL formulation should observe url encoding rules.