Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: UPA example

From: "Pete Cordell" <petexmldev@---------.--->
To: "C. M. Sperberg-McQueen" <cmsmcq@---.--->
Date: 7/1/2008 11:07:00 PM
- Original Message From: "C. M. Sperberg-McQueen"

> On 25 Jun 2008, at 04:49 , Pete Cordell wrote:
> > ...
> > So I take it that under the XSD 1.1 rules, the instance would be  valid 
> > and have particle assigment corresponding to:
> >
> > <apple/> validated by element
> > <apple/> validated by any
> > <apple/> validated by any
> >
> > Rather than:
> >
> > <apple/> validated by element
> > <apple/> validated by any
> > <apple/> validated by element
>
> No, I don't think so.

I have to confess that while I noticed that the first pass through the 
sequence would require a match to the xs:any, I didn't carry on the 
reasoning and consider that on the second pass a match was also required and 
hence the instance was a little short.  Similarly I didn't realise how the 
RE backtracking that Boris mentioned was relevant and concluded he was using 
the term loosely.  I can now see how it related.  (I could argue that I only 
considered the above instances to be fragments of a larger instances, but 
can't :-)

I think the important thing for me is that, having fixed the length of the 
instance, the following is the association:

<apple/> validated by element
<apple/> validated by any
<apple/> validated by element
<apple/> validated by any

and not:

<apple/> validated by element
<apple/> validated by any
<apple/> validated by any
<apple/> validated by any

Thanks,

Pete Cordell
Codalogic
For XML C++ data binding visit http://www.codalogic.com/lmx/



From cmsmcq@a... Tue Jul 01 21:50:35 2008
Received: from [128.30.52.63] (helo=bart.w3.org)
	b


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent