Hi Tom, Yes you are right, my concern is about the absence of elements with classes names in the data. Of course, in the schema you can find the class name in the construct:
<xs:complextype name="class_name".....> but not elements <xs:element name="class_name" type="..."> Thus, it does not permit to have path class\attribute\class... in XML data. For instance, <xs:complexType name="COMPOSITION"> <xs:complexContent> <xs:extension base="st <http://oceaninformatics.biz/schema/documentation/Composition.xsd.html#ns_st>:LOCATABLE <http://oceaninformatics.biz/schema/documentation/Structure.xsd.html_h911858792.html>"> <xs:sequence> <xs:element name="category" type="bt <http://oceaninformatics.biz/schema/documentation/Composition.xsd.html#ns_bt>:DV_CODED_TEXT <http://oceaninformatics.biz/schema/documentation/BaseTypes.xsd.html_h1544425981.html>"/> ...... </xs:sequence> <xs:attribute name="rm_version" type="xs <http://oceaninformatics.biz/schema/documentation/Composition.xsd.html#ns_xs>:string" use="required"/> </xs:extension> </xs:complexContent> </xs:complexType> let's focus on attribute category of type DV_CODED_TEXT: <xs:complexType name="DV_CODED_TEXT"> <xs:complexContent> <xs:extension base="DV_TEXT <http://oceaninformatics.biz/schema/documentation/BaseTypes.xsd.html_h1838339253.html>"> <xs:sequence> <xs:element name="defining_code" type="CODE_PHRASE <http://oceaninformatics.biz/schema/documentation/BaseTypes.xsd.html_h1592245190.html>"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> and type "code_phrase" is: <xs:complexType name="CODE_PHRASE"> <xs:sequence> <xs:element name="code_string" type="xs <http://oceaninformatics.biz/schema/documentation/BaseTypes.xsd.html#ns_xs>:string" maxOccurs="1" minOccurs="1"/> <xs:element name="terminology_id" type="TERMINOLOGY_ID <http://oceaninformatics.biz/schema/documentation/BaseTypes.xsd.html_h-2068009492.html>" maxOccurs="1" minOccurs="1"/> </xs:sequence> </xs:complexType> so in the xml documents the element "category" would be: <category> ........ (attributes defined in DV_TEXT) <defining_code> <code_string> here_a_code </code_string> <terminology_id> .....</terminology_id> </defining_code> </category> so all the path in data are chains of attribute names. Probably, I have misunderstood the aim of the XML-Schema, I suppose that it defines XML documents compliant with the RM. regards Thomas Beale escribi: > > Hi Alberto, > > Jose Alberto Maldonado wrote: > >> Hi, >> >> Just a doubt. >> >> Why the classes names are not included in the XML-Schema?. For >> instance, it would convenient for multi-valued attributes in order to >> distinguish one data instance from another (imagine the potential >> mess if the attribute is not ordered). It will also make it "more >> compatible" with paths of the form class\attribute\class\attribute of >> archetypes. Beside, much typing information is lost, this makes the >> XML document less self-descriptive. > > > to be more precise, I suspect you are asking why the class names are > not in the data - they are in the schema. I think it would be better. > But can you provide specific comments to show why the paths won't > match the archetype paths (which is what we want - so if it doesn't > work, we will change the schema). > > - thomas > - > If you have any questions about using this list, > please send a message to d.lloyd at openehr.org > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20051021/9f4e8087/attachment.html>
