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

Klaus Hartke <hartke@projectcool.de> Sat, 10 November 2018 09:01 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 448D7130E13 for <core@ietfa.amsl.com>; Sat, 10 Nov 2018 01:01:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_FAIL=0.001, URIBL_BLOCKED=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 Onm4JTVEy8Z1 for <core@ietfa.amsl.com>; Sat, 10 Nov 2018 01:01:38 -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 CEBD0130DED for <core@ietf.org>; Sat, 10 Nov 2018 01:01:37 -0800 (PST)
Received: from mail-qk1-f180.google.com ([209.85.222.180]); authenticated by wp382.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) id 1gLP93-0000xT-E1; Sat, 10 Nov 2018 10:01:34 +0100
Received: by mail-qk1-f180.google.com with SMTP id m5so5829845qka.9 for <core@ietf.org>; Sat, 10 Nov 2018 01:01:33 -0800 (PST)
X-Gm-Message-State: AGRZ1gL3bZk88uOY28u9Wp/ANwUgAXYhRBWLSkMzOLamrJh1PTG+iLHH dPKW8PABKVWg+p3xaBCLZ2IcT04socxheU3hrQI=
X-Google-Smtp-Source: AJdET5eS+lGOudqDaXihu6mVE9Q5b7qU76MhJH4v/t6OS8NzE//scl/SG0LYFlQSdJ4uRorgu8I7/8iE6m7qXIfqWZc=
X-Received: by 2002:aed:26a3:: with SMTP id q32mr11955086qtd.106.1541840492423; Sat, 10 Nov 2018 01:01:32 -0800 (PST)
MIME-Version: 1.0
References: <CAAzbHvYk9dUvGmYsX1U=0qcU7330bYO6YjGAa51gFKMGGoy-Dg@mail.gmail.com> <20181105123604.GA9680@hephaistos.amsuess.com>
In-Reply-To: <20181105123604.GA9680@hephaistos.amsuess.com>
From: Klaus Hartke <hartke@projectcool.de>
Date: Sat, 10 Nov 2018 10:00:59 +0100
X-Gmail-Original-Message-ID: <CAAzbHvaizPq03RJe4CybEamkoRVcM5pbs+cvK3eM04r1KLvsbg@mail.gmail.com>
Message-ID: <CAAzbHvaizPq03RJe4CybEamkoRVcM5pbs+cvK3eM04r1KLvsbg@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; 1541840497; 9b17b6ec;
X-HE-SMSGID: 1gLP93-0000xT-E1
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/yjDfT210LsVS7r7YTUnXZWV5hj0>
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: Sat, 10 Nov 2018 09:01:40 -0000

Christian Amsüss wrote:
> >       #using iana = <http://www.iana.org/assignments/relation/>
> >       #using attr = <http://TBD2/>
> >
> >       iana:terms-of-service </tos> {
> >          attr:title "Nutzungsbedingungen" { attr:hreflang "de" }
> >          attr:title "Terms of use"        { attr:hreflang "en" }
> >       }
>
> That's kind of neat and kind of scary. The scary comes from the
> implications of
>
>     hosts </present> {
>         attr:title "Gift" { attr:hreflang "en" }
>         attr:title "Geschenk" { attr:hreflang "de" }
>     }
>     hosts </posion> {
>         attr:title "Poison" { attr:hreflang "en" }
>         attr:title "Gift" { attr:hreflang "de" }
>     }
>
> which may be read to imply that there is a string "Gift" that is both
> English and German and describes both resources.

Literals as link targets indeed seem to need some fine-tuning. Besides
language tags, I can also imagine other kinds of information attached
to a literal, such as a unit:

    hosts </temperature> {
        example:value 21 {
            example:unit <http://unitsofmeasure.org/example/Cel>
        }
    }
    hosts </weight> {
        example:value 21 {
            example:unit <http://unitsofmeasure.org/example/kg>
        }
   }

This may be read to imply that there is a resource identified by the
integer 21, which has the unit degree Celsius and contradictorily also
the unit kilogram...

Klaus