Lists Home |
Date Index |
"Dare Obasanjo" <firstname.lastname@example.org> writes:
>> First, is there any mailing list dedicated to just W3C schema
>> questions? I may have a few in the near future and don't want
>> to clutter up xml-dev.
Subscribe by email to email@example.com
>> Let's say I declare element alpha to have a sequence of one
>> or more xs:any children with processContents="lax". Then I
>> declare element beta to have a specific content model. I can
>> put beta elements and anything else as children of alpha, and
>> if any of those beta elements violate the declared content
>> model, a schema-validating parser will flag it as an error.
>> However, if a beta element that violates the declared content
>> model is a *grandchild* of alpha instead of being a direct
>> child, the schema-validating parser isn't supposed to flag it.
>> Do I understand this correctly?
Um, beg to differ. Lax processing is recursive, so the non-beta
children of alpha will be laxly validated as well, unto the n-th
The relevant quote from the REC is:
"[A]n element information item's schema validity may be laxly
assessed if [it was accepted by a 'lax' wildcard and no top-level
declaration for it was found] by validating with respect to the
Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
Half-time member of W3C Team
2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
Fax: (44) 131 650-4587, e-mail: firstname.lastname@example.org
[mail really from me _always_ has this .sig -- mail without it is forged spam]