- From: Lehmann, Steen <slehmann@silverstream.com>
- Date: Thu, 21 Feb 2002 09:24:07 +0100
- To: "'www-forms-editor@w3.org'" <www-forms-editor@w3.org>
Following up on my own mail since this seems to be a problem with most <any> elements in the Last Call Working Draft XForms schema - they require at least one element to be present. According to the documentation for the elements <schema>, <instance>, <caption>, <hint>, <help>, <alert> and <value> they can all have empty content if a reference attribute is specified. The schema should reflect this by using the minOccurs attribute or many legal XForms documents will not validate correctly. Verified this in Xerces and our internal validator, maybe XML Spy (which apparently was used to author the XForms schema) has a bug regarding <any> handling? -- Steen >It occurs to me that the <schema> and <instance> elements in the XForms >schema should have minOccurs=0 on their definitions, since they are allowed >to have empty content (if an href= attribute is specified, as in the >examples). The default for minOccurs is 1 unless specified, so this would >require at least some content to be present, since processContents is strict >(also the default). /** * Steen Lehmann - <mailto:slehmann@silverstream.com> * Senior Software Engineer (R&D), SilverStream Software * <http://www.silverstream.com> */
Received on Thursday, 21 February 2002 03:29:27 UTC