From owner-sc22wg5+sc22wg5-dom9=www.open-std.org@open-std.org  Thu Mar 14 21:36:02 2024
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 886E4356D1D; Thu, 14 Mar 2024 21:36:02 +0100 (CET)
Delivered-To: sc22wg5@open-std.org
Received: from mail-vk1-f170.google.com (mail-vk1-f170.google.com [209.85.221.170])
	by www.open-std.org (Postfix) with ESMTP id 1ED5E356D0C
	for <sc22wg5@open-std.org>; Thu, 14 Mar 2024 21:36:02 +0100 (CET)
Received: by mail-vk1-f170.google.com with SMTP id 71dfb90a1353d-4d42ac6a0bcso304650e0c.2
        for <sc22wg5@open-std.org>; Thu, 14 Mar 2024 13:36:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=stevelionel.com; s=google; t=1710448561; x=1711053361; darn=open-std.org;
        h=to:subject:message-id:date:from:in-reply-to:references:mime-version
         :from:to:cc:subject:date:message-id:reply-to;
        bh=lhdMcQhrbFiurFvVFMDRPlpGni3m5S3h7R+kgc/NYgc=;
        b=fxbnKce0s5O7VhC5vJSHzZuvtSJknNxc4SwfcTf92o0epjGvQYEAvbHlPgShRDUSm5
         KZaeKGazobXkohUBwK1k9HwJXN0X8Wq+3pzW0e/ErCZSjxXg4dzRrozjRQ5hvpw90H/c
         Ud8l2gWQdI7kLv4jsgmJr9Z4blwak4rfZ8CN4=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20230601; t=1710448561; x=1711053361;
        h=to:subject:message-id:date:from:in-reply-to:references:mime-version
         :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to;
        bh=lhdMcQhrbFiurFvVFMDRPlpGni3m5S3h7R+kgc/NYgc=;
        b=aLxrDZ8bGHwiOqHCdJwXo7hM8O8HDREH2TXkBLiSMZG2Fugsrksc3liNtlkBPLS7MF
         hZ7DAza1dTlXNLN6pt2m+cdSIHcfKJyZf6zV9uzM271Z5ZtIomwwfmn3SrfltSH0g3lt
         Ew3oP2JNW5qsHAcyM1XPpT1Qu3i2aVi54bvlEDztK5h5nQaHsPFXLVITTyl7ohYDY3cb
         5c37wHT5K3SnRFRZxaKEEoGwLqj+QnVmS5rzQS5bZmi2iyYtk8DyEJduQmwF+eFi09ZS
         NKhanEV/I99KUXYbkhMNlH1SQ+qUzF1+5IO5WIaLsRAp6BgnvUyfQFkhgz6aVw6UOJ25
         PK7w==
X-Gm-Message-State: AOJu0YzzB5ZnVJ4kGA3XEZ8SAd1uNm0ALkh/YNpnAOY9+u6x/fX72f/H
	f3NVjAIN6q5Wf5HRfKwaU/oK47ucDhrVoBJ8+fe1f5R8Q565MEfkv64qocgi8aAZCAmX16cZOhI
	tF4w+5aYAnXQPIZ3eszkVJb7YU0jzR/Pfup7DMaTnt4WWBSsh
X-Google-Smtp-Source: AGHT+IH7KgR2w5rteMtcvUZX2TpM+T6Tv0kaGDCgWhiU2ImhNUb4+Md2j8B+9+19t7s766gKdYT+EM7Sd91p+WYdmYA=
X-Received: by 2002:a05:6122:2193:b0:4d3:45a2:ae52 with SMTP id
 j19-20020a056122219300b004d345a2ae52mr3588680vkd.4.1710448560786; Thu, 14 Mar
 2024 13:36:00 -0700 (PDT)
MIME-Version: 1.0
References: <753b20b5-de49-4f60-bb27-0284bbcc8b0f@dmk.com>
In-Reply-To: <753b20b5-de49-4f60-bb27-0284bbcc8b0f@dmk.com>
From: Steve Lionel <steve@stevelionel.com>
Date: Thu, 14 Mar 2024 16:35:50 -0400
Message-ID: <CAEH1ojPrm7EeNekDf4uxRX3qQ2359VV68mHg6eraGYYvgKewKw@mail.gmail.com>
Subject: Fwd: [SC 22 Convenors] WGs Subject to Disbandment
To: WG5 <sc22wg5@open-std.org>
Content-Type: multipart/alternative; boundary="000000000000df6b540613a4d6c0"
Sender: owner-sc22wg5@open-std.org
Precedence: bulk

