W3C home > Mailing lists > Public > www-forms@w3.org > August 2001

RE: Levels of XForms (was: RE: Form function and presentation - S chema usage)

From: Sebastian Schnitzenbaumer <schnitz@mozquito.com>
Date: Thu, 23 Aug 2001 15:44:49 +0200
Message-ID: <D0F1529EE943B3449F755CA1A40887461116BB@winserver.windomain.mozquito.com>
To: "Roarty, Denis" <droarty@csc.cps.k12.il.us>, <www-forms@w3.org>
Denis,

<snip/>

> The idea of multiple levels of xforms compliance seems to 
> suit the needs of
> the wide variety of clients and developers that are likely to 
> benefit from
> this standard.  In fact, it nicely answers many of the issues 
> raised in the
> working draft regarding whether to support or not support 
> certain features
> that would be "too expensive" for small devices.
> 
> A more difficult question will be what constitutes the details of each
> level?  So far, I like the outline you propose.  

<snip/>

I'm sharing with you and the others on this list the
internal working group's "laundry list of open questions", 
what constitutes the details of each level. Below are
the questions, the working group is currently working on
the answers. Until now, we are discussing the Basic and
Full level. The XForms Core level is new (came out of this
discussion based on Joern's feedback) and the working group 
still has to discuss and agree on it before we can consider 
it.

But any proposals from you or the others for answering those
questions might help the working group to find the right
decision on these very sensitive, critical issues.

- Sebastian

---

The following sections don't clearly identify whether they are part of
XForms Basic or Full:

Chapter 2 "Concepts"
  - Overall. Are the examples here Basic or Full?

Chapter 5 "The XForms Model"
  - For each model item property: Full or basic?
    (type, readOnly, required, relevant, calculate, isValid, minOccurs,
maxOccurs)

  - For each binding constraint need to state Basic or full

  - Allowed inline Schema for Basic vs. Full

Chapter 6 "XPath Expressions in XForms"
  - All methods defined here need to state ...

Chapter 7 "Form Controls"
  - All form controls need to state ...

  - All common markup needs to state ...

Chapter 8 "XForms Actions"
  - All XForms Actions need to state ...

Chapter 9 "XForms User Interface"
  - All aggregate form controls (group, repeat, switch, component) need
to
state ...

Chapter 11 "Processing Model and Conformance"
  - Serialization methods ("xml", "urlencoded", "form-data") need to
state
...

---

> Sebastian wrote:
> Would the following solve your problem:
> 
> We define a new level of XForms conformance next
> to the two existing ones:
> 
> XForms Core: The basic XForms concept of 
>   Model-View-Controller, the binding mechanism
>   and the core XForms module(s) (<xform>, <model> &
>   <instance>). You may yourself choose and use any 
>   pre-existing or custom model language and any
>   UI language as well as of course any arbitrary
>   XML instance for data.
> 
> XForms Basic: XForms Core + Concrete Model as 
>   W3C XML Schema Subset (Part 2 Datatypes) 
>   + XForms UI.
> 
> XForms Full: XForms Core + Concrete Model as 
>   Full W3C XML Schema + XForms UI.
> 
> 
> Food for thought. Others on this list: Opinions?
> 
> Thanks,
> 
> - Sebastian
> 
> 
Received on Thursday, 23 August 2001 09:45:20 GMT

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