AOM XML Schema
After checking the schema, I have seen some places that the schema (specifically basetypes.xsd) is missing things that are indeed supported by ADL (namely assumed_values, lists, etc.) What is the process to update the schema?
Constraints on class methods
I found that offset was a stored value at openEHR RM 0.95 (back in 2005), but then it became a computed method. 2012/1/15 Thomas Beale thomas.beale at oceaninformatics.com Life would have been much easier if Event recorded 'offset' as a stored value, and the 'time' was the property being computed. I argued strenuously for that years ago, precisely to avoid the problem we are talking about here, but lost the battle ;-) ___ openEHR-technical mailing list openEHR-technical at openehr.org http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical -- David Moner Cano Grupo de Inform?tica Biom?dica - IBIME Instituto ITACA http://www.ibime.upv.es Universidad Polit?cnica de Valencia (UPV) Camino de Vera, s/n, Edificio G-8, Acceso B, 3? planta Valencia ? 46022 (Espa?a) -- next part -- An HTML attachment was scrubbed... URL: http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20120116/f2d17f07/attachment.html
Constraints on class methods
On 16/01/2012 06:12, David Moner wrote: A possible problem I can envision is that this opens the door to the creation of invalid archetypes without the possibility of validating them at design time. A quick and dirty example just to get the idea. In an archetype, the HISTORY.origin is fixed to T10:00:00, a child EVENT.time is fixed to T18:00;00, and finally the EVENT.offset is fixed to PT5H. Offset is clearly not valid regarding time and origin, but we do not know it since the expression to calculate it is not explicit anywhere (only at the RM specifications). that problem can occur even with just two normal attributes, if they happen to have a mathematical relationship... - thomas
