[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: Namespaces, W3C XML Schema (was Re: ANN: SAX FiltersforNamespaceProc
> > <!-- schema definition --> > > <s:schema xmlns:s="http://www.w3.org/2001/XMLSchema" > > xmlns:tns="http://example.org/foo" > > targetNamespace="http://example.org/foo" > > elementFormDefault="qualified"> > > <s:element name="bar" type="s:string"/> > > <s:complexType name="fooType"> > > <s:sequence> > > <s:element name="bar" type="s:string"/> > > </s:sequence> > > </s:complexType> > > <s:element name="foo" type="tns:fooType"/> > > </s:schema> > > > > <!-- instance --> > > <f:foo xmlns:f="http://example.org/foo"> > > <f:bar/> <--| > > </f:foo> | > > | > > | > > Even when everything is qualified, you still can't figure out which bar > > element this is just by looking at the QName and ignoring context (is it > > the global or local qualified bar element?). > > This doesn't feel like the same problem to me - it feels like a bad case > of non-deterministic content modeling. I thought XML Schema went to > great lengths to avoid that, but maybe this is legal. That is not a valid schema. Dave
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|