|
|
|
|
Returning to the
Italian theme with which this talk began
|
|
The top layer includes presentational markups
like XHTML, SVG and VoiceXML as well as markups aimed at helping to provide
underlying interactions and behaviors, like XForms and XBL2.
|
|
The bottom layer is the platform technologies
on which we rely, such as a DOM parser, DOM events, an XPath engine for
addressing XML, and JS/AJAX for helping to provide the consistent new
functionality in existing web browsers
|
|
The Rich Web Application Backplane, then, would
be a middle layer that provides
|
|
meaning for mixed markup through a compound
document framework
|
|
a basis for managing XML data that components
can bind to and interact with
|
|
an ability to synchronize component behaviors
based on XML events and handlers
|
|
the capacity to annotate data with properties
accessible to all components
|
|
a powerful capacity to interact with server
side modules and data sources
|
|
A systematic means of controlling the
availability and interactions of components within a large web application
|
|
And the ability to recurse all of the above via
an XML application component model (XAC model)
|
|
This final slide
is perhaps a bit of a good news story for the W3C since all but one of the
blocks are either covered in some form or another by a W3C Recommendation
Track document or by a technology considered to be foundational by the W3C. In some cases, there are direct technical
reports covering the topic, such as XML Events or SCXML. In other cases, such as the model property
broker or submission object, there is a technical report that contains at
least some version of the technology, making it easier to draw from both the
architectural and practical implementation experience within the W3C to help
achieve the rich web application backplane.
|
|
The only
component not yet on the W3C Rec track is the application component (XAC)
model. Not only is that likely to
change soon, but it is also the subject of the next talk in this session.
|
