On Fri, 23 Jul 2004, Sandy Gao wrote: > If you want an error, why did you put "lax" there?
*I* didn't - that's the problem :) > <choice> > <any namespace="##targetNamespace" processContents="strict"/> > <any namespace="##local" processContents="lax/skip"/> > <any namespace="##other" processContents="lax/skip"/> > </choice> Thanks - that's a neat idea which I shall keep in mind. Unfortunately in this case I can't (directly) change the schema in question. In reality a schema that forms the basis of a standard with an extensible content model has to use "lax" to be workable; but inevitably some users of the schema will have a requirement to ensure that a particular extension that they employ is correct according to their own schema, which is made a lot harder if the top level element can have a typo and still "validate"! This seems to me to be one of the primary use cases for lax validation, thus my original query about the warning; but I realise I'm out on a limb as far as the spec. is concerned here :( Lucian -- Lucian Holland, Technical Architect +44-1865-203192 DecisionSoft Limited http://www.decisionsoft.com XML Development and Services --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
