Re: [core] Link target attributes in CoRAL (was: Review of CoRAL)

Klaus Hartke <hartke@projectcool.de> Tue, 06 November 2018 08:22 UTC

Return-Path: <hartke@projectcool.de>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC9B1128A6E for <core@ietfa.amsl.com>; Tue, 6 Nov 2018 00:22:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_FAIL=0.001] autolearn=no autolearn_force=no
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 WneRJFiA8FMm for <core@ietfa.amsl.com>; Tue, 6 Nov 2018 00:22:15 -0800 (PST)
Received: from wp382.webpack.hosteurope.de (wp382.webpack.hosteurope.de [IPv6:2a01:488:42:1000:50ed:8597::]) (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 22658128A5C for <core@ietf.org>; Tue, 6 Nov 2018 00:22:15 -0800 (PST)
Received: from mail-qt1-f178.google.com ([209.85.160.178]); authenticated by wp382.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) id 1gJwcn-0006Ic-Ig; Tue, 06 Nov 2018 09:22:13 +0100
Received: by mail-qt1-f178.google.com with SMTP id v11so1648909qtc.2 for <core@ietf.org>; Tue, 06 Nov 2018 00:22:13 -0800 (PST)
X-Gm-Message-State: AGRZ1gJIwdFuKF34RMfpl9somWuWFgguKMYRZxOBh6GaW9hTOuFmzGXx r/ha5s+4T7FJddPNNWgvkJK0T4oU52cfHDyjzj8=
X-Google-Smtp-Source: AJdET5c8K3osixvTXRcV3EisFRZLZIgusYvpdT90dXAJuZ8kgodepQkiYF3Ai0StVOI9mMTLWj8H7tq5gZOaOW0xyqU=
X-Received: by 2002:a0c:ae30:: with SMTP id y45mr24201639qvc.145.1541492532625; Tue, 06 Nov 2018 00:22:12 -0800 (PST)
MIME-Version: 1.0
References: <CAAzbHvYk9dUvGmYsX1U=0qcU7330bYO6YjGAa51gFKMGGoy-Dg@mail.gmail.com> <20181105123604.GA9680@hephaistos.amsuess.com> <CAAzbHvZ=4GaPH6FXj4ZuOzMLrQbWUo-Oc6CUmiA4O2b3PhK-rA@mail.gmail.com>
In-Reply-To: <CAAzbHvZ=4GaPH6FXj4ZuOzMLrQbWUo-Oc6CUmiA4O2b3PhK-rA@mail.gmail.com>
From: Klaus Hartke <hartke@projectcool.de>
Date: Tue, 6 Nov 2018 09:21:36 +0100
X-Gmail-Original-Message-ID: <CAAzbHvaSDzc62-dY-ALQxW6bGKS7avCv795-DUMh0PVRF+yaqw@mail.gmail.com>
Message-ID: <CAAzbHvaSDzc62-dY-ALQxW6bGKS7avCv795-DUMh0PVRF+yaqw@mail.gmail.com>
To: =?UTF-8?Q?Christian_M=2E_Ams=C3=BCss?= <christian@amsuess.com>
Cc: "core@ietf.org WG" <core@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-bounce-key: webpack.hosteurope.de; hartke@projectcool.de; 1541492535; 81477c85;
X-HE-SMSGID: 1gJwcn-0006Ic-Ig
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/Aw13IuuucsW7cqVU3cBY-y262OE>
Subject: Re: [core] Link target attributes in CoRAL (was: Review of CoRAL)
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2018 08:22:17 -0000

Klaus Hartke wrote:
> Christian Amsüss wrote:
> > I don't think we need a guarantee for that. We can, as they pop up, for
> > some funny-string-valued attributes define equivalent more semantic
> > attributes, each with their own mapping. So a general CoRAL processor
> > you could encounter both `attr: rt="x y"` or `split-attr:rt rt:x,
> > split-attr rt:y` and needs to know of the equivalence.
>
> This is exactly what I'd like to avoid.

Of course, we could for new link target attributes, as they pop up,
define an equivalent more semantic link relation type. In Link Format
you would use the link target attribute; in CoRAL, the link relation
type. If a converter encounters a new, unknown attribute, it would fail.

Klaus