Preliminary Minutes For Friday f2f

[Tom Rutt <tom@coastin.com>]

The prelim minutes for friday f2f are posted.

The final minutes will be posted later today to the web site.

-- 
----------------------------------------------------
Tom Rutt		email: tom@coastin.com; trutt@fsw.fujitsu.com
Tel: +1 732 801 5744          Fax: +1 732 774 5133

Title: Corrections to WS-Relibility working Draft

 

Preliminary Minutes F2F Friday

 

11   Corrections to Working Drafts

11.2Corrections to WS-Reliability working Draft .51

 

Change:

“

If the MessageOrder element appears in the message sent, the receiver of the message is REQUIRED to make this message available to the application layer only after all messages with lower sequence number with the same GroupId have been made available to the application.

“

to:

“

If the MessageOrder SequenceNumber element appears in the message sent, the receiver of the message is REQUIRED to make this message available to the application layer only after all messages with lower sequence number with the same GroupId have been made available to the application.

 

Change:

“

1.1        RefToSequenceNo Element

The RefToGroupId element is a REQUIRED element for Acknowledgment message or Fault message when the original message was delivered with Guranteed Message Ordering.

“

to:

“

1.2        RefToSequenceNo Element

The RefToGroupId RefToSequenceNo element is a REQUIRED element for Acknowledgment message or Fault message when the original message was delivered with Guaranteed Message Ordering.

“

 

Add new figure in Section 3 to illustrate the header blocks.

 

11.3Corrections to Requirements V0.9

The requirement:

R3.6 The Specification must support the Polling RM-Reply Pattern for one-way WSDL 1.1 operations.

 

Needs to be changed to:

R3.6 The Specification must support the Polling RM-Reply Pattern for one-way and request-response WSDL 1.1 operations.

 

12   Discussion for Finalizing WSRM Deliverables

12.2Requirements

Question: are we going to take the requirements document thru the formal OASIS approval process.

 

Doug B: we can deliver it by letting people see it, but it should not be put out for formal OASIS Standard approval.

 

It was agreed that the requirements working draft will remain in the documents folder.  It will be changed to reflect resolutions of further TC comments on the Requirements.

 

12.3WS-Reliability Spec

This will go for formal OASIS approval as a standard.

 

From the TC process:

Approval of a Committee Draft

 

Upon completion of a specification the TC may approve the work as a Committee Draft. The approval of a Committee Draft shall require at least 2/3 of the total membership of a TC voting to approve and no more than 1/4 voting to disapprove.

 

OASIS TC Administration must be notified at the completion of any ballot to approve a Committee Draft, regardless of the outcome of the ballot.

 

The name of a Committee Draft may not include any trademarks or service marks not owned by OASIS. The Committee Draft must use the OASIS-approved document templates and naming, and must include the OASIS copyright.

 

(b). Approval of an OASIS Standard

 

Public Review

 

Before the TC can submit its Committee Draft to OASIS membership for review and approval as an OASIS Standard, the TC must conduct a public review of the work. The decision by the TC to submit the work for public review requires a majority vote. The review must be announced by the TC Administrator on the OASIS members mail list and optionally on other public mail lists. Review must take place for a minimum of 30 days, during which time no changes may be made to the document. Comments must be collected via the TC's archived public comment facility. The TC must record the comments received as well as the resolution of those comments.

 

The TC may conduct any number of additional review cycles (i.e. collecting comments, making edits to the specification, sending out a revised version for review again, etc.) before deciding that the review is complete. If substantive changes are made to the specification after the start of the public review then the TC should conduct another review cycle. After the conclusion of the review and final changes to the document, the TC must re-approve the work as a Committee Draft before submitting it to OASIS.

 

Member Approval

 

A TC may recommend that the Committee Draft be made an OASIS Standard.

 

Steps for approval of WS-Reliability as OASIS standard:

a) TC approves a document as Committee draft.

b) Public review of Committee Draft (30 days)

c) Resolve public review comments to produce second Committee Draft (30 days)

d) Submit Committee Draft for Member approval

 

Assume there is a meeting at end of October 27 - 29.  We could have the output of the October meeting is one step before TC vote for committee draft.

Teleconferences: Nov 11, 18

 

Another F2F in early January.

 

Potential timeline:

• Nov 3: Candidate Committee Draft for TC internal Comments.
• Nov 20:  second Candidate Committee draft for TC vote
• Dec 1 – Begin Public Review - approved Committee Draft
• Jan 1 – Public Review period completed.
• Feb 1 – Submit approved Second Committee draft to OASIS for member approval.

 

Step a) target:

13   Teleconference

13.2Roll

 

First Name	Last Name	Email	Role	Company
Pramila	Mullan	pramila.mullan@rd.francetelecom.com	Member	France Telecom
Tom	Rutt	tom@coastin.com	TC Chair	Fujitsu
Robert	Freund	bob.freund@hitachisoftware.com	Member	Hitachi
Eisaku	Nishiyama	nishiy_e@itg.hitachi.co.jp	Member	Hitachi
Nobuyuki	Yamamoto	no_yama@bisd.hitachi.co.jp	Member	Hitachi
Ben	Bloch	ben_b54@hotmail.com	Member	Individual
Dock	Allen	Dock@mitre.org	Member	Mitre Corporation
Junichi	Tatemura	tatemura@ccrl.sj.nec.com	Member	NEC Corporation
Alan	Weissberger	ajwdct@technologist.com	Member	NEC Corporation
Magdolna	Gerendai	magdolna.gerendai@nokia.com	Member	Nokia
Szabolcs	Payrits	Szabolcs.Payrits@nokia.com	Secretary	Nokia
Sunil	Kunisetty	Sunil.Kunisetty@oracle.com	Member	Oracle
jeff	mischkinsky	jeff.mischkinsky@oracle.com	Member	Oracle
marc	goodner	marc.andrue.goodner@sap.com	Secretary	SAP
Doug	Bunting	doug.bunting@Sun.com	Secretary	Sun Microsystems
Chi-Yuen	Ng	cyng@csis.hku.hk	Member	Univ of Hong Kong
Prasad	Yendluri	pyendluri@webmethods.com	Member	webMethods, Inc.

 

13.3Voting

 

Accept Minutes of 8/26/2003 WSRM Teleconf.

 Sunil moved, Dock seconds. No opposition, motion passed.

 

Accept Pending resolutions on requirements:

Rel 56,

 Doug moved, Jeff M seconded.  No opposition, motion passed.

 

Accept Pending resolutions on Spec issues:

Rel 27, 28, 37, 40, 41, 58, 81, 88

 Sunil Moved, Bob seconded.  No opposition, motion passed.

 

Progress the Requirements V0.9 to Working Draft status (applying correction from minutes).

 Payrits moved, Magdolna seconded. .   No opposition to approval, motion passed.

 

Progress the WS-Reliability V.51 to Working Draft status (applying correction from minutes).

 Jeff moved, Bob seconded.  No opposition, motion passed.

 

Make all our TC documents  available to the public.

 Jeff moved, Dock seconded.  No opposition, motion passed.

 

13.4Formation of TC Subgroups

There was general agreement from Thursday to work on a charter for a future subcommittee.

 

The purposes of a the new TC subgroup would be, to:

• Provide a mechanism for interoperability testing across different implementers of the specification
• Provide concrete specific feedback to the TC regarding implementation experience with the specification.
• Provide promotion/PR capability for the realization of this specification.
• Provide test tool standards, specifications, and test case definitions, for those choosing to participate in interoperability testing of WSRM.

 

Doug clarified that a subcommittee would get extra page on web site, gets its own list and get it own chair.

 

Jacques Durand, or Bob Freund,. should be contacted if a member wants to participate in forming the charter.

 

Bob Freund stated that this should be part of the TC.  The key reason to make it a subgroup of the TC is that this gives IPR protection in operating as part of a standards body.  They would enjoy operating under the umbrella of the OASIS process.

 

Bob Freund stated that this Subgroup would give a way to encourage wider adoption.

 

Doug B would like the discussion for this to be on our public list.

 

Bob Freund agreed to have all charter discussions to be on the WSRM List.

13.5Future meeting planning

 

To meet the roadmap schedule there was agreement to have a f2f Meeting during the last week of October.

 

Agreed to dates October 28 39, 30.  In the CA bay area.  Will be hosted by France telecom research or sap.

 

Agreed to Weekly teleconf thru November and December, and first week of January.

 

Take off Dec 23 and 30.

 

Have January F2F in Europe (UK or Budapest) on Jan 12, 13 14.

 

Face to Face on January 12 thru 14.  Potentially in Budapest.

 

Tom Rutt thanked Dock for the great hosting arrangements, and the editors for their great work during the week.

 

The meeting adjourned at 11:05 AM EDT.