Following a discussion in the SEC yesterday. Where there was agreements on all the outstanding issues for the migration of the community to ADL2.4. (Huge success for the community! proving a willingness to work together on difficult topics and to make significant compromises/investments for a shared…

@pablo let’s do the discussion here: [image] Archetypes in YAML +1 on the comment by @sebastian.iancu I don’t want to start a discussion on which format is “better”, just wanted to point out those formats were mentioned in the NL SEC meeting. [image] Archetypes in YAML is that for JSON the…

[image] joostholslag: Ideally I’d have ADL artefacts in YAML primarily, because of (arbitrary) legibility over json, do validation using json (or yaml) schema. And work together on an export/serializer to json (in this case of the archetype, not the aom/adl meta schema). Off course I’m not agai…

[image] pablo: that’s “model based transformation”, for instance YAML ==(parse)=> AOM instance ==(serialize)=> JSON or JSON ==(parse)=> AOM instance ==(serialize)=> YAML If we only discuss YAML and JSON as possible formats, the conversion should be direct, using standard libraries for convert…

[image] borut.jures: however Silje and Thomas are saying there are “many” editors who edit archetypes by hand. It would be great to hear what “many” means in this case and if they only make “small” changes by hand (which wouldn’t be that painful in JSON). Very arbitrary, but: My best guess w…

It is certainly not ‘common’ to have to edit ADL manually but it is definitely needed occasionally. I’ve edited the YAML samples to use 2 spaces and I think the nesting is probably visually not an issue and I presume a decent editor will help validate incorrect spacing e.g if new content is added. …

Unsupported comments in JSON are a “feature”. I use all the “comments” and documentation in my generators to include as much helpful into in the generated artifacts. The node identifiers are taken from the terminology section and added to the nodes. We will not loose these in YAML/JSON. p.s. I ha…

Can you give an example of your ‘commented’ json archetype

In these discussions about the ADL we tend to forget that ADL is just a format for serialization and exchange, but the real modeling formalism is AOM. I mention this because probably we should not waste time discussing about choosing one format or the other, but assume that the systems should suppo…

[image] ian.mcnicoll: Can you give an example of your ‘commented’ json archetype Comments in JSON could use a similar approach as types: "_comment": "some text" I’m not suggesting to add _comment to the JSON – I prefer the current documentation properties/attributes. I’m not using comments…

[image] damoca: In these discussions about the ADL we tend to forget that ADL is just a format for serialization and exchange, but the real modeling formalism is AOM. If we talk about the cADL part of ADL (the definition part), ADL is a human level format like a programming language. All the …

ADL formalisms

Specifications ADL

Topic		Replies	Views
Separating Models from Implementation New to openEHR?	107	6116	11 December 2021
occurrences and cardinality in ADL, XML, JSON Technical (archive)	30	158	21 November 2011
SNOMEDCT - correct representation Implementers (archive)	49	350	20 May 2017
JSON Schema and OpenAPI: current state, and how to progress ITS rest-apis , json	40	4945	8 April 2025
Archetypes in YAML ADL yaml	26	542	21 June 2024
New ADL/AOM proposals to solve some old problems Technical (archive)	15	73	29 April 2013
Agreeing on optional user interface hints in templates Specifications ux , forms	53	2856	29 April 2026
Rules in archetypes - a migration path ADL	17	591	28 January 2021
Looking ahead to openEHRv2 Specifications openehrv2	27	617	11 May 2026
Coding element and event names Specifications template	59	1519	28 August 2026

ADL formalisms

Related topics