[J3] [SC22WG5.6612] Fwd: [SC 22 Convenors] ISO On-line Standards Development platform
Steve Lionel
steve at stevelionel.com
Mon Nov 4 01:24:06 UTC 2024
I do hope that we will be allowed to continue using LaTeX. Or, seek to
publish under a different standards body.
Steve
-------- Forwarded Message --------
Subject: [SC 22 Convenors] ISO On-line Standards Development platform
Date: Sun, 3 Nov 2024 17:19:38 -0800
From: David Keaton <dmk at dmk.com>
To: Jeff Shimoda <jshimoda137 at gmail.com>, Steve Lionel
<steve at stevelionel.com>, Pat Rogers <rogers at adacore.com>, Robert Seacord
(Woven Planet) <robert.seacord at woven-planet.global>, 'Ulrich Neumerkel'
<ulrich at complang.tuwien.ac.at>, Herb Sutter <herb.sutter at gmail.com>,
Stephen Michell <Stephen.Michell at maurya.on.ca>, Yong Woo Lee
<ywlee at uos.ac.kr>
CC: Bill Ash <bash at itic.org>
Dear SC 22 Convenors,
In the JTC 1 plenary today, there was a rather shocking announcement
that everyone should know about. Starting January 1, 2025, all projects
will be required to use the ISO On-line Standards Development (OSD)
platform unless they can provide a technical justification why the OSD
cannot be used.
For many revisions of existing documents, the use of typesetting systems
such as LaTeX would preclude the use of the OSD. However, for new
documents, there might not be a way to avoid the OSD.
The problem with the OSD is that it allows ISO editors to go in and make
any modifications they wish. We have had many problems with ISO making
changes that they think are editorial, but have actually changed the
technical meaning of documents. More bluntly, the use of OSD implies a
level of trust in ISO that has not been earned.
One way to avoid this problem is to publish new TR- and TS-like
documents in alternate venues, such as SC 22 white papers. A white paper
has no ISO editing or development requirements, and only requires
approval at the SC 22 level.
David
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.j3-fortran.org/pipermail/j3/attachments/20241103/75b7e35a/attachment.htm>
More information about the J3
mailing list