Welcome to the WSCM Technical Committee

1
Welcome to the WSCM Technical Committee

• First face to face meeting
• January 7-9, 2002
• IBM Research
• Hawthorne, NY

2
This Meeting

• Kick off the Technical Committee (OASIS process)
• Agenda for the remainder of the meeting
• Day 1 Requirements and technology overview
  presentations
• IBM, Epicentric, WebCollage, CrossWeave, HP,
  Kinzan, Bowstreet, Cyclone Commerce, Rex Brooks
  (HML), Fujitsu
• Summarization of requirements
• Day 2 Defining the WSCM roadmap
• Related XML and web services standards
• Strawman framework for WSCM and relationship to
  the web services stack, and positioning of talks
  against it
• Breakout sessions into prospective subcommittees
• Setting milestones based on breakout reports
• Day 3 Plan for moving forward and communications
• Relationship with other TCs and working groups
• Conference and paper plans
• WSCM meeting schedule and format

3
Charter of the WSCM Technical Committee Goals

• The aims of the WSCM TC shall be as follows
• Create an XML and web services centric component
  model for interactive web applications. The
  designs must achieve two main goals enable
  businesses to distribute web applications through
  multiple revenue channels, and enable new
  services or applications to be created by
  leveraging existing applications across the Web.
• To harmonize WSCM as far as practical with
  existing web application programming models (e.g.
  Portals, Macromedia Flash, etc.), with the work
  of the W3C (e.g.XForms, DOM, XML Events, XPath,
  XLink, XML Component API task force), emerging
  web services standards (e.g. SOAP, WSDL, WSFL),
  and with the work of other appropriate business
  information bodies.
• Ensure that WSCM applications can be deployed on
  any tier on the network and remain target device
  and output markup neutral.
• Ultimately, to promote WSCM to the status of an
  international standard for the conduct of XML and
  Web Services based web application development,
  deployment and management.

4
Charter of the WSCM Technical Committee
Deliverables

• The primary deliverable of the WSCM TC is a
  coordinated set of XML vocabularies and Web
  Services interfaces that will allow businesses
  to
• 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
• Create web applications that can be easily
  modified, adapted, aggregated, coordinated,
  synchronized or integrated by simple declarative
  means to ultimately leverage a worldwide pallet
  of web application components.

5
Charter of the WSCM Technical Committee Phases
of work

• As currently envisioned, the WSCM work will take
  place in five phases
• A first phase to gather requirements across web
  application deployment, development and
  management vendors.
• A second phase to define a set of "base" web
  services interfaces that can be used to expose
  web application function and adaptation.
• A third phase to define a "wiring mechanism" to
  declaratively specify web application semantics.
• 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).
• A fifth phase to define a set of design patterns
  to guide WSCM developers in creating re-useable
  application components. In addition the TC will
  encourage implementations, test suites and
  interoperability guidelines.

6
WSCM Positioning in the Web Services standards
stack
Security / Privacy
Quality of service
Management
7
Existing and WSCM-specific elements of a user
interface framework
WSCM Data Service
WSCM Presentation Service
WSCM Base Service
WSCM Container
WSCM Event Controller
Event wiring
WSFL - Flow modeling
WSFL - Global modeling
WSDL - Operations
Existing WS infrastructure
WSCM
8
Existing and WSCM-specific elements of a user
interface framework - as amended by TC
User and device profiling
WSCM Data Service
WSCM Presentation Service
WSCM Base Service
WSCM Container
WSCM Event Controller
Event wiring
WSFL - Flow modeling
WSFL - Global modeling
WSDL - Operations
Stateful services
Events
Existing WS infrastructure
WSCM
Required WS infrastructure
9
Layering on top of evolving WS stack

• Address more general issues of WS infrastructure
  (sessions, context, transactions, security)
  through OASIS/W3C liaison roles
• Retain focus of this TC on interactive
  applications
• TC name Web Services for Interactive Applications

