• From: Aaron Skonnard <aarons@d...>
• To: "'David E. Cleary'" <davec@p...>, 'Xml-Dev' <xml-dev@l...>
• Date: Thu, 02 Aug 2001 09:07:16 -0700

> > > <!-- 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>
> > >

<snip/>

> > 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

Yes it is.

-aaron

• References:
  • RE: Namespaces, W3C XML Schema (was Re: ANN: SAX FiltersforNamespaceProcessing)
    • From: "David E. Cleary" <davec@p...>

• Prev by Date: RE: Standards (yet again) was RE: Use of XML ?
• Next by Date: RE: SAX Filters for Namespace Processing
• Previous by thread: RE: Namespaces, W3C XML Schema (was Re: ANN: SAX FiltersforNamespaceProcessing)
• Next by thread: RE: Namespaces, W3C XML Schema (was Re: ANN: SAX Filters forNamespaceProcessing)
• Index(es):
  • Date
  • Thread