W3C home > Mailing lists > Public > xmlschema-dev@w3.org > December 2010

Re: The particle of the type is not a valid restriction of the particle of the base.

From: Michael Kay <mike@saxonica.com>
Date: Wed, 15 Dec 2010 23:36:15 +0000
Message-ID: <4D0950EF.6030904@saxonica.com>
To: Shai Gotlib <Shai.Gotlib@amdocs.com>
CC: "xmlschema-dev@w3.org" <xmlschema-dev@w3.org>
The elements such as <xsl:element name="billTo"> are in a different 
namespace from those in the base type. The only way to solve this in XSD 
1.0 is for the restricted type to be defined in the same namespace as 
the base type - which might mean trampling on a namespace you don't own. 
XSD 1.1 allows local element declarations in this situation to have a 
targetNamespace attribute differing from that of the containing xs:schema.

Michael Kay
Saxonica

On 15/12/2010 16:37, Shai Gotlib wrote:
>
> Hi,
>
> I Would like to understand what do I do wrong (or the <oXygen> wrong) 
> – please help.
>
> I tried to define a restricted complexType.
>
> If I do it in the same file were the base file was defined - it is ok.
>
> Whenever I move the restriction definition to other xsd file (and 
> import the source file) I fail with:
>
> “Error for type 'RestrictedPurchaseOrderTypeAA'.  The particle of the 
> type is not a valid restriction of the particle of the base.”
>
> Enclosed:
>
> ·transactionSchemaFull.xsd that includes 
> 'RestrictedPurchaseOrderTypeA' – pass validation.
>
> ·BCMObjects.xsd that includes 'RestrictedPurchaseOrderTypeAA' – 
> validation fail
>
> Notice – 'RestrictedPurchaseOrderTypeAA' is identical to 
> 'RestrictedPurchaseOrderTypeA'
>
> Thanks in advance,
>
> Shai
>
> This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
> you may review at http://www.amdocs.com/email_disclaimer.asp
>
Received on Wednesday, 15 December 2010 23:36:43 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:56:18 UTC