From owner-sc22wg5+sc22wg5-dom9=www.open-std.org@open-std.org  Mon Nov 10 12:54:30 2025
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 637CD356BF7; Mon, 10 Nov 2025 12:54:30 +0100 (CET)
Delivered-To: sc22wg5@open-std.org
Received: from mail-pj1-f51.google.com (mail-pj1-f51.google.com [209.85.216.51])
	by www.open-std.org (Postfix) with ESMTP id D247C3569EC
	for <sc22wg5@open-std.org>; Mon, 10 Nov 2025 12:54:29 +0100 (CET)
Received: by mail-pj1-f51.google.com with SMTP id 98e67ed59e1d1-340bcc92c7dso2652555a91.0
        for <sc22wg5@open-std.org>; Mon, 10 Nov 2025 03:54:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=stevelionel.com; s=google; t=1762775667; x=1763380467; 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=BmsUvKpla/BN6aC+K3D0Cx7ug0qstd4eEi82J+wdT0I=;
        b=1mE8mx8+K7oBx1en2aCHU459A+aheen6jYoXiXJ70VDcz99ur1G61NievR38NBalI0
         ug0kFlGvT2voy1ErUSjoMT+d8s1fzG+nmqsN9dQ2Jta0jqODzZKSPs/9by1z662z+Ymx
         ucYsxi0tzBKPoSWbkolGAaUfp4wr5lrEcBzGc=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20230601; t=1762775667; x=1763380467;
        h=to:subject:message-id:date:from:in-reply-to:references:mime-version
         :x-gm-gg:x-gm-message-state:from:to:cc:subject:date:message-id
         :reply-to;
        bh=BmsUvKpla/BN6aC+K3D0Cx7ug0qstd4eEi82J+wdT0I=;
        b=HTl/zdXqV8qoby7Pz4kTMvrw/siAEp+keBik3W4bDZ++bfKuiNbZF0ebJQBjJCFeSj
         JF+0i4qto9MYly/L/liFxjv0jPgRrWyJl647A+QaHg72AQXKSGMFe0W7nGAKU9UMkezx
         ZhjAdLhipZDdPJ+zq03yecQFHC3yJNqOZQD0klpoa6FgIsC9cfomgbw1BkgfmoP7HUGb
         u/drQX78/p7SQpozaqEjF+02FWBqP2a7E6RbaqHYNHWBqVXQ0/Il7+HSRM70w8t/phjW
         vM6pm4GOuB0HUQaThD3jWXyN4n+GXIQDjtEdKAGd+lR1abT21L5UHaGCwkrhvSdye3Cm
         TLJQ==
X-Gm-Message-State: AOJu0YxfsmipESTABOd/k+S2tFvEH8UZQd5Qcm/KmtE8nwfEsRN7WVvP
	aN32+6uDrAH/TlmtJThs8xgaozQqoXa5Lg00+woac2dN0D875XF0Ko98D4CLPWhJrrIfnRqV0Mn
	qNKx455VhGZzLgD4Em137ylNNCSSQcqryw3S8gwG6RadSVkJj1kSp
X-Gm-Gg: ASbGncv62Zt5PvICbNimRlTbkDg5RxPqNjTmaq9HBV/8HgTiwc38strevOmAAO6zCtw
	S+rfgJVkStE6hUORiqK8aoKAWOEJwCYBqmLg1JFt2+5A4z51KYERb1bheX3JUcVqacM9GGkO/po
	gjYJnDRn5ST/gwqzAnZsJQatx4t4sS/BHoGhb7Ym5Bbbt2JGEY48SMzwJYUE4m1x3gCibQyde82
	ja/6Xbrr7gqTHZqmGdXSfXi6c9r6C1MlsdfogsaBlm9/bT4tcrcYxldipfXxCFhysr7DvUOPRYf
	NqA0nQ==
