Make the triplestore the 'master' database

This is part of a possible solution to SolidarityEconomyAssociation/open-data-and-maps-outreach#89.

The CSV is effectively the 'master'. To publish LOD, we

Allow highly-granular operations to update the triplestore directly. For example:

Change the object of one existing triple (subject, and predicate already exist)
Add a new triple (regardless of existence of subject and predicate)
Delete a triple
Replace all triples related to an sse-initiative with a new set. This begs the question: what do we mean here by 'related to'? Further investigation needed. For a start, look at the concept of Linked Data Platform Containers in the Linked Data Platform .
Delete an sse-initiative including all its related triples. Again this begs the same question as above: What do we mean here by 'related'?
Add more triples to an existing sse-initiative

This is a big question! The 'obvious' (?) mechanism is to use SPARQL 1.1 UPDATE operations.

Things to look at:

SPARQL 1.1 Update
SPARQL 1.1 Graph Store HTTP Protocol
Open Link RDF editor, as an example of editing RDF
Dokieli - Interesting tech for maintaining distributed docs with distributed comments, etc
Solid, Solid on GitHub.
- Note: Solid uses LDP.
Linked Data Platform - essential reading

Linked Data Platform (LDP) defines a set of rules for HTTP operations on web resources, some based on RDF, to provide an architecture for read-write Linked Data on the web.
and Using Virtuoso as LDP Client and Server
public-rww mailing list - a good place to ask a question about best practices
W3C Solid Community Group (Matt is a member)

A key (no pun intended!) part of allowing updates directly to the triplestore is authentication of those making the updates.

DigitalCommons / open-data-and-maps