Open Issues from WS App Note discussion + 2nd Revised outline for WS RF App Note

["Alan Weissberger" <ajwdct@technologist.com>]

Disclaimer: Katy Warr will be taking over ownership of this document, as I am not funded to pursue it. 

 

Key open issues from October 27 f2f meeting discussion:

1.      Alan AI: send an email to William that captures what we’d like WSDM TC members to contribute to the WSRF App Note, regarding their use of the WSRF specs.  The response will hopefully be used in the WSDM section of the WSRF App Note (see outline below)

2.      Need volunteers to work on all sections of this document.  Initial contributions would be appreciated in the following areas:

A]the composability of the WSRF specs with each other,

B] the composability of WSRF and WS-N,

C] examples of WS applications that could use WSRF specs.

3.      Need a volunteer for second editor.  This assumes Katy Warr of IBM-UK will be the primary editor of this document

4.      We need to consider which non- normative sections of the 2 white papers (The WS-Resource Framework and Modelling Stateful Resources with Web Services) to fold into the App Note and how we should reference the new WS Resource document

5.      (Brian) Are there any issues from the WSRF Issues list that are non normative and need clarification or suggested solutions?

I. Introduction/ Abstract

The purpose of the WSRF App Note is to produce a non-normative document that describes how to use the WS-RF family of specs.  Building on the WSRF Primer, it clarifies non normative issues of the WSRF spec, while providing composability aspects with related specs.  The focus of the document is on three types of "how to use WS-RF specs" with appropriate examples:

1] Composing WS-RF specs with each other, e.g. WS-RP, WS-RL, and WS Service Groups (maybe WS Resource too?)

2] How other WS specs might use the WS-RF specs, e.g. WS-Notification (modeling a subscription as a WS Resource), WSDM, WS-Portlets, others TBD

3] How new WS applications (with stateful resources) might use the WS-RF specs, e.g. modeling peripheral (e.g. printers) and network equipment as WS-Resources, modeling other types of stateful resources that exist behind a WS interface.

II. Detailed Outline for the WS-RF App Note document:

A. High level overview of the WS-RF specs: WS-Resource, WS-Resource Properties, WS-RL, WS-BF, WS-SG, WS-Renewable References (if published)

(Only one or two paragraphs to describe each spec description)

B. Reference to Definitions of various terms+: WS Resource, Implied Resource Pattern, Factory Pattern, Resource Lifetime, Renewable Resource, etc

+ The normative definitions are in WS Resource. The WSRF Primer should have a complete listing of definitions, and if so, we can point to it here.

C.  Information from the two white papers (suggest we extract relevant applications- related information from the two white papers (The WS-Resource Framework and Modelling Stateful Resources with Web Services). 

What sections parts of the white papers should be extracted?

 

C. Motivation: WS Applications/ Use Cases for the WS-RF specs

Potential applications for WS-RF specs include: examples of Web Services that contain stateful resources behind the WS interface, Grid Infrastructure layer (formerly known as OGSI- see OGSI Primer and OGSA Use Case document), WSDM specs use of WS-RF capabilities, Modeling remote portlets (WS-RP) as WS resources, modeling a subscription to a notification pattern as a WS resource (WS-Notification), other WS specs that might make use of WSRF specs (TBD by the contributors- what about WS Security?)

D. Composability Details

1. How the individual WS RF specs compose, i.e. are used together (including any dependencies and interactions). Which one's are used together (e.g. WS-Resource, WS-Resource Property and WS-RL) vs WS RF specs which might stand alone (e.g. WS Base Faults)

2. How WS-RF specs could be used with WS-Notification specs (as per Peter Niblett's presentation to both TCs at f2f meeting)

3. How WSDM specs (MUWS and MOWS) make use of WS-RF specs (input from WSDM TC  will be solicited).

4. How WS Remote Portlets could be modeled as WS Resources and make use of WS-RF specs (which one's?).  This might be a placeholder till we get volunteers to work on it.

E. Clarification of the issues from the WSRF issues list that we feel are implementation dependent (and therefore non normative/ not subject to standardization). This also includes best practices* and recommendations. For example, possible interpretations of fault messages, potential recovery options, policy issues effecting any of the WS-RF spec

* We specifically stated that Issue WSRF48: Specify behavior of nillable properties was a candidate for the App Note/Primer. "This should be clarified or described as a best practice in the Primer, should we decide to write a Primer."

We will discuss next Wed at 10AM in detail

Alan Weissberger

NEC

1 408 863 6042 voice

1 408 863 6099 fax

 

--

___________________________________________________________
Sign-up for Ads Free at Mail.com
http://www.mail.com/? sr=signup