WSRP-WSIA Joint Interfaces/Metadata Conference Call, Tuesday May 7

Attendees

Charlie Wiecha, Lothar Merk, Srinivas Vadhri, Rich Thompson, Bill Cox, Steve Pruett, Rex Brooks, Monica Martin, Thomas Schaeck, Mike Freedman, Gil Tayar, Jeff Broberg, Graeme Riddell, Mike Hillerman, Alan Kropp

 

Requirements

There is a need to focus on high-level requirements...for instance, a general requirement “Lifecycle” which encompasses several of the detailed requirements. 

Interfaces discussion should proceed in parallel with requirements, facilitated by introducing the following “buckets” to classify aspects of the common specification:

·    Lifecycle (state)

·    Properties

·    Output/Actions

·    Events

·    Self-description

·    Access control

Security is more an aspect of the interface (or protocol), and not a discreet interface or protocol. 

There was some discussion around portlet modes as a template for access control.  Two models:  the access control is contained within the producer service, or is delegated to the consumer.

Actions are always end-user initiated (with expectation that markup will be generated)?  This will continue to be debated.

Interface Strawman

Focus on some of the buckets identified:

·      Lifecycle

·      Properties

·      Actions

·      Self-description

Gil and Eilon have been working on a document that maps IWS and WSXL.  Formalize into a (sub?)sub-group effort, including:  Rich, Jeff B., Thomas, Mike F., Alan.

Will work from proposed API’s (IWS, WSXL, MWS) to define a strawman…bottom-up analogue to top-down requirements refining discussions.

Charter

Walk through the proposed charter

Official name:  WSRP/WSIA Joint Interfaces/Metadata Subcommittee.

Deliverable schedule tied to joint face-to-face in June, as well as WSRP July specification (initial draft).

New version of the charter follows below.

Lifecycle

 Began walk-through of diagram.  It is very apparent that the four states (Unknown, Known, Active, Inactive) are high-level, and we should drill down to discover useful substates (e.g., Registered as a sub-state somewhere between Known and Unknown).

The Inactive state is likely to be out-of-scope for now (Charlie:  more applet-like at this stage).

Separate Producer-specific vs. Consumer-specific states

Logistics

Alan is unavailable next week, will coordinate with Rich about next Tuesday’s joint interfaces telecon.

We should begin to surface requirements and interface discussions asap in WSRP..this week’s WSRP Interfaces & Protocol telecon (Thursday)?  Agenda item for next WSRP TC telecon?

 

Charter

The purpose of the OASIS WSIA/WSRP Joint Interfaces Subcommittee is to specify the set of common interfaces that underlie both WSRP and WSIA.  The goal is to leverage the work of both technical committees in the creation of a common remote services invocation and metadata specification, which both the WSIA and WSRP specifications may look to as a foundation.

NAME

The name of this Subcommittee shall be the OASIS WSIA/WSRP Joint Interfaces/Metadata Subcommittee.

PURPOSE

The aims of this subcommittee shall be as follows:

  1. Define the set of requirements that address the WSIA Embedded use case and relevant scenarios.
  2. Harmonize this set of requirements with the requirements that emerge from ongoing discussions in WSRP.  Requirements must be sufficiently broad to account fully for WSRP needs within the scope of WSIA Embedded services.  Where it’s obvious that additional specificity is needed on the WSRP side that goes beyond the WSIA Embedded scope, the relevant specifics should be captured for illustrative purposes.
  3. Draw up a draft specification that covers the common requirements.  .

DELIVERABLES

The primary deliverable of the subcommittee is a draft specification of the joint WSRP/WSIA interfaces and metadata:

As currently envisioned, the subcommittee’s work will take place in two phases:

  1. A first phase to gather requirements and draft a specification as outlined above.  The delivery date for this draft is timed for presentation at the joint face-to-face meeting the week of June 24th.  Follow-on work to synchronize with the WSRP initial draft specification due in July.  
  2. The next phase takes place in the time frame after the face-to-face, at which point requirements from the Customized use case will be ready for consideration as part of the final draft of the joint specification.