Minutes of the GGF6 OGSI-WG Meeting
Chicago
15/Oct/2002

Session 1: Overview and Update
==============================

Steve Tuecke (Slides available on the web site)

Documents:

   Grid Service Spec v4 (Major working document), 

   Timestamp for Distributed Computing (Tabled by the working group),

   Handle URI Definitions (May come into existence within this WG, e.g. http(s), SGNP).
   This group does have more to do here before the actual creation of these documents.

   Physiology of the Grid (Several options are possible, but likely to move to OGSA-WG for final clean up)

   Primer (Status uncertain)

Compliance Service: Pending a document proposal before this WG would take it on. A prototype is in process along with 
OGSA-DAI project. Possibly before this group again at GGF7.

Other OGSA related activity (OGSA, OGSA Security, DAIS, Usage Record, Resource Usage, Java Containers)

W3C and WSDL Evolution (v1.2) This WG pushed for Open Content and portType extension. Plans are that they will be there 
in 1.2. Also work proceeding on SOAP, OASIS (General Security issues), Project Liberty (Identity Federation).

Implementations (Globus Tech preview toward GT3; Unicore will do something but not at the same time scale as GT3 Alpha 
Jan 15th 2003; IBM will be providing something within WebSphere via a common implementation with GT3 through the 
community source process; Python hosting environment implementation coming on the Spring time scale; G-SOAP 
implementation from Florida with in GridLab project.

Activities Since GGF5 (9 Teleconferences, 1 three day interim meeting, broad participation).

Document Schedule:

   GGF6: Draft 4
   Nov 11; Draft 5
   Nov 14-15: Interim meeting
   Dec 15: Submit to GGF document process
   GGF7: Approval as GGF Document.

Version 1.1: There may be a need for this, so we are planning for it through minimal temporary solutions. Question: Drop
 or delay? Leaning toward toward drop rather than delay.

Bugzilla: The document is finished when bugizza is empty.

Weekly phone calls will continue through December.

Interim Meeting 2: at ANL November 14-15.

IPR Statements: Copyright issues cleared with initial authors of GSS. Open statement from IBM for RF status with respect
 to GSS. The status of WS-Inspection specifically is still being pursued. Sun reiterated a RF approach to any GGF 
document. We will rely on GGF to make this status clear for this and other specifications.

WSDL 1.2 Timing: Will probably slip past the 4Q/02. Options:

Delay with W3C:
Shoe horn into WSDL 1.1:
Subset functionality into WSDL 1.1 and adapt:
Go as if WSDL 1.2 was complete:
Press on W3C between now and the Interim meeting: - This seems to be the consensus at this point.

Technical issues for later meetings, see program for times.

Session 2: Notification and Events 
==================================

Background: Today we have ServiceData which is a 'view' on the service's state. Nothing is said specifically about 
coherency. Access to the data is possible through findServiceData and Notification. There is also lifetime management on
 the ServiceData. There is a notion of 'edge' versus 'level' triggered notifications. The current spec only supports 
level triggering. Note that all ServiceData is subject to access controls. There is a difference between the reliability
 of the service data changes being observed by the service and the reliable  delivery of those changes to the client. 
Part of this stems from the push/pull model. The tie between push and pull model could be tighter in the model.

Where do we go from here?

Shel F: Do we need reliable delivery in the spec? In this context we do need to keep the distinction between reliable 
delivery and  availability of complete data distinct.

Steve G: Asynchronous messaging is critical to Grid Service world. Patterns are the key. Notifications are tied to 
ServiceData. Made a general proposal for decoupling messaging from the message content. Note that the pattern needs to 
be kept...