All right then, so now I know how I should proceed. Thank you very much for your help. It was a lot faster to understand the schema by your input rather than starting to read some XSD documentation.
Regards, Mattias 2006/11/17, Andrew Patterson <andrewpatto at gmail.com>: > > > 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20061117/c88465e0/attachment.html> -------------- next part -------------- _______________________________________________ openEHR-technical mailing list openEHR-technical at openehr.org http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
