I agree with you, except for how damn limiting pure json* is. Any attempt
to introduce long-ints or annotation take you to vertical-specific json+.
* json is javascript, so has type and other limitations.
On Fri, Feb 15, 2019, 7:39 PM Bert Verhees A few last words on this.
>
> It is easy for
> The folks doing CIMI use at least the JSON mode. It also generates XML, via
> custom serialiser.
> One of the jobs I never completed is a deserialiser for the 3 regular
> formats, but it is nearly trivial.
Exactly my point, I completely agree with this.
Bert
>
> Venkat Subramaniam, who
A few last words on this.
It is easy for JSON based archetype repository to cooperate with an ADL based
repository. Serializing of an AOM structure to ADL is very easy to do, this
counts for the DADL and CADL part. The other way around, to convert the ADL
definition part to JSON is harder,
Sent from my Xperia™ by Sony smartphone
Original Message
Subject: Re: JSON for definitions-notation
Sent: 15 Feb 2019 22:46
From: Bert Verhees
To: Pieter Bos
Cc:
Not many people find archetypes readable. I can read them and I have done that
many times, but most modelers I know
Archie offers a json serializer and deserializer. For Odin they are present as
well, but has not been tested with archetypes, may need a small bit of work.
Yaml should be a matter of adding a dependency and configuring it.
We're still working on XML - the bindings are there and it works, but the
The object dump is a common use-case for JSON.
There a few things that are needed more then the object dump.
What we would still need is standardised naming-notation of classes and
properties, so there cannot be a conflict on that. I think the current
format used in OpenEhr is very good,
JSON, YAML and ODIN are all just object-dump serial formats that result
from traversing an in-memory object graph, so it is a generic operation
to generate them from tools (XML is more problematic due to being
irregular in many ways and being schema-dependent).
In the case of archetypes, the
I always admired OpenEhr for its ability to notate archetype-definitions
and now also BMM definitions in any type.
I saw experiments in XML, but the official endorsed notation language is
ADL.
I wonder, would it also be possible to write archetypes and
reference-models in JSON?
If so, it
8 matches
Mail list logo
