[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [office] OASIS process
Waldo, Bastian, Waldo wrote: >ODF 1.0 has passed step #6 already. I understand your question to mean where the process for ODF 1.1 should start. I expect that to be step #1. > > > I am not certain that is what is meant by the rules. Consider that ODF 1.0 has not stopped being an OASIS specification from the ODF TC simply because it is now also an OASIS Standard. In order to handle errata and that sort of thing for an OASIS standard, it would make sense to have the 15 day rule, that is to start at step #3. That puts only the parts that are changed under public review, etc., and then for a shorter period of time. I don't know of any reason why errata should be treated as though we were creating an entirely new standard. That reading allows both the full 60 day review for an OASIS standard and yet also allows a 15 day public review for correcting errata. To me that gives all the rules a meaningful place in the TC process. If we were writing another standard, then I think you would be entirely correct and we would have to start over at step 1. Hope you are looking forward to a great weekend! Patrick >Waldo Bastian >Linux Client Architect - Channel Platform Solutions Group >Intel Corporation - http://www.intel.com/go/linux >OSDL DTL Tech Board Chairman >________________________________________ >From: firstname.lastname@example.org [mailto:email@example.com] >Sent: Friday, March 17, 2006 6:18 AM >To: OpenDocument Mailing List >Subject: Re: [office] OASIS process > >Michael Brauer - Sun Germany - ham02 - Hamburg <Michael.Brauer@Sun.COM> wrote on 03/17/2006 06:59:20 AM: > > >>1. The OpenDocument TC approves a specification as committee draft. >>2. A public review of the committee draft takes place for a minimum >>of 60 days. >>3. If comments are received that require a change of the specification, the >>spcification is changed accordingly, and a public review of the changes takes >>place for 15 days. This step may be repeated. >>4. The TC approves the specification as committee specification. >>5. The TC submits the Committee Specification to the membership of OASIS for >>consideration as an OASIS Standard. This submission must be requested by the >>15th of a month. >>6. Starting at the 1st of the next month, the voting takes place. >> >> > >So, the question is this: If we make changes to ODF 1.0 in response to comments, does this send us back to step #1? Or does that send us back to step #3? > >-Rob > >--------------------------------------------------------------------- >To unsubscribe from this mail list, you must leave the OASIS TC that >generates this mail. You may a link to this group and all your TCs in OASIS >at: >https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php > > > > > > -- Patrick Durusau Patrick@Durusau.net Chair, V1 - Text Processing: Office and Publishing Systems Interface Co-Editor, ISO 13250, Topic Maps -- Reference Model Member, Text Encoding Initiative Board of Directors, 2003-2005 Topic Maps: Human, not artificial, intelligence at work!