> go back to your example, why didn't you use xsi:type in some places, for > example: > > <description> > <original_author> > <item> ... > > Is you used it here it would be: > > <description xsi:type="RESOURCE_DESCRIPTION"> > <original_author xsi:type="hashTableStringString"> > <item xsi:type="dictionaryItem"> ...
because there are no doubts about the actual type of 'description' (i.e. it has no subclasses), when the serialiazer gets to the 'description' node. it knows what to expect. If we had a RESOURCE_DESCRIPTION_EXTENDED complexType that was based on RESOURCE_DESCRIPTION, then we would need to use xsi:type. Andrew _______________________________________________ openEHR-technical mailing list openEHR-technical at openehr.org http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
