From owner-sc22wg5+sc22wg5-dom9=www.open-std.org@open-std.org Tue Nov 21 20:48:49 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 ED939356BAE; Tue, 21 Nov 2023 20:48:48 +0100 (CET) Delivered-To: sc22wg5@open-std.org X-Greylist: delayed 3350 seconds by postgrey-1.34 at www5.open-std.org; Tue, 21 Nov 2023 20:48:48 CET Received: from mx0b-002e3701.pphosted.com (mx0b-002e3701.pphosted.com [148.163.143.35]) by www.open-std.org (Postfix) with ESMTP id 58474356A61 for ; Tue, 21 Nov 2023 20:48:47 +0100 (CET) Received: from pps.filterd (m0134425.ppops.net [127.0.0.1]) by mx0b-002e3701.pphosted.com (8.17.1.19/8.17.1.19) with ESMTP id 3ALHur80020207; Tue, 21 Nov 2023 18:52:52 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hpe.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=pps0720; bh=8xXZGnPEvZGaecWlrvDThlmSa+UOOSHjgkb/HGmJQo8=; b=XzY/iFNOI5k6XZHYIMIxX31ZNFYNKVrW3kkO0HfwFoaaAb/ohkP14VdeuIvs+fEsxn/U AiW+8Ee/uWJyJA/07NwQxh+yMk0PWp2SZG4vmQV19IEfEHmbHA/Guy9x8vURXXrGEWC8 W0UpnW+KOvqWVyQ3dIHy+c3/XkedJxu0RjmUwMoycm8EfsytEcnUgyf3q4zSfZoFS57k 3VAzozJzVUGbUzsN12xqgNS1+9eFx/fDgIkII2dBES8jBrFUu93nErrHl33/oav+DQM1 daPGDVAVybaTctwSwX6dfy+ksvzCw6mPQpv7usF1h7UPTLLCmVWDnN2Ezci0mnlVX6Jo rg== Received: from p1lg14880.it.hpe.com ([16.230.97.201]) by mx0b-002e3701.pphosted.com (PPS) with ESMTPS id 3ugxcw25nn-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 21 Nov 2023 18:52:51 +0000 Received: from p1wg14924.americas.hpqcorp.net (unknown [10.119.18.113]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by p1lg14880.it.hpe.com (Postfix) with ESMTPS id BCF488005EF; Tue, 21 Nov 2023 18:52:50 +0000 (UTC) Received: from p1wg14925.americas.hpqcorp.net (10.119.18.114) by p1wg14924.americas.hpqcorp.net (10.119.18.113) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.986.42; Tue, 21 Nov 2023 06:52:16 -1200 Received: from P1WG14918.americas.hpqcorp.net (16.230.19.121) by p1wg14925.americas.hpqcorp.net (10.119.18.114) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.986.42 via Frontend Transport; Tue, 21 Nov 2023 06:52:16 -1200 Received: from NAM11-CO1-obe.outbound.protection.outlook.com (192.58.206.38) by edge.it.hpe.com (16.230.19.121) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.986.42; Tue, 21 Nov 2023 18:52:16 +0000 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ltH0H4vgVtyDT73VslldvEW7WjC61mjBdoKh5v6oAnyOCPq8S7nH0qtgpzmXYX72iAW+vIv0Txi1Sw5ulpbBqVc7/DRB58wasdjhDgxV2OA44kdCCmc+QJDvzOa4k9RSyD5xxXq1Ot6TMFoXj52Ljo4DCr2UFKW0K3jNRiQVjsRpqksxOKdYEWiUQCrTq30Gl45QwvB8Jlq0OhCG3qUOwDu8F1fQmcCgRz3uyy+9IeOwlbpy1d65ptsjNcA1qlkYiJYhGHK10sNHCBdnE3uCSnC4+15kstPYBeQrwRyEJtAYCJtQzviAEymAju048+bRoWWJq5LVK9DqLlriyXUWfw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=8xXZGnPEvZGaecWlrvDThlmSa+UOOSHjgkb/HGmJQo8=; b=dU8j4relbU4lapD5sRd7IDqvxuzEHLu4sVI/OLZmJH1uevUCBSq76c0acjbMcJO4duGhyBD2F4TzUtRxNJ9SUAAKla14OSlpW8DQggWlB58afSLI/+uB7kzDv+ktlC851U1n7ngUgepX7Kf2Rrse5DHKWrgM0anxTODIgF67HJCOC84OKgtec7ush5OSTQVuUNiwiI+wqfnMRo66QHAbj7QD7OmCRrTT1YQh/b+57A+I6vyiS8nyqjXJvPL1PnPyG8pWfhg110h2sB3S1RCHWFO9Uk48MR+Xx1JhWEai/cOASMxF0nXIuN8jLqnyXImOPX1SQ+OKUXBkm3CMBhIq3w== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=hpe.com; dmarc=pass action=none header.from=hpe.com; dkim=pass header.d=hpe.com; arc=none Received: from MW4PR84MB1851.NAMPRD84.PROD.OUTLOOK.COM (2603:10b6:303:1b2::16) by LV3PR84MB3478.NAMPRD84.PROD.OUTLOOK.COM (2603:10b6:408:213::8) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7002.28; Tue, 21 Nov 2023 18:52:14 +0000 Received: from MW4PR84MB1851.NAMPRD84.PROD.OUTLOOK.COM ([fe80::7445:5f0a:887d:35da]) by MW4PR84MB1851.NAMPRD84.PROD.OUTLOOK.COM ([fe80::7445:5f0a:887d:35da%4]) with mapi id 15.20.7002.027; Tue, 21 Nov 2023 18:52:13 +0000 From: "Long, Bill F" To: Gary Klimowicz CC: General J3 interest list , WG5 List , Malcolm Cohen Subject: Re: [J3] [SC22WG5.6512] RE: [ukfortran] Fwd: [SC 22 Convenors] JTC 1 plenary wrap-up - Electronic attachments to standard Thread-Topic: [J3] [SC22WG5.6512] RE: [ukfortran] Fwd: [SC 22 Convenors] JTC 1 plenary wrap-up - Electronic attachments to standard Thread-Index: AQHaHEepKNNraf+WR0aeVoms6AerIrCFCL+AgAAGFEOAAATigIAABt/q Date: Tue, 21 Nov 2023 18:52:13 +0000 Message-ID: References: <88db4232-2af2-47a2-9a28-f999095078f3@dmk.com> <20231120210233.6A33E356B79@www.open-std.org> <20231121065421.7C32D356B8E@www.open-std.org> <2B3E59A4-1FA3-4FDC-B508-2925B32B19CC@dancingbear.dev> In-Reply-To: <2B3E59A4-1FA3-4FDC-B508-2925B32B19CC@dancingbear.dev> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: msip_labels: x-ms-publictraffictype: Email x-ms-traffictypediagnostic: MW4PR84MB1851:EE_|LV3PR84MB3478:EE_ x-ms-office365-filtering-correlation-id: b9fa23c4-e162-4b8a-42f3-08dbeac2f9d3 x-ms-exchange-senderadcheck: 1 x-ms-exchange-antispam-relay: 0 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: gNx5GCGccdYz3FNFwg/yob0BLeX6s21UL9KiPLlk/k9BqrcM4JYr2/f++9pxS8o3/sYiAcSi5+kh4lxN9LxzBFUcTaSniVMwYt1PraSSFtQblnNV38xpxmX426AIqCt5bySU87B6qo2lLxw0w2Rqkx6WxRzOITgABQkUBaDonHaSnVBbDdj7n1L8EJeWph8Oh/4CNs4NbxTWBlrfJVZNybG7dsiETtn3gE1GFXrEyaodk+cZvEwik54dTMHVxWMgmedZfcoYPbKE7f2FZ+PYTFoCcZujsRNuaGKdio3sQlZF4Nh966JHXpY4JSDXxBx+9dZccZgPMn9xPtc99daMpCymSd6YnJgBu8cTmSnHl9/WYyLbB/tc8FZMXrvqtuxMS+ldn21h8SSPJ9mzjBfSZbwnLzgz/kmORkeMiBuXvFLJSRfRv2HcoYnybGyY+T4s59GFg18woZ1gssvlM2zfaUXMsEGrt7t66k9icVfkMtHhdHydvh9o0zJgeJBNHrKTqQ+XXnrifWmjm5xuNrxL05V8ZkMbS3KSyodUSlE15Ndx5cCcSJegQmwryDpuWMARFTDEhyW+GbbBszS5iflIOVFgL3jCC4W/9PXqf35RiIsDWAp/nxDnVt+pCeIhmCLn x-forefront-antispam-report: CIP:255.255.255.255;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:MW4PR84MB1851.NAMPRD84.PROD.OUTLOOK.COM;PTR:;CAT:NONE;SFS:(13230031)(346002)(136003)(396003)(376002)(39860400002)(366004)(230922051799003)(451199024)(64100799003)(186009)(1800799012)(83380400001)(9686003)(53546011)(26005)(55236004)(52536014)(38100700002)(4326008)(8676002)(8936002)(41300700001)(2906002)(5660300002)(478600001)(54906003)(7696005)(71200400001)(91956017)(76116006)(6916009)(66446008)(66476007)(66946007)(316002)(66556008)(64756008)(6506007)(33656002)(122000001)(86362001)(38070700009)(55016003)(19627405001)(82960400001);DIR:OUT;SFP:1102; x-ms-exchange-antispam-messagedata-chunkcount: 1 x-ms-exchange-antispam-messagedata-0: =?us-ascii?Q?vIR7L6PJ5Jxkfg9DfIa8AsGcCWvLo8Y9k4WGiLvM71GzqzCAYD2Oub8Rrsvm?= =?us-ascii?Q?eUQIqY+TLnTdy/jHK9Asl8K40K9k1UlcOGboktFzvLX4BPA9K6AsB1W2p0fr?= =?us-ascii?Q?TO/LfzW1RUzSKrk2DlHYpM815AVhfaJ/wpNSRHmdGxyXBkYQSTFupeyrzkFj?= =?us-ascii?Q?4WRAxxd2IEttExnwNN5Pyf5ougynWI2b/JizZUOi4N7DfM7znhZQmbTIqGiS?= =?us-ascii?Q?NDLWv31ZaHckTrYsb6uuWxmaW7tMNeZUbvZHrAPVaqSLqrCzbw1OLYB8S6xy?= =?us-ascii?Q?QsxripapFFlXtqDhBp1Jj/zFGZ0SnCmn8vEnHEb6MR2d/6FFtWe4Ftpfo7X3?= =?us-ascii?Q?u6uMbi/LcyaNebd6pNJ8OuP/vJOOyA3oLkkugvnmgl8ukkh5Cd8hFFtALaSH?= =?us-ascii?Q?hQMWwNbzWSxDCtZCukm5+oHI7jAXz82Vz7SIAf2IE0yrXICobCm5CxVFBk/K?= =?us-ascii?Q?9t8kMY/8u7X3ogvzfVQUokHVPrPNMNssl72pxbGNv6xoB1gXvA+tZFoaEMrF?= =?us-ascii?Q?rm+ewKIvntFcNBpE8Sy+O0viQmZa3HrUy1XldC0kCKB8p9aNJ5iHlZ1jF0yI?= =?us-ascii?Q?MzvxGFeBn5tuzz6a+S0yyYs/Iue0mlJJdZdvlOeYHJZwlvo5Oc9AByW5yoej?= =?us-ascii?Q?9XS0P3gC8bKZfz9uDUT7XwYieL2/Zw+GDcK1PrvEaGiUOagKLATQb6DHt657?= =?us-ascii?Q?cMyVXXksBgazi2EKFBsLDIpvfP0jHoTsonjgDi0D0h/UIU2Gbmi1MdbXNlfq?= =?us-ascii?Q?LqG09dwCt1vn08x5aiYIFIE+TyqPKfOZt2u3ZT0HDBrIiNM8YWiz7RUWB5Y8?= =?us-ascii?Q?AG2SRgumcyuWbkK8Et14OR5lHLSind7LUWaTAJ7Gwr5mi5d/hvryoUIPdz9n?= =?us-ascii?Q?FetBtHPYRHhw5+4Zl5HWhrFIFsqYNolBxr/ihvtvaP7a0CHVng07mP1H///7?= =?us-ascii?Q?c9y9KQc/lD6+qLrN8why2T/3WQdcuOKtk3c291csQFvHfgk7vHb6ku1dtHrs?= =?us-ascii?Q?6SgfHPfaEXADhcVsxWOENi+biytuxSKhVybF2y1IyYYeG6qXLUeSlWNYrVWo?= =?us-ascii?Q?fWymLOIJjpGrumYuGjxx/lyZgJpaU8uHcZWhNzj6uEcdz2eI2vNeTkTzJPbG?= =?us-ascii?Q?RwWsEvt1g1WNupMU/CJf8cjD8sCgShRkFSaJ2xFUWsBExTwKBtsjwghvERGh?= =?us-ascii?Q?RWtGr2JS6NN2mRCcbKd3oMrfqTkzfPuY9Qf4QUG59ZkrE5NezKJmvi6mI9NF?= =?us-ascii?Q?7PoJ1IRjnicNO1WfKSqg6AF8O8gXYKd8r4H6/sfdPLS7TRE3EpJj9LpzzWlb?= =?us-ascii?Q?T1ZxxGSp3bwYCw9Y/ZunI47LtUePj8X0xGudcuzaM8E8Bu5KdWZRFGFVbMvM?= =?us-ascii?Q?043gfo9OGnznZu58Go94v/1Th4vjC/DYneP5Mp/gDTR37ZEY4glMz4SrLAg6?= =?us-ascii?Q?Mjs0YnCMXL5B3FNmkwscj1NHmxi2P3v9PPzj7QVcc8Uk/yI7T/KHp+QK8eCC?= =?us-ascii?Q?+4qHzZHwuS7ay8fNwurzx/gevGfTCliLuB5+VsOByFzu/+hOMy9YrQoBXeYp?= =?us-ascii?Q?tpTlxJrN6g2bttLDPCU=3D?= Content-Type: multipart/alternative; boundary="_000_MW4PR84MB185174A2A7B151C98AF5A8D297BBAMW4PR84MB1851NAMP_" X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: MW4PR84MB1851.NAMPRD84.PROD.OUTLOOK.COM X-MS-Exchange-CrossTenant-Network-Message-Id: b9fa23c4-e162-4b8a-42f3-08dbeac2f9d3 X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Nov 2023 18:52:13.8666 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 105b2061-b669-4b31-92ac-24d304d195dc X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: gXk3LSl/zVekGGfm44RyAIGz9BoGXeRh0lIcdaYQ9ab9ZfIEp6iAiHmiJE6hUB+lwgkZdO85Fenc4EF4dvJiYQ== X-MS-Exchange-Transport-CrossTenantHeadersStamped: LV3PR84MB3478 X-OriginatorOrg: hpe.com X-Proofpoint-GUID: jpJQYfMHnLR1bh29BllPFeLMGNHY8Ej- X-Proofpoint-ORIG-GUID: jpJQYfMHnLR1bh29BllPFeLMGNHY8Ej- X-Proofpoint-UnRewURL: 0 URL was un-rewritten MIME-Version: 1.0 X-HPE-SCL: -1 X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.272,Aquarius:18.0.987,Hydra:6.0.619,FMLib:17.11.176.26 definitions=2023-11-21_10,2023-11-21_01,2023-05-22_02 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 adultscore=0 mlxscore=0 bulkscore=0 impostorscore=0 malwarescore=0 suspectscore=0 phishscore=0 mlxlogscore=655 lowpriorityscore=0 priorityscore=1501 clxscore=1015 spamscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2311060000 definitions=main-2311210148 Sender: owner-sc22wg5@open-std.org Precedence: bulk --_000_MW4PR84MB185174A2A7B151C98AF5A8D297BBAMW4PR84MB1851NAMP_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable People have been cutting and pasting from PDF files for years. And I fear = that ISO would consider a "text file" to be a MS-WORD document. Regarding test cases, these seem useful. We can already include illustrat= ive code examples in NOTE sections. Perhaps we could do more of that. Self-= contained executable are the most useful ________________________________ From: Gary Klimowicz Sent: Tuesday, November 21, 2023 12:11 PM To: Long, Bill F Cc: General J3 interest list ; WG5 List ; Malcolm Cohen Subject: Re: [J3] [SC22WG5.6512] RE: [ukfortran] Fwd: [SC 22 Convenors] JTC= 1 plenary wrap-up - Electronic attachments to standard It's about it being in plain text, not in PDF form. As an Annex, they're di= fficult to manipulate textually. As plain text, I can image tools we could write for automatically generatin= g parser definitions (especially for formal definition tools like SDF or Ma= ude). Identifying changes between version would be much easier. I also heard from some of the Flang developers that it would have been help= ful to be able to map the constraint numbers and to highlight textual diffe= rences in the constraints between versions of the standard. On Nov 21, 2023, at 09:54, Long, Bill F wrote: Such lists would seem more natural in an Annex as part of the standard. ________________________________ From: J3 on behalf of Gary Klimowicz vi= a J3 Sent: Tuesday, November 21, 2023 11:32 AM To: General J3 interest list Cc: Gary Klimowicz ; WG5 List ; = Malcolm Cohen Subject: Re: [J3] [SC22WG5.6512] RE: [ukfortran] Fwd: [SC 22 Convenors] JTC= 1 plenary wrap-up - Electronic attachments to standard I can imagine it would also be helpful to attach as separate text files a l= ist of the rules and a list of the constraints. On Nov 20, 2023, at 22:47, Malcolm Cohen via J3 = wrote: It would have been useful many years ago, for the source code of the ISO_VA= RYING_STRING module. Van suggests: > Could we publish the "standard" as an abstract on paper, and the "real" s= tandard as an electronic attachment? No. The normative text has to be part of the standard. Cheers, -- ..............Malcolm Cohen, NAG Oxford/Tokyo. From: Steve Lionel > Sent: Tuesday, November 21, 2023 6:03 AM To: WG5 List > Subject: [ukfortran] [SC22WG5.6510] Fwd: [SC 22 Convenors] JTC 1 plenary wr= ap-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 To: Dear SC 22 Convenors, There is one item I forgot to mention from last week's JTC 1 plenary meetin= g. ISO and IEC have approved the concept of "electronic attachments" to sta= ndards. These have several interesting properties. * Electronic attachments are distributed together with the standard, so any= one 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, pic= tures, databases, or even text. Text attachments might include such things = as a list of identifiers, a cross-reference list, or a change history of th= e 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 les= s money. Electronic attachments create some pretty exciting possibilities, and I hop= e you will keep them in mind during standards development. David --_000_MW4PR84MB185174A2A7B151C98AF5A8D297BBAMW4PR84MB1851NAMP_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
People have been cutting and pasting from PDF files for years.  And I = fear that ISO would consider a "text file" to be a MS-WORD docume= nt. 

Regarding test cases, these seem useful.   We can already include= illustrative code examples in NOTE sections. Perhaps we could do more of t= hat. Self-contained executable are the most useful


From: Gary Klimowicz <ga= k@dancingbear.dev>
Sent: Tuesday, November 21, 2023 12:11 PM
To: Long, Bill F <william.long@hpe.com>
Cc: General J3 interest list <j3@mailman.j3-fortran.org>; WG5 = List <sc22wg5@open-std.org>; Malcolm Cohen <malcolm@nag-j.co.jp>= ;
Subject: Re: [J3] [SC22WG5.6512] RE: [ukfortran] Fwd: [SC 22 Conveno= rs] JTC 1 plenary wrap-up - Electronic attachments to standard
 
It's about it being in plain te= xt, not in PDF form. As an Annex, they're difficult to manipulate textually= .

As plain text, I can image tools we could write for automatically gene= rating parser definitions (especially for formal definition tools like SDF = or Maude). Identifying changes between version would be much easier.

I also heard from some of the Flang developers that it would have been= helpful to be able to map the constraint numbers and to highlight textual = differences in the constraints between versions of the standard.



On Nov 21, 2023, at 09:54, Long, Bill F <william.long@hpe.com> w= rote:

Such lists would seem more natural in an Annex as part of the standard. 


From: J3 <j3-bounces@mailman= .j3-fortran.org> on behalf of Gary Klimowicz via J3 <j3@mailman.j3-fo= rtran.org>
Sent: Tuesday, N= ovember 21, 2023 11:32 AM
To: General J3 i= nterest list <j3@mailman.j3-fortran.org>
Cc: Gary Klimowi= cz <gak@dancingbear.dev>; WG5 List <sc22wg5@open-std.org>; Malc= olm Cohen <malcolm@nag-j.co.jp>
Subject: Re: [J3= ] [SC22WG5.6512] RE: [ukfortran] Fwd: [SC 22 Convenors] JTC 1 plenary wrap-= up - Electronic attachments to standard
 
I can imagine it would also be helpful to attach as separate text files a l= ist of the rules and a list of the constraints.

On Nov 20, 2023, at 22:47, Malcolm Cohen via J3 <j3@mailman.j3-fort= ran.org> wrote:

I= t would have been useful many years ago, for the source code of the ISO_VAR= YING_STRING module.
&= nbsp;
V= an suggests:
&= gt; Could we publish the "standard" as an abstract on paper, and = the "real" standard as an electronic attachment?
&= nbsp;
N= o. The normative text has to be part of the standard.
&= nbsp;
C= heers,
-- 
..............Malcolm Cohen= , NAG Oxford/Tokyo.
&= nbsp;
<= b>From: Steve Lio= nel <steve@stevelionel.com> 
Sent: Tuesday,= November 21, 2023 6:03 AM
To: WG5 List &= lt;sc22wg5@open-std.org>
Subject: [ukfo= rtran] [SC22WG5.6510] Fwd: [SC 22 Convenors] JTC 1 plenary wrap-up - Electr= onic attachments to standard
&= nbsp;
Interesting concept - I wonder if there's anything we can do with it.<= /div>
-= ------- Forwarded Message -------- 
Subject: 
R= e: [SC 22 Convenors] JTC 1 plenary wrap-up
Date: 
M= on, 20 Nov 2023 12:45:33 -0800
From: 
D= avid Keaton <= ;dmk@dmk.com>
To: 
<= br>
Dear SC 22 Convenors,

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

* Electronic attachments are distributed together with the standard, so any= one 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, pic= tures, 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 hop= e you will keep them in mind during standards development.

David

--_000_MW4PR84MB185174A2A7B151C98AF5A8D297BBAMW4PR84MB1851NAMP_--