{"id":228,"date":"2009-06-23T10:50:00","date_gmt":"2009-06-23T15:50:00","guid":{"rendered":"http:\/\/2d823b65bb.nxcli.io\/2009\/06\/odf-tc-timeline.html"},"modified":"2009-06-23T10:50:00","modified_gmt":"2009-06-23T15:50:00","slug":"odf-tc-timeline","status":"publish","type":"post","link":"https:\/\/www.robweir.com\/blog\/2009\/06\/odf-tc-timeline.html","title":{"rendered":"ODF TC timeline"},"content":{"rendered":"<p>I used a variation of this chart at the recent <a href=\"http:\/\/plugfest.opendocsociety.org\/doku.php\">ODF Plugfest<\/a> in the Netherlands.  But the aspect ratio of a presentation slide doesn&#8217;t suit this type of chart well, so here is a fuller version of what I showed there.<\/p>\n<p>Those who are not familiar with standards development are sometimes amazed at how long it takes to develop a good standard. Perhaps the single-vendor, 6,000 page, 12-month escapade of OOXML in Ecma has <a href=\"https:\/\/2d823b65bb.nxcli.io\/blog\/attachments\/spec-speed.png\">skewed<\/a> expectations.  Fortunately, OOXML is the exception, not the rule.  Achieving a multi-vendor consensus around a substantial technical standard will always be time-consuming, but it is time that is well spent.<\/p>\n<p>OASIS standards go through several stages of development:<\/p>\n<ol>\n<li>Working Draft (WD)<\/li>\n<li>Committee Draft (CD)<\/li>\n<li>Public Review Draft<\/li>\n<li>Committee Specification<\/li>\n<li>OASIS Standard<\/li>\n<\/ol>\n<p>Progressing from one step to another is by ballot.  The first 4 stages are advanced by vote of the Technical Committee (TC), while the last stage (OASIS Standard) is by a ballot of all OASIS members.  As a draft advances through stages 1-4, an increasing degree of consensus is required. So, a CD requires only simple majority, whereas a Committee Specification requires 2\/3 approval, with no more than 1\/4 disapproval.  Some of these stages allow iteration.  So we can, and typically do, have several WD&#8217;s and several CD&#8217;s.<\/p>\n<p>If you want more detail on the nitty-gritty details, <a href=\"http:\/\/docs.oasis-open.org\/templates\/MindMaps\/SpecificationLifeCycle\/index.html\">here<\/a> is a flow chart of the OASIS standards approval process.<\/p>\n<p>I occasionally get a question along the lines of: &#8220;What has the ODF TC been doing for the past couple of years?&#8221;  The following timeline should give you an idea.  I&#8217;ve indicated the time spent developing ODF 1.0 and ODF 1.1, along with some other milestone activities, such as the PAS transposition of ISO\/IEC 26300, the publication of ODF 1.0 Approved Errata 01 and the creation of the various ODF subcommittees.  I&#8217;ve also indicated the dates of each of the ODF 1.2 WD&#8217;s and CD&#8217;s.<\/p>\n<p>As you can see, we&#8217;ve been quite busy.  After iterating on WD&#8217;s during 2007 and 2008, we&#8217;ve now moved on to CD&#8217;s.  This is <u>not<\/u> a drawn out process, but simply the ODF TC working with full transparency, making all of the intermediate drafts available for public inspection.<\/p>\n<p>All of the planned feature work for ODF 1.2 is now completed.  The remaining work is to address the various editorial and technical comments that have been submitted to our <a href=\"http:\/\/lists.oasis-open.org\/archives\/office-comment\/\">comment list<\/a>, as well comments from TC members and JTC1\/SC34. The goal is to have no known defects in ODF 1.2 before we send it out for a Public Review.   Of course, previously-unknown defects will likely be identified during the Public Review, and we have a process for handling these.  I&#8217;ll comment more on that process, and Public Reviews in general, when we get closer to that stage.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/2d823b65bb.nxcli.io\/blog\/images\/odf-tc-timeline.png\" \/><\/p>\n","protected":false},"excerpt":{"rendered":"<p>I used a variation of this chart at the recent ODF Plugfest in the Netherlands. But the aspect ratio of a presentation slide doesn&#8217;t suit this type of chart well, so here is a fuller version of what I showed there. Those who are not familiar with standards development are sometimes amazed at how long [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"","footnotes":""},"categories":[9],"tags":[],"class_list":{"0":"post-228","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-odf","7":"entry"},"_links":{"self":[{"href":"https:\/\/www.robweir.com\/blog\/wp-json\/wp\/v2\/posts\/228","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.robweir.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.robweir.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.robweir.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.robweir.com\/blog\/wp-json\/wp\/v2\/comments?post=228"}],"version-history":[{"count":0,"href":"https:\/\/www.robweir.com\/blog\/wp-json\/wp\/v2\/posts\/228\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.robweir.com\/blog\/wp-json\/wp\/v2\/media?parent=228"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.robweir.com\/blog\/wp-json\/wp\/v2\/categories?post=228"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.robweir.com\/blog\/wp-json\/wp\/v2\/tags?post=228"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}