Re: Old directions in social media.

"Kurt Andersen (IETF)" <kurta+ietf@drkurt.com> Tue, 05 January 2021 18:59 UTC

Return-Path: <kurta@drkurt.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DD503A11DD for <ietf@ietfa.amsl.com>; Tue, 5 Jan 2021 10:59:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
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: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=drkurt.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cRbiID_-Mt7Z for <ietf@ietfa.amsl.com>; Tue, 5 Jan 2021 10:59:50 -0800 (PST)
Received: from mail-il1-x12e.google.com (mail-il1-x12e.google.com [IPv6:2607:f8b0:4864:20::12e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 43B7C3A11BE for <ietf@ietf.org>; Tue, 5 Jan 2021 10:59:48 -0800 (PST)
Received: by mail-il1-x12e.google.com with SMTP id q5so657146ilc.10 for <ietf@ietf.org>; Tue, 05 Jan 2021 10:59:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=drkurt.com; s=20130612; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=w9CIqxxkTLVh3HJFWc4haHGZLdPKGcLDbb55KxOrWjY=; b=H5XsWArFcoRpZDTYaj3rWugWc3Ae2SJ4iCQFMX5Yo6/1i4rhaLU5Rr+TzBIEdk5QwS 3erwrm3RGsEzq70d8VNEJBs/0YEgdiODaMK+HZWA2ijk6utUq9ywesemeCfOVvsOzmfE uZaOOsJ5v+QWWopBea9iSC+wUU+TNI+E7aV+I=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=w9CIqxxkTLVh3HJFWc4haHGZLdPKGcLDbb55KxOrWjY=; b=nSA64i+X7udHnOYi64Bmel/Yuk7FaSkbJKz5YItuRVyRQazfIUNta88ItTCRkcpU07 OvkF5NvTrgUQnOlbhG1EUmcBuwhaY7y6N3uouZ15FfpZnqRpAzJ5HpZMmn4nvE/YpcLz DAJWhEQHotV7TxtngQCH8dKDgj2nElEsdNCZUkFrBk3LcaeVobD4F0TxY2z+J9zl3WGe GuMNGxc4JaCcBG7hs5DMuAAcn19OPjsV4dls8pkma4l+OBIsLjC6z0bqwh968CJjn8p0 OSB8EUkrea3gAb7NPMDB/KHg2lgcIcr1KymStu3dxRKBSEMnKsjGBzT+HDp8O/9Py3HR WcHA==
X-Gm-Message-State: AOAM531xmOIPMK6bdVJ05kWMRTPPJksvDeUiS5rscQN9g1cSgTohOs1s 5LmLZyEhmBlfRwwBC/l6Y2q+8sKtu0Lm1M+GIU9bPA==
X-Google-Smtp-Source: ABdhPJy7o+d5aDL1crGHn7P4i7q4PEl40byiqRjm9qjCg/gXrVyWtB3YXIw0dLdDMwefoLkrb19diODaeTme4shcuA0=
X-Received: by 2002:a05:6e02:152f:: with SMTP id i15mr991854ilu.104.1609873187407; Tue, 05 Jan 2021 10:59:47 -0800 (PST)
MIME-Version: 1.0
References: <CAMm+Lwg1-pxKU8vMinFDUbVca52VgFzTOOSJMnJjaUJvF6PLew@mail.gmail.com>
In-Reply-To: <CAMm+Lwg1-pxKU8vMinFDUbVca52VgFzTOOSJMnJjaUJvF6PLew@mail.gmail.com>
From: "Kurt Andersen (IETF)" <kurta+ietf@drkurt.com>
Date: Tue, 05 Jan 2021 10:59:20 -0800
Message-ID: <CABuGu1oQcgjHa7CVKcWjs5B6xB0+KZSWxVCuCv1HnKw5uANO6Q@mail.gmail.com>
Subject: Re: Old directions in social media.
To: Phillip Hallam-Baker <phill@hallambaker.com>, IETF discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000781f1905b82bcffb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/oGnNNKAF8IRazLpyCdEaGMPc138>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jan 2021 18:59:58 -0000

On Mon, Jan 4, 2021 at 9:40 AM Phillip Hallam-Baker <phill@hallambaker.com>
wrote:

>
> It should be possible to scan through a document and annotate individual
> paragraphs with comments tagged with lightweight semantics such as:
>
> agree
> disagree
> nit [typographic issues, spelling etc.]
> vocabulary [use/choice of defined terms]
> requirement
> use-case
> interop
>
> The open meeting vocabulary was limited to six moves. It is possible that
> we could make use of a slightly larger vocabulary. But it is probably best
> to start out constrained and add slowly.
>
> The process part comes in when an editor is creating a new version of the
> document. We might assign an editor a separate set of moves:
>
> accept
> reject
> assign-issue
>
> So if I am editing a document and someone has given me a list of typos, I
> just go through and clear them. But some comments might well require more
> discussion. And we can write rules that identify those comments.
>

Having worked with a hybrid of git and Google docs to develop a recent RFC,
I'd suggest that there are at least two additional key functions:
* replace [text range] with [new text] (potentially with a coordinated
change several places in the document)
* free text comment

--Kurt