Re: [EXTERNAL] Question about Codimd for w.g. minutes

Kyle Rose <> Fri, 30 July 2021 07:46 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id DCFCB3A2095 for <>; Fri, 30 Jul 2021 00:46:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id vrSBhkr89ya8 for <>; Fri, 30 Jul 2021 00:46:54 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::32d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id EEA503A2093 for <>; Fri, 30 Jul 2021 00:46:53 -0700 (PDT)
Received: by with SMTP id f14-20020a05600c154eb02902519e4abe10so8532142wmg.4 for <>; Fri, 30 Jul 2021 00:46:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=EhWz0p/0NlbSJOpD6o3dqMGmWaD3op9bJ9/KVYixS6M=; b=JZfmVVHDMLP0MwcykMUi30RvOOrelWMdSKETVKPQ4JgvNFgpWqmf7Tlaf8qhIm87i5 6YASjLGsBVT64fdlppSr0xdiVaqkf/j1eOQ51+ixZAr9mp8GWAShIuA/blT9XgCbG9Ng KmeLGEiHqs6e/QYgwfRcSSTtgLvFzQ9rCvvHM=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=EhWz0p/0NlbSJOpD6o3dqMGmWaD3op9bJ9/KVYixS6M=; b=SDah+V4YlZCDqdn5bA6agdrQTDd1f493bjKz23RmpymBF4Ecspe5TFDksLkUImIzCw pbX9lVQ56vxwBAMG1FgWkXzhkf8FKdZNa1NLguY/0hWO0/uBKEJBUWcZa+7KBJON19oG zAcPK566kmzyVctoQNYbZZ4g/TZ5lDqC6fG3CQjsKFNN40DAzGYoR9dKtiV+pyIJjtCt +3+AGB8VPAFfA3duXLqksmI21pB3iumY5x0ccJvfpYfY6EUw6vgq5Bp9ZTyWDsXRko5t jBGv0vqDEm0rLvcjDHPFZ+TXUgSG+vNK+wjuAYsQvLWEnnGaDuuyjBIEIRWxFeHPEJeP JAzQ==
X-Gm-Message-State: AOAM530Dfcm/PB2HE9fN1bin5aelJbXrOZ50ql17RPP95vjjrJF6NORH nAb98+93HIarqbBqg25dgp0prgZzLTZvVMWQk3kXcQ==
X-Google-Smtp-Source: ABdhPJwi+7gCNyOrWdFeLqfucztk2BLJRIoiZrWZ5mhW1wK3L9TF1Pyq8QUpHlrWbskiot0hb+eJMsU1Vc8HVUAmybM=
X-Received: by 2002:a1c:2642:: with SMTP id m63mr1357643wmm.13.1627631210835; Fri, 30 Jul 2021 00:46:50 -0700 (PDT)
MIME-Version: 1.0
References: <> <> <> <> <> <> <> <> <> <>
In-Reply-To: <>
From: Kyle Rose <>
Date: Fri, 30 Jul 2021 03:46:39 -0400
Message-ID: <>
Subject: Re: [EXTERNAL] Question about Codimd for w.g. minutes
Cc: Carsten Bormann <>, Working Group Chairs <>
Content-Type: multipart/alternative; boundary="00000000000025c87e05c8526cc6"
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working Group Chairs <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 30 Jul 2021 07:46:59 -0000

On Thu, Jul 29, 2021 at 4:14 PM STARK, BARBARA H <> wrote:

> Really, I suspect at least one of your 2 notetakers was either too lazy to
> insert those extra blank lines while typing or didn't want to impact the
> experience of people who might be following the discussion using the
> rendered CodiMD notes (because the additional blank lines create blank
> lines in the CodiMD rendering).

I think it's probably less laziness than unfamiliarity with the quirks of
markdown, combined with the fact that CodiMD renders those single newlines
as line breaks, so it "LGTM"  in the side-by-side or rendered view. It's
only when processed through other tools in what is ostensibly the same
ecosystem that the faulty assumption is revealed.

This is a fairly benign version of a more general problem of
under-specification of semantics. (JSON and YAML come to mind.)