OASIS Web Services Component Model (WSCM) TC

OASIS Web Services for Interactive Applications
Technical Committee

29 March 2002
teleconference 12:00-1:00pm EST
Minutes

Attendance

Agenda

1. Roll call, minutes and action items from 3/15 meeting
2. Brief report from Sean on his talk on WSIA at OMG workshop
3. Update on April F2F logistics and agenda
4. Discussion of alignment with WSRP TC
   • summary of first WSRP F2F March 18-20
   • proposal for WSIA/WSRP joint subcommittee to do base interfaces
   • proposal for joint F2F meetings, beginning June 24
5. Current draft of requirements for Embedded use case: Alan and Rich
6. Current draft of requirements for Customized use case: Eilon and Ravi

Meeting

Minutes approved. Actions all set, except:

action: Charlie to mail out the presentation from XML/WebServices.

action: Graeme to send list of non-participants to Charlie to get "refresh" of committee participants.

General interest, (the first after lunch on Friday ). 10 minute presentation, similar response to that at the XML conference. People generally interested/intrigued.

Should probably produce a whitepaper and review the communication plan when the requirements are firmer. Eg, executive level white paper.

Expect there to be four things on the agenda.

1. crawl through Embedded and Customized use cases and requirements and carry along the Coordinated and Orchestrated use cases
2. get heads around where WSRP is going/relationship to WSIA
3. review interfaces and proposals already on the table eg WSXL, and see how they address requirements of WSIA and WSRP
4. charter subcommittees

action: all - anyone with any other ideas for April F2F agenda, mail them to Charlie.

(Deferred question on meeting dates overlap with WS-I.org).

Seems that there's a real sense of urgency/aggressive timelines with WSRP. Possibly tied in with overlap with JSR 168 (Portlet Specification). JSR 168 has a reference implementation target for September, and December for a 1.0 reference implementation.This timeline is carrying over to WSRP which is aiming for a first draft in June.

Hoping for a WSIA/WSRP joint meeting around June 24.

action: all - anyone wishing to be involved respond to Alan's email of conf call.

For the joint meeting hoping to have esssentially 2 meetings back-to-back over the 4 days.

action: Charlie to confirm June 24 is ok given conflict with OMG meeting June 24-28.

For now we're assuming that our next meeting will be June 24.

action: all - need to let Charlie know if June 24 is not a good date.

At WSRP Jeff volunteered to handle the common glossary for the 2 groups, so he's waiting for their set of definitions. Help with the glossary would be appreciated.

action: Jeff to send out mail to the list
action: all - anyone interested in helping Jeff with the glossary, please reply to his email

Q: Are we in touch with JSR 168 terms?
A: We're aiming to take a look at them as a starting point, but note that they are portlet and Java specific, whereas we're aiming to be more general than that.

Aiming to

1. define boundary between embedded and customized, and
2. clarify differences between producer and consumer customizations.

Embedded is kind of implying that consumer is doing no producer-specific work. In the Customized case it's likely that the consumer is doing things that are producer-specific.

Q: So CSS changes?
A: Are not Customized - they fall under the Embedded case. But picking on producer-specific tags in the stream and tweaking the response would be the Customized case.

Q: Do we have a means for the consumer to ask the producer what "things" he supports?
A: Yes, in the Embedded requirements.

Section 7 - changed layout so the description precedes the first requirement statement.

WSRP notion of states: a) Persistent state (mainly for design time), and (b) session state. There's a feeling that 100% of the Embedded falls into WSRP, and some of Customized.

So all customization in the Embedded case is generic.

Lifecycle. WSRP has a particular model of session and admin. They call it "bindClient" and then have transient sessions to portlet - seems very portal/portlet specific, we might want to represent a more general case and allow WSRP to be a subset.

So we need to be careful about thinking that WSRP might "cover" Embedded.

URL tagging - probably very appropriate for the joint WSIA/WSRP group to consider.

Q: What about URL's that are generated by Javascript that is part of the markup? Could only work if the base part of the URL was there already?
A: Might be handled by producer-side URL rewriting, which then gets problematic in a multistep value chain. Need to address dynamically generated URLs.

action: Rich - to add dynamically generated URLs to the Embedded case.

Also in 7.3 added references to other known security activities. General point is that we aim to leverage the work being done elsewhere on this.Karl Best is trying to coordinate OASIS efforts with other groups.

action: Charlie - to follow up with Karl on how this coordination process should work.

7.4 - Pointing out that this is not a closed definition. Needs to be open to extensions.

Q: 7.6 - is this Customized?
A: In 7.6.7 there are items that map to properties that are probably generic. Are the generic properties part of Embedded, or is this a "Customized" mechanism? There needs to be some discussion of where this lies - are there 2 mechanisms or one, and if only one how do we restrict it to the base set when not Customized.

Broadly speaking (quickly!).. The alternative customization techniques were discussed, and the subgroups were found to overlap across both mechanisms. (See emails on list). So there are a set of general requirements that are property based, and some are of the opinion that we should have a property description file.

Also under discussion is whether there are 2 styles of customization or one. We might look at stream-oriented as an additional layer that might do preprocessing at the producer side and come back with a property based interface.

action: Embedded/Customized subgroups - probably appropriate to open up these discussions to the whole group now and get extra feedback.

Q: Ravi is particularly looking for a property description language that can accommodate both defined and new properties. With features to accommodate both stream oriented properties and action oriented properties.
A: Maybe should consider XForms constraints for this.