W3C home > Mailing lists > Public > public-forms@w3.org > January 2010

Minimal content model for xf:group and text

From: Klotz, Leigh <Leigh.Klotz@xerox.com>
Date: Mon, 11 Jan 2010 09:56:33 -0800
Message-ID: <E254B0A7E0268949ABFE5EA97B7D0CF4099822ED@USA7061MS01.na.xerox.net>
To: "Forms WG" <public-forms@w3.org>
Cc: "Owen Newnan" <onewnan@gmail.com>
Owen Newnan reports that test 4.6.3.a uses text as direct child of xf:group, yet the minimal content model of xf:group does not allow text.
The XForms 1.1 XSD schema comments that the host language should add to the content model of group, case, and repeat, but doesn't include text per se.
The test case 4.6.3.a though clearly requires it.
The RNC schema allows UI Inline content under group, repeat, and case, but I can't find a justification for that in the XForms 1.1 Recommendation.
Here's what I did find in the recommendation:
- Element xf:label is described as having "inline text" and it's in the XSD and RNC schemas a UI Inline, but there's no explicit mention of "UI Inline" in the prose.
- Non-toplevel elements generally don't have a table specifying Minimal Content Model, so that may be why the prose for xf:label has some statements about text.
- Element xf:message does have a Minimal Content Model and does allow text: PCDATA|UI Inline.
We might want to consider adding to the errata list that the minimal content model for group, repeat, and the prose for case to include PCDATA|UI Inline.
Or do we consider presentation of text (other than label and message) to be wholly a host language issue?


From: Owen Newnan [mailto:onewnan@gmail.com] 
Sent: Sunday, January 10, 2010 7:26 AM
To: Klotz, Leigh
Subject: whether text content should be allowed in controls


As regards message
Chapt04/4.6/4.6.3/4.6.3.a.xhtml:49:24: cvc-complex-type.2.3: Element 'xforms:group' cannot have character [children], because the type's content type is element-only.

with content
When a value is selected you must see the output "xforms-select". The value in
indicates which form control the event came from,the select or select1 control.
The output may be followed by the output for the Value Change sequence ("xforms-recalculate",
"xforms-revalidate", "xforms-refresh", and "xforms-value-changed").

Looking over the spec it's not obvious wto me hether text content should be allowed in controls (it obviously is in instances). Please advise.

Owen Newnan

cell 720 260-5753
home 303 697 1925
Received on Monday, 11 January 2010 17:57:09 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:48:39 UTC