Shi3ld for HTTP operations
- Authorization for r/w HTTP Methods on RDF resources
- RDF Resource-oriented
- Policy Language in RDF/SPARQL or RDF only
- "Context-aware" Policies
The policy vocabularies namespace documents are available at:
Shi3ld for HTTP supports three different scenarios and are available in this repository branches:
- Shi3ld for SPARQL Graph Store Protocol
- Shi3ld for Linked Data Platform (SPARQL-based)
- Shi3ld for Linked Data Platform (SPARQL-less)
Scenarios are detailed in our paper Access Control for HTTP Operations on Linked Data
All Shi3ld scenarios are Java server side modules that run in a java application server (e.g. Tomcat)
config.properties property file needs to be customized with the policy storage path and the triple storage path.
The Shi3ld-GSP scenario is compatible with the GSP-compliant Fuseki SPARQL engine needs the Fuseki server URL and the Fuseki dataset name.
The Shi3ld-LDP scenarios embed the Corese/KGRAM RDF store and SPARQL processor.
Shi3ld-HTTP can be tested with a standalone client shipped with sample client attributes.
Sample Access Policies can be found here.