W3C home > Mailing lists > Public > www-forms@w3.org > November 2006

RE: [Fwd: Re: [ops-users] Support of embedded schemas]

From: Klotz, Leigh <Leigh.Klotz@xerox.com>
Date: Fri, 10 Nov 2006 14:47:13 -0800
Message-ID: <E254B0A7E0268949ABFE5EA97B7D0CF40271844C@usa7061ms01.na.xerox.net>
To: "Erik Bruchez" <ebruchez@orbeon.com>, "www-forms" <www-forms@w3.org>

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 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 10 March 2012 06:22:08 GMT