Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: XSD 1.1 Proposal: Naming wildcard extension sites

From: "Michael Kay" <mike@--------.--->
To: "'Bryan Rasmussen'" <BRS@----.-->, "'Pete Cordell'" <petexmldev@--------------.--->, <xmlschema-dev@--.--->
Date: 3/12/2007 11:42:00 AM
> Basically what 
> I need is the ability to say I want any namespace with a 
> particular structure to it, and I suppose it would be best 
> served by using the regular expressions ability of XSD.
> 
> We would find it a boon and a blessing to say that any 
> namespace is allowed inside of an extension element as long 
> as it starts with rep.oio.dk. 

In XML Schema 1.1* (and in the next Saxon release) you will be able to say

<xs:assert test="starts-with(namespace-uri(*[last()]), 'rep.oio.dk'))"/>

* (actually the current W3C draft defines a rather restrictive XPath subset
for assertions. But it allows processors to implement the whole of XPath
2.0, and that's what Saxon will do.)

I think xs:assert is going to prove an immensely popular feature, assuming
that vendors don't cripple it to the extent suggested in the current draft.
For this particular use case it's a bit awkward that you can only put
xs:assert on a complex type - not on the element wildcard itself - but it's
not too hard to work around that.

Michael Kay
http://www.saxonica.com/


From swvemuri@c... Tue Mar 13 08:25:41 2007
Received: from 


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent