On 11/11/2011 08:15, Shinji KOBAYASHI wrote: > Hi Thomas and colleagues, > > I would like to discuss about the other serialization form of archetype, too. > I thought YAML could be an alternative of them.
I had forgotten about YAML I have to admit. It would be interesting to support that in the ADL 1.5 tools as well. I will look into it. > However, JSON/YAML are based on weakly typing languages, do not have > established scheme definition, such as XSD/ADL. > > inline. > > 2011/11/11 Thomas Beale<thomas.beale at oceaninformatics.com>: > >> ~~~~~~~~~~ first question: occurrences and cardinality ~~~~~~~~~~~~~~~~ >> but the upper limit is commonly unbounded, i.e. '*' in typical UML-like >> syntax. We could do: >> >> occurrences =< >> lower =<2> -- Integer field >> upper_bounded =<True> -- Boolean field > I think upper_bounded is typo for upper_unbounded, but this format has the oops - you are right. Sorry about that. > most conformance to INTERVAL specification of assumed types library. > I agree this, because this form is easier to parse and generate an > INTERVAL instance. > I also agree with the first way of XML scheme with the same reason. > > BTW, Rubyist might be prefer this format(YAML): > > occurrence: > 2.. well, that's close to what I generate in dADL right now: but XML developers don't like that. - thomas -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20111111/e861b406/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: ajbbddgj.png Type: image/png Size: 2382 bytes Desc: not available URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20111111/e861b406/attachment.png>
