Changes between Version 2 and Version 3 of BluePrint/HXL


Ignore:
Timestamp:
01/29/14 23:04:56 (8 years ago)
Author:
Dominic König
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrint/HXL

    v2 v3  
    3939(Note that this RDF/XML example is only one possible notation)
    4040
    41 Typically, data-producing EM applications would export such a description of their data resources to a common database (triple store), which can then be queried from consuming applications using standard APIs (e.g. RDF/SPARQL) and export the data into standard formats, e.g. DOC, KML, or XLS.
     41Typically, data-producing EM applications would export such a description of their data resources to a common database (triple store), which can then be queried from consuming applications using standard APIs (e.g. RDF/SPARQL) and extract/export the data into standard formats, e.g. DOC, KML, or XLS.
    4242
    43 The purpose of this BluePrint is to define the role of Eden as HXL exporting application, or as triple store with RDF/SPARQL API or as HXL consumer.
     43The purpose of this BluePrint is to define the role of Eden as
     44  - HXL exporting application
     45  - as triple store with RDF/SPARQL API
     46  - as HXL consumer application
    4447
    45 The most obvious role for Eden at this point is that of the HXL exporter. A proof-of-concept prototype XSLT template has been implemented for the project_activity resource.
     48The most obvious role for Eden at this point is that of the HXL exporter.
     49
     50A proof-of-concept prototype XSLT template has been implemented for the project_activity resource.
    4651== Stakeholders ==
    4752