OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ws-caf message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [With Attendees] Re: [ws-caf] Minutes from Monday Call (2004/3/29)


Resent, with attendees included.

Joe

Chiusano Joseph wrote:
> 
> Please find the minutes of our Monday call below.
> --
> Kind Regards,
> Joseph Chiusano
> Associate
> Booz | Allen | Hamilton
> 
>   ------------------------------------------------------------------------
> WS-CAF Phone Conference  March 29, 2004
> 
> 1. Agenda review
> 
> 2. roll call/ member changes
> 
> 3. assign Scribe
> 
>   * Joseph Chiusano selected to scribe.
> 
> 4. Actions
> 
> Action: Eric to update FAQ based on f2f comments
> 
>   * In process.
> 
> ACTION: editors to draft a model diagram from which the normative specification is derived.
> 
>   * Done.
> 
>   * We also discussed 2 previous actions:
>        - Automatic update of Bugzilla: In process (Mark Little)
>        - Is Bugzilla account creation restricted to WS-CAF members: Closed (Mark Little sent e-mail with instructions)
> 
> 5. Minutes
> 
>   ratify minutes of March 15
> 
>   * Correction: This was actually March 8th (there was no meeting on March 15th)
>   * Minutes were approved.
> 
> 6. Review and approve model diagram and text
> 
>   * Discussion centered around the recently released WS-Context UML diagram and the subsequent discussion around context-by-value
> 
>   * Greg P. summarized:
>        - TC discussed model and diagram on 3/21 call
>        - A series of questions were raised about the material that was published to the list – questions went out to list, with multiple responses
>        - One response from Peter F. related to the continuation of the discussion of  context-by-value vs. context-by-reference, as well as a general question about
>           what it means to have multiple ALSs associated with a particular protocol and how those ALSs manage dependencies among themselves
>        - There was not much followup discussion on our list – currently pursuing this issue in Editor’s group to massage the model description to account for this issue
>        - Editor's group hopes to have something out to TC later this week to clarify questions and push discussion along
> 
>   * Alastair entered, and inquired about the discussion of the parent/child relationship issue – was there any discussion of this on the call yet?
>        - No discussion yet - but discussed now
>        - It was not clear from the WS-Context model text what the intent was in terms of parent/child relationship and context – what is point of having a context
>          wrapper in first place?
>        - Editor's group has had a lot of discussion on this [see note above about “push discussion along”]
> 
>   * We are coming close to convergence on this issue
> 
>   * Eric thanked to everyone for their inputs and comments so far
> 
> 7. Review and discuss document schedule
> 
>   * Eric described how at the Jan F2F, we wanted to have committee draft by end of April
>        - This is one month from now
>        - This includes spec review and closing outstanding issues at the next F2F (April 28th and 29th); could possibly have draft out a few days later
> 
>   * We should have a draft published officially in advance of a meeting, to give folks time to review; Eric recommended this being done by April 21st, one week
>      in advance of the F2F
>        - We should also have a call before draft is published to discuss any outstanding issues
> 
>   * Doug expressed that we should focus on a draft version as input for a meeting; that is, to make it as good as possible for the meeting, whether or not it will
>      become a committee draft
>        - Others liked this suggestion
>        - We would then have a separate discussion on the committee draft-“worthiness”
>       - We could discuss the draft on the next call (April 12th)
> 
> 8. Review plan for F2F week of April 27
> 
>   * Eric asked: What else do we need to do in addition to document review?
>        - Some possibilities:
>            > Revisit roadmap for other specs
>            > Revisit plans for interop demo
>            > Liaisons with other groups
>            > Meetings with other groups
> 
>   * The document, of course, is top priority
> 
>   * Most TC members will attend the F2F
> 
>   * Martin pointed out that we might have a quorum problem, as some will be floating between meetings
>        - Perhaps we can advertise certain time slots in which we will need votes
> 
>   * Eric will set up a Kavi ballot for attendance
> 
> 9. Update on Issues
> 
>   * This is regarding the Bugzilla issuesthat were voted on and accepted
> 
>   * Mark reported:
>       - All schema updates are done – will be checked in to CVS repository
>       - Editors have made document updates – will merge 3 copies of document into one
>       -All issues will then be marked “resolved”
> 
>   * Issue #7 – will not be changed
> 
>   * Lots of editorial issues (spelling errors, etc.)
> 
>   * All others issues depend on the model
> 
> 10. AOB
> 
>   * Main priority for editors is to get the model out asap
>       - May possibly conduct an ad hoc call to discuss the model; if a number of substantive issues remain, we will schedule a call in which we can vote on issues
> 
>   * Next meeting will be April 12th (conference call)
>       - There was concern expressed from the European members that they may not be able to attend as April 12th is Easter Monday
>       - The TC explored the possibility of other dates/after during that week, but no informal agreement could be reached
>       - A motion was made to hold the call on April 12th, and it was voted on
>            > Voting results: 11 yes, 4 no
> 
>   * The subject of dialin access for the F2F was discussed
>       - A phone is very expensive, and therefore has not been requested
>       - We might see if someone can volunteer their cell air time, if they have a speakerphone capability
> 
>   * Someone needs to bring a projector for the F2F - otherwise we will have to pay
> 
> Meeting adjourned.

-- 
Kind Regards,
Joseph Chiusano
Associate
Booz | Allen | Hamilton
WS-CAF Phone Conference  March 29, 2004

Attendees:

David Ingham Arjuna Technologies Limited 
Mark Little  Arjuna Technologies Limited 
Joseph Chiusano  Booz Allen Hamilton 
Tony Fletcher  Choreology Ltd 
Peter Furniss  Choreology Ltd 
Alastair Green  Choreology Ltd 
Robert Haugen  Choreology Ltd 
Dale Moberg  Cyclone Commerce 
Krishna Cheemalamarri  Fujitsu 
Bryan Murray  Hewlett-Packard 
Ben Bloch  Individual 
John Fuller  Individual 
Bill Pope  Individual 
Eric Newcomer  IONA 
Martin Chapman  Oracle 
Simeon Greene  Oracle 
jeff mischkinsky Oracle 
Greg Pavlik  Oracle 
Doug Bunting  Sun Microsystems 
Ramesh Nagappan  Sun Microsystems 
Jan Alexander  Systinet 

1. Agenda review

2. roll call/ member changes
   
3. assign Scribe

  * Joseph Chiusano selected to scribe.

4. Actions

Action: Eric to update FAQ based on f2f comments

  * In process.

ACTION: editors to draft a model diagram from which the normative specification is derived. 

  * Done.

  * We also discussed 2 previous actions:
       - Automatic update of Bugzilla: In process (Mark Little)
       - Is Bugzilla account creation restricted to WS-CAF members: Closed (Mark Little sent e-mail with instructions)

5. Minutes

  ratify minutes of March 15 

  * Correction: This was actually March 8th (there was no meeting on March 15th)
  * Minutes were approved.

6. Review and approve model diagram and text

  * Discussion centered around the recently released WS-Context UML diagram and the subsequent discussion around context-by-value

  * Greg P. summarized:
       - TC discussed model and diagram on 3/21 call
       - A series of questions were raised about the material that was published to the list – questions went out to list, with multiple responses
       - One response from Peter F. related to the continuation of the discussion of  context-by-value vs. context-by-reference, as well as a general question about 
          what it means to have multiple ALSs associated with a particular protocol and how those ALSs manage dependencies among themselves
       - There was not much followup discussion on our list – currently pursuing this issue in Editor’s group to massage the model description to account for this issue
       - Editor's group hopes to have something out to TC later this week to clarify questions and push discussion along

  * Alastair entered, and inquired about the discussion of the parent/child relationship issue – was there any discussion of this on the call yet? 
       - No discussion yet - but discussed now
       - It was not clear from the WS-Context model text what the intent was in terms of parent/child relationship and context – what is point of having a context 
         wrapper in first place?
       - Editor's group has had a lot of discussion on this [see note above about “push discussion along”]

  * We are coming close to convergence on this issue

  * Eric thanked to everyone for their inputs and comments so far

7. Review and discuss document schedule

  * Eric described how at the Jan F2F, we wanted to have committee draft by end of April 
       - This is one month from now
       - This includes spec review and closing outstanding issues at the next F2F (April 28th and 29th); could possibly have draft out a few days later

  * We should have a draft published officially in advance of a meeting, to give folks time to review; Eric recommended this being done by April 21st, one week 
     in advance of the F2F
       - We should also have a call before draft is published to discuss any outstanding issues

  * Doug expressed that we should focus on a draft version as input for a meeting; that is, to make it as good as possible for the meeting, whether or not it will 
     become a committee draft 
       - Others liked this suggestion
       - We would then have a separate discussion on the committee draft-“worthiness” 
      - We could discuss the draft on the next call (April 12th) 

8. Review plan for F2F week of April 27

  * Eric asked: What else do we need to do in addition to document review?
       - Some possibilities:
           > Revisit roadmap for other specs
           > Revisit plans for interop demo
           > Liaisons with other groups
           > Meetings with other groups

  * The document, of course, is top priority

  * Most TC members will attend the F2F

  * Martin pointed out that we might have a quorum problem, as some will be floating between meetings
       - Perhaps we can advertise certain time slots in which we will need votes

  * Eric will set up a Kavi ballot for attendance

9. Update on Issues

  * This is regarding the Bugzilla issuesthat were voted on and accepted

  * Mark reported:
      - All schema updates are done – will be checked in to CVS repository
      - Editors have made document updates – will merge 3 copies of document into one
      -All issues will then be marked “resolved”

  * Issue #7 – will not be changed

  * Lots of editorial issues (spelling errors, etc.)

  * All others issues depend on the model

10. AOB

  * Main priority for editors is to get the model out asap
      - May possibly conduct an ad hoc call to discuss the model; if a number of substantive issues remain, we will schedule a call in which we can vote on issues

  * Next meeting will be April 12th (conference call)
      - There was concern expressed from the European members that they may not be able to attend as April 12th is Easter Monday
      - The TC explored the possibility of other dates/after during that week, but no informal agreement could be reached
      - A motion was made to hold the call on April 12th, and it was voted on
           > Voting results: 11 yes, 4 no

  * The subject of dialin access for the F2F was discussed
      - A phone is very expensive, and therefore has not been requested
      - We might see if someone can volunteer their cell air time, if they have a speakerphone capability

  * Someone needs to bring a projector for the F2F - otherwise we will have to pay

Meeting adjourned.



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]