X-Google-Smtp-Source: AGHT+IE6rZcaPKGBI8NzuEEdnRj/SynHr8vq+OAqL7kf6IA6/x8Theb/DIj3dcWpGipqsZq+0PQT27TNHgOKGl7utYs=
X-Received: by 2002:a17:90b:3c05:b0:340:b572:3b81 with SMTP id
 98e67ed59e1d1-3436ac9da07mr9863669a91.11.1762775667286; Mon, 10 Nov 2025
 03:54:27 -0800 (PST)
MIME-Version: 1.0
References: <ba68307e-f408-45da-8292-5dc072e0872d@dmk.com>
In-Reply-To: <ba68307e-f408-45da-8292-5dc072e0872d@dmk.com>
From: Steve Lionel <steve@stevelionel.com>
Date: Mon, 10 Nov 2025 06:54:16 -0500
X-Gm-Features: AWmQ_blR-oYV0IT2oUORsXUWM6P4pe1odUDaX6fjaDLJ5pcHfT4bu8VRRyCYO0Q
Message-ID: <CAEH1ojO2S0zfb7HD5dmubVrfzptVtdOj3A=EmxVw2mVNOyqJRQ@mail.gmail.com>
Subject: Fwd: [SC 22 Convenors] ITTF updates
To: WG5 <sc22wg5@open-std.org>
Content-Type: multipart/alternative; boundary="00000000000077b20e06433c315e"
Sender: owner-sc22wg5@open-std.org
Precedence: bulk

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

---------- Forwarded message ---------
From: David Keaton <dmk@dmk.com>
Date: Mon, Nov 10, 2025 at 12:18=E2=80=AFAM
Subject: [SC 22 Convenors] ITTF updates
To:


Dear SC 22 Convenors,

      In this week's JTC 1 plenary, ITTF has provided us some updates on
pending issues.  Feel free to pass the information along to interested
people in your WGs.

* There are no updates to the Directives for 2025 because they are being
rewritten to harmonize between ISO, IEC, and JTC 1.