--000000000000df6b540613a4d6c0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

This is in response to a conversation I had with David Keaton and Bill Ash
about an item I noticed in the latest ISO Communique, when I asked just
what it meant. I will be filing for a Preliminary Work Item for F202Y -
this will give us six years to finish it (I'm hoping for four!)

Steve

---------- Forwarded message ---------
From: David Keaton <dmk@dmk.com>
Date: Thu, Mar 14, 2024 at 4:29=E2=80=AFPM
Subject: [SC 22 Convenors] WGs Subject to Disbandment
Cc: Bill Ash <bash@itic.org>


Dear SC 22 Convenors,

      This is the second piece of news in one day.  Unfortunately, this
time it is not as good.

      You should have received the latest TMB Communique today.  It
announces that beginning May 1, a WG shall be disbanded six months after
completion of its last project.  We knew this was coming, and we have
talked about it before.  Now it is more explicit.

      If your WG does not have an active project at the moment, and you
choose for the WG to continue, you will need to create an active project
immediately.

      This can be anything: a revision or amendment of your main
standard, or an auxiliary document such as a Technical Report or
Technical Specification.

      If you know you will have a project in the future but you have
been waiting to start the clock because you think it will take longer
than three years, you can start a Preliminary Work Item (PWI).  A
project can take up to six years, three under PWI status and three under
the normal process.

      I do not think SC 22 NBs will tolerate disbanding a WG outside of
a plenary given events that have happened in the past, so in practice, I
believe the SC 22 interpretation will be that WGs are disbanded at the
next plenary after they have been inactive for six months.  However,
given ISO's announcement, it is best not to depend on this.  If your WG
is inactive and you wish to keep it going, take action now.

                                        David

--000000000000df6b540613a4d6c0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">This is in response to a conversation I had with David Kea=
ton and Bill Ash about an item I noticed in the latest ISO Communique, when=
 I asked just what it meant. I will be filing for a Preliminary Work Item f=
or F202Y - this will give us six years to finish it (I&#39;m hoping for fou=
r!)<div><br></div><div>Steve<br><br><div class=3D"gmail_quote"><div dir=3D"=
ltr" class=3D"gmail_attr">---------- Forwarded message ---------<br>From: <=
strong class=3D"gmail_sendername" dir=3D"auto">David Keaton</strong> <span =
dir=3D"auto">&lt;<a href=3D"mailto:dmk@dmk.com">dmk@dmk.com</a>&gt;</span><=
br>Date: Thu, Mar 14, 2024 at 4:29=E2=80=AFPM<br>Subject: [SC 22 Convenors]=
 WGs Subject to Disbandment<br>Cc: Bill Ash &lt;<a href=3D"mailto:bash@itic=
.org">bash@itic.org</a>&gt;<br></div><br><br>Dear SC 22 Convenors,<br>
<br>
=C2=A0 =C2=A0 =C2=A0 This is the second piece of news in one day.=C2=A0 Unf=
ortunately, this <br>
time it is not as good.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 You should have received the latest TMB Communique tod=
ay.=C2=A0 It <br>
announces that beginning May 1, a WG shall be disbanded six months after <b=
r>
completion of its last project.=C2=A0 We knew this was coming, and we have =
<br>
talked about it before.=C2=A0 Now it is more explicit.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 If your WG does not have an active project at the mome=
nt, and you <br>
choose for the WG to continue, you will need to create an active project <b=
r>
immediately.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 This can be anything: a revision or amendment of your =
main <br>
standard, or an auxiliary document such as a Technical Report or <br>
Technical Specification.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 If you know you will have a project in the future but =
you have <br>
been waiting to start the clock because you think it will take longer <br>
than three years, you can start a Preliminary Work Item (PWI).=C2=A0 A <br>
project can take up to six years, three under PWI status and three under <b=
r>
the normal process.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 I do not think SC 22 NBs will tolerate disbanding a WG=
 outside of <br>
a plenary given events that have happened in the past, so in practice, I <b=
r>
believe the SC 22 interpretation will be that WGs are disbanded at the <br>
next plenary after they have been inactive for six months.=C2=A0 However, <=
br>
given ISO&#39;s announcement, it is best not to depend on this.=C2=A0 If yo=
ur WG <br>
is inactive and you wish to keep it going, take action now.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 David<br=
>
</div></div></div>

--000000000000df6b540613a4d6c0--
