Clarify Desired Export Functionality

[Aklakan]

There are several scenarios for customization of the data. Each of these formats is useful, however the applicable use cases differ:

• A table showing the triples corresponding to a certain node in the facet tree. Useful for export of all information directly related to a set of resources. Such table could be directly serialized as CSV and one of the RDF formats.

  [subject, predicate, object]
  <http://rdf.freebase.com/ns/m.07-nxm> rdfs:label "Europa-Park"@en
  <http://rdf.freebase.com/ns/m.07-nxm> rdfs:label "Europa-Park"@de

• A table where facets have been linked to columns. Works well with the http://fp7-pp.publicdata.eu/sparql dataset, where one can e.g. create a table with columns [project, partner, amount] with the purpose of viewing fundings of project partners. CSV export of such table is straight forward. RDF export would include only the triples relevant for the construction of the table. [project, partner, amount] [LOD2, UniLei, 1.3mio]

  This approach may lead to denormalized tables: [item, rdfs:label, rdfs:type]

  <http://rdf.freebase.com/ns/m.07-nxm> "Europa-Park"@en freebase:AmusementPark
  <http://rdf.freebase.com/ns/m.07-nxm> "Europa-Park"@de fbo:AmusementPark
  <http://rdf.freebase.com/ns/m.07-nxm> "Europa-Park"@en owl:Thing
  <http://rdf.freebase.com/ns/m.07-nxm> "Europa-Park"@de owl:Thing

• A list for each property with the corresponding values. This corresponds to grouping and nesting the data, and thus JSON and XML could be suitable export formats. CSV export would yield a two column table with a 'key' and a 'values' column (the latter containing a list of values). RDF export would include all relevant triples.

  rdfs:label: "Europa-Park"@en, "Europa-Park"@de
  rdf:type: fbo:AmusementPark, owl:Thing

• Multiple tables. We could add support for the definition of multiple tables. The user could then export each table as a separate CSV file.

[Aklakan]

There is now an exporter for Sparql result sets as XML and CSV. A missing piece is using the Sparql result set + meta information of the facet selection in order to generate an RDF file.

Essentially, all triples that back the sparql result set need to be exported. If there is just one column, yield artificial triples with ?s a rdf:Resource. (If the type was desired, it could be added to the table)

[Aklakan]

Closing this issue as I suppose the questions are resolved for now.