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

RE: Minimal content model for xf:group and text

From: John Boyer <boyerj@ca.ibm.com>
Date: Tue, 12 Jan 2010 09:34:14 -0800
To: "Klotz, Leigh" <Leigh.Klotz@xerox.com>
Cc: "Owen Newnan" <onewnan@gmail.com>, "Forms WG" <public-forms@w3.org>
Message-ID: <OF014AE4CC.3C8731B2-ON882576A9.005F73B2-882576A9.00608549@ca.ibm.com>
Hi Leigh,

I double-checked this just now, and the XML schema for XForms 1.1 does 
apply the mixed="true" attribute to the declarations of label, help, hint, 
alert and message.  This means that the output elements provided by the 
UI.content group can be combined with PCDATA, as per the minimal content 
model in Section 8.1 of XForms 1.1. 
So, I think the schema is OK.  Were you looking only at UI.Content, or are 
you seeing an actual validation error?
I think the fact that the mixed-ness is not expressed directly on the 
UI.Content definition may have thrown you off the track here, and I agree 
it would be better if it were there, rather than on the actual label, 
help, hint, alert and message elements.  I don't know why it was not done 
that way.  A limitation in XML schema expressiveness? If so, then adding a 
comment to UI.Content to indicate what we really want to say would be 
warranted.  But if you (or Owen) happen to know what to say to get 
UI.Content to be "mixed" PCDATA and output elements, then let's get that 
changed.

Best regards,
John M. Boyer, Ph.D.
STSM, Lotus Forms
Workplace, Portal and Collaboration Software
IBM Victoria Software Lab
E-Mail: boyerj@ca.ibm.com 

Blog: http://www.ibm.com/developerworks/blogs/page/JohnBoyer
Blog RSS feed: 
http://www.ibm.com/developerworks/blogs/rss/JohnBoyer?flavor=rssdw





From:
"Klotz, Leigh" <Leigh.Klotz@xerox.com>
To:
John Boyer/CanWest/IBM@IBMCA
Cc:
"Owen Newnan" <onewnan@gmail.com>, "Forms WG" <public-forms@w3.org>
Date:
01/11/2010 02:54 PM
Subject:
RE: Minimal content model for xf:group and text



Even if we have already decided this in the past for group, repeat, and 
case and it is just test suite issue, we still have a problem with label, 
which doesn't allow text in the XSD schema.

 
From: John Boyer [mailto:boyerj@ca.ibm.com] 
Sent: Monday, January 11, 2010 2:28 PM
To: Klotz, Leigh
Cc: Owen Newnan; Forms WG
Subject: Re: Minimal content model for xf:group and text


Hi Leigh, 

We have already fixed a number of other tests in which the test author 
forgot to put a surrounding label on the text, and 4.6.3.a should be 
similarly fixed (The test as currently written would need such a feature, 
but the test does not require mixed content for what it is testing.) 

It is better to leave the presentation of text as part of the overall 
enhancement to container control content models that may optionally be 
performed by host languages.  For example, we would like to see ODF 
improved in the future to include XForms form controls, not just the 
XForms model, but in ODF the text and form controls are at different 
layers, so there would be an indirection involved in connecting them. 

Cheers, 
John M. Boyer, Ph.D.
STSM, Lotus Forms
Workplace, Portal and Collaboration Software
IBM Victoria Software Lab
E-Mail: boyerj@ca.ibm.com 

Blog: http://www.ibm.com/developerworks/blogs/page/JohnBoyer
Blog RSS feed: 
http://www.ibm.com/developerworks/blogs/rss/JohnBoyer?flavor=rssdw




From: 
"Klotz, Leigh" <Leigh.Klotz@xerox.com> 
To: 
"Forms WG" <public-forms@w3.org> 
Cc: 
"Owen Newnan" <onewnan@gmail.com> 
Date: 
01/11/2010 09:57 AM 
Subject: 
Minimal content model for xf:group and text




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? 
  
Leigh. 

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

Leigh, 

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 
<xforms:group>
When a value is selected you must see the output "xforms-select". The 
value in
parentheses
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").
</xforms:group> 

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.
-- 
Best,

Owen Newnan

cell 720 260-5753
home 303 697 1925
http://www.linkedin.com/in/OwenNewnan
Received on Tuesday, 12 January 2010 17:34:51 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 October 2013 22:06:53 UTC