Minutes of the Eleventh OGSI-WG Teleconference
11/Dec/2002 @ 21:30-23:00 GMT

Attendees:

Karl Czajkowski <USC/ISI>
Steve Graham <IBM>
Andreas Savva <Fujitsu>
Dave Snelling <Fujitsu>
Steve Teucke <ANL>
Pete Vanderbilt <NASA>

1. Approval of Minutes - OK

2. Review actions

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. - Pending

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

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

Action: Dave S Faults summary. - Pending

Action: Steve Graham and Pete to drive the creation of an XML Schema for the specification (#35). Dependent on service data and some pointers on WSDL 1.2 syntax. - Pending

Action: Dave Snelling and Andrew Grimshaw to look at requirements and solutions for pull like semantics. - Pending

Action: Dave S to put a proposition for registration portType, together
with exact text. - Pending

Action: Andrew G to write a document describing the options for reslover behavior. - Pending

Action: Steve Graham to craft language for recommendations to developers for use of resolvers (#17) - Pending

Action: Steve T. Email list of proposed resolve->verified bugs - Done.

Action: Pete V. and Steve T. to propose a more general solution to the extensibility argument pattern, see bug 34. - 
Pending

Action: Pete V. to create XML schema for locator elements, see bug 37 - Done.

3.  Workgroup Interim meeting:

Planned for Jan. 22-24 2003. Any one wishing to host should contact STeve T before the end of the week, or we will 
default to Chicago. 

4. Close loose ends on mutability and modifiability:

>From the list Peter V. wrote:

------
Second, "setOnce" implies that there may be a state in which the SDE
is not initialized.  Presumably a settable SDE is present to affect or
control the service.  But if it's not set, then we have a service
that's not completely initialized.  What does the service do if it
gets a request before the SDE is set?  What happens if the SDE is
referenced before it is set?  Is there a standard representation for
an uninitialized SDE?

In my opinion, this is an unnecessary complication.  If the SDE is not
modifiable, the service should set the value at service-creation time.
If the SDE should be supplied by the client, make it a parameter to
the factory's createService method.  In both cases, the service is
fully ready to go immediately after creation and none of these
complications come into play.
-------

The discussion covered the question of wether an SDE could remain unset for a time or had to be present when the service
 started. One proposal was to drop the setOnce concept and let it be covered by minoccuss and lifetime management. 
However, it was felt that the setOnce concept was rather useful, but that the model was cleaner with the above proposal.
 therefore:

Resolved: setOnce SDE MUST be initialized before the service is accessible to clients.

Therefore the table of options is now:

Mutability     Modifiability     Comments
----------     -------------     --------
constant       false             Appears in the WSDL only.
setOnce        false             Not in the WSDL, exists as soon as the service exists, better name?
append         true              Can be used with minoccurs=0 maxoccurs =1 to do client side "setOnce" semantics.
append         false             As before
mutable        true              As before
mutable        false             As before


5. Service data 

We had a short discussion of the Service Data document under preparation by Steve G. and company. There are several 
issues that will arise around this document. These were highlighted briefly in discussions. To summarize:

- Generally agreed that...