From owner-sc22wg5+sc22wg5-dom9=www.open-std.org@open-std.org  Wed May 13 23:00:26 2026
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 D9739356DE1; Wed, 13 May 2026 23:00:26 +0200 (CEST)
Delivered-To: sc22wg5@open-std.org
Received: from mail-qk1-f173.google.com (mail-qk1-f173.google.com [209.85.222.173])
	by www.open-std.org (Postfix) with ESMTP id 58A04356882
	for <sc22wg5@open-std.org>; Wed, 13 May 2026 23:00:26 +0200 (CEST)
Received: by mail-qk1-f173.google.com with SMTP id af79cd13be357-8cb40149037so673465485a.2
        for <sc22wg5@open-std.org>; Wed, 13 May 2026 14:00:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=stevelionel.com; s=google; t=1778706025; x=1779310825; darn=open-std.org;
        h=subject:from:to:content-language:user-agent:mime-version:date
         :message-id:from:to:cc:subject:date:message-id:reply-to;
        bh=UPcqJL+PTRlCn2dhheGNRoFHUcjTwTVnDjVduZWCRyI=;
        b=LIAKcWlO73oHJfECTRJfemOcGpvNnGJ4epHuh41+MPdYWI9g/N6Wjn612Zyt+/gZp7
         SXkZSYEQ/sj77yk18tm9gO5LmCgG7y0eRJ5ZLkJ2e41hdBIdHDUqIf9eW5HLcTZUOhom
         myBM9rG0Z0meS9TxEPYz75Gl7P7JL0cgaMyGo=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20251104; t=1778706025; x=1779310825;
        h=subject:from:to:content-language:user-agent:mime-version:date
         :message-id:x-gm-gg:x-gm-message-state:from:to:cc:subject:date
         :message-id:reply-to;
        bh=UPcqJL+PTRlCn2dhheGNRoFHUcjTwTVnDjVduZWCRyI=;
        b=JCgsuTlyPHyUlc2PGSAdPIu/6u5KBgAYEWL+mSzO5r1zKAjK1h2GEn7hNQpuba1xbY
         O2fEcctJvQHWq1kXA+YxcMVb1LaKhAcoOT7FUgkAiZRvh8yKvZr82G7vEti08ZqCHB1Y
         TT9hJadMemshd0G8soV9PilBi/gIPMThYP9e0ik/zbSyhc/l7AnkZeMcFE0AK50g09g2
         7b/5sxcAxGJXx4mI3z6JIeMZCoANVcvQL/xlw81PJgzBNYIX4ZFmOPNnoX5wRygJsYwM
         8J3Nj4w9t9YPOm/shdQJZMwI24ZTR2x5anELBVBrzwmifypMtageUUsugDrRRwbngl8O
         9ZOg==
X-Gm-Message-State: AOJu0YwOFJh0FznR4p79OpOcJGADsx60fkoIx1hx0wtAe0ILzaxABADM
	vA26Ydb8fQ+PcYG8PfhKVNxiDPtmeYESqey8vn0b0/TVc5qIOwS21TZUWWx/0JdxzbL/W8Pewc4
	EQ2CP
X-Gm-Gg: Acq92OE8GaNA0Qjt7jRtseFWmKaOV4zza9BZ4asIX2OjxLurfn53xlXoy9iZhYgpum4
	lxPYyLxwFKVGOK0Ra63/sVgCVVzn32vMjVJ2/jEW/KIGj9QMJh66TsJPz4tBdrKOG/FeqXZkpNj
	5reIyIu+C0gM+FaAgHz/u8zs3q58ffYdK7fyPDGE2JQ8Hj9zNdxvoDjq0HbLCRh4pfL8ECjEwoC
	CH51yzAbbTwBvDMuVcAwo5ajanwmEIvLg7mkWzux/FzU/yD6uBS3xpRmUdvGDYa88KtJQz8sBwc
	+x5AuKAuOtpeYtbNPXuVyORo/RqIatfJRNruYLSd1raez0iBIHvKrcwV0wvLuV9himn6vaoPpmN
	0Ufg10k1bauC5/yhkFPpaakzohhz3hohSOIVu9OubOrCxqbiXm0DUt4PG3WFS+C14YQFd5eKigJ
	Y5SYtf2jUJUEBRxLzttbE66XemeOrp9amL5achPJ+g1End
X-Received: by 2002:a05:620a:472a:b0:8cd:9b31:23b1 with SMTP id af79cd13be357-90f8b7b8f32mr780788585a.53.1778706019833;
        Wed, 13 May 2026 14:00:19 -0700 (PDT)
Received: from [192.168.50.238] ([216.212.3.233])
        by smtp.gmail.com with ESMTPSA id af79cd13be357-910bc83f926sm63011885a.30.2026.05.13.14.00.18
        for <sc22wg5@open-std.org>
        (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128);
        Wed, 13 May 2026 14:00:19 -0700 (PDT)
Content-Type: multipart/alternative;
 boundary="------------dv0hwjkAIeCaB0NKlMBQOWRP"
Message-ID: <d888d2ad-27c4-41e0-b260-6ac9808d0e5c@stevelionel.com>
Date: Wed, 13 May 2026 17:00:18 -0400
MIME-Version: 1.0
User-Agent: Betterbird (Windows)
Content-Language: en-US
To: WG5 List <sc22wg5@open-std.org>
From: Steve Lionel <steve@stevelionel.com>
Subject: ISO Directives changes related to meeting types
X-Clacks-Overhead: GNU Terry Pratchett
Sender: owner-sc22wg5@open-std.org
Precedence: bulk

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

Hello again all,

As a follow-up to my earlier email about the updated ISO directives 
coming out later this year, Makki noticed a change that concerned him 
(rightfully so):

    Change 14: Meeting rules are consolidated and timelines are standardized

    What’s changing
    All meeting-related rules are brought together in a single clause,
    with updated timelines.
    • One consolidated framework for planning, running, and reporting
    meetings
    •Only two meeting formats: face-to-face and virtual
    • Standardized deadlines for agendas, documents, and reporting


One could interpret this as disallowing hybrid meetings, which would be 
a serious problem for WG5, so I asked David Keaton what it meant. He 
replied:

      Every type of meeting that is currently allowed will continue to 
be allowed; they are just changing the names.

      In the new directives, there will be two base types:

    *  Face-to-face, and

    *  Virtual.

    However, the face-to-face type will be subdivided into two categories:

    *  Face-to-face, and

    *  Face-to-face with remote participation.

    The latter is what we have been calling hybrid.

          The rules are that if the meeting is virtual, you have to redo
    a vote if a technology failure prevented someone from participating
    and they request a revote, but if the meeting is face-to-face with
    remote participation, the remote aspect is best-effort, and the
    meeting does not have to make any accommodations for technology
    glitches.

          I'm not sure why they decided to rename things.  I think it
    simplified the text in the new Directives.  In any case, it is only
    a renaming, not a change to what is allowed.

With a big sigh of relief...

Steve

--------------dv0hwjkAIeCaB0NKlMBQOWRP
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE html>
<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Hello again all,</p>
    <p>As a follow-up to my earlier email about the updated ISO
      directives coming out later this year, Makki noticed a change that
      concerned him (rightfully so):</p>
    <blockquote>
      <div
style="color: rgb(34, 34, 34); font-family: Arial, Helvetica, sans-serif; font-size: small; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(255, 255, 255); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;"><span
          style="color: rgb(255, 0, 0);">Change 14</span>: Meeting rules
        are consolidated and timelines are standardized</div>
      <div
style="color: rgb(34, 34, 34); font-family: Arial, Helvetica, sans-serif; font-size: small; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(255, 255, 255); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;"><br>
        What’s changing<br>
        All meeting-related rules are brought together in a single
        clause, with updated timelines.<br>
        • One consolidated framework for planning, running, and
        reporting meetings</div>
      <div
style="color: rgb(34, 34, 34); font-family: Arial, Helvetica, sans-serif; font-size: small; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(255, 255, 255); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;">•<span> </span><span
style="background-color: rgb(255, 255, 255); color: rgb(255, 0, 0);">Only
          two meeting formats: face-to-face and virtual</span><br>
        • Standardized deadlines for agendas, documents, and reporting</div>
    </blockquote>
    <span class="im"
style="color: rgb(34, 34, 34); font-family: Arial, Helvetica, sans-serif; font-size: small; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(255, 255, 255); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;">
      <div><br>
      </div>
      <div>One could interpret this as disallowing hybrid meetings,
        which would be a serious problem for WG5, so I asked David
        Keaton what it meant. He replied:</div>
      <div><br>
      </div>
      <div>     Every type of meeting that is currently allowed will
        continue to be allowed; they are just changing the names.
        <br>
        <br>
        <blockquote> In the new directives, there will be two base
          types:
          <br>
          <br>
          *  Face-to-face, and
          <br>
          <br>
          *  Virtual.
          <br>
          <br>
          However, the face-to-face type will be subdivided into two
          categories:
          <br>
          <br>
          *  Face-to-face, and
          <br>
          <br>
          *  Face-to-face with remote participation.
          <br>
          <br>
          The latter is what we have been calling hybrid.
          <br>
          <br>
               The rules are that if the meeting is virtual, you have to
          redo a vote if a technology failure prevented someone from
          participating and they request a revote, but if the meeting is
          face-to-face with remote participation, the remote aspect is
          best-effort, and the meeting does not have to make any
          accommodations for technology glitches.
          <br>
          <br>
               I'm not sure why they decided to rename things.  I think
          it simplified the text in the new Directives.  In any case, it
          is only a renaming, not a change to what is allowed.
          <br>
        </blockquote>
      </div>
    </span>
    <p>With a big sigh of relief...</p>
    <p>Steve</p>
  </body>
</html>

--------------dv0hwjkAIeCaB0NKlMBQOWRP--
