Re: Reference document requirements

Mark Nottingham <> Tue, 24 September 2019 23:26 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7A39F120845 for <>; Tue, 24 Sep 2019 16:26:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.7
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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key) header.b=mzJFwYR1; dkim=pass (2048-bit key) header.b=wViA3RHp
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 6_waAlxQJSxE for <>; Tue, 24 Sep 2019 16:26:35 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B55A81201AA for <>; Tue, 24 Sep 2019 16:26:35 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal []) by mailout.nyi.internal (Postfix) with ESMTP id 1EDF521FE5; Tue, 24 Sep 2019 19:26:35 -0400 (EDT)
Received: from mailfrontend2 ([]) by compute3.internal (MEProxy); Tue, 24 Sep 2019 19:26:35 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm3; bh=E 36taa46e8mVsyKRrobr7dZPR9ObH1fDm4wCsJ0ax9M=; b=mzJFwYR1CTzsMI9qF 5LbbcwHpD7/gazYtx3jfjQePaJwxJqOiHhNZ6OBLwGvZxUbnQxYe1q+iyp9sr300 HvHNuha7v0OtFQQVO+wiTSJvEA2vJ7RUX6i5keIpKlmPtsbCwvceO1IVZnFkJxyR JcCV7gmqdDpsJ6CyL7GT3FLCAHWKlYwhyC93lH2Mgizc7nJC3OUD8X+xiwYA6CWk 68RxQtn19VfpZDl0WW5a3vi4/AFFD6YovEyk1ZOmzVlStYPJG4dRhNuYeQo3T2Ue 5aYbR7PUa3GHshFW6XDHCM91YaCGrzovLJEctd+HXsswdHBA3Q0lIal8syHdjjjU +At5w==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=E36taa46e8mVsyKRrobr7dZPR9ObH1fDm4wCsJ0ax 9M=; b=wViA3RHpJddp9RX16idwkwoBlJdhNZwijJ85WuzlQoEAl3nRCuaydCE97 QmaWnCa4GHf/sUm67K3m/uLdilN7hPVbCCK7iEcTWBjRfdboahUloNl0EAKDXU5Z T/GIWts7K0KhQ0PsIzraJTducIAOHQ8JSHWaiz9UbZ24gKH6u4yUPZcY2zzAQ45O L+Pb2LmYjDgkHQASmJiDElMeLs1qimyuciN/VsbmFDdaAyG0nnrITTBHJXTqSALA s4lwekE6oXtLgjtNMk3Bg/x1xlzx2QdZI+XPYnrGvfGA+amEJlKW/70pNgXRIVzr GO7gt88fDIm3k6UYk1VqBVJRYeVRQ==
X-ME-Sender: <xms:KqaKXbanhqoWw76bZTspD77moQaOuR400UeXRCqfJyGxKHFpUi2kCg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrfedugddvfecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpegtggfuhfgjfffgkfhfvffosehtqhhmtdhhtddvnecuhfhrohhmpeforghrkhcu pfhothhtihhnghhhrghmuceomhhnohhtsehmnhhothdrnhgvtheqnecuffhomhgrihhnpe hgihhthhhusgdrtghomhdpihgvthhfrdhorhhgpdhmnhhothdrnhgvthenucfkphepuddv uddrvddttddrjedrudeggeenucfrrghrrghmpehmrghilhhfrhhomhepmhhnohhtsehmnh hothdrnhgvthenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:KqaKXayg2c-N4glOiw-cxwMqxgj75BKPqkpDb7Gm6IINTkCoUguHBA> <xmx:KqaKXfH-TcuE73ZjAQqbFcgbvIGSjuSxHgJU_A62Xn7PprjKpl18DQ> <xmx:KqaKXdrDP0W22b78-XxehN9nRN_6IqMlDnzmmO-5_X34eQ_7VBn1Qg> <xmx:K6aKXbPF2pT3TvEuED27vMuFuPz0ZhOinxwgT24juAdUqUsPjr6KCg>
Received: from ( []) by (Postfix) with ESMTPA id 45C02D6005E; Tue, 24 Sep 2019 19:26:32 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: Reference document requirements
From: Mark Nottingham <>
In-Reply-To: <>
Date: Wed, 25 Sep 2019 09:26:30 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <>
To: Michael Koster <>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 24 Sep 2019 23:26:37 -0000

Hi Michael,

If there's a draft of some sort and it's developed enough where it's reasonable to think it will be published without changing the name, that's adequate.

Alternatively, if you open an issue for the relation, that would serve as a placeholder until it's ready for registration (i.e., we'd see and deal with any potential conflict). See:


> On 25 Sep 2019, at 9:04 am, Michael Koster <> wrote:
> Hi,
> We (Open Connectivity Foundation) would like to register a new link relation to use in a forthcoming specification, but the document won't be published until later this year due to being in IPR review.
> Is there any way we can reserve or pre-register the new term before the document is published? For example, can we provide a paragraph or two in a short informational ID?
> Best regards,
> Michael
> Relation Name: ruleinput
> Description: The target resource provides a value to be used as the input to a rule resource which is present at the link context.
> Reference: OCF Core Specification (TBD) 
> _______________________________________________
> link-relations mailing list

Mark Nottingham