I.                   WSRP-WSIA Joint Interfaces/Metadata Conference Call

II.                July 9, 2002

 

 

William Cox

BEA

 

Graeme Riddell

Bowstreet

 

Srinivas Vadhri

Commerce One

Y

Monica Martin

Drake Certivo

Y

Alan Kropp

Epicentric (chair)

Y

Charles Wiecha

IBM

Y

Rich Thompson

IBM

 

Carsten Leue

IBM

 

Thomas Schaeck

IBM

Y

Rex Brooks

Individual

 

Joe Rudnicki

U.S. Navy

Y

Mike Freedman

Oracle

 

Stefan Beck

SAP

 

Jeffrey C. Broberg

Silverstream

 

Suresh Damodaran

Sterling Commerce

 

Eilon Reshef

WebCollage

 

Gil Tayar

WebCollage

 

Steve Pruett

Silverstream

 

Mike Hillerman

Peoplesoft

 

Aditi Karandikar

France Telecom

Y

Ravi Konuru

IBM

 

Howard Melman

Silverstream

 

Angel Diaz

IBM

Y

Alejandro Abdelnur

Sun

Y

Eric van Lyndegraf

Kinzan

 

Agenda

For this week's joint interfaces agenda, we can focus on two related issues:

 

1.  A user guide for the specification.  What should be included?  How structured?  Who wants to participate?

 

2.  The context objects we discussed at the face-to-face are the mechanism to parameterize aspects of a Consumer, a Client, the request, etc.  How should they be structured?  What is required information that should be included?  Nice-to-have information?

 

Specification

The current version encompasses comments from the initial draft reviewers, and is now in circulation on the lists.

 

Parameters, extensibility

Refactoring of parameters should also imply refactoring the operations themselves (Charlie).

 

Basic questions:  What data should be represented as top-level parameters?  What data should be pushed into structured parameters?

 

We need a formal object model as part of this exercise, in particular with regards to extensibility (Charlie). 

 

The Consumer should be able to tell the Producer explicitly to release a session ID, or the markup parameters that represent a “session” when the Producer is stateless (Mike).

 

User Guide

Mike F.’s presentation at the face-to-face would make a good starting point for the guide (Rex).

 

Monica asked what the guide is intended to provide: implementation or deployment information.  Consensus is that this is an implementation guide.

 

Re-structure the layered scenarios that are now part of the specification, define multiple “axes” instead (Rich).  Axes may include:

 

The guide should reference relevant sections in the specification (Monica).

 

Alan offered to put together an outline of the user guide.

 

Other

Need to stay informed on the progress of the new OASIS Security committee (Monica).