- From: Andrew Leslie <info@structuredinformation.co.uk>
- Date: Wed, 2 Mar 2011 11:40:48 -0000
- To: <XMLSchema@xml4pharma.com>
- Cc: <xmlschema-dev@w3.org>
- Message-ID: <002301cbd8ce$b1ee5400$15cafc00$@structuredinformation.co.uk>
Hi Jozef, Following on from the redefine details you kindly provided me, this still doesn't quite provide me with an answer. I need to modify certain content models within the main proced.xsd schema. Rather than modifying this schema directly, or for that matter (similar to xlink) including the extended xsd within the proced.xsd, is there a way of referencing the proced.xsd and the extended xsd from the header of the XML instance so that it parses against both of them ? I want to avoid redefining a whole plethora of sub elements and attributes already defined in the main proced.xsd as this adds in all the namespace attributes into the element when inserted during authoring. Regards, Andy Andrew Leslie Director Structured Information Limited Beer, East Devon, UK, EX12 3LU t: +44 (0)1297 625572 m: +44 (0)7811 188615 e: <mailto:info@structuredinformation.co.uk> info@structuredinformation.co.uk w: <http://www.structuredinformation.co.uk> www.structuredinformation.co.uk Registered in England and Wales No. 5687809. Registered Address: South Riding, Underleys, Beer, East Devon, EX12 3LU CONFIDENTIALITY NOTICE: This e-mail and any attachments are strictly confidential and may be protected by legal privilege. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of this e-mail or any attachment is STRICTLY PROHIBITED. If you have received this e-mail in error, please notify us immediately by returning it to the sender and deleting this copy from your system. Thank you for your co-operation.
Received on Wednesday, 2 March 2011 11:57:13 UTC