Back-end storage options (from Kingsley Idehen)

[gklyne]

From Kingsley Idehen: https://lists.w3.org/Archives/Public/public-lod/2015Feb/0116.html
[email protected]

Kingsley requests at least one of:

1. LDP
2. WebDAV
3. SPARQL Graph Protocol
4. SPARQL 1.1 Insert, Update, Delete.

My comment: WebDAV(ish) was on the original roadmap - see #32. The intent has been to use vanilla HTTP as far as possible (GET, PUT, POST, etc.) and then use WebDAV PROPFIND(?) to enumerate directory contents. The more complex stuff isn't needed.

Kingsley also mentions not to worry about access control, but leave that to the backend. But it woud be the Annalist server, not the browser, that acesses the backend data so there would need to be some way to convey whatever authentication/authosization tokens are needed. My rough plan was to use an OAUTH2/OIDC enabled backend that should be a small extension from the current OIDC authentication logic already used by Annalist, but the details still need to be worked out.

[gklyne]

See also: SoLiD (https://github.com/solid/solid-spec), which is a spec that builds on LDP. Of particular interest to future developments is the Live Updates aspect (https://github.com/solid/solid-spec#live-updates), though I had been contemplating something more akin to Provenance Pingbacks (http://www.w3.org/TR/prov-aq/#provenance-pingback).