Re: Problem with XForms 1.0 Basic Profile document when used with XFo rms Full processor

Thank you for your comment on XForms Basic [1]; the
Working Group apologizes for the delay in responding.

Your issue has revealed a problem in XForms 1.0 SE recommendation for
the processing of the "type" model item property.

The working group has therefore issued the following resolution:
   "Issue an erratum for '6.1.1 Type property' about how the type is bound
to the data.  It mustn't be done by equivalency to xsi:type attribute." [2]

As you have recently rejoined the XForms Working Group, we trust you will
participate in the development of this erratum.

Your understanding that in the Basic Profile that the model attribute
schema is ignored and that inline xsd:schema elements are ignored is
incorrect.  In XForms Basic, Section 3 "Conformance"
[http://www.w3.org/TR/xforms-basic/#id2606183], indicates that type
libraries obtained by the schema attribute and inline schemas are
processed to find global simpleType definitions, and these named type
definitions can be used by the bind type model item property, and by
xsi:type.  As complex types are not processed, any reference by xsi:type
or the type model item property to a complexType is ignored.  Note that
an ignored xsi:type declaration in the instance data would be processed
as if the declaration were absent, and that an ignored bind type model
item property will be processed according to the definition in XForms
1.0 Section 6.1.1.

We hope that this reply solves your issue. We would appreciate if you  
would reply to this mail indicating that you are satisfied that it has  
been resolved.

Best wishes,

Steven Pemberton and John Boyer
For the Forms Working Group

[1] http://lists.w3.org/Archives/Public/www-forms-editor/2004Aug/0003
[2] (member only link: http://www.w3.org/2006/03/23-xforms-minutes#item02)

Received on Thursday, 15 June 2006 22:27:12 UTC