Minutes of the Third Interim Face to Face Minutes
January 22-24, 2003

Attendees:

Shel Finkelstein, Sun
Steve Tuecke, ANL
Steve Graham, IBM
Tom Maguire, IBM
Jeffery Frey, IBM
Karl Czajkowski, ISI
Ellen Stokes, IBM
Jay Unger, IBM
Dave Snelling, Fujitsu
Pete Vanderbilt, NASA

1) Approve previous minutes - OK

2) WSDL Working Group Review

The following is an edited extract from Steve Graham's mail reporting from the WSDL Group meeting:

  "The conclusion the WSDL group reached was to consider that operation names have
  a combination of namespace name and operation (local) name.  The uniqueness
  constraint is that operation local name (e.g. op name) + namespace must be
  unique within a portType.  Note: we did not explicitly call this a QName, 
  since the WSDL use of QName typically implies a uniqueness and
  referenceability properties (think portType Qname) which are not appropriate
  for operations."

  "One of the WSDL 1.2 Spec authors agreed to write up the following
  for next Tuesday, in time for discussion on the WSDL WG telecon next
  Thursday.  The rush on this was based on our request (I mentioned about our
  goal for 02/15 for GS Spec draft).  The components of the write up are as
  follows:"

  "a) add a namespace property to operation (both at the binding and portType
      usage), this includes a footnote to clarify why this is not called a Qname"
  "b) specify the uniqueness constraint in terms of namespace + name
      of the operation within a portType."
  "c) explore removing the namespace property from the soap binding (it is now
      redundant as it would now be part of the operation name)."
  "d) add a "best practice note" for reusable portTypes (eg when one is
      designing a portType, make sure the names are unique within the namespace)."

Issues:

- Are we happy with this?

We were not entirely happy with the need to qualify all operations with namespaces, but the overall feeling was that we 
could live with this improvement compared to the previous state of affairs, e.g. operation names needing to be unique 
for all time. 

- Implementation strategy for Grid Services

   1) Do XML extended schema for gwsdl:portType (including Open Content and extends)
      and gwsdl:service to support extension.

   2) Use Open Content for Service Data with a Service Data namespace (sd).

   3) A note on the issues of overloading and name clashes, unique names within
      a namespace, differentiation of operations with respect to namespace at both
      client and server bindings.
 
Action: Steve T. and Steve G. to make sure that the WSDL group is aware of the OGSI's use of the WSDL 1.2 draft.

Action: Steve G. clarify the relationship between ports and service in the proposed WSDL 1.2 extension - Done See item (
7) below.

3) Contents of the portType Service Data Element.

We had the discussion about whether the service description portType SDE should include only the most derived portType 
or all portTypes explicitly.

Resolved:
    - The maxOccurs="unbounded".
    - This collection MUST be the transitive closure of the portTypes implemented
      by the service, e.g. all portTypes of the most derived portType, subject as always to
      access restrictions.

4) Action Review.

Action: Jeff Frey to draw up a description of how to integrate the 'implicit' verses 'SDE' state dichotomy. Also look 
into other issues of coherency control (#75, #76). - Done

Action: Steve T&G to push on W3C to get what we need (portType extension without breaking encapsulation). Take ownership
. - Done.

Action: Tom Maguire and John R, not being happy with the mutability language, will propose new language reflecting the 
current meaning. - Dropped.

Action: Dave S Faults summary (#42). - Done.

Action: Tom M. provide XML Schema and WSDL for the specification. Dependent on service data and some pointers on WSDL 1.
2 syntax (#35). - Pending

Action: Pete V. to propose a more general solution to the extensibility argument pattern (#34). -...