Changes between Version 2 and Version 3 of BluePrint/HXL

Timestamp:

01/29/14 23:04:56 (11 years ago)

Author:

Dominic König

Comment:

--

BluePrint/HXL

@@ -39 +39 @@
 (Note that this RDF/XML example is only one possible notation)
 
-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.
+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 extract/export the data into standard formats, e.g. DOC, KML, or XLS.
 
-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. 
+The purpose of this BluePrint is to define the role of Eden as 
+  - HXL exporting application
+  - as triple store with RDF/SPARQL API 
+  - as HXL consumer application
 
-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.
+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.
 == Stakeholders ==