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

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

From: Hugh Wallis <hugh_wallis@hyperion.com>
Date: Fri, 10 Oct 2003 12:37:41 -0400
Message-ID: <073a01c38f4c$d32c2d00$c1941bac@hwallis2>
To: "Priscilla Walmsley" <priscilla@walmsley.com>, <xmlschema-dev@w3.org>
Cc: "Rob Blake" <robblake@microsoft.com>

Thanks Dare

We just got a similar comment here as follows:

>>

Having an extra sequence in between should not make any difference
in parser's behaviour of particle checking since redundant levels of
sequences are supposed to be collapsed by the requirement described
at: http://www.w3.org/TR/xmlschema-1/#cos-particle-restrict

Indeed, the sequence that contains <any/> in tupleType definition is
reduced before particle checking, that makes the comparison to be
between <any/> (base) and <sequence/> (derived), which appears to
result in success since that <any/> particle has a big capacity of
occurrence range (0 to unbounded).

<<

Do you have any suggestions as to how to fix the original issue?

Cheers

Hugh
----- Original Message ----- 
To: "Hugh Wallis" <hugh_wallis@hyperion.com>; "Priscilla Walmsley"
<priscilla@walmsley.com>; <xmlschema-dev@w3.org>
Cc: "Rob Blake" <robblake@microsoft.com>
Sent: Friday, 10 October, 2003 12:16 PM
Subject: RE: Problem with .NET - Invalid particle derivation by restriction



A sequence with minOccurs/maxOccurs of 1/1 nested in another sequence is
pointless so it is removed thus there is no difference between the example
Priscilla showed you and the original version in your schema.

________________________________

From: Hugh Wallis [mailto:hugh_wallis@hyperion.com]
Sent: Fri 10/10/2003 7:49 AM
To: Priscilla Walmsley; xmlschema-dev@w3.org
Cc: Dare Obasanjo; Rob Blake
Subject: Re: Problem with .NET - Invalid particle derivation by restriction



Thanks Priscilla

Unfortunately .NET continues to give the same error message with this change

Any other ideas?

Hugh
----- Original Message -----
From: "Priscilla Walmsley" <priscilla@walmsley.com>
To: "'Hugh Wallis'" <hugh_wallis@hyperion.com>; <xmlschema-dev@w3.org>
Cc: "'Dare Obasanjo'" <dareo@microsoft.com>; "'Rob Blake'"
<robblake@microsoft.com>
Sent: Friday, 10 October, 2003 10:34 AM
Subject: RE: Problem with .NET - Invalid particle derivation by restriction


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">
          <sequence>
            <sequence>
              <element ref="ci:Name" minOccurs="1" maxOccurs="1" />
              <element ref="ci:Salary" minOccurs="0" maxOccurs="1" />
            </sequence>
          </sequence>
        </restriction>

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

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

[1]
http://www.w3.org/2001/05/xmlschema-rec-comments#pfiWildcardRestriction


-----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
www.hyperion.com




************************************************************************

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
www.hyperion.com





************************************************************************

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 www.hyperion.com
Received on Friday, 10 October 2003 12:38:12 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 January 2011 00:14:40 GMT