[Mtgvenue] meta-terms (was: Re: Comments on draft-baker-mtgvenue-iaoc-venue-selection-process-02)

Dave Crocker <dcrocker@gmail.com> Mon, 31 October 2016 18:49 UTC

Return-Path: <dcrocker@gmail.com>
X-Original-To: mtgvenue@ietfa.amsl.com
Delivered-To: mtgvenue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8D1D1299D3 for <mtgvenue@ietfa.amsl.com>; Mon, 31 Oct 2016 11:49:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 nOwaWRLFT4nL for <mtgvenue@ietfa.amsl.com>; Mon, 31 Oct 2016 11:49:55 -0700 (PDT)
Received: from mail-yw0-x231.google.com (mail-yw0-x231.google.com [IPv6:2607:f8b0:4002:c05::231]) (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 8A621129A1D for <mtgvenue@ietf.org>; Mon, 31 Oct 2016 11:49:50 -0700 (PDT)
Received: by mail-yw0-x231.google.com with SMTP id r204so43087833ywb.0 for <mtgvenue@ietf.org>; Mon, 31 Oct 2016 11:49:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:subject:to:references:organization:reply-to:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=hlVx31bn2Ajeph2Bjk3ZNCEG30cObpjAARJ4kMlTNCA=; b=p8EknmcQIqhpFUWfCS76OJ67oIZbJVXUKxrT22zJNoBXJVIiL72Np3/+Ll12gD8dZt EZ31LCC/jACveuHECyHWrNZtimaDRG+ZmKdwrrIXSRqikrJsMbU66RikrwAk/7Tpkrfz FRzwyrPrZPIyPvOMzw3SHMWma6PczMi5Qxjm6kY9BCrDBQqrOvMJK4nzGMwvm7WsaDSj O0uvVmA6jGJUSUHKXvyx8Ms0bQrdyPlUyIBmnaRROoddZrCdvb+nIhYzAGawRXYdvujg t3GtHuIv83Y3K+GpND3xixBVna5Zo8ZyXwTi7ZwKyURUT8rY3MmdptQEGLvjRP5sZ3yk M/nw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:subject:to:references:organization:reply-to :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=hlVx31bn2Ajeph2Bjk3ZNCEG30cObpjAARJ4kMlTNCA=; b=MFmEp/EldtFJzUhgGJ8L/ivBMw6pA6y6QwKv4lIJUc/8qB9q2HOagun+XZFw6nKGbi U+UsXm8+PFO7bTSHQObWnT8sF8xqzy8rGMQzfv/l7kSIqh6NXdyOQPjNqRdvyW2xVkHm A3sjvBapsX5I3wrByV+zFJ8nRUeuRPGC3F2fxVFihKr1hbjTiwBl/3N+FxANlHuIbE+9 aK2BZd/YhtL0xkJqtBny/SEVmGt2rvK3Gy80E2jiBPh5gLnMvmpUxPkpQy2Hr+qXqNN7 H/r9SOtaUXZi92cDFhwCW7m32Ks928zvlfVTGMmw7WCk/tolCtyATQBfseA6gsQzyUuv nR9w==
X-Gm-Message-State: ABUngvfjGfkmRSlqm04FnkVXFzAD4SliX4yi2EV92HAyEI8Q2lbGwqAu4ErbpVahlzRRfg==
X-Received: by 10.129.178.135 with SMTP id q129mr28861569ywh.31.1477939789658; Mon, 31 Oct 2016 11:49:49 -0700 (PDT)
Received: from ?IPv6:2602:304:cda0:8800:922:74ff:c09d:9746? ([2602:304:cda0:8800:922:74ff:c09d:9746]) by smtp.gmail.com with ESMTPSA id m126sm10001594ywf.14.2016.10.31.11.49.48 for <mtgvenue@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 31 Oct 2016 11:49:49 -0700 (PDT)
From: Dave Crocker <dcrocker@gmail.com>
X-Google-Original-From: Dave Crocker <dhc@dcrocker.net>
To: mtgvenue@ietf.org
References: <E3C933A5-6141-437A-ABA9-CF881BC8149E@cooperw.in>
Organization: Brandenburg InternetWorking
Message-ID: <70ae528b-5f9d-a3bb-9723-4b3391a88e86@dcrocker.net>
Date: Mon, 31 Oct 2016 11:49:34 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <E3C933A5-6141-437A-ABA9-CF881BC8149E@cooperw.in>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mtgvenue/ybcpD3zdeR7SCt-awbE1HjL56r0>
Subject: [Mtgvenue] meta-terms (was: Re: Comments on draft-baker-mtgvenue-iaoc-venue-selection-process-02)
X-BeenThere: mtgvenue@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: "List for email discussion of the IAOC meeting venue selection process." <mtgvenue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mtgvenue>, <mailto:mtgvenue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mtgvenue/>
List-Post: <mailto:mtgvenue@ietf.org>
List-Help: <mailto:mtgvenue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mtgvenue>, <mailto:mtgvenue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Oct 2016 18:49:57 -0000

On 6/21/2016 9:49 PM, Alissa Cooper wrote:
> Similarly, 3.1.1 contains a mix of criteria and requirements for
> meetings committee operation. For example, for every city under
> consideration, the meetings committee can research and carefully
> consider health risks. That is not a criteria. It doesn't differentiate
> between cities. It just tells the meetings committee what to do. For
> this to be turned into actionable criteria, it would need to describe
> (in some abstract way) what level of health risk would count against a
> city in the venue selection process.


Criteria, requirements, considerations...

By virtue of its explicitly seeking to relate some basic terms we've 
been using, the above text crystallized a confusion I've been having 
about the use of these terms.  The text clearly is based on a very solid 
sense of what the terms mean, how they differ and how they should be used.

The problem is that the meanings and differences and uses aren't 
entirely obvious to me.  Worse, I suspect each of us would offer 
different meanings and uses, and relative differences.

In other words, I think we all tend to use terms of art, like these, 
with an assumption of shared meaning that does not actually exist. 
However the role of these terms is too important for there to be 
divergent meaning.

To the extent that these terms are to be used in this document in 
anything approaching a clarifying or even normative fashion, we need 
text that defines them.  Unfortunately, since I'm confused about what 
they ought to mean here, I'm inclined to ask for others to offer text...

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net