...
Item | Presenter | Goals | Notes | |
|---|---|---|---|---|
5 min | Opening | USEFUL Jira RESOURCE: CRs I have not accepted. | ||
20 min | Releases | Status update Done In Progress
Next
| ||
30 min | Citations / Refs / managed lists | agree approach to requirements | ||
10 min | REST / JSON | Seref Arikan (Personal) : follow up JSON schema / OpenAPI discussion. OpenAPI flavour of openEHR REST APIs. | Need a Confluence ITS (-JSON) related page to share knowledge about tools. Seref Arikan 3 kinds of JSON artefact (Code24 JSON schema; Nedap JSON schema; Nedap OpenAPI form) - how do they interoperate from POV of a) instance validation and b) code generation (the 2 functions that matter for this kind of artefact). Pieter Bos OpenAPI form when used in validation will sometimes accept too much. Seref Arikan took OpenAPI and did a forward code generation to TypeScript. Idea is to provide a developer artefact for populating e.g. screen form fields. Need to solve typing anomalies; if we can do that - then we have a micro-API object building approach for React & similar JS UI dev envs. | |
AQL | Seref Arikan - Need to agree subset of vendor-originated semantics across vendors. Currently no approach to demographics. Diego Bosca don’t forget Integration model. Thomas Beale consider Q of dependence (or not) on openEHR RM specifically. Diego Bosca - consider concrete identifier representation, namespaces and other details. Seref Arikan we should limit to scope to commercially relevant functionality, no more. | |||
10 min | AQL | Ian McNicoll : Reference following in queries; | ||
Next SEC call | ||||
Agenda items for next call: | ||||
Outstanding topics:
| ||||
...