yes, what I mean is attributes like ID or even invalid characters in the names (like ':'). This is a problem with the parser (and also with classes identifiers)
2011/9/10 Thomas Beale <thomas.beale at oceaninformatics.com>: > On 10/09/2011 12:59, Diego Bosc? wrote: >> >> This kind of problems has given us a lot of problems when using ADL to >> work with other models like HL7 CDA or CDISC ODM, where there isn't >> any kind of rule (for example, in ADL CLASSES must be upercase and the >> attributes lowercase, and in CDA this is not true) > > actually there is no rule in ADL. You can use CamelCase, and it has been > working for the entire lifetime of the tools. Indeed you will see it in > the 13606 and 21090 schemas, which are processed by the ADL Workbench. > It's just that the documents use a particular convention which happens > to be the underscore convention, for better readability. My view is that > any given model should stick to one or the or the convention > consistently, whatever convention that may be. > > - thomas > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical >
