The Architecture overview specification needs to be updated with various high-level elements - component and packages etc, and some better diagrams. Tool-generated UML diagrams should be used, and newer packages need to be added in.
your JSON is using various rules I don't know about, e.g. @archetype_node_id, and field 'type' etc. But we don't have an agreement in openEHR on things like that, apart from the "_type" we agreed in the REST API?
you may have an opinion on this.
I don't know what the JSON should really look like, but what I put there probably is not quite right. How do we fix that?
Json schema is more or less formal specification and uses some reserved keywords (e.g. type) to represent the schema. Point was that is easy to convert to other representations
and it's undoubtedly a Good Thing; I just don't think we are sufficiently on top of it (or maybe just me) to know exactly what flavour of JSON we should be using in these specs. If you / Erik do know and agree, feel free to give me a corrected version of the example I included in this spec and I'll fix the text accordingly.
Or - we can document the example as being 'typical JSON'...
i don't think we should add any schema unless we have a formal agreement on what version of the schema specification should that be based;
about '_type': we indeed agreed on, but it is missing from your example example Thomas. I think you need to add it to OBSERVATION, ITEM_LIST, EVENT (i guess is POINT_EVENT). Also, the magnitudes should been float instead of string? Here is my example: https://pastebin.com/jMFRzF8c
thanks - I've replaced the JSON with yours and uploaded. I think this is now good enough to use. Agree that formal agreement should come later.