Adam & Lisa, There is a very specific rationale and it is consistent. The XML Schema is a direct serialisation of the UML openEHR reference models. Every class is an XML schema type and every attribute is an element except for archetype_node_id as it is a metadata attribute. So in the case of CODE_PHRASE, it has an attribute of terminology_id (hence the element template_id) of type TERMINOLOGY_ID. TERMINOLOGY_ID has an attribute of value of type string (hence the element value). Paths are absolutely critical in openEHR and they are based on XPath. If we start arbitrarily changing the schema based on what someone thinks is good XML we will break the openEHR path to XPath correspondence making any mapping rules more complex and error prone. This is why the terminology ID value is not represented as a value attribute or element text node. Yes it might seem inefficient but it was deemed to be important to make sure the logical model to implementation mapping was consistent and ensure paths worked. In comparison to HL7 v3, the data:noise ratio is still considerably less.
Regards Heath > -----Original Message----- > From: openehr-technical-bounces at openehr.org [mailto:openehr-technical- > bounces at openehr.org] On Behalf Of Lisa Thurston > Sent: Tuesday, 11 December 2007 10:23 AM > To: For openEHR technical discussions > Subject: Re: Suggestion wrt XML Archetypes & Templates > > Adam Flinton wrote: > > I would like though to enquire wrt the rationale of containing _id info > > in a separate <value/> element. > > > > If you are being consistent > > instead of : > > > > <terminology_id> > > <value>ISO_639-1</value> > > </terminology_id> > > > > it should be simply: > > > > <terminology_id>ISO_639-1</terminology_id> > > > > > > or <terminology_id value="ISO_639-1"/> > > > > Adam > > > There is no special rationale. It is simply the default serialisation of > the type TERMINOLOGY_ID. > > Lisa > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
