W3C home > Mailing lists > Public > www-forms-editor@w3.org > November 2009

Attached: draft XSDs to validate XForms 1.1 instances hosted with XHTML 1.0.

From: Owen Newnan <onewnan@gmail.com>
Date: Sun, 29 Nov 2009 11:34:18 -0700
Message-ID: <72162e1b0911291034v6ac7a52fl537467ac1bca9371@mail.gmail.com>
To: www-forms-editor@w3.org, xsltforms-support@lists.sourceforge.net
Cc: boyerj@ca.ibm.com, COUTHURES Alain <alain.couthures@agencexml.com>, dan@danmccreary.com
This is to share with you draft schemas to validate XForms applications.

I have mailed information about these schemas in recent days to both the W3C
www-forms-editor and XSLTForms support mailing lists.  I today discovered
that "for greater convenience to the community in the  future, the working
group is taking action to define a working group note that specifically
targets validation of XHTML with
XForms<http://lists.w3.org/Archives/Public/www-forms-editor/2009Nov/0001.html>".
  Therefore, please consider the attached an interim implementation until
W3C issues the note, or possibly a contribution to that note..

Clearly an integration with the XHTML 2 modular schemas would be desirable
but I had issues getting them to work with my tools, hence the 1.0
integration.  Perhaps it would be helfpul to provide more than one profile?

The XForms 1.1 specification says ""A host language is expected to add
attributes such as xml:lang as well as an attribute, named class, that holds
a list of strings that can be matched by CSS class selectors."  However, the
XForms 1.1 schema does not include a class attribute.  The intention seems
to be that this attribute will be supplied via the host language
integration.  The approached used in the attached is to use the XForms
schema verbatim--so it is not modified from a copyright perspective--and
then redefines it so it incorporates the XHTML UI attributes.

Testing this script suggests there may be error(s) in the XForms 1.1 schema..
 The specification states "Core form controls always have labels directly
associated with them as child elements— this is a key feature designed to
enhance accessibility" [where core forms are listed at
http://www.w3.org/TR/xforms11/#def-core-form-control]."  However, it appears
in some cases the schema requires labels for non core form controls where
the spec does not, e.g., for case and group.  Thus, a label is required for
the case element per the schema; but there are examples of it in the spec
without labels.

FYI, I also attached an ant script to validate XForms instances using the
schemas.


-- 
Best,

Owen Newnan

cell 720 260-5753
home 303 697 1925
http://www.linkedin.com/in/OwenNewnan



Received on Sunday, 29 November 2009 19:41:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 29 November 2009 19:41:33 GMT