Re: [link-relations] where to spec the "license" link relation [was: NEW RELATION REQUEST: Relation name: "next"]

Mark Nottingham <mnot@mnot.net> Fri, 29 October 2010 04:38 UTC

Return-Path: <mnot@mnot.net>
X-Original-To: link-relations@core3.amsl.com
Delivered-To: link-relations@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7ADB63A6A07 for <link-relations@core3.amsl.com>; Thu, 28 Oct 2010 21:38:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.552
X-Spam-Level:
X-Spam-Status: No, score=-105.552 tagged_above=-999 required=5 tests=[AWL=-2.953, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uMBvcS4ElL3i for <link-relations@core3.amsl.com>; Thu, 28 Oct 2010 21:38:41 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by core3.amsl.com (Postfix) with ESMTP id 00C073A67FF for <link-relations@ietf.org>; Thu, 28 Oct 2010 21:34:00 -0700 (PDT)
Received: from chancetrain-lm.mnot.net (unknown [118.209.39.135]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 9A6EC509D9; Fri, 29 Oct 2010 00:35:40 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset="us-ascii"
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <20101006152920.GE81427@sideshowbarker>
Date: Fri, 29 Oct 2010 15:35:37 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <2931AB73-C6B6-483C-9994-F2C7F7CC314F@mnot.net>
References: <20100902081410.GD58403@sideshowbarker> <31E56538-C14F-40A7-92FC-C2D05E6AF7E1@mnot.net> <20101006152920.GE81427@sideshowbarker>
To: Michael Smith <mike@w3.org>
X-Mailer: Apple Mail (2.1081)
Cc: link-relations@ietf.org
Subject: Re: [link-relations] where to spec the "license" link relation [was: NEW RELATION REQUEST: Relation name: "next"]
X-BeenThere: link-relations@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <link-relations.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/link-relations>, <mailto:link-relations-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/link-relations>
List-Post: <mailto:link-relations@ietf.org>
List-Help: <mailto:link-relations-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/link-relations>, <mailto:link-relations-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Oct 2010 04:38:54 -0000

Hi Michael,

Sorry about the delay; been travelling and catching up (badly).

I think having an I-D define the license relation is certainly workable, but it'd be easier to just note the format-specific implications directly in the registration; e.g.,

---8<---

Relation Name:
 license

Description:
 Refers to a license associated with the link's context.

Reference:
 [RFC4946]

Notes:
  For implications of use in HTML, see: http://www.w3.org/TR/html5/links.html#link-type-license

--->---

Is that workable for the HTML WG?

Cheers,


On 07/10/2010, at 2:29 AM, Michael(tm) Smith wrote:

> Mark Nottingham <mnot@mnot.net>, 2010-09-02 21:34 +1000:
> 
>> 3) Updating registrations from other sources, including:
>>  license / up / last / first
>> 
>> These might need a bit more discussion, especially license,
>> which is currently defined by RFC4946. Is there any reason that
>> its definition isn't adequate for HTML5?
> 
> After some further thought about this, I think the reason is to
> keep the definition at point of use in the HTML5 spec unless
> there's a really compelling need not to.
> 
> I personally would not feel terrifically confident trying to argue
> that readers of the HTML5 spec would be particularly well-served
> by being required to read a separate protocol spec -- one that is
> arguably relatively obscure and one in which the definition of the
> "license" link relation is a relatively small part -- rather than
> just having a definition at point of use in the HTML5 spec.
> 
> Another suggested way to handle this would seem to be to leave the
> text in the HTML5 spec and RFC4946 as-is, but to:
> 
>  1. Have somebody create a tiny Internet Draft that provides a
>     general explanation of what the "license" link relation is.
> 
>  2. Have that ID cite both the HTML5 spec and RFC4946 for details
>     about how the "license" link relation is used in the
>     technologies defined by those two specs.
> 
> -- 
> Michael(tm) Smith
> http://people.w3.org/mike

--
Mark Nottingham   http://www.mnot.net/