On Fri, 2002-06-28 at 12:04, Anderson, John wrote:
> Eric,
> 
> Isn't this what maxOccurs is intended for? 
Yes, except that it will raise an error, not a warning.
> If the schema allows un unlimited
> amount of bars, and your implementation doesn't, then your implementation
> isn't conformant to the schema. 
That's one way to see it. You can also consider that it's a partial
implementation and that you want to get a warning when the mismatch
happens.
> 
> How is this different to a schema which specifies:
> <!ELEMENT foo (bar*,somethingElse)> 
> when your implementation doesn't store somethingElse at all?
In this 2nd case, any valid document will cause a problem and should
raise a warning. In my example, it's really a 3 states thing (valid,
valid but causing problem and invalid). 
> Or am I missing something here?
If your application and format are tighly coupled, you don't need to
differentiate between warning and error. The distinction make only sense
if you decouple them.
Eric
> John
> 
-- 
See you in San Diego.
                               http://conferences.oreillynet.com/os2002/
------------------------------------------------------------------------
Eric van der Vlist       http://xmlfr.org            http://dyomedea.com
(W3C) XML Schema ISBN:0-596-00252-1 http://oreilly.com/catalog/xmlschema
------------------------------------------------------------------------
Received on Fri Jun 28 13:20:01 2002
This archive was generated by hypermail 2.1.8 : Fri Dec 03 2004 - 14:29:47 UTC