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

Re: XForms 1.1 RNC Schema xf:instance

From: John Boyer <boyerj@ca.ibm.com>
Date: Mon, 11 Jan 2010 14:18:12 -0800
To: "Klotz, Leigh" <Leigh.Klotz@xerox.com>
Cc: "Forms WG" <public-forms@w3.org>
Message-ID: <OFA01FB933.5CC7752C-ON882576A8.00799FBE-882576A8.007A8490@ca.ibm.com>
Hi Leigh,

I agree.  I don't know why it would say anyElement* since if you put more 
than one element, processing will halt with an exception anyway.

If there is a src attribute, it takes precedence over inline content, so 
perhaps there "should" be nothing there, but you don't get an exception if 
there is, so there is not a real need to enforce it.

There is an analogous co-occurrence constraint with resource, but it works 
the other way around.  If there is inline content, then the resource 
attribute is ignored.  So one might be inclined to say there should not be 
a resource attribute if there is inline content.  However, the reason I 
advocated for the resource attribute is so that a document (e.g. ODF, XFDL 
or even prepopulated HTML) could be responsive to state other than the 
initial empty states without having to modify the part of the document 
associated with the "application" description, which may be digitally 
signed. So, it is expected that inline instance data and the resource 
attribute can co-exist and that the well-defined precedence order 
indicates what to do.  It is not unreasonable, then, to take the same 
approach for handling co-occurrence of src and inline data.

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: 

"Klotz, Leigh" <Leigh.Klotz@xerox.com>
"Forms WG" <public-forms@w3.org>
01/11/2010 10:04 AM
XForms 1.1 RNC Schema xf:instance

We should change
xforms.instance.content = xforms.anyElement*
xforms.instance.content = xforms.anyElement?
There may lexical co-occurrence constraints with @src but there are none 
with @resource so I believe this change is sufficient.


From: Owen Newnan [mailto:onewnan@gmail.com] 
Sent: Saturday, January 09, 2010 5:56 PM
To: Klotz, Leigh
Subject: invalid instance data?


I get the message

Chapt03/3.3/3.3.2/3.3.2.g.xhtml:11:20: cvc-complex-type.2.4.d: Invalid 
content was found starting with element 'numberB'. No child element is 
expected at this point.

I think this message is right, the spec says

If the initial instance data is given by inline content, then instance 
data is obtained by first creating a detached copy of the inline content 
(including namespaces inherited from the enveloping ancestors), then 
creating an XPath data model over the detached copy. The detached copy 
must consist of content that would be well-formed XML if it existed in a 
separate document. Note that this restricts the element content of 
instance to a single child element.

However, I get no err on the RNC side.  Same thing with 3.3.2.h.xhtml.

Owen Newnan

cell 720 260-5753
home 303 697 1925
Received on Monday, 11 January 2010 22:18:45 UTC

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