- From: Erik Bruchez <ebruchez@orbeon.com>
- Date: Mon, 20 Sep 2010 11:30:48 -0700
- To: public-forms@w3.org
It seems to be an unnecessary constraint for the form author to mandate that UI Common elements be all grouped together. So my vote goes for the more lax solution, whatever the impact on the XForms schema might be. -Erik On Mon, Sep 20, 2010 at 10:35 AM, Leigh L Klotz Jr <leigh.klotz@xerox.com> wrote: > John and I implemented the select and select1 content model erratum > differently. > > At the time, we polled implementors and asked if any cared about whether the > help/hint/alert/action had any ordering constraints against item and > itemset, and the answer was no. > > Unfortunately, we're in a state at the moment with the proposed erratum in > the wiki [errata] and the RNG schema are at odds. > > So the question is: Must UI Common content all be together, or can be be > split with some before the List and some after? > > Since we asked implementors before what they accepted, I'd like to ask again > if anyone cares so we can fine-tune the erratum and the schema. > > Details: > Here's what the XForms 1.1 RNC says: > > xforms.select1.content = > xforms.label, ((xforms.UI.Common.content, xforms.List.UI.Common.content) | > (xforms.List.UI.Common.content, xforms.UI.Common.content)) > > The proposed erratum says this: > label, (UI Common)*, (List UI Common)+, (UI Common)* > > To be consistent with the proposed erratum, we'd change the RNC to this: > > xforms.select1.content = > xforms.label, xforms.UI.Common.content, xforms.List.UI.Common.content, > xforms.UI.Common.content > > Or, we would change the proposed erratum to this: > label, ((UI Common)*, (List UI Common)+) | ((List UI Common)+, (UI > Common)*) > > > [errata] > http://www.w3.org/MarkUp/Forms/wiki/XForms_1.1_First_Edition_Errata > > Leigh. > >
Received on Monday, 20 September 2010 18:31:40 UTC