Stephen Michell is inviting you to a scheduled Zoom meeting.
Topic: SC 22/WG 23 Meeting 77
Time: September 26, 2024 13:00 Universal Time UTC
https://iso.zoom.us/j/94035258225?pwd=rkCJWWF0CLXAm7GaV0BtdL7n11ZJGL.1
Password: 244709
The main meeting schedule is to progress documents in sub-WG meetings. On an as-needed basis a meeting of the full group is scheduled to progress work to SC 22 for ISO balloting, to propose to SC 22 add or remove documents from the WG 23 schedule and to manage general WG 23 work.
The main topic of this meeting is the free availability of ISO/IEC 24772, all parts. Note from the SC 22 chair:
Today
in a meeting of JTC 1/AHG 5, the JTC 1 chair announced that ISO and
IEC have largely approved our request to improve the criteria for
no-cost availability of deliverables.
This
directly affects some SC 22 documents favorably, notably at the
moment a suite of documents in development in WG 23, but also
others.
I
have attached two documents that show the results. If ISO
incorrectly rejects your application for no-cost availability, you
can show them these documents to explain why they should have been
accepted.
The
new criteria are laid out clearly on the last page of the first
document, JTC 1/AHG 5 N 49. Most importantly to us, amendments
and revisions of documents that were previously approved for free
availability will now be approved as long as their scope has not been
expanded. There are a few things to note.
*
ISO and IEC have approved these new criteria for a one-year
trial period (as shown in the second attached document). The
JTC 1 chair notes that it will probably not be exactly a year; it
could be anywhere from 9-18 months. Consequently, now is the
time to push through any documents that you want to get approved
under the new criteria. There is a good chance the new criteria
will be extended after the trial period, but there are no
guarantees.
*
Technical Reports and Technical Specifications have had their
eligibility for
free availability restored.
There is no longer a need to upgrade a document to a standard for
the sole purpose of getting it approved for no-cost availability.
*
There will be a new web site for free downloads, and it will require
people to create an account for themselves and tell ISO and IEC who
they are. This does not affect their ability to get documents for
free; ISO and IEC are just frustrated that currently there are no
data on how widely no-cost documents are being used, and they want to
collect some.
*
The current free download web site says that the documents are being
made available for purposes of standardization. ISO and IEC recognize
that this statement is meaningless because *all* documents are
available for free for the purpose of standardization. They recognize
that because everyone knows this, they will see that the statement on
the web site as
meaningless and will ignore it. However, they are going to retain the
wording because some companies have downloaded free ISO and IEC
documents and bundled them into larger libraries for sale, and there
needs to be some kind of statement that says they can't do that. The
current statement is not ideal for that purpose, but they are
retaining it while they decide
what to do.
I
want to acknowledge the JTC 1 chair for leading the charge and
pressing our case to ISO and IEC. The current success would not have
been achieved without his enthusiastic support.
24772-1 has been balloted and approved as an International Standard. However, it is possible that we will want to ballot the other parts, 24772-2 Ada, 24772-3 C, etc. as TR/'s is open for discussion.
The documents that the SC 22 chair talks about are registered as WG 23 documents N1384 and 1385.
The convenor has put the following documents on the web site formatted as international standards. They have had some wording changes to meet with the ISO editorial demands, such as no “shall” or “may” (the no “shall” is because we have always considered the documents as providing “avoidance mechanisms” that the organization, team or individual apply as demanded by other safety standards, security standards, or organization requirements).
ISO/IEC 24772-2 Ada, document N411
ISO/IEC 2472-3 C, document N1413
ISO/IEC 24772-6 SPARK, document N1410
ISO/IEC 24772-8 Fortran, document N1396
ISO/IEC 24772-4 Python, document TBD.
N1396 Fortran,
N1410 SPARK,
N1411 Ada,
N1413 C
will be discussed, but will likely be subject to further review and
discussion before submitting for ballot. The convenor edited all of
these documents mostly for wording to align them with the editorial
changes applied as part of the FDIS submission of 24772-1. However,
the convenor did add some material where it was obvious that items
were absent, such as discussion in clause 6.X.1 to justify a
recommendation in 6.X.2.
N1413 C had more significant edits since it had not been touched in a while and was also missing clause 6.65 Modifying constants.
A discussion is required as to how we edit/correct/approve these documents and get them into DIS ballot.
While ISO/IEC 24772-1 was going through the final touch-up and balloting phases, we encountered another vulnerability that we believe needs adding to all documents as 6.66.
The issue is that the 32-bit character set includes characters that can be problematic for many languages. In particular, characters that are visually identical to some of the basic ASCII characters, and the presence of text direction-changing characters can at a minimum mask illicit behaviour.
The convenor proposes that WG 23 initiate an amendment to ISO/IEC 24772-1:2020 to capture this vulnerability, to be followed by amendments to the other documents that are published within the next year.