[wsrp-wsia] Customization Requirements

[Eilon Reshef <eilon.reshef@webcollage.com>]

Hi All,

Wanted to bring up several requirements that came up in the context of
the WSIA Customization sub-committee, and which I feel may be relevant
to push down to the joint committee. Naturally, these will be discussed
in more length in the F2F, but I thought it might provide some food for
thought for earlier discussions.

In the discussion below, context data = transient state specific in the
entity/user scope.

Eilon

It should be possible for a Consumer to initialize the Producer's
context data that is computed dynamically in run-time by the Consumer. 
  (This is different from WSRP where all initialization is done
off-line).

It should be possible for a Consumer to set Producer context data during
any user interaction, at defined points in the request lifecycle, not
only at the initialization of the Producer.
  (This is an extension of the above).

It should be possible for a Consumer to receive context data from the
Producer at the end of its interaction with the end user. 
  (This is different from WSRP where no data transfer is available)

It should be possible for a Consumer to read Producer context data
during any user interaction not only at the initialization of the
Producer.
  (This is an extension of the above).

Throughout the interaction with the end user, it should be possible for
a Consumer to dynamically receive context data from the Producer,
compute corresponding context data, and send the computed context data
dynamically back to the Producer.
  (This defines the need for a back-and-forth mechanism)

The Consumer should be able to send to the Producer context data that
affects the Presentation Fragment generated. 
  (This means that the Consumer should be able to send data before 
   the presentation is transmitted). 

The Consumer should be able to receive from the Producer context data
that depends on the last user action. 
  (This means that the Consumer must be able to receive the data after 
   the user interaction is accepted).

The Consumer should be able to read and set a Producer's context data
multiple times during a single user interaction. 
  (This is an extension of the above)