* New editions of the directives normally appear in May, and were
previously expected in May, 2026.  Now the Directives Part 1 rewrite is
expected in Q3 or Q4 of 2026, and the next Directives Part 2 update is
expected in 2027.  (This means that paragraph numbers will definitely
not be allowed in final published documents before 2027 at the earliest,
even if JTC 1's pending request, submitted by SC 22, is approved.)

* The Online Standards Development (OSD) platform is the default for new
documents.  A technical justification is required to develop a standard
in a different way.  (Many of our standards are developed in LaTeX and
maintained in git, which qualifies as a technical justification.)  If
you decide to use the OSD, be aware that ISO editors will be able to go
in and make any change to your document at any time, and there may not
always be a way to be alerted when this happens.  We have it better than
IEC-based committees, which are not allowed any exceptions to using the
OSD, even technical ones.

* Documents that are available for zero cost have now been moved from
the old, obscure, ITTF web page into the ISO and IEC web stores.  Due to
the new publicity that this provides, free standards are downloaded four
times more often than before.  ISO and IEC have lost some revenue from
this, because the previous arrangement tricked some people into paying
for standards that they could have received for free.

* JTC 1 Standing Document 23 on Document Access allows us the freedom to
make certain working documents available to the public.  ISO has been
trying to shut that down, and JTC 1 has pushed back hard, using
ammunition from SC 22 and other SCs.  ISO and IEC are resisting, partly
because national bodies are currently allowed to sell working drafts and
committee drafts for revenue.  The debate rages on, and definitely will
not conclude before the topic is discussed in major ISO and IEC business
meetings in March, 2026.  (In separate communication, the JTC 1 chair
indicated to me that he believed the issue would not be settled before
the middle of 2026.)  While the debate continues, we are still allowed
to operate under the existing SD 23 rules.  When a settlement is
reached, we will definitely lose the right to make some things public,
but hopefully not everything.  Old documents that were made public while
SD 23 was in force will not be required to be withdrawn from the public.

                                        David

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

<div><br></div><div><br><div class=3D"gmail_quote gmail_quote_container"><d=
iv dir=3D"ltr" class=3D"gmail_attr">---------- Forwarded message ---------<=
br>From: <strong class=3D"gmail_sendername" dir=3D"auto">David Keaton</stro=
ng> <span dir=3D"auto">&lt;<a href=3D"mailto:dmk@dmk.com">dmk@dmk.com</a>&g=
t;</span><br>Date: Mon, Nov 10, 2025 at 12:18=E2=80=AFAM<br>Subject: [SC 22=
 Convenors] ITTF updates<br>To:<br></div><br><br>Dear SC 22 Convenors,<br>
<br>
=C2=A0 =C2=A0 =C2=A0 In this week&#39;s JTC 1 plenary, ITTF has provided us=
 some updates on <br>
pending issues.=C2=A0 Feel free to pass the information along to interested=
 <br>
people in your WGs.<br>
<br>
* There are no updates to the Directives for 2025 because they are being <b=
r>
rewritten to harmonize between ISO, IEC, and JTC 1.<br>
<br>
* New editions of the directives normally appear in May, and were <br>
previously expected in May, 2026.=C2=A0 Now the Directives Part 1 rewrite i=
s <br>
expected in Q3 or Q4 of 2026, and the next Directives Part 2 update is <br>
expected in 2027.=C2=A0 (This means that paragraph numbers will definitely =
<br>
not be allowed in final published documents before 2027 at the earliest, <b=
r>
even if JTC 1&#39;s pending request, submitted by SC 22, is approved.)<br>
<br>
* The Online Standards Development (OSD) platform is the default for new <b=
r>
documents.=C2=A0 A technical justification is required to develop a standar=
d <br>
in a different way.=C2=A0 (Many of our standards are developed in LaTeX and=
 <br>
maintained in git, which qualifies as a technical justification.)=C2=A0 If =
<br>
you decide to use the OSD, be aware that ISO editors will be able to go <br=
>
in and make any change to your document at any time, and there may not <br>
always be a way to be alerted when this happens.=C2=A0 We have it better th=
an <br>
IEC-based committees, which are not allowed any exceptions to using the <br=
>
OSD, even technical ones.<br>
<br>
* Documents that are available for zero cost have now been moved from <br>
the old, obscure, ITTF web page into the ISO and IEC web stores.=C2=A0 Due =
to <br>
the new publicity that this provides, free standards are downloaded four <b=
r>
times more often than before.=C2=A0 ISO and IEC have lost some revenue from=
 <br>
this, because the previous arrangement tricked some people into paying <br>
for standards that they could have received for free.<br>
<br>
* JTC 1 Standing Document 23 on Document Access allows us the freedom to <b=
r>
make certain working documents available to the public.=C2=A0 ISO has been =
<br>
trying to shut that down, and JTC 1 has pushed back hard, using <br>
ammunition from SC 22 and other SCs.=C2=A0 ISO and IEC are resisting, partl=
y <br>
because national bodies are currently allowed to sell working drafts and <b=
r>
committee drafts for revenue.=C2=A0 The debate rages on, and definitely wil=
l <br>
not conclude before the topic is discussed in major ISO and IEC business <b=
r>
meetings in March, 2026.=C2=A0 (In separate communication, the JTC 1 chair =
<br>
indicated to me that he believed the issue would not be settled before <br>
the middle of 2026.)=C2=A0 While the debate continues, we are still allowed=
 <br>
to operate under the existing SD 23 rules.=C2=A0 When a settlement is <br>
reached, we will definitely lose the right to make some things public, <br>
but hopefully not everything.=C2=A0 Old documents that were made public whi=
le <br>
SD 23 was in force will not be required to be withdrawn from the public.<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=
>
<br>
</div></div>

--00000000000077b20e06433c315e--
