From owner-sc22wg5+sc22wg5-dom9=www.open-std.org@open-std.org  Wed Dec  9 23:11:02 2020
Return-Path: <owner-sc22wg5+sc22wg5-dom9=www.open-std.org@open-std.org>
X-Original-To: sc22wg5-dom9
Delivered-To: sc22wg5-dom9@www.open-std.org
Received: by www.open-std.org (Postfix, from userid 521)
	id 9A5CC358993; Wed,  9 Dec 2020 23:11:02 +0100 (CET)
Delivered-To: sc22wg5@open-std.org
Received: from mail-qt1-f182.google.com (mail-qt1-f182.google.com [209.85.160.182])
	(using TLSv1 with cipher AES128-SHA (128/128 bits))
	(No client certificate requested)
	by www.open-std.org (Postfix) with ESMTP id 3D3A53567F0
	for <sc22wg5@open-std.org>; Wed,  9 Dec 2020 23:11:02 +0100 (CET)
Received: by mail-qt1-f182.google.com with SMTP id z20so2232872qtq.3
        for <sc22wg5@open-std.org>; Wed, 09 Dec 2020 14:11:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=stevelionel.com; s=google;
        h=subject:references:to:from:message-id:date:user-agent:mime-version
         :in-reply-to:content-language:content-transfer-encoding;
        bh=tXF2pLrpS1xkDk8lcKWM6EH+ORA3unvuD4B3g/Lm0fk=;
        b=Gv73h+vP1TScQUXnGKLt6p4aNgE73mQrb6IvoCAyOP+GFjwChI/pUPZqbVgtVbFUHD
         HkoWfraqs4WpHqXJ7mPyykBW9eCgl4eQR4WwzHoN640WUyFeiLtm7hsRejaE758UOY7F
         CLJk9Uq/OHT/fqifhyqI7uD3Le2j0ky0tFpL0=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:subject:references:to:from:message-id:date
         :user-agent:mime-version:in-reply-to:content-language
         :content-transfer-encoding;
        bh=tXF2pLrpS1xkDk8lcKWM6EH+ORA3unvuD4B3g/Lm0fk=;
        b=dyU/BBCpKJDwUclRA2knwFHtF8GQDzLPOzkW5H7KlmJ2/6VXs0/GRaSBk6Jo8N6XGq
         3XM7Q0kKEg45h/BYNMextYJ6xb5tCAn0DQUw1PhP/reIEiFwEPiv/5cZ2Z8Axtrw20pJ
         nfrcXpRgRtio82DT5YDR8GnwIc2XBhcQ3iRo0wmPqamFqpDILqSn5YJH+GMZN32MlI+4
         /NKulOFCUmpiU9s1hmeekF9HGWwZ2Bt4aNzw0VQEKIkWtV9ExGLZ1QBsP5xMObzRdmcC
         hQ8lQSGVo3iZ5nUdcOT4G8aAMEnkfYMqpptmgkc8hAPBZlORyFGI2OQqogfc+LRutGjl
         ruUA==
X-Gm-Message-State: AOAM532Gq5Wl/mJ1YT+rkx1IQPupyDJjkKGelSJnUHjdqX4v4h4K8t4g
	wUUHtXOHKqzax05lm94qcTRJDN5enqNSrRcw
X-Google-Smtp-Source: ABdhPJyYss1sQuBkiqhwxuTmBIvkm0aEWp5GpPYbCKHNuLdJNmftjf+kwE8G/nqm4zZPRi+VC3G0VA==
X-Received: by 2002:ac8:4f13:: with SMTP id b19mr5518516qte.150.1607551860245;
        Wed, 09 Dec 2020 14:11:00 -0800 (PST)
Received: from [192.168.1.2] ([71.169.144.145])
        by smtp.gmail.com with ESMTPSA id d11sm2088835qta.64.2020.12.09.14.10.59
        for <sc22wg5@open-std.org>
        (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128);
        Wed, 09 Dec 2020 14:10:59 -0800 (PST)
Subject: Fwd: [SC 22 Convenors] Elimination of Limits on Technical Corrigenda
References: <86fa983a-0c70-c7e2-5319-339ed3e33792@dmk.com>
To: WG5 List <sc22wg5@open-std.org>
From: Steve Lionel <steve@stevelionel.com>
X-Clacks-Overhead:  GNU Terry Pratchett
X-Forwarded-Message-Id: <86fa983a-0c70-c7e2-5319-339ed3e33792@dmk.com>
Message-ID: <42a39c4b-65df-b21a-2183-1957ee9861a1@stevelionel.com>
Date: Wed, 9 Dec 2020 17:10:57 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.5.1
MIME-Version: 1.0
In-Reply-To: <86fa983a-0c70-c7e2-5319-339ed3e33792@dmk.com>
Content-Type: text/html; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: owner-sc22wg5@open-std.org
Precedence: bulk

<html style="direction: ltr;">
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
    <style id="bidiui-paragraph-margins" type="text/css">body p { margin-bottom: 0cm; margin-top: 0pt; } </style>
  </head>
  <body bidimailui-charset-is-forced="true" style="direction: ltr;">
    <p>Good news for us!</p>
    <p><br>
    </p>
    <p>Steve<br>
    </p>
    <div class="moz-forward-container"><br>
      -------- Forwarded Message --------
      <table class="moz-email-headers-table" cellspacing="0"
        cellpadding="0" border="0">
        <tbody>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">Subject:
            </th>
            <td>[SC 22 Convenors] Elimination of Limits on Technical
              Corrigenda</td>
          </tr>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">Date: </th>
            <td>Wed, 9 Dec 2020 14:09:05 -0800</td>
          </tr>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">From: </th>
            <td>David Keaton <a class="moz-txt-link-rfc2396E" href="mailto:dmk@dmk.com">&lt;dmk@dmk.com&gt;</a></td>
          </tr>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">To: </th>
            <td><br>
            </td>
          </tr>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">CC: </th>
            <td>Bill Ash <a class="moz-txt-link-rfc2396E" href="mailto:bash@itic.org">&lt;bash@itic.org&gt;</a></td>
          </tr>
        </tbody>
      </table>
      <br>
      <br>
      Dear SC 22 Convenors,<br>
      <br>
      It has been a few years since SC 22 first brought this issue to
      the attention of JTC 1, but I think you will be pleased with the
      outcome.<br>
      <br>
      Currently, no edition of a standard may have more than two
      Technical Corrigenda (CORs), and all CORs must be issued within
      the first three years of the standard's publication. This means
      that after two CORs or three years, it is impossible to correct an
      existing edition of a standard, meaning that it is impossible to
      correct a standard in a way that affects legal contracts that
      depend on a particular edition.<br>
      <br>
      JTC 1 standards in general, and SC 22 standards in particular, are
      much larger than the average of about 40 pages for other ISO and
      IEC standards, so it can be up to 100 times more likely for an SC
      22 standard to need CORs than for other ISO and IEC standards.<br>
      <br>
      JTC 1 chair Phil Wennblom has been working on our behalf. It has
      not been easy to get the Joint ISO/IEC Directives Management Team
      (JDMT) to listen, but at a meeting this week, the JDMT finally
      decided that for the 2021 edition of the Directives, they will
      eliminate the limitations on number and timing of Technical
      Corrigenda.<br>
      <br>
      Some SC 22 WGs no longer publish CORs. However, some may still
      need to publish them, and beginning with the 2021 edition of the
      Directives, that option will be available without the current
      restrictions on number and timing.<br>
      <br>
      David<br>
    </div>
  </body>
</html>
