Re: [xml-dev] restriction design, inherit processContents="lax" for my namespace

Bryan Rasmussen <> writes:


> If I do the following restriction
> 	
> <complexType name="InvoiceType">
> <complexContent>
> <restriction base="pie:laxInvoiceType">
> <sequence>
>  <element ref="com:ID"/>
>  <element ref="com:IssueDate"/>
>  <element ref="pie:TypeCode" maxOccurs="1"/>
>  <element ref="com:SellerParty"/>
>  . . .
> </restriction>
> </complexContent>
> </complexType>
>
> <complexType name="laxInvoiceType">
> <sequence>
>  <any namespace="http://thecomnamespace" processContents="lax" 
> 	   minOccurs="0" maxOccurs="unbounded" />
>  <element ref="pie:TypeCode" maxOccurs="1"/>
>  <element ref="main:InvoiceCurrencyCode" minOccurs="0"/>
>  <any namespace="http://thecomnamespace" processContents="lax" 
> 	   minOccurs="0" maxOccurs="unbounded" />
> </sequence>
> </complexType>
>
> will that mean that all the elements in the com namespace under my
> pie:Invoice will be processed Lax?

No.  There's no such thing as lax processing of items being validated
by a declared element, unless/until an error occurs or an explicit
wildcard is involved.

> Any good xsd lists to send this too anyway?

 (subscribe via ,
archives at http://lists.w3.org/Archives/Public/xmlschema-dev/)

ht
-- 
 Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
                     Half-time member of W3C Team
    2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
            Fax: (44) 131 650-4587, e-mail: 
                   URL: http://www.ltg.ed.ac.uk/~ht/
[mail really from me _always_ has this .sig -- mail without it is forged spam]