W3C home > Mailing lists > Public > xmlschema-dev@w3.org > October 2003

RE: Problem with .NET - Invalid particle derivation by restriction

From: Priscilla Walmsley <priscilla@walmsley.com>
Date: Fri, 10 Oct 2003 10:34:58 -0400
To: "'Hugh Wallis'" <hugh_wallis@hyperion.com>, <xmlschema-dev@w3.org>
Cc: "'Dare Obasanjo'" <dareo@microsoft.com>, "'Rob Blake'" <robblake@microsoft.com>
Message-ID: <000701c38f3b$aefd8ac0$ef2efea9@WALMSLEYPH>

Hi Hugh,

I believe the spec prevents you from restricting one wildcard with two
element declarations.  Try adding an extra sequence in your type
definition, i.e.

        <restriction base="xbrli:tupleType">
              <element ref="ci:Name" minOccurs="1" maxOccurs="1" />
              <element ref="ci:Salary" minOccurs="0" maxOccurs="1" />

This will mean that you have a one to one match between your particles
(the one "sequence" particle restricts the one wildcard particle).

This has been reported as a bug [1], but has not yet been resolved.

Hope that helps,

Priscilla Walmsley             priscilla@walmsley.com
Author, Definitive XML Schema     (Prentice Hall PTR)


-----Original Message-----
From: xmlschema-dev-request@w3.org [mailto:xmlschema-dev-request@w3.org]
On Behalf Of Hugh Wallis
Sent: Friday, October 10, 2003 9:33 AM
To: xmlschema-dev@w3.org
Cc: Dare Obasanjo; Rob Blake
Subject: Problem with .NET - Invalid particle derivation by restriction 

In the attached set of files .NET objects with "Invalid particle
derivation by restriction" at line 22 in ComplexConcept.xsd

No other validator I have tried gives the same (or any) error and I
can't for the life of me figure out what might be the problem (nor can a
whole host of other very smart XML knowledgeable folks around the world
that have looked at this)

Could someone please confirm what is wrong or what is right please

Many thanks

Hugh Wallis


If you have received this e-mail in error, please delete it and notify
the sender as soon as possible. The contents of this e-mail may be
confidential and the unauthorized use, copying, or dissemination of it
and any attachments to it, is prohibited. 

Internet communications are not secure and Hyperion does not, therefore,
accept legal responsibility for the contents of this message nor for any
damage caused by viruses. The views expressed here do not necessarily
represent those of Hyperion.

For more information about Hyperion, please visit our Web site at
Received on Friday, 10 October 2003 10:40:59 UTC

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