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

Attendees:

Karl Czajkowski <USC/ISI>
Frank Siebenlist <ANL>
Shel Finkelstein <Sun>
Jeff Frey <IBM>
Steve Graham <IBM>
Bill Horn <IBM>
John Rofrana <IBM>
Andreas Savva <Fujitsu>
Dave Snelling <Fujitsu>
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: Steve G & John R to update Service Data document and integrate the Set service Data Document - Done

Action: Dave S Faults summary. - Pending

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

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

Action: Steve G. and Jeff F. to send new position on topic based notification - Done

Action: Shel will follow-up Events use cases for events and notification - Done.

Resolution: All event like proposals (e.g. from a request for a simple deliver w/ ack based on Service Data through to the full support of topics) were punted. They should be looked at in the OGSA-WG and sent back to us for V1.1 or to other WGs. We will monitor WS activity in the meantime.

The reasons for this decision included the limited time to discuss and reslove what could be a very big time consumer; the number of proposals already on the table plus those from places like DAIS; and that it was 
dependent on a better collective understanding of service Data (which means we can't even start discussing it yet).

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

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. Resolve the Lifetime of GSH question.

Background: GSHs are never recycled. GSRs have variable lifetimes, possibly quite short. Both may contain internal life-
cycle attributes, as the details of each are outside the spec. The gsdl:serviceLocator contains zero or more gsdl:
serviceHandle elements and zero or more gsdl:serviceReference elements. The questions to answer are where do we put life
 time attributes and are the required?

  1- On the gsdl:serviceReference elements
  2- On the gsdl:serviceHandle elements
  3- On the gsdl:serviceLocator container itself

Process: Agree that these are the questions that need to be answered and then answer them.

The process was agreed after clarification that handles and references are put together in the locator (i.e. there is 
not separate structures in the locator for each).

It was noted that 1 and 3 mean different things: (1) refers to the lifetime of the individual references and (3) 
referred to the binding between GSHs and GSRs in the locator. However, life time attributes on 3 was also though to be 
confusing, as some interpreted is as service of GSH lifetime.

Resolution:

There will be no life time attributes on the handle or the locator as a whole.

The goodFrom and goodUntil will be listed as optional attributes on the reference. See bug 37 for...