[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Raw chat log of the 11/6 conf-call
Room information was updated by: Gil
888-967-2253 / 650-607-2253
meeting #: 517378
passcode: 203873
gilbert.pilz: OW!
gilbert.pilz: scribe: gilbert.pilz
gilbert.pilz: meeting is not quorate at this time
gilbert.pilz: topic: agenda
gilbert.pilz: resolution: agenda approved
Sanjay: How do I unmute?
gilbert.pilz: topic: new issues
gilbert.pilz: sanjay: typo in WSRM
Charlie: trying to unmute
gilbert.pilz: charlie: (describes issue)
gilbert.pilz: n the RM spec the exemplar for CloseSequence uses:
<wsrm:LastMsgNumber> wsrm:MessageNumberType </wsrm:LastMsgNumber> ?
But in the pros around it, it has:
/wsrm:CloseSequence/wsrm:LastMessageNumber
Notice the "Msg" vs "Message" difference.
The schema uses "Msg" so I the pros text is incorrect. This should be treated as an errata/typo type of issue.
gilbert.pilz: gil: moves to accept this as an issue
gilbert.pilz: charlies: 2nds
gilbert.pilz: resolution: issue accepted as new issue
gilbert.pilz: ram: considering where we stand in the process, what do we do with these new issues?
gilbert.pilz: charlie: in the text of the issue, Doug targets this as errata
gilbert.pilz: sanjay: Doug was pointing out the trivial nature of the issue
gilbert.pilz: sanjay: simplest route would be to incorporate this as eratta to the CS
gilbert.pilz: ... do another round of CS approval then proceed to OS
gilbert.pilz: ram: wondering about the process of continually re-approving CS's
gilbert.pilz: gil: since we're not quorate, can we do this?
gilbert.pilz: sanjay: you're right, we can't conduct any official business
gilbert.pilz: ram: other editorial issue
gilbert.pilz: A sharp-eyed Oracle developer pointed out to me that lines 709-710 of WS-MC 1.1 [1] contain the URL value:
http://docs.oasis-open.org/ws-rx/wsrm/200702/anonymous?id=550e8400-e29b-11d4-a716-446655440000
Clearly this should read:
http://docs.oasis-open.org/ws-rx/wsmc/200702/anonymous?id=550e8400-e29b-11d4-a716-446655440000
FWIW
[1] http://docs.oasis-open.org/ws-rx/wsmc/200702/wsmc-1.1-spec-cd-01.pdf
gilbert.pilz: topic: review of status on designated cross-references
gilbert.pilz: sanjay: status of WS-SX specs?
gilbert.pilz: ram:
gilbert.pilz: ram: ws-sx has voted to initiate a CS ballot - expected to finish on 11/14
gilbert.pilz: ... what happens when specs are approved as CS's on 11/14?
gilbert.pilz: ... move to member vote some time in Jan
gilbert.pilz: ... how do we proceed along with SX?
gilbert.pilz: sanjay: what happens afters SX specs gain CS?
gilbert.pilz: ... what should we do to proceed with member approval for our specs?
gilbert.pilz: ... as far as SX get's CS approval, that completes our dependencies on the SX specs
gilbert.pilz: ... (assuming their ballots are successful)
gilbert.pilz: ... essentially our specs get CS status at that time
gilbert.pilz: ... should we consider going for OASIS membership vote along with SX?
gilbert.pilz: ... I think that is a good idea
gilbert.pilz: ram: it should be easier to campaign for RX and SX together
gilbert.pilz: ... since we don't have to answer all the cross questions, etc.
gilbert.pilz: sanjay: should save us effort
gilbert.pilz: (ashok joins)
gilbert.pilz: we are now quorate
gilbert.pilz: topic: approval of minutes from 10/9/2008
gilbert.pilz: charlie: moves to approve minutes from 10/9/2008
gilbert.pilz: ram: 2nds
gilbert.pilz: resolution: minutes from 10/9/2008 approved
gilbert.pilz: topic: new issues
gilbert.pilz: gil: moves to accept issue around typo in WS-MC 1.1
gilbert.pilz: ram: 2nds
gilbert.pilz: resolution: issue accepted by UC
gilbert.pilz: charlie: moves to accept Doug's new issue
gilbert.pilz: gil: 2nds
gilbert.pilz: resolution: issue accepted by UC
gilbert.pilz: ram:
gilbert.pilz: ram: one thing we could do (I know we are meeting sometime again in Decemeber - but we may not reach quorum)
gilbert.pilz: ... on this call, is to appprove taking the CS to a member vote
gilbert.pilz: ... all we need to do is get the editor's to prepare the specs and packages
gilbert.pilz: sanjay: there are other things we need to do as well
gilbert.pilz: ... we need to get 3 members to ratify that these specs are implementable, etc.
gilbert.pilz: ram: for us to start the process, we need to agree as a TC that this is what we want to do
gilbert.pilz: ... I looked at the previous ballots
gilbert.pilz: ... and I hand-edited them to something like this:
Ram (Microsoft): Proposed motion for going to member vote:
Approve submission of WS-ReliableMessaging v1.2 Committee Specification to OASIS for approval as an OASIS Standard (pending approval of referenced SX specifications as Committee Specifications):
Do you approve submission of WS-ReliableMessaging 1.2 Committee Specification to OASIS for approval as an OASIS Standard?
This Specification Approval Motion includes a Designated Cross-Reference Change per Section 2.18 of the OASIS TC Process document to the following specifications:
WS-Security Policy 1.3
Expected approval status: Committee Specification, 30 November 2008
http://docs.oasis-open.org/ws-sx/ws-securitypolicy/v1.3/cd/ws-securitypolicy-1.3-spec-cd-01.doc
WS-Trust 1.4
Expected approval status: Committee Specification, 30 November 2008
http://docs.oasis-open.org/ws-sx/ws-trust/v1.4/cd/ws-trust-1.4-spec-cd-01.doc
WS-SecureConversation 1.4
Expected approval status: Committee Specification, 30 November 2008
http://docs.oasis-open.org/ws-sx/ws-secureconversation/v1.4/cd/ws-secureconversation-1.4-cd-01.doc
WS-ReliableMessagingPolicy 1.2 (currently under ballot for CS approval).
http://docs.oasis-open.org/ws-rx/wsrmp/200702/wsrmp-1.2-spec-cd-01.doc
Expected approval status: Committee Specification, 10 September 2008
The TC acknowledges that approval and publication of the specification may be delayed by the Designated Cross-Reference Changes.
http://docs.oasis-open.org/ws-rx/wsrm/200702/wsrm-1.2-spec-cd-01.doc
http://docs.oasis-open.org/ws-rx/wsrm/200702
Approve submission of WS-ReliableMessagingPolicy v1.2 Committee Specification to OASIS for approval as an OASIS Standard (pending approval of referenced SX specifications as Committee Specifications):
Do you approve submission of WS-ReliableMessagingPolicy 1.2 Committee Specification to OASIS for approval as an OASIS Standard?
This Specification Approval Motion includes a Designated Cross-Reference Change per Section 2.18 of the OASIS TC Process document to the following specifications:
WS-Security Policy 1.3
Expected approval status: Committee Specification, 30 November 2008
http://docs.oasis-open.org/ws-sx/ws-securitypolicy/v1.3/cd/ws-securitypolicy-1.3-spec-cd-01.doc
WS-ReliableMessaging 1.2 (currently under ballot for CS approval).
http://docs.oasis-open.org/ws-rx/wsrm/200702/wsrm-1.2-spec-cd-01.doc
Expected approval status: Committee Specification, 10 September 2008
The TC acknowledges that approval and publication of the specification may be delayed by the Designated Cross-Reference Changes.
http://docs.oasis-open.org/ws-rx/wsrmp/200702/wsrmp-1.2-spec-cd-01.doc
http://docs.oasis-open.org/ws-rx/wsrmp/200702
Approve submission of WS-MakeConnection v1.1 Committee Specification to OASIS for approval as an OASIS Standard (pending approval of referenced SX specifications as Committee Specifications):
Do you approve submission of WS-MakeConnection 1.1 Committee Specification to OASIS for approval as an OASIS Standard?
This Specification Approval Motion includes a Designated Cross-Reference Change per Section 2.18 of the OASIS TC Process document to the following specifications:
WS-Security Policy 1.3
Expected approval status: Committee Specification, 30 November 2008
http://docs.oasis-open.org/ws-sx/ws-securitypolicy/v1.3/cd/ws-securitypolicy-1.3-spec-cd-01.doc
WS-Trust 1.4
Expected approval status: Committee Specification, 30 November 2008
http://docs.oasis-open.org/ws-sx/ws-trust/v1.4/cd/ws-trust-1.4-spec-cd-01.doc
WS-SecureConversation 1.4
Expected approval status: Committee Specification, 30 November 2008
http://docs.oasis-open.org/ws-sx/ws-secureconversation/v1.4/cd/ws-secureconversation-1.4-cd-01.doc
WS-ReliableMessaging 1.2 (currently under ballot for CS approval).
http://docs.oasis-open.org/ws-rx/wsrm/200702/wsrm-1.2-spec-cd-01.doc
Expected approval status: Committee Specification, 10 September 2008
WS-ReliableMessagingPolicy 1.2 (currently under ballot for CS approval).
http://docs.oasis-open.org/ws-rx/wsrmp/200702/wsrmp-1.2-spec-cd-01.doc
Expected approval status: Committee Specification, 10 September 2008
The TC acknowledges that approval and publication of the specification may be delayed by the Designated Cross-Reference Changes.
http://docs.oasis-open.org/ws-rx/wsmc/200702/wsmc-1.1-spec-cd-01.doc
http://docs.oasis-open.org/ws-rx/wsmc/200702
gilbert.pilz: ram: there are three parts to it
gilbert.pilz: ram: if we as a TC agree that this is the right thing to do going forward - this clears the road for us to get to a member vote
gilbert.pilz: gil: are you asking us to accept this proposal on this call?
gilbert.pilz: ram: yes, get the TC's approval to proceed to a member vote
gilbert.pilz: sanjay: so the set of events are: 11/14 - SX approves CS, 11/14+ TX TC conducts a vote to ???
gilbert.pilz: ram: what we can do today is to approve a motion to go to member vote pending the SX approval of CS
gilbert.pilz: sanjay: that needs a special majority
gilbert.pilz: ... (reads OASIS process docs)
gilbert.pilz: ram: in that case we need an electronic ballot
gilbert.pilz: sanjay: one thing we could do is wait until SX TC approves their CS
gilbert.pilz: ... on next call (12/4) we can decide to conduct a special majority vote to go to member approval
gilbert.pilz: ... if that starts the following week, we could get a package sumitted to OASIS staff by 12/20
gilbert.pilz: ... deferring until 12/4 might be a little late
gilbert.pilz: ... are you sure SX intends to go to member vote in January?
gilbert.pilz: ram: yes, later January
gilbert.pilz: ... OASIS process requires that member votes happen during later period of the month
gilbert.pilz: ... if we miss that window, then we have to target 2/15+
gilbert.pilz: sanjay: OASIS staff submits package to membership at the begining of the month
gilbert.pilz: ... first half of month is used by the membership to review the material
gilbert.pilz: ... second half of the month is used to vote
gilbert.pilz: ... need to submit package by 15th of the previous month
gilbert.pilz: ram: we can take the following baby steps
gilbert.pilz: ... we need three statements of use (1)
gilbert.pilz: ... then we are blocked on SX until 11/14
gilbert.pilz: ... once we get past these two we can proceed on preparing packages for OASIS
gilbert.pilz: sanjay: maybe we should think about having a call after 11/4
gilbert.pilz: ... maybe a call on 11/20?
gilbert.pilz: gil: what's so bad about losing a month?
Sanjay: Gil is worried about missing the RX calls http://webconf.soaphub.org/conf/smile.gif
gilbert.pilz: ram: certainly there is no hurry here - we can proceed at our own pace
gilbert.pilz: ... in the past I remember having to beat the bushes to get OASIS members to vote
gilbert.pilz: ... we need to band together with SX to get this to happen
gilbert.pilz: ... much easier to lobby the same people for multiple votes
gilbert.pilz: tom: questions the feasability of expecting OASIS staff to do anything over holidays
gilbert.pilz: +1
gilbert.pilz: sanjay: if we have a call on 11/20 we'll have good visibility of what SX is planning on doing
gilbert.pilz: ... anybody opposed to next concall on 11/20
gilbert.pilz: gil: I probably won't be able to attend (not that anyone cares)
gilbert.pilz: sanjay: let's have the call on 11/20 and see what we can do
gilbert.pilz: resolution: next concall on 11/20
gilbert.pilz: sanjay: can we dispose of the two new issues today?
Ram (Microsoft): Issues list: http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssues.xml
gilbert.pilz: topic: i164 (typo in WS-MC 1.1 example)
gilbert.pilz: gil: moves to resolve i164 by correcting typo
gilbert.pilz: charlies: 2nds
gilbert.pilz: resolution: motion to resolve i164 passes by UC
gilbert.pilz: topic: i165 (typo in WSRM)
gilbert.pilz: charlie: moves to resolve i165 by correcting typo
gilbert.pilz: gil: 2nds
gilbert.pilz: resolution: motion to resolve i165 passes by UC
gilbert.pilz: topic: item 6 (other business)
gilbert.pilz: sanjay: request editors to be ready with a draft that addresses i164, i165 by next meeting
gilbert.pilz: ram: we need statements of use from implementers
gilbert.pilz: ... who are the implmeneters that are willing to produce statements of use
gilbert.pilz: sanjay: urge implementers to publicly make statements of use
gilbert.pilz: ram: what would the next draft be?
gilbert.pilz: sanjay: it'll turn into a CD
gilbert.pilz: ... call draft with fixed typos next CD
gilbert.pilz: ... use these as next CS and submit them for the membership vote
gilbert.pilz: (have to do - can we discuss this on the mailing list?)
gilbert.pilz: s/do/go/
Charlie: i need to drop off too
Sanjay: The timeline for submission to OASIS vote would not be affected if we incorporated the resolution of the issues 164 and 165 and conducted a single ballot for - a> approve the new drafts as CS and b> approve submission of the CS draft for OS vote.
Sanjay: Next call - Nov 20th
Sanjay: Next call - Nov 20th
Sanjay: Mtg adjourned at 2:06 PM Pacific Time
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
