...
- Ocean (XML?)
- Marand (JSON, see below)
- DIPS (JSON, see below)
- All the LiU-EEE-specific schemas are at https://github.com/LiU-IMT/EEE/tree/master/src/main/xsd
- Our experimental result format for queries of XML data (originally intended for openEHR AQL queries) in that directory is at https://github.com/LiU-IMT/EEE/blob/master/src/main/xsd/xml-result-v1.xsd It was inspired by SPARQL's result set at http://www.w3.org/TR/rdf-sparql-XMLres/
- ...but agreeing on a JSON-format is probably more urgent than for XML.
- The JSON format for SPARQL might be a useful input for thought though, see http://www.w3.org/TR/2013/REC-sparql11-results-json-20130321/ The "head" and "bindings" stuff using vairables from the query might be interesting. The SPARQL response looks a bit more like the Marand than the DIPS version. I am not sure that using terms like "rows" and "columns" (like in the DIPS-version) is the best for tree-shaped NoSQL data (even though they are logically some kind of rows).
- Archie (has RM serialization in JSON & XML?)
- Code24 (see below)
Marand Ehrscape result set
...
| Code Block | ||
|---|---|---|
| ||
"data" : {
"type" : "HISTORY",
"name" : {
"type" : "DV_TEXT",
"value" : "history"
},
"archetype_node_id" : "id2",
"events" : [ {
"type" : "POINT_EVENT",
"name" : {
"type" : "DV_TEXT",
"value" : "any event"
},
"archetype_node_id" : "id7",
"time" : {
"type" : "DV_DATE_TIME",
"magnitude" : 1466427403,
"value" : "2016-06-20T14:56:43.702+02:00"
},
"data" : {
"type" : "ITEM_TREE",
"name" : {
"type" : "DV_TEXT"
},
"archetype_node_id" : "id4",
"items" : [ {
"type" : "ELEMENT",
"name" : {
"type" : "DV_TEXT",
"value" : "Systolic"
},
"archetype_node_id" : "id5",
"value" : {
"type" : "DV_QUANTITY",
"magnitude" : 120.0,
"precision" : 0,
"units" : "mm[Hg]"
},
"path" : "/data[id2]/event[id7]/data[id4]/item[id5]"
}, {
"type" : "ELEMENT",
"name" : {
"type" : "DV_TEXT",
"value" : "Diastolic"
},
"archetype_node_id" : "id6",
"value" : {
"type" : "DV_QUANTITY",
"magnitude" : 80.0,
"precision" : 0,
"units" : "mm[Hg]"
},
"path" : "/data[id2]/event[id7]/data[id4]/item[id6]"
},
|
Code24
Code24 does not have yet implemented AQL, but most probably it will be ready in Q3/Q4 2016. Intention is to follow the same JSON as Marand's example above. The current RESTApi that we have at this time is published at http://rest.base24.nl/docs
JSON Specifics
Proposed Standard
...