LDPizer

Aim of the LDPizer

LDPs are data-driven system and their deployment involves deploying both the data and the system. Current solutions for LDP addresse only the latter part. There is currently no solution for automatizing the deployment of data in LDP. The aim of the LDPizer is to automatize the deployment of RDF and non-RDF data into LDPs.

How it works:

The LDPizer takes as input:

1. A design document
2. Some parameters provided by the user which includes at least the base URL of the LDP. If for sending POST request, authentication is required, username and password have to be specified. Currently, the LDPizer support only basic authentication

The design document is written using the vocabulary. For information on how the LDPizer process the design document, refer to the LDPizer repository

Demonstration:

1. Deploy the Paris data catalog using the design document. An instance of an LDP using this design document is running at http://ci.emse.fr/marmotta/ldp
2. Deploy the Toulouse data catalog using modifying the data source of the design document for Paris data catalog.
3. Deploy a dataset extracted from LinkGeoData using the SPARQL Construct Query which relates to geographical places in Paris using a design document
4. Use our LDP Browser to load the LDP (http://ci.emse.fr/marmotta/ldp) deployed using the Paris Design document in (1) and show the resulting LDP automatically deployed using the LDPizer. The LDP Browser can be used for any LDP. To use it, use the LDP base IRI, and load it with the browser