Minutes for twentysecond OGSI-WG Teleconference
February 12, 2003 @ 16:30 - 18:30 GMT

Pete V.
Dave S.
Steve T.
Steve G.
Karl C.


1) Approve minutes of February 5th, 7th, 10th, 11th Teleconferences - Skipped.

2) Consolidated Actions Review - Skipped.

Action: ---: Feb 12: Steve T: To check if Incorrectvalue is the right fault name in SetServiceData operation.

Action: ---: Feb 12: Steve T: Remove fault hierarchy from Spec. Deferred to V2.

Action:  49: Feb 13: Tom M: Make PT extensions explicit in the wsdl.

Action: 86: Feb 12: Steve T: Check that our service data elements that need coherency semantics, e.g. non-static/non-
constant, have them specified.

Action: ---: Feb 11: Steve G: Add to the spec as a minOccurs=0, (Including explanatory text) next time with the pen [
Done by DS, Feb 11 draft].

Action: ---: Feb 12: Steve G: To answer issues around SOAP 1.2 requirement for use of WSDL 1.2.

Action: ---: Feb 12: Steve T: To talk to Thomas about the tooling issue in more detail.

Action: ---: Feb 12: Steve T: To produce a GWSDL Draft.
Action: ---: Feb 05: Steve G: Draft of GWSDL definitions (See Section 5) - moved to Steve T.

Action: ---: Feb 11: ---- --: Discussion of fault architecture (See Section 7.7)

Action:  55: Feb 11: Shel  F: Provide feedback on timestamp model in OASIS, we plan to punt to v1.1

Action:  35: Feb 06: Steve T: Push Tom M. and Thomas S. to provide XML Schema and WSDL for the specification

Action: 17 & 82: --- --: Steve G: Finish the handle resolver protocol discussion (See Section 10)

Action: ---: --- --: Steve G: Create non-normative text for the service data section describing forward looking solutions to query processing via XPath/XQuery. (Sections 9.2.1.2/3, 6.2.1, 9.2.3)

Action: 93, 94: --- --: Steve T: Check and fix these bugzilla items

Action: Steve T: Substitute service data description with service data declaration.

Action: Steve T: some types use "ServiceType", and some use "GridServiceType".  Make these consistent

Action:  19: --- --: Steve T: Check as this bug has been resolved already. May just need to remove highlighting. (Section 12.2.1)

Action: ---: --- --: Steve T: Make sure that the WSDL group is aware of the OGSI's use of the WSDL 1.2 draft. Use the gwsdl draft to package notification.

Action:  42: --- --: ----- -: Andrea & Steve T & Dave: Complete the faults for all operations in all portTypes (Action on Feb 5).

Action:  67: --- --: ----- -: Check that draft schema support optional parameters, e.g. empty extensibility, See Section 9, and resolved bug 67.  Options: Define a <nil> element that can go into a ##any, or use substitution group, or use XSD nillable


3) Review Faults Section

Meta Issue:

From Steve T: The biggest comment/issue that I see is that our model of having each fault
              reflected in a WSDL fault element in the operation declaration won't work
              for extensible operations such as FindServiceData. Should we go back to having
              just a single fault in the WSDL operation of type GridServiceFaultType, which
              is extended as necessary?

F2F Strategy was to include a WSDL part with the same name as the type for each subtype of GridServiceFault.

Problem: A subtype adding faults to existing operations. This creates two classes of fault. Those that have WSDL parts 
and those that don't.

The F2F advantage was direct tooling from the WSDL parts to Java exceptions for example.

Resolved: The WSDL for operations will contain fault elements for all faults listed for the operation. When throwing a 
subtype of a portType specified fault, use a derived type and use an xsitype to indicate the actual fault type. Tooling 
could either catch the fault included in the WSDL part or inspect the xsitype information and throw the more refined 
fault subtype.

Action: ---: Feb 13: Steve T: Check with Thomas about tooling impact.

Resolved: We confirmed that all operations can throw GridServiceFault.

Resolved: We confirmed the...