W3C home > Mailing lists > Public > xmlschema-dev@w3.org > August 2013

Re: Context Sensitive Element Definitions in W3C XSD Schema?

From: Michael Kay <mike@saxonica.com>
Date: Mon, 26 Aug 2013 08:45:23 +0100
Cc: xmlschema-dev@w3.org, sam moltek <byland@moltek.net>
Message-Id: <FE36AB3B-C70B-4CDA-81D6-5A599CF93028@saxonica.com>
To: batides@moltek.net
Yes, very non-intuitive.

XSD 1.1 allows a targetNamespace attribute on a local xs:element, but only under very restricted circumstances. I argued for removing all restrictions and allowing it anywhere, but others wanted to keep a stronger relationship between schema modules and namespaces, so I didn't win that one.

Michael Kay
Saxonica

On 26 Aug 2013, at 00:51, Steve Batides wrote:

> Michael,
> 
> It's non-intuitive (to me) that the namespace distinction can be achieved by wrapping the local declaration in a group declaration, but I guess it sort of makes sense after a bit of thought. I have only tested it with one editor, but I implemented one such group in the desired IF namespace but containing a "customized" local declaration of the IF element, and it works. I'll test a couple other validators later, but your suggestion was correct. Thanks VERY much; it's a bit of work to build the infrastructure XSLT to modify and maintain it, but I now have a solution that is going to do what we need. I should have found this forum years ago...
> 
> 
> 
> -- 
> Regards,
> 
> steve...
> 
> 
> --
> 
> Steve Batides
> MOLTEK Inc.
> mobile: 1-727-505-1473
> vmail:     1-877-650-8479  x1002
> batides@moltek.net
> www.moltek.com
> 
> 
> **THE CONTENT OF THIS EMAIL IS MOLTEK PROPRIETARY**
> 
> DISCLAIMER 
> 
> Encryption and Viruses: This e-mail and any attachments may not have not been encrypted and therefore they may be liable to be compromised. Viruses and compromises of security are inherent risks in relation to e-mail and consequently it is your responsibility to scan this e-mail and any attachments for viruses. We do not, to the extent permitted by law, accept any liability (whether in contract, negligence or otherwise) for any virus infection and/or external compromise of security and/or confidentiality in relation to transmissions sent by e-mail.
> 
> Confidentiality Notice: The information contained within this is confidential and is intended for the named recipients only. If you are not one of the intended recipients as indicated in the TO, CC and BCC fields, please return it to this firm by e-mail quoting the name of the sender and the addressee. Please then delete it from your system.


Received on Monday, 26 August 2013 07:45:48 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:16:05 UTC