XML Schema do not represent the RM very well. Review necessary

Description

In structure.xsd is following element defined:
<xs:element name="items" type="LOCATABLE"/>
In composition.xsd is the following element defined
<xs:element name="composition" type="COMPOSITION"/>

So, there are only two globally defined elements in the complete schema-structure.

Because Structure.xsd is included in Content.xsd, which is again, included in Composition.xsd, Structure.xsd is in fact the grandparent of all Locatable-derived XMLSchema types.
------------------------------------- The structured XSD's validate OK, that is not the problem. The problem is that they are too restricted to represent the RM.

Only globally-defined elements can be the root element of an XML Schema-based XML-instance.
------------------------------------- So, suppose, I want to create a valid XML instance on base of Content.xsd, only the begin-element "items" is allowed.

So, suppose, I want to create a valid XML instance on base of Structure.xsd, only the begin-element "items" is allowed.

So, suppose, I want to create a valid XML instance on base of Composition.xsd, only the begin-element "items" and the beginelement "composition" is allowed.

I had this discussion in November 2012, Peter Gummer advised me to create a JIRA-entry for this issue.

http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/2012-November/007418.html

Environment

None

Reporter

Bert Verhees

Labels

Components

Affects versions

Priority

Major
Configure