restriction design, inherit processContents="lax" for my namespace

[Bryan Rasmussen <bry@itnisk.com>]

-- 
Bryan Rasmussen

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="main:InvoiceCurrencyCode" minOccurs="0"/>
		<element ref="com:Note" minOccurs="0"/>
		<element ref="com:BuyersReferenceID" minOccurs="0" />
		<element ref="com:ReferencedOrder" />
		<element ref="com:BuyerParty"/>
		<element ref="com:SellerParty"/>
		<element ref="com:PaymentMeans" minOccurs="0"/>
		<element ref="com:PaymentTerms" minOccurs="0"/>
		<element ref="com:AllowanceCharge" minOccurs="0" maxOccurs="unbounded"/>
		<element ref="com:TaxTotal" minOccurs="0" maxOccurs="unbounded"/>
		<element ref="com:LegalTotals"/>
		<element ref="com:InvoiceLine" maxOccurs="unbounded"/>
		<element ref="com:ValidatedSignature" minOccurs="0"/>
				</sequence>
</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 processedLax? It doesn't seem reasonable to me that it would be, but
then how otherwise can one inherit a processing style? Any good xsd lists to
send this too anyway?