Micah Dubinko wrote:
> Erik Bruchez wrote: > >> We could support embedding XForms models in page views only in certain >> circumstances (static XHTML), or we could determine that if an XForms >> model is embedded in XHTML, it supercedes an XForms model declared in >> the Page Flow. The processing would be: >> >> Run view -> XForms engine detects embedded model -> XForms engine >> processes model / instance as per spec. >> >> Now this breaks the page model, which was expecting access to an >> XForms instance, with default values filled-in, etc. >> >> Thoughts? > > > I don't think a server-side engine should have to go out of its way > to support inline-models. So, how about the current out-of-line > XForms Model? Can that contain an <xs:schema> element with one or > several <simpleType> definitions that can be used in the form, for > example to limit entry to 20 characters?
The entire XForms instance can be validated with a schema. The BizDoc example illustrates this. When validation errors are limited to simple types, we intercept those and mark the relevant elements as invalid. This has limitations: it does not validate attributes, and we depend on the Schema validator reporting errors correctly.
As far as importing schemas and using those types directly in the XForms instance, this is not yet possible. It would be fairly easy to do, assuming the Schema validator allows access to access simple type definitions and validate them.
-Erik
------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ orbeon-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/orbeon-user
