[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [tab] Re: [opencsa-liaison] RE: Quick update on DCR
IMHO a pending status chafe means only changes allowed in 2.18(6), but agree that needs clarification. Martin. On 16 Aug 2011, at 19:58, Chet Ensign <chet.ensign@oasis-open.org> wrote: > This is a scenario that TCA and TAB are discussing. Approval of > replacing Beta CSD02 with Beta CS02 (for example) is not a problem > because the presumption is that nothing is changing in Beta CSD02 > except its stage in the OASIS document hierarchy. > > Moving from CSD01 to CSD02 on the other hand means that the content of > Beta *has* changed. Our discussion is about whether or not a public > review should therefore be required. > > Under the present wording, the intent of the section is not crystal > clear. The wording refers to "... a pending status change..." but the > meaning of status change is not defined. > > /chet > > On Tue, Aug 16, 2011 at 2:49 PM, Patil, Sanjay <sanjay.patil@sap.com> wrote: >> Pretty much except I would phrase the last step as: >> Motion to update Alpha CSD01 (replace reference to Beta CSD01 with Beta CSD02) and approve it to become Alpha CS01 >> >> [Note that Beta CSD01 has progressed to Beta CSD02 in the previous step, hence there is no need of a DCR this time] >> >> Sanjay >> >> -----Original Message----- >> From: Chet Ensign [mailto:chet.ensign@oasis-open.org] >> Sent: Tuesday, August 16, 2011 11:38 AM >> To: Patil, Sanjay >> Cc: Martin Chapman; Mike Edwards; Anish Karmarkar; Simon Holdsworth; OASIS TAB; OASIS Liaison >> Subject: Re: [opencsa-liaison] RE: Quick update on DCR >> >> Sanjay, let me layout this out in a bit more detail to make sure we >> fully understand the scenario: >> >> >> TC Alpha TC Beta >> >> Alpha WD01 references-> Beta WD01 >> >> Alpha WD01 appv'd for CSD & PR w/ DCR motion to -> Beta WD01 becoming >> Beta CSD01 >> >> Beta WD01 appv'd as >> Beta CSD01 >> >> Alpha CSD01 is pub'd w/ reference to Beta CSD01 >> >> New round of work: >> Beta WD02 appv'd as Beta CSD02 >> >> Alpha CSD01 appv'd for CS01 w/ DCR motion to Beta WD02 becoming Beta CSD02 >> >> If I understand correctly, you are asking if the TC could approve >> CSD01 to become CS01 with a DCR motion to update the cross-reference >> from Beta CSD01 to Beta CSD02. (And obviously not requiring that CSD01 >> be pushed up to CSD02 and put through another round of public review.) >> >> Am I reading your request correctly? >> >> Thx - /chet >> >> >> On Tue, Aug 16, 2011 at 2:24 PM, Patil, Sanjay <sanjay.patil@sap.com> wrote: >>> Is the following scenario valid? Would that be supported? >>> >>> Motion for A wd to be csd/pr with a DCR to csd/pr X >>> Content changes to X, leading to another round of csd/pr for X >>> Time passes, no content changes to A >>> Update A pr with new reference for X (without a second round of pr for A) >>> Motion for updated A pr to cs >>> >>> Thanks, >>> Sanjay >>> >>> -----Original Message----- >>> From: Martin Chapman [mailto:MARTIN.CHAPMAN@ORACLE.COM] >>> Sent: Tuesday, August 16, 2011 10:48 AM >>> To: Patil, Sanjay; Chet Ensign; Mike Edwards; Anish Karmarkar; Simon Holdsworth; OASIS TAB; OASIS Liaison >>> Subject: RE: [opencsa-liaison] RE: Quick update on DCR >>> >>> Why not? A DCR can accompany a CS/CN motion. So the flow would be: >>> >>> Motion for A wd to be cd/pr with a DCR to cd/pr X >>> <time passes, no content changes to A or X> >>> Motion for A pr to cs with a DCR to X cs >>> >>> Note that any direct transition cd->pr->cs/cn->cos->os is safe. >>> >>>> One quick comment on the proposal - While extending the DCR process to PRs >>>> might help, I think it still would not allow adjusting the references in >>>> post PR versions even if a TC can approve of such a change as safe! >>>> >>>> Best wishes, >>>> Sanjay >>>> >>>> -----Original Message----- >>>> From: Chet Ensign [mailto:chet.ensign@oasis-open.org] >>>> Sent: Tuesday, August 16, 2011 9:16 AM >>>> To: Patil, Sanjay; Mike Edwards; Anish Karmarkar; Simon Holdsworth; OASIS >>>> TAB >>>> Subject: Quick update on DCR >>>> >>>> Anish, Mike, Sanjay, Simon - >>>> >>>> Just a quick status update. TC Admin and the TAB are going to discuss >>>> our proposal for modifying DCR handling at our regular meeting next >>>> Friday, 8/26. Key thing from your perspective is that we are >>>> discussing extending the ability to make motions for DCR's to >>>> approvals of Committee Specification/Note Drafts and approvals for >>>> Public Reviews. I want to hold off on a detailed response to your >>>> questions until we have had our discussion in order to ensure that I >>>> give you the correct information. (Simon, you had a specific question >>>> that I will answer separately - it is already covered by the current >>>> TC Process.) >>>> >>>> If you have any pressing issues that need to be handled now, please >>>> let me know and we can get on the phone and discuss how to handle >>>> them. Otherwise, I will send you the detailed response after our >>>> meeting. >>>> >>>> Best regards, >>>> >>>> /chet >>>> ---------------- >>>> Chet Ensign >>>> Director of Standards Development and TC Administration >>>> OASIS: Advancing open standards for the information society >>>> http://www.oasis-open.org >>>> >>>> Primary: +1 973-378-3472 >>>> Mobile: +1 201-341-1393 >>>> >>>> Follow OASIS on: >>>> LinkedIn: http://linkd.in/OASISopen >>>> Twitter: http://twitter.com/OASISopen >>>> Facebook: http://facebook.com/oasis.open >>>> >>>> --------------------------------------------------------------------- >>>> 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 >>>> >>> >> >> >> >> -- >> >> /chet >> ---------------- >> Chet Ensign >> Director of Standards Development and TC Administration >> OASIS: Advancing open standards for the information society >> http://www.oasis-open.org >> >> Primary: +1 973-378-3472 >> Mobile: +1 201-341-1393 >> >> Follow OASIS on: >> LinkedIn: http://linkd.in/OASISopen >> Twitter: http://twitter.com/OASISopen >> Facebook: http://facebook.com/oasis.open >> >> --------------------------------------------------------------------- >> 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 >> >> > > > > -- > > /chet > ---------------- > Chet Ensign > Director of Standards Development and TC Administration > OASIS: Advancing open standards for the information society > http://www.oasis-open.org > > Primary: +1 973-378-3472 > Mobile: +1 201-341-1393 > > Follow OASIS on: > LinkedIn: http://linkd.in/OASISopen > Twitter: http://twitter.com/OASISopen > Facebook: http://facebook.com/oasis.open > > --------------------------------------------------------------------- > 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 >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]