From owner-sc22wg5+sc22wg5-dom9=www.open-std.org@open-std.org Tue Nov 21 07:54:21 2023 Return-Path: X-Original-To: sc22wg5-dom9 Delivered-To: sc22wg5-dom9@www.open-std.org Received: by www.open-std.org (Postfix, from userid 521) id 60966356B71; Tue, 21 Nov 2023 07:54:21 +0100 (CET) Delivered-To: sc22wg5@open-std.org X-Greylist: delayed 398 seconds by postgrey-1.34 at www5.open-std.org; Tue, 21 Nov 2023 07:54:20 CET Received: from nag-j.co.jp (bvdeuz19.secure.ne.jp [180.222.80.19]) by www.open-std.org (Postfix) with SMTP id 32A1E356B29 for ; Tue, 21 Nov 2023 07:54:19 +0100 (CET) Received: (qmail 72132 invoked from network); 21 Nov 2023 15:47:37 +0900 Received: from unknown (HELO Maru10) (218.42.159.105) by 0 with SMTP; 21 Nov 2023 15:47:37 +0900 From: "Malcolm Cohen" To: "'WG5 List'" References: <88db4232-2af2-47a2-9a28-f999095078f3@dmk.com> <20231120210233.6A33E356B79@www.open-std.org> In-Reply-To: <20231120210233.6A33E356B79@www.open-std.org> Subject: RE: [ukfortran] [SC22WG5.6510] Fwd: [SC 22 Convenors] JTC 1 plenary wrap-up - Electronic attachments to standard Date: Tue, 21 Nov 2023 15:47:37 +0900 Message-ID: <01ad01da1c46$9d877680$d8966380$@nag-j.co.jp> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_01AE_01DA1C92.0D6F1E80" X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQMqA/c4/4fmbyu11RV3vZS0nSfSoAHVT3mzrdXZ1zA= Content-Language: ja Sender: owner-sc22wg5@open-std.org Precedence: bulk This is a multipart message in MIME format. ------=_NextPart_000_01AE_01DA1C92.0D6F1E80 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable It would have been useful many years ago, for the source code of the = ISO_VARYING_STRING module. =20 Van suggests: > Could we publish the "standard" as an abstract on paper, and the = "real" standard as an electronic attachment? =20 No. The normative text has to be part of the standard. =20 Cheers, --=20 ..............Malcolm Cohen, NAG Oxford/Tokyo. =20 From: Steve Lionel =20 Sent: Tuesday, November 21, 2023 6:03 AM To: WG5 List Subject: [ukfortran] [SC22WG5.6510] Fwd: [SC 22 Convenors] JTC 1 plenary = wrap-up - Electronic attachments to standard =20 Interesting concept - I wonder if there's anything we can do with it. -------- Forwarded Message --------=20 Subject:=20 Re: [SC 22 Convenors] JTC 1 plenary wrap-up Date:=20 Mon, 20 Nov 2023 12:45:33 -0800 From:=20 David Keaton To:=20 =09 Dear SC 22 Convenors, There is one item I forgot to mention from last week's JTC 1 plenary = meeting. ISO and IEC have approved the concept of "electronic = attachments" to standards. These have several interesting properties. * Electronic attachments are distributed together with the standard, so = anyone who buys the standard has the attachments. * An electronic attachment can contain any kind of data, such as a = machine-readable grammar for a programming language, a sample computer = program, pictures, databases, or even text. Text attachments might = include such things as a list of identifiers, a cross-reference list, or = a change history of the standard. ISO and IEC do not need to know how to = process the attachments; they are only for use by the customers of the = standard. * Customers are charged by the page of the standard. Electronic = attachments are not counted; they are included for free. Consequently, = some items that might otherwise have resulted in large annexes could = instead be submitted as electronic attachments, giving customers access = to the same data for less money. Electronic attachments create some pretty exciting possibilities, and I = hope you will keep them in mind during standards development. David ------=_NextPart_000_01AE_01DA1C92.0D6F1E80 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

It would have been useful many = years ago, for the source code of the ISO_VARYING_STRING = module.

 

Van suggests:

> = Could we publish the "standard" as an abstract on paper, and = the "real" standard as an electronic = attachment?

 

No. The normative text has to be part of the = standard.

 

Cheers,

--

..............Malcolm Cohen, NAG = Oxford/Tokyo.

 

From: Steve Lionel = <steve@stevelionel.com>
Sent: Tuesday, November 21, = 2023 6:03 AM
To: WG5 List = <sc22wg5@open-std.org>
Subject: [ukfortran] = [SC22WG5.6510] Fwd: [SC 22 Convenors] JTC 1 plenary wrap-up - Electronic = attachments to standard

 

Interesting concept - I wonder = if there's anything we can do with it.

-------- Forwarded Message -------- =

Subject:

Re: [SC 22 = Convenors] JTC 1 plenary wrap-up

Date: =

Mon, 20 Nov 2023 12:45:33 = -0800

From:

David Keaton <dmk@dmk.com>

To: =



Dear SC 22 = Convenors,

There is one item I forgot to mention from last week's = JTC 1 plenary meeting. ISO and IEC have approved the concept of = "electronic attachments" to standards. These have several = interesting properties.

* Electronic attachments are distributed = together with the standard, so anyone who buys the standard has the = attachments.

* An electronic attachment can contain any kind of = data, such as a machine-readable grammar for a programming language, a = sample computer program, pictures, databases, or even text. Text = attachments might include such things as a list of identifiers, a = cross-reference list, or a change history of the standard. ISO and IEC = do not need to know how to process the attachments; they are only for = use by the customers of the standard.

* Customers are charged by = the page of the standard. Electronic attachments are not counted; they = are included for free. Consequently, some items that might otherwise = have resulted in large annexes could instead be submitted as electronic = attachments, giving customers access to the same data for less = money.

Electronic attachments create some pretty exciting = possibilities, and I hope you will keep them in mind during standards = development.

David

------=_NextPart_000_01AE_01DA1C92.0D6F1E80--