Re: [httpapi] JSON serialization for Web Linking

Evert Pot <me@evertpot.com> Sun, 15 November 2020 22:57 UTC

Return-Path: <me@evertpot.com>
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 35C1F3A103C for <httpapi@ietfa.amsl.com>; Sun, 15 Nov 2020 14:57:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=evertpot.com header.b=Xevy88ck; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=pUe0UGiq
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 XX-jqtpbxxGj for <httpapi@ietfa.amsl.com>; Sun, 15 Nov 2020 14:57:05 -0800 (PST)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 584623A101C for <httpapi@ietf.org>; Sun, 15 Nov 2020 14:57:05 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 47B755C00D7 for <httpapi@ietf.org>; Sun, 15 Nov 2020 17:57:04 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Sun, 15 Nov 2020 17:57:04 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=evertpot.com; h= subject:to:references:from:message-id:date:mime-version :in-reply-to:content-type; s=mesmtp; bh=9fuMdLpRCZot4O2j7SBJvl+M P8H151MnPd/AxSbtpTk=; b=Xevy88ckIJCBnCJr4pRWHz52dwUtTgfmlxH4NSWa OuqJYcepLqa2C2WefXEoQxiN+Y6bMzlBEkLPgXZQiJbi/k2AyAF45qazoO+uyjVh bVAnvVPYsPI/8ixdh4aL2e+ORWUPgEeQEtoxf05glOA3ulhfpsjmkVM+BRTFv6k1 9Po=
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=fm1; bh=9fuMdL pRCZot4O2j7SBJvl+MP8H151MnPd/AxSbtpTk=; b=pUe0UGiq/nw/C+nfV2/7IC 04Vu4vJRwSUdeeYoO6mGPPrDDSgvfKfCGEPhJNbXczCkQuDYuDG26YHWeRCpHfSr SIMAP4IPlesq7Fzv/h6Anh0drt+5IBD25tQY2qbjBr/v0yuO1SjDjPPYDKeURQTh QlpDwcJYh7wOX3dJ/C/q2Ce6qPHEQn2wikIDqa7whZBf7IfqCshVddim7gX1qczY bTh1/IQDBsGPQnWgwzKroOVCsuWfOBXEj3V4yVUXHr+h5WVxH5Xi+lsaxwrg/HRn thW5yMeflp/18iF8pXqak7i9P6RplK5f5mtF7O8N2O7dyylGJ2PxXXp7ZJr3pffg ==
X-ME-Sender: <xms:P7KxX6XmGpsJ0GM7Le0tsWCtNlvifSKyP_VxdDU0k6pEZyEHioITDg> <xme:P7KxX2mOvjP-M7qWHXcwS5mvX7eqwodqgzce207CK58iLi6VyDfP2tePns3lrvwUt eUnLD1waXcn8JFd>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrudeftddgtdehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefuvfhfhffkffgfgggjtgesrgdtre ertdefheenucfhrhhomhepgfhvvghrthcurfhothcuoehmvgesvghvvghrthhpohhtrdgt ohhmqeenucggtffrrghtthgvrhhnpedvteevheejudelkeelveduvdffgfeuueekfeehge eiieeghfekgeejiedtueeltdenucffohhmrghinhephhhtthhprdhithdpshgthhgvmhgr rdhorhhgpdhivghtfhdrohhrghenucfkphepudegvddruddviedrudehfedrleehnecuve hluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhgvsegvvhgv rhhtphhothdrtghomh
X-ME-Proxy: <xmx:P7KxX-ZQQYqqaqmFl1qIOx6OeHmNd5YCY3McqcUCJRM7nooyZLMOfw> <xmx:P7KxXxWCadmiTK6cBqHsA0wspZ7bt4dgyEGxB9k_7frw7XdQIqFSsw> <xmx:P7KxX0kFa7rTXSkgxzP9-NfrlT9UsN1ebZoXsg1JCRo6Ma4VWhYxng> <xmx:QLKxXwyh4RDjqUqjOuuTXdc5oYp57w-JMfgtKlFHsMkAressE7BS9w>
Received: from [192.168.2.61] (unknown [142.126.153.95]) by mail.messagingengine.com (Postfix) with ESMTPA id C96D73280065 for <httpapi@ietf.org>; Sun, 15 Nov 2020 17:57:03 -0500 (EST)
To: httpapi@ietf.org
References: <5a806987-70c7-e7fe-e773-11625d9c51dc@evertpot.com> <c5aa2c46-571f-47a1-da30-62b36d996ce3@dret.net> <ae814f24-50fa-5eb3-0f42-988eb6b6d8e1@evertpot.com> <3bf0efa9-10f3-30e2-2173-2e7f2140ea89@dret.net> <DM6PR00MB084512239A74950A7B08F26AF0E41@DM6PR00MB0845.namprd00.prod.outlook.com>
From: Evert Pot <me@evertpot.com>
Message-ID: <f27b9129-b618-947f-5a07-f5bf3aa23f0b@evertpot.com>
Date: Sun, 15 Nov 2020 17:57:00 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.3.2
MIME-Version: 1.0
In-Reply-To: <DM6PR00MB084512239A74950A7B08F26AF0E41@DM6PR00MB0845.namprd00.prod.outlook.com>
Content-Type: multipart/alternative; boundary="------------EE7BE01DEF18EC18E54529F0"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/t0v8lbO83OoI068z_qNIff1uptQ>
Subject: Re: [httpapi] JSON serialization for Web Linking
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: Sun, 15 Nov 2020 22:57:14 -0000

Hi Darrel,

On 2020-11-15 5:26 p.m., Darrel Miller wrote:
>
> Hey Evert,
>
> While I agree it would be great if there were a common way of 
> serializing links across media types, I’m concerned we are going to 
> head down a path of bikeshedding.  I remember a lot of debates when 
> HAL chose to use an object to serialize links instead of an array.  
> There were valid arguments for both the array form and the object 
> form.  It is a warning sign for me that these two drafts take the 
> opposite approaches.
>
I 100% agree, it would be better if the two drafts used the same format.

> My other concern is it seems like the intent of the draft is to try 
> and standardize a concept that will then be used by other media types 
> and frameworks. Your draft does declare the application/links+json but 
> that seems like a secondary goal of the spec.  While I understand the 
> desire to create standard building blocks for JSON documents, such a 
> mechanism doesn’t exists within HTTP.  It seems more closely related 
> to efforts like schema.org.
>
>
I think it's definitely fair to say that this draft does not directly 
tie to HTTP, and more to JSON in a more general way. I thought this 
could be a good place to submit it here nonetheless. The group is 
described as "Building Blocks for HTTP APIs", and given that many HTTP 
APIs are ultimately going to be using JSON, and there's a good chance 
they would want to encode a link, it feels like the perfect building block.

My hope is that afterwards, json-links may be extended to get other 
formats to rfc status, such as:

https://tools.ietf.org/html/draft-nottingham-json-home-06
https://tools.ietf.org/html/draft-nottingham-link-hint-02

There's so many efforts in this space that will have a need for this. I 
hope we can look past things like the array/object bike-shedding and get 
behind something that is generally good enough.

If taking out the bits around "application/links+json" and 
document-level links gives this a higher chance of success, I think this 
is worth it.

Evert