OASIS Web Services Interactive Applications TC

The original Call For Participation for this TC may be found at http://lists.oasis-open.org/archives/tc-announce/200110/msg00005.html

The charter for this TC was last modified on 21 January 2002; this change was announced at http://lists.oasis-open.org/archives/tc-announce/200201/msg00009.html

Upon resolution of the WSIA TC membership that their work has completed, (see http://lists.oasis-open.org/archives/wsia/200307/maillist.html for voting, and the summary at http://lists.oasis-open.org/archives/wsia/200310/msg00000.html) the OASIS WSIA TC is closed.

The charter for this TC is as follows.


OASIS Web Services Interactive Applications (WSIA) TC.

Statement of Purpose

The purpose of the OASIS Web Services for Interactive Applications (WSIA) TC is to create an XML and web services centric framework for interactive web applications; harmonize WSIA as far as practical with existing web application programming models, with the work of the W3C, emerging web services standards, and with the work of other appropriate business information bodies; ensure that WSIA applications can be deployed on any tier on the network and remain target device and output markup neutral; and promote WSIA to the status of an international standard for the conduct of XML and Web Services based web application development, deployment and management.

List of Deliverables

The primary deliverable of the WSIA TC is a coordinated set of XML vocabularies and Web Services interfaces that will allow businesses to: 1) deliver web applications to end users through a diversity of deployment channels: directly to a browser or mobile device, indirectly through a portal, or by embedding into a 3rd party web application; and 2) Create web applications that can be easily be modified, adapted, aggregated, coordinated, synchronized or integrated by simple declarative means to ultimately leverage a worldwide pallet of web application components.

As currently envisioned, the WSIA work will take place in five phases:

  1. A first phase to gather requirements across web application deployment, development and management vendors.
  2. A second phase to define a set of "base" web services interfaces that can be used to expose web application function and adaptation.
  3. A third phase to define a "wiring mechanism" to declaratively specify web application semantics.
  4. A fourth phase to define a set of web services interfaces that can be used to partition web applications into model, view and control (MVC).
  5. A fifth phase to define a set of design patterns to guide WSIA developers in creating re-useable application components. In addition the TC will encourage implementations, test suites and interoperability guidelines.

If the work actually does take place in this form, then it is estimated that the first, second and third phases will take roughly one year to complete and that the fourth and fifth phase will take roughly one year.

If phases can be combined or run in parallel, then it is estimated that delivery of an initial set of specifications will take one to two years.