[
Lists Home |
Date Index |
Thread Index
]
Title: RE: [xml-dev] Best Practice - beyond schema
Unfortunately, this mechanism below would not seem to remove mainteneance of multiple schemas. If you use restriction, any change to the global type will (potentially) require all the redefines also to be modified (or at least, checked for consistency).
One of the ugly parts of type restriction.
John
<snip>
global.xsd
<complexType name="electionReport">
<sequence>
. . .
<element ref="auditReport" minOccurs="0"/>
. . .
</sequence>
</complexType>
UK.xsd
<redefine schemaLocation="global.xsd">
. . .
<complexType name="electionReport">
<complexContent>
<restriction base="electionReport">
<sequence>
. . .
<element ref="auditReport"/>
. . .
</sequence>
</restriction>
</complexContent>
</complexType>
. . .
</redefine>
US.xsd
<redefine schemaLocation="global.xsd">
. . .
<complexType name="electionReport">
<complexContent>
<restriction base="electionReport">
<sequence>
. . .
<element ref="auditReport" maxOccurs="0"/>
. . .
</sequence>
</restriction>
</complexContent>
</complexType>
. . .
</redefine>
</snip>
The information transmitted by this e-mail message is intended solely for the use of the person to whom or entity to which it is addressed. The message may contain information that is privileged and confidential. Disclosure, dissemination, distribution, review, retransmission to, other use of or taking any action in reliance upon this information by anyone other than the intended recipient is prohibited. If you are not the intended recipient, please do not disseminate, distribute or copy this communication, by e-mail or otherwise. Instead, please notify us immediately by return e-mail (including the original message with your reply) and then delete and discard all copies of the message.
Although we have taken precautions to minimize the risk of transmitting viruses we nevertheless advise you to carry out your own virus checks on any attachment to this message. We accept no liability for any loss or damage caused by viruses.
| 