From owner-sc22wg5+sc22wg5-dom9=www.open-std.org@open-std.org  Mon Nov 20 22:02:33 2023
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 3D9E7356BAD; Mon, 20 Nov 2023 22:02:33 +0100 (CET)
Delivered-To: sc22wg5@open-std.org
Received: from mail-qk1-f177.google.com (mail-qk1-f177.google.com [209.85.222.177])
	by www.open-std.org (Postfix) with ESMTP id C740E356B39
	for <sc22wg5@open-std.org>; Mon, 20 Nov 2023 22:02:32 +0100 (CET)
Received: by mail-qk1-f177.google.com with SMTP id af79cd13be357-777754138bdso316640485a.1
        for <sc22wg5@open-std.org>; Mon, 20 Nov 2023 13:02:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=stevelionel.com; s=google; t=1700514151; x=1701118951; darn=open-std.org;
        h=in-reply-to:from:to:references:content-language:subject:user-agent
         :mime-version:date:message-id:from:to:cc:subject:date:message-id
         :reply-to;
        bh=zCFf37lAqiKrqZyCPDqGkgmoN3gSDBy7A82dAV8Pk9Q=;
        b=CJ7AfFvaTie/58LnNWr/8m+um+d5ZI+brOZoLkd/Vs3QPJlKgL8e+ef1h5HZL5KzfY
         Clh+KHIb+4wMm6uuQBQTRqDvCicBGpJNYTBYVQJtlF0QXDie/sGGSGJHvl4/aJlfydli
         Jk/KS3FLZwL31rzMoVmLfCTV/xqxXv/cBt2w8=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20230601; t=1700514151; x=1701118951;
        h=in-reply-to:from:to:references:content-language:subject:user-agent
         :mime-version:date:message-id:x-gm-message-state:from:to:cc:subject
         :date:message-id:reply-to;
        bh=zCFf37lAqiKrqZyCPDqGkgmoN3gSDBy7A82dAV8Pk9Q=;
        b=YJZUhM1lOOZoauIbzUKEs8cu6Xvg8i9DHNw+5JrmLXPXRPMIwT3V2Gsq1ynQkcgQg3
         9IOovlOlBUSbDyigEJD4Rci5MmBrYh16mN5TSp0Ue8v+RieZZjW8VRH6zM++32tTBsOy
         MDEgoUQwMx3uXGy2RjS/XRdMbiK4XHIaOdjnoOGXMSEojFaPvHxEqITA1LLsT6EyyrBh
         ZcDPBJH/f7MlouJjSpp2G1ML4ogFVILdwv7lL6dHj1TfCIx8K3lLwusjZ7oq4eTB9kQA
         PIIznodzjuHJUiirIZa+u2Y9bkDB2F3GihTlEXkhdqsPTK3R7WHEb/wEOg1dKti59x1g
         bLzQ==
X-Gm-Message-State: AOJu0YyTin5ikRZvq1UC0Z4Q/rUogjIAczLelWQUF40RU7lTGbnZ0cIS
	TCLP6Go+zCwLIScZUNhnaS+rnZxxiHthtwaUIzg=
X-Google-Smtp-Source: AGHT+IGdSxxHeHUAPN7pPe6MlmPU5zSf6FMzLMnJ5L3DjHZPtuFVQnpwBmIqT25E71nMlcvAXYL6hA==
X-Received: by 2002:a05:6214:f2e:b0:677:fba2:21e2 with SMTP id iw14-20020a0562140f2e00b00677fba221e2mr11794519qvb.65.1700514151126;
        Mon, 20 Nov 2023 13:02:31 -0800 (PST)
Received: from [192.168.1.203] ([216.212.3.233])
        by smtp.gmail.com with ESMTPSA id bp14-20020a05620a458e00b0077263636a95sm2963671qkb.93.2023.11.20.13.02.30
        for <sc22wg5@open-std.org>
        (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128);
        Mon, 20 Nov 2023 13:02:30 -0800 (PST)
Content-Type: multipart/alternative;
 boundary="------------H6MWYvQhvqu8HvDucIfCOf4i"
Message-ID: <721d4b19-91fd-4b06-b4f3-4bf2aba31c5a@stevelionel.com>
Date: Mon, 20 Nov 2023 16:02:30 -0500
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Fwd: [SC 22 Convenors] JTC 1 plenary wrap-up - Electronic attachments
 to standard
Content-Language: en-US
References: <88db4232-2af2-47a2-9a28-f999095078f3@dmk.com>
To: WG5 List <sc22wg5@open-std.org>
From: Steve Lionel <steve@stevelionel.com>
X-Clacks-Overhead: GNU Terry Pratchett
In-Reply-To: <88db4232-2af2-47a2-9a28-f999095078f3@dmk.com>
X-Forwarded-Message-Id: <88db4232-2af2-47a2-9a28-f999095078f3@dmk.com>
Sender: owner-sc22wg5@open-std.org
Precedence: bulk

This is a multi-part message in MIME format.
--------------H6MWYvQhvqu8HvDucIfCOf4i
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

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
--------------H6MWYvQhvqu8HvDucIfCOf4i
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<!DOCTYPE html>
<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Interesting concept - I wonder if there's anything we can do with
      it.<br>
    </p>
    <div class="moz-forward-container">-------- Forwarded Message
      --------
      <table class="moz-email-headers-table" cellspacing="0"
        cellpadding="0" border="0">
        <tbody>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">Subject:
            </th>
            <td>Re: [SC 22 Convenors] JTC 1 plenary wrap-up</td>
          </tr>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">Date: </th>
            <td>Mon, 20 Nov 2023 12:45:33 -0800</td>
          </tr>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">From: </th>
            <td>David Keaton <a class="moz-txt-link-rfc2396E" href="mailto:dmk@dmk.com">&lt;dmk@dmk.com&gt;</a></td>
          </tr>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">To: </th>
            <td><br>
            </td>
          </tr>
        </tbody>
      </table>
      <br>
      <br>
      Dear SC 22 Convenors,<br>
      <br>
      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.<br>
      <br>
      * Electronic attachments are distributed together with the
      standard, so anyone who buys the standard has the attachments.<br>
      <br>
      * 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.<br>
      <br>
      * 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.<br>
      <br>
      Electronic attachments create some pretty exciting possibilities,
      and I hope you will keep them in mind during standards
      development.<br>
      <br>
      David<br>
    </div>
  </body>
</html>

--------------H6MWYvQhvqu8HvDucIfCOf4i--
