This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/go/projects.ogsi-wg/discussion.meeting_notes.2002_11_20_telecon at Sun, 06 Nov 2022 15:21:18 GMT SourceForge : Post

Project Home

Tracker

Documents

Tasks

Source Code

Discussions

File Releases

Wiki

Project Admin
Project: OGSI-WG     Discussion > Meeting Notes > 2002-11-20 TELECON > List of Posts
Forum Topic - 2002-11-20 TELECON: (1 Item)
View:  as 
 
 
2002-11-20 TELECON
Minutes of the Eleventh OGSI-WG Teleconference
20/Nov/2002 @ 21:30-23:00 GMT

Attendees:

Tim Bank <IBM>
Karl Czajkowski <USC/ISI>
Shel Finkelstein <Sun>
Bill Horn <IBM>
John Rofrana <IBM>
Andreas Savva <Fujitsu>
Dave Snelling <Fujitsu>
Steve Tuecke <ANL>
Pete Vanderbilt <NASA>

---------------------

1. Approval of Minutes

Rofrano didn't recall "Rejected: Add a delete operation. It will remain as proposed."  Will leave the delete operation 
in his latest proposal.  We can remove later as we evaluate the updated proposal.

---------------------

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: Pete to go through the SDEs in the spec to see if these changes have any gotchas.
  Done: Emailed results the list.  There were some gotchas.  Follow-up list.

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

Action: Dave S Faults summary. - Pending

Action: Dave S to write up a proposal
  Done (not sure what this is)

Action: Steve Graham and Pete to drive the creation of an XML Schema for the specification (#35) - Pending

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

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

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

Action: All to post use cases for Notification/Events to the list.
  Done.

Action: Keith to post pointers to the Python implementation.
  Done.

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

Action John Rofrano and Ellen Stokes will propose a setServiceDataByName(s) text.
Also by DB style Update if possible. Done, but reissued request for a new draft
following discussions on Nov 6th.

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

Action: Steve T. publish spec and Resloved/Fixed bug numbers.
  Done.

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

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

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


---------------------

3. Bugzilla sweep

Bug 5: Reject (resolve, wontfix)

This is out of bounds of ogsi.  This is either a property of the service implementation, or is a language/domain 
specific extension to the base factory functionality.

Bug 17: Already an action

Bug 19: Resolve, later

Resolution:

  Change terminationTime input to be the <terminationTime> element, containing both the
      before and after values, to be initial values to the instance.
  Keep ServiceParameters input
  Keep ServiceLocator output
  Change CurrentTerminationTime output to also be a <terminationTime> element.
  Keep ServiceTimestamp to be consistent with setTermination* operation.  Rename to
      include the word "Current", to maintain symmetry with the setTermination* operations
  Remove MaximumExtension.
  Keep ExtensibilityOutput (but perhaps rename to be more consistent with input parameter name)

Bug 30, 31: Leave open

Bug 34: Leave open

Rename to: How to specify choices for extensibility arguments to operations

Do we have the right model for these operation templates?
To give more complete specifications, we start duplicating WSDL...
View Full Message

 
 


The Open Grid Forum Contact Webmaster | Report a problem | GridForge Help
This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/go/projects.ogsi-wg/discussion.meeting_notes.2002_11_20_telecon at Sun, 06 Nov 2022 15:21:18 GMT