2006/11/17, Andrew Patterson <andrewpatto at gmail.com>: > > > I know that the C_MULTIPLE_ATTRIBUTE class has a property of 'members' > in > > the AOM (since I know the AOM very much in detail), but it's not in the > XML > > schema specification. I have not followed the AOM, because I thought I > was > > only supposed to look at the schema. > > The AOM is at fault in this instance - the AOM has a field defined in > C_ATTRIBUTE called 'children', and then proceeds to rename this field > to 'attributes' and 'members' in the two subclasses C_SINGLE_ATTRIBUTE > and C_MULTIPLE_ATTRIBUTE. This of course is not really implementable > in any OO style language or XML.. the XML schema does the correct > thing and just defines 'children' in the base C_ATTRIBUTE class.
No, it proceeds to rename this field to 'alternatives' (not attributes) and 'members'. I agree, that it's not OO style, but why isn't it implementable in XML? XML isn't OO, it's just a way of storing structured information, and the guys building the XML parsers to create the AOM objects again can probably deal with that. But since the AOM is OO I guess it wouldn't be a bad idea if the contents of the XML instances were in OO style. Mattias I have followed the XSD exactly in my serialization.. I believe the > intention is that the archetype XSD reflects the AOM model 1:1 > (as much as possible). I see the archetype XSD as a formal > definition of the cotnent of the AOM document. > > Andrew > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-technical > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20061117/e9597093/attachment.html> -------------- next part -------------- _______________________________________________ openEHR-technical mailing list openEHR-technical at openehr.org http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
