[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [ws-rx] Designated Cross References
Paul, I agree, the difference is subtle but quite important. The DCR gives us the capability to update now. This will ensure the WS-RX set used for the final ballot will point to CS version of WS-SX specifications. More importantly, it mitigates any chance of comments or swaying of votes. We as a WS-RX TC may understand the mechanics oblivious to member voting entities. If the specification used for the final vote does not have the CS WS-SX set of references, there is a chance some members may vote NO during the final ballot, since they may be concerned that the specification is pointing to editors' drafts of the WS-SX set. I'd be cautious in pursuing other than Option #1. Thanks. -----Original Message----- From: Paul Fremantle [mailto:paul@wso2.com] Sent: Saturday, July 26, 2008 3:59 AM To: Monica Martin Cc: Patil, Sanjay; wsrx; Ram Jeyaraman Subject: Re: [ws-rx] Designated Cross References Monica Doesn't the DCR guarantee that the references will be updated in time? In effect we are asking Members to vote on "the RX spec with the references eventually updated", and the guarantee that the RX spec won't become OS until such time as the references are updated. This seems analogous to the sort of conditional ballots we do quite regularly like this one: http://www.oasis-open.org/apps/org/workgroup/ws-rx/ballot.php?id=1384 Paul Monica Martin wrote: > Everyone, > Option #1 allows us to update the references at Committee Specification stage and prior to a Member Vote (MV). Otherwise, we could enter the MV with WS-SX editors' draft references. This could raise concerns, result in comments, or influence votes for OASIS Standard. I suggest we take the safer bet with Option #1. > > Regards. > Monica J. Martin > Microsoft Corporation > > -----Original Message----- > From: Paul Fremantle [mailto:paul@wso2.com] > Sent: Wednesday, July 23, 2008 9:04 AM > To: Patil, Sanjay > Cc: wsrx > Subject: Re: [ws-rx] Designated Cross References > > Sanjay > > I'm afraid that I didn't understand your point at the time! > I agree option 2 seems more intelligent. > > Paul > > Patil, Sanjay wrote: >> Option 2) makes a lot of sense to me (I tried to point this out on our >> last conf-call). OS is a terminal stage and deferring the DCR to OS >> leaves us with more independence in progressing our TC's specs through >> other stages (CS, and possibly another CD, etc) as and when we want. >> >> -- Sanjay >> >>> -----Original Message----- >>> From: Paul Fremantle [mailto:paul@wso2.com] >>> Sent: Wednesday, Jul 23, 2008 8:31 AM >>> To: wsrx >>> Subject: [ws-rx] Designated Cross References >>> >>> Folks, >>> >>> Our TC administrator has pointed out that there are two options for >>> using the "designated cross references" to the SX committee. >>> >>> 1) We do a DCR to SX it at this stage (CS), and our TC then >>> waits until >>> the SX TC gets to CS. >>> >>> 2) We do NOT do a DCR to SX a this stage (CS), which means >>> we get to CS >>> almost immediately. Then we do an OASIS Standard Vote in >>> the next cycle >>> and do the DCR to SX at that stage instead. That means our >>> specs go out >>> for vote to the OASIS membership and we are effectively >>> done. Once the >>> SX specs become OASIS Standard then we also become OASIS Standard. >>> >>> Effectively, what Mary is saying is that we can finish our >>> work earlier >>> by delaying the DCR-to-SX until the OASIS Standard vote. >>> >>> This seems to make sense to me, and was something I hadn't >>> considered, >>> so before we start the CS vote I wanted the TC to comment. >>> >>> Paul >>> >>> PS it seems like the WSTX TC is going through the same >>> decision process >>> at this point. >>> >>> -- >>> Paul Fremantle >>> CTO and Co-Founder, WSO2 >>> OASIS WS-RX TC Co-chair >>> VP, Apache Synapse >>> >>> Office: +44 844 484 8143 >>> Cell: +44 798 447 4618 >>> >>> blog: http://pzf.fremantle.org >>> paul@wso2.com >>> >>> "Oxygenating the Web Service Platform", www.wso2.com >>> >>> --------------------------------------------------------------------- >>> To unsubscribe from this mail list, you must leave the OASIS TC that >>> generates this mail. Follow this link to all your TCs in OASIS at: >>> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgr >>> oups.php >>> >>> >> --------------------------------------------------------------------- >> To unsubscribe from this mail list, you must leave the OASIS TC that >> generates this mail. Follow this link to all your TCs in OASIS at: >> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php >> >> > > -- > Paul Fremantle > CTO and Co-Founder, WSO2 > OASIS WS-RX TC Co-chair > VP, Apache Synapse > > Office: +44 844 484 8143 > Cell: +44 798 447 4618 > > blog: http://pzf.fremantle.org > paul@wso2.com > > "Oxygenating the Web Service Platform", www.wso2.com > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. Follow this link to all your TCs in OASIS at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php > > > -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair VP, Apache Synapse Office: +44 844 484 8143 Cell: +44 798 447 4618 blog: http://pzf.fremantle.org paul@wso2.com "Oxygenating the Web Service Platform", www.wso2.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]