Discussion: Add a controller to components

[alangrafu]

The lack of a controller component was an intentional in the first versions of lodspk. However more and more I see the need of it for other functions besides data publishing:

• You want to add data form other sources
• You want to manage data using other libraries (e.g., statistical libraries) that are beyond of what lodspk and Haanga can/want to do
• You want to enable read/write operations
• You want to control which queries will be executed depending on previous results
  • Corolary: change the endpoint of a query?
• You want to list all the services, types and uri components available in a lodspk installation without doing a hack :)

For all this, we need to specify:

• If no controller exists, keep things as usual (execute queries, apply results in template)
• If controller is available, support:
  • HTTP PUT, DELETE and POST at least
  • Flow control
  • Api for accessing SPARQL endpoint?
  • Others

[alangrafu]

VERY PRELIMINARY idea of how a controller should look like

require_once('abstractController.php');

class myService extends abstractController{

  public function doGet(){
    global $lodspk;
    global $models;
    $this->query('.'); //run first level of queries (in dir queries/)
    if($lodspk['foo'] == 'bar'){
      $this->query('dbpedia'); //run queries in dir queries/endpoint.dbpedia
    }else{
      $this->query('logd'); //run first in dir queries/endpoint.logd
    }


  public function doDelete($args){
    global $lodspk;
    $uri = Utils::curie2uri($args[1]);
    $this->deleteAll($uri, null); //delete all triples where $uri is involved in the default named graph
  }

}