This page summarizes the relationships among specifications, whether they are finished standards or drafts. Below, each title
links to the most recent version of a document.
For related introductory information, see: Scripting and Ajax.
Completed Work
W3C Recommendations have
been reviewed by W3C Members, by software developers, and by other
W3C groups and interested parties, and are endorsed by the
Director as Web Standards. Learn more about the W3C Recommendation
Track.
Group Notes are not standards and do not
have the same level of W3C endorsement.
Standards
|
2009-10-20
|
translations
·
errata
XForms is an XML application that represents the next generation
of forms for the Web. XForms is not a free-standing document type,
but is intended to be integrated into other markup languages, such
as XHTML, ODF or SVG. An XForms-based web form gathers
and processes XML data using an architecture that separates
presentation, purpose and content. The underlying data of a form is
organized into instances of data schema (though formal
schema definitions are not required). An XForm allows processing of
data to occur using three mechanisms:
-
a declarative model composed of formulae for data
calculations and constraints, data type and other property
declarations, and data submission parameters
-
a view layer composed of intent-based user interface
controls
-
an imperative controller for orchestrating data
manipulations, interactions between the model and view layers, and
data submissions.
Thus, XForms accommodates form component reuse, fosters strong
data type validation, eliminates unnecessary round-trips to the
server, offers device independence and reduces the need for
scripting.
XForms 1.1 refines the XML processing platform introduced by
[XForms 1.0] by adding several new
submission capabilities, action handlers, utility functions, user
interface improvements, and helpful datatypes as well as a more
powerful action processing facility, including conditional,
iterated and background execution, the ability to manipulate data
arbitrarily and to access event context information.
|
Group Notes
|
2007-09-12
|
The Charter of the
Web Application Formats Working Group
includes a deliverable titled
Specification of a declarative format for applications and user interfaces.
This document includes the status of this deliverable and
a recommendation that the Working Group stop formal work on
this deliverable and consider this Note as the one and only
publication for this deliverable.
This Note also includes some potential options if W3C Members
choose to do related work.
|
|
2006-11-16
|
This paper introduces the concept of a "Rich Web Application Backplane" --
a set of common building blocks for web applications. We argue that
submission, data models, model-view binding and behavior, and web components
can provide a common infrastructure for multiple markup formats. Further, we
propose a common infrastructure for both declarative and imperative web
programming languages. By aligning APIs and their declarative
representations, we hope to support both implementation approaches and
increase interoperability between them.
|
Drafts
Below are draft documents:
Candidate Recommendations, other Working Drafts.
Some of these may become Web Standards through the W3C Recommendation Track
process. Others may be published as Group Notes or
become obsolete specifications.
Candidate Recommendations
|
2003-10-14
|
The XForms Basic Profile describes a minimal level of XForms processing
tailored to the needs of constrained devices and environments.
|
Other Working Drafts
|
2010-12-16
|
This document describes SCXML, or the "State Chart extensible
Markup Language". SCXML provides a generic state-machine based
execution environment based on CCXML and Harel State Tables.
|
W3C
