The example at http://www.w3.org/TR/xforms/index-all.html#concepts-model shows no mode/@schema fragment reference necessary, but there is no normative text I can locate that says that the processing model for xsd:schema is that it be applied. My intention in moving the schema attribute to model was to provide for automatic processing of all inline Schemas. Note that the model/@schema attribute is not a list of namespace-resource pairs as it is in xsd:schemaLocation, so each Schema (inline or external) must specify its tagret namespace. -----Original Message----- From: www-forms-request@w3.org [mailto:www-forms-request@w3.org] On Behalf Of Erik Bruchez Sent: Thursday, November 09, 2006 12:35 PM To: 'www-forms' Subject: [Fwd: Re: [ops-users] Support of embedded schemas] All, See the attached question about embedded schemas. How should the spec be interpreted? Is it enough to embed an xsd:schema under a model, or does the id need to be referenced in the model's @schema attribute? -Erik -- Orbeon Forms - XForms Everywhere http://www.orbeon.com/blog/Received on Friday, 10 November 2006 22:47:57 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:37:54 UTC