IETF Logo Mail Archive

Re: [httpapi] Fwd: New Version Notification for draft-nottingham-link-template-03.txt

Max Maton <info@maxmaton.nl> Thu, 02 September 2021 00:50 UTC

Return-Path: <info@maxmaton.nl>
X-Original-To: httpapi@ietfa.amsl.com
Delivered-To: httpapi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 339463A2092 for <httpapi@ietfa.amsl.com>; Wed, 1 Sep 2021 17:50:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.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 Yua9kjsRuzAX for <httpapi@ietfa.amsl.com>; Wed, 1 Sep 2021 17:50:19 -0700 (PDT)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D9923A2097 for <httpapi@ietf.org>; Wed, 1 Sep 2021 17:50:19 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 6F8D25C00FD; Wed, 1 Sep 2021 20:50:18 -0400 (EDT)
Received: from imap44 ([10.202.2.94]) by compute5.internal (MEProxy); Wed, 01 Sep 2021 20:50:18 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=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=uXjEET +Evn7fbKoh6rzxID4uYd5JZBmGa3wGcW/U+po=; b=gtTzqcZDJegq4W3TY5Sek6 R3dWbmc+URTmdHPKlYUkgY8lwPesmFwHdH1BvLgu/yl+GW9UW8EQSeZvuxyAeLJs OLZht/9AbyQAvWYmRDhikYpESPa4T/GeEXAemlWYfiwbfhXGZ3aMz3ly49gOjbaE RY/Xnpv1pXWhGGxjpYOkXU9HikalewV5scySi1a2hYcr7a/KCTs9GCeuCoJyc6SQ 0ejcxE2ashhgPYg+3/jaRqvaZfs5bllwFPMRSdpZiu/e9OUkD3l3OGTqrLPmJFw7 b52rHbMfce1alYtyv8lmYfZ2XfVj56StlUMn6SImt19XMiBrgfdrvrXlYyzTznRQ ==
X-ME-Sender: <xms:yR8wYWJV7TQs7aFQpgSEENJJWsTWa7JQVunow90JZADoy4LBFfEmkQ> <xme:yR8wYeKCEb5z6GZJfcFR4tuz8NmtwboStZEnrHbyRT0Vz14JLnepOuKCA-aBK7iVR aSOpnLP9tGWWD4img>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddruddvgedgfeekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesrgdtreerreerjeenucfhrhhomhepfdforgig ucforghtohhnfdcuoehinhhfohesmhgrgihmrghtohhnrdhnlheqnecuggftrfgrthhtvg hrnhepteelhfeggeegjedufeetgedttdeltefgvdegtdfhieetiefglefhveejgeegffdu necuffhomhgrihhnpehivghtfhdrohhrghdpmhhnohhtrdhnvghtnecuvehluhhsthgvrh fuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepihhnfhhosehmrgigmhgrthho nhdrnhhl
X-ME-Proxy: <xmx:yR8wYWsexESeK3PgxxzsEFmmnmogETGb3KsQ6sc4BbI6ikGJNdHjCg> <xmx:yR8wYbaBXJR91VVRXJbMpVv1zosUBvbrX2Ith4IKTtNN5ebIrHBDHA> <xmx:yR8wYdaC-OuItUxHE5BfY3ZNEdWsJuoMJEuDZNtvXkqmOvBg7bXW_w> <xmx:yh8wYf1v-hjD33wg-k-ATWRYnfSKq9IxqbkPIhavCqB8zEqIGr1DCQ>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 43570FA0AA4; Wed, 1 Sep 2021 20:50:17 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-1126-g6962059b07-fm-20210901.001-g6962059b
Mime-Version: 1.0
Message-Id: <5d5ed837-1a47-4363-8f8a-ed065f9f2edb@www.fastmail.com>
In-Reply-To: <63DA4A31-930D-444D-9A4D-A639DB4D22E6@mnot.net>
References: <163047452150.9745.15606863469504346040@ietfa.amsl.com> <63DA4A31-930D-444D-9A4D-A639DB4D22E6@mnot.net>
Date: Thu, 02 Sep 2021 02:49:53 +0200
From: Max Maton <info@maxmaton.nl>
To: Mark Nottingham <mnot@mnot.net>, httpapi@ietf.org
Content-Type: multipart/alternative; boundary="173be9473d8a460389fb0e4d4a0237a0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/b_bOL1HG9f7rICUjJS9KHwuyt2A>
Subject: Re: [httpapi] Fwd: New Version Notification for draft-nottingham-link-template-03.txt
X-BeenThere: httpapi@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Building Blocks for HTTP APIs <httpapi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/httpapi>, <mailto:httpapi-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/httpapi/>
List-Post: <mailto:httpapi@ietf.org>
List-Help: <mailto:httpapi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/httpapi>, <mailto:httpapi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Sep 2021 00:50:27 -0000

Hi Mark,

It seems an interesting proposal, currently we use the Link header with an `templated="true"` property. I have a two questions:

 - Am I correct in assuming that the variables are defined by the media type documentation for the returned Content-Type?
 - If so, wouldn't it make sense to leave the var-base out of the specification, given that people defining media types are free to add parameters and are free to define rules about how to resolve the variables? 

Best regards,

Max Maton



On Wed, Sep 1, 2021, at 07:36, Mark Nottingham wrote:
> Hi all,
> 
> I've had this spec on the back burner for a *long* time, because I wanted to make sure it was actually useful to someone before progressing it.
> 
> I've heard from a few people that it would be useful for them in the real world, so I'd like the WG to consider adoption.
> 
> Any thoughts?
> 
> Cheers,
> 
> 
>> Begin forwarded message:
>> 
>> *From: *internet-drafts@ietf.org
>> *Subject: **New Version Notification for draft-nottingham-link-template-03.txt*
>> *Date: *1 September 2021 at 3:35:21 pm AEST
>> *To: *"Mark Nottingham" <mnot@mnot.net>
>> 
>> 
>> A new version of I-D, draft-nottingham-link-template-03.txt
>> has been successfully submitted by Mark Nottingham and posted to the
>> IETF repository.
>> 
>> Name: draft-nottingham-link-template
>> Revision: 03
>> Title: The Link-Template HTTP Header Field
>> Document date: 2021-09-01
>> Group: Individual Submission
>> Pages: 5
>> URL:            https://www.ietf.org/archive/id/draft-nottingham-link-template-03.txt
>> Status:         https://datatracker.ietf.org/doc/draft-nottingham-link-template/
>> Html:           https://www.ietf.org/archive/id/draft-nottingham-link-template-03.html
>> Htmlized:       https://datatracker.ietf.org/doc/html/draft-nottingham-link-template
>> Diff:           https://www.ietf.org/rfcdiff?url2=draft-nottingham-link-template-03
>> 
>> Abstract:
>>   This specification defines the Link-Template HTTP header field,
>>   providing a means for describing the structure of a link between two
>>   resources, so that new links can be generated.
>> 
>> 
>> 
>> 
>> The IETF Secretariat
>> 
> 
> --
> Mark Nottingham   https://www.mnot.net/
> -- 
> httpapi mailing list
> httpapi@ietf.org
> https://www.ietf.org/mailman/listinfo/httpapi
>

v2.23.0 | Report a Bug | By Email