Very interesting thoughts Tom! My initial impression of the proposal is very positive. If I understand things correctly this will enable shorter and more readable serializations not only in ADL but also in other formalisms.
If we consider ADL being a DSL<http://en.wikipedia.org/wiki/Domain-specific_language> mainly targeted for constraining health-related RMs then simplifications towards that goal are welcome. The only potential catch is implementation issues. Have you already tried implementing a parser for this in some language? (If so, please provide a link.) I guess the suggestion could make some implementation parts easier and some a bit trickier. Best regards, Erik Sundvall LiO: erik.sundvall at lio.se http://www.lio.se/Verksamheter/IT-centrum/ LiU: erik.sundvall at liu.se http://www.imt.liu.se/~erisu/ P.s. [/daydreaming] It might be interesting to connect a future updated AOM 1.5 in Java with (de)serialization using Jackson, see https://github.com/FasterXML Jackson already supports several highly configurable serialization format options, perhaps ADL or ODIN databindings would be possible too ;-) RM bindings might be a more interesting use case than AM bindings though... On Wed, Apr 24, 2013 at 7:03 PM, Thomas Beale < thomas.beale at oceaninformatics.com> wrote: > > In openEHR we use custom syntax in archetypes to express ordinal > constraints, quantity constraints and coded text constraints - i..e > constraints on what are probably the most ubiquitous data types in health. > > I have been mulling over feedback from previous debates here and in CIMI > about the 'undesirability' of this syntax. > > I have posted some new ideas on how to solve this > here<http://www.openehr.org/wiki/display/spec/ADL+1.5+Power+Syntax+Proposals> > . > > The executive summary is: > > - let's treat 'code' as a built in type, like a Date or a Uri; this > then makes an AOM type that constrains this trivial; > - ADL can be augmented in a generic way to enable tuples to be > constrained, which would better solve the Quantity constraint problem > - The Ordinal constraint syntax would be replaced by a combination of > both of the above. > > Feedback welcome. > > - thomas > > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at lists.openehr.org > > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130425/0eaf65da/attachment.html>