10
Coarse-grained interaction
Providers
Integrator
Client
Application Back End Services
User Experience Services
11
Define a set of "base" web services interfaces
that can be used to expose web application
function
Coarse-grained interaction
User and device profiling
WSCM Data Service
WSCM Presentation Service
WSCM Base Service
WSCM Container
WSCM Event Controller
Event wiring
Flow modeling
Global modeling
WSDL - Operations
Stateful services
Events
Existing WS infrastructure
WSCM
Required WS infrastructure
12
Define a "wiring mechanism" to declaratively
specify web application semantics.
Interaction wiring
User and device profiling
WSCM Data Service
WSCM Presentation Service
WSCM Base Service
WSCM Container
WSCM Event Controller
Event wiring
WSFL - Flow modeling
WSFL - Global modeling
WSDL - Operations
Stateful services
Events
Existing WS infrastructure
WSCM
Required WS infrastructure
13
Fine-grained interaction
Providers
Integrator
Client
WSXL Data
WSXL Pres
WSXL Control
Application Back End Services
User Experience Services
14
Define a set of web services interfaces that can
be used to partition web user interfaces into
model, view and control (MVC) services
User and device profiling
WSCM Data Service
WSCM Presentation Service
WSCM Base Service
WSCM Container
WSCM Event Controller
Event wiring
WSFL - Flow modeling
WSFL - Global modeling
WSDL - Operations
Stateful services
Events
Existing WS infrastructure
WSCM
Required WS infrastructure
15
Work phases

• Base service definition - coarse grained
• what are the types, messages, and operations of
  the service interface?
• How is flow managed across pages?
• How is state shared between provider and
  integrator?
• How is the target device context indicated?
• Wiring definitions
• How are services wired together? - XML events,
  XLINK language, handlers for event
  transformations
• MVC service definition - fine grained
• What are the operations of the data and
  presentation service interfaces?
• Service adaptation
• Market requirements for platforms, migration
• Discussion in group as a whole

16
Breakout group Producer

• Goals and purpose
• What set of requirements fall onto the Producer?
• What are any additional ones?
• What uses cases illustrate these reqs?
• What market segments exist for Producers
  (portlet, ASP, separate web app?)
• What are the priorities among the reqs (1, 2, 3)
• Work products
• What are the relevant WSIA interfaces and XML
  languages to be defined?
• Relationship with existing standards
• Open questions
• Can composition be enabled through existing or
  emerging service-composition languages such as
• WSFL Global Modeling? Can flows be enabled
  through WSFL Flow Composition?
• Milestones
• Gather requirements across web application
  deployment, development and management vendors

17
Breakout group Consumer

• Goals and purpose
• What set of requirements fall onto the Consumer?
• What are any additional ones?
• What uses cases illustrate these reqs?
• What market segments exist for Consumers
  (portals, ASP, separate web app?)
• What are the priorities among the reqs (1, 2, 3)
• Work products
• What are the relevant WSIA interfaces and XML
  languages to be defined?
• Relationship with existing standards
• Open questions
• Can composition be enabled through existing or
  emerging service-composition languages such as
• WSFL Global Modeling? Can flows be enabled
  through WSFL Flow Composition?
• Milestones
• Gather requirements across web application
  deployment, development and management vendors

18
Breakout group Service Adaptation

• Goals and purpose
• Define an XML language for specifying how
  developers are allowed to adapt applications and
  the markup
• they generate for the varying requirements of
  multiple channels.
• What set of requirements fall onto the Service
  Adaptation?
• What are any additional ones?
• What uses cases illustrate these reqs?
• What are the priorities among the reqs (1, 2, 3)
• Work products
• What are the relevant WSIA interfaces and XML
  languages to be defined?
• Relationship with existing standards
• Open questions
• Milestones

19
Open Issues and Focus Areas

• Business considerations
• Usage patterns and requirements
• Core functionality and architecture of the UI
  framework
• Base interfaces base service, data inputs and
  outputs, page entry points, and
  collection/container
• Flow composition
• Aggregation (global composition)
• Event interaction and composition
• Surrounding issues
• Security
• Management model
• Agreements
• Availability, failure and recovery semantics
• Adoption
• Core implementation product support - which
  platforms?
• Performance
• Tooling
• Development models
• Standardization
• Standardization process for core architecture

20
Summary

• Goals for remainder of this meeting
• identify major stages of work, prospective
  subcommittees
• for each stage, identify plan for developing
  business and technical requirements, plan for
  identifying available technologies, refine
  milestones, list open issues
• Follow up
• Process for on-going meetings
• Date for next face to face meeting
• Discussion of milestones from breakout sessions
• Identify sub-topics for off-line work