Lists Home |
Date Index |
Title: RE: [xml-dev] Best Practice - beyond schema
Interesting idea. This, of course, assumes that I will always know exactly which parts are going to change and which aren't when I start building Version 1 Alpha of my base schemas.
If I knew that, I could just build the final and perfect version of all the schemas straight away and there would be no maintenance problem.
> Yes, but good style therefore suggests using a named model group for
> the unchanged parts, in which the schema processor will do
> the copying
> for you.
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.