Comments (3)
Discussion starter: Personally I see most value in some natural-language-independent, AQL-path-based version along the lines of ECISFLAT described in https://github.com/ethercis/ethercis/blob/master/doc/flat%20json.md that could be used for cut&paste of paths from tools.
If we want compact language-specific, human-readable serialization, then perhaps it would be of higher priority to complete an official spec on TDS3 that is partially described at https://openehr.atlassian.net/wiki/spaces/spec/pages/30408770/Template+Data+Schema+TDS+Specification+and+associated+Template+Data+Document+TDD (maybe a JSON version of it could be derived/specified too)
from specifications-its-rest.
When 1.0 of the rest spec is done, the "flat JSON format" discussion should be picked up again for version 1.1 of the REST spec. Some updates/revisions to the discussion starter above follow.
- Language independence is likely not possible when there are otherwise identical sibling nodes.
- Two versions of a flat format might actually be a good thing for different use cases
- Full flat - showing the as canonical paths as possible (paths often found in archetype/template tools), including archetype ID's and at-codes where appropriate. Inspiration: ECISFLAT.
- Compact flat - does it need to be dependent on some future standardized form definition or is it enough to know the template to make it compact? Inspiration: Marand's flat format
- The relevant REST calls can likely be unmodified just new content types (and formal format specifications) added in https://openehr.org/releases/ITS/latest/docs/ehr.html#design-considerations-data-representation. Some idea starters
- Current canonical XML: application/xml
- Current canonical JSON: application/json
- Full flat JSON: application/openehr.flat+json
- Compact flat: application/openehr.flat.compact+json
- Possibly flat formats using other formalisms like XML etc could be added later like application/openehr.flat+xml
- TDS3/TDD is likely a different use case (and XML centric) that should not be mixed with this Github issue.
from specifications-its-rest.
This is taken care in abstract SM, in https://openehr.atlassian.net/browse/SPECITS-33 and https://github.com/openEHR/simplified-format-incubator
from specifications-its-rest.
Related Issues (20)
- PUT composition - typo on no content request?
- Create EHR request defines invalid RM data for Ehr_Status HOT 5
- Clarify RM types for returned data when creating an EHR HOT 2
- Remove reference to deleted EHRs from description of Get EHR_STATUS version by time HOT 1
- Get Versioned_Ehr_Status description in REST api is inconsistent
- Clarify if ORIGINAL_VERSION can be returned where VERSION is expected HOT 1
- Incorrect contens for ORIGINAL_VERSION body contents
- Content-Type header in REST API calls should not be mandatory for empty content HOT 2
- Behaviour for use of composition uid's in POST requests needs clarification HOT 3
- REST: Behaviour of POST when COMPOSITION has a uid should be clarified HOT 2
- REST: Query specifications should reference Definitions HOT 1
- {preceding_version_uid} as path or header parameter? HOT 2
- Split template definition endpoints to adl1.4 one and adl2 one
- Add an undelete operation to the composition endpoint
- Example body for stored AQL query is incorrect.
- Remove version support for template endpoint for adl 1.4 HOT 12
- Documentation issue PUT Composition HOT 3
- Content-Type header in 204 Responses
- GET Template ADL 2 - small inconsistency
- Error on the development build process HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from specifications-its-rest.