[httpapi] Re: Link Hint 02 feedback
Mark Nottingham <mnot@mnot.net> Thu, 27 February 2025 01:29 UTC
Return-Path: <mnot@mnot.net>
X-Original-To: httpapi@mail2.ietf.org
Delivered-To: httpapi@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 667C0275C89 for <httpapi@mail2.ietf.org>; Wed, 26 Feb 2025 17:29:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 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, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_SBL_A=0.1] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietfa.org (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b="VFLrJhqP"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="Ok+Gwtpi"
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietfa.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uEtmXTRWrDon for <httpapi@mail2.ietf.org>; Wed, 26 Feb 2025 17:29:56 -0800 (PST)
Received: from fout-a1-smtp.messagingengine.com (fout-a1-smtp.messagingengine.com [103.168.172.144]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 2C9F3275C30 for <httpapi@ietf.org>; Wed, 26 Feb 2025 17:29:39 -0800 (PST)
Received: from phl-compute-01.internal (phl-compute-01.phl.internal [10.202.2.41]) by mailfout.phl.internal (Postfix) with ESMTP id 19FAB1382ED4; Wed, 26 Feb 2025 20:29:39 -0500 (EST)
Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-01.internal (MEProxy); Wed, 26 Feb 2025 20:29:39 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=cc :cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm2; t=1740619779; x=1740706179; bh=56PbN1PWfWZrg84DadkqA8VLSeg11Y4+Bx3IPOEyJNY=; b= VFLrJhqP1L/S/toZWh89hUJJDB4VnZc1ND1QYxIFCkwyMvG1wlBbR9FUiKV8JrFB Ic6UW8e2yumnTW2xdbKtSmNBhr5mCRbQR09O6+HoQVRRXGYB5CA1zA4c+U+OQ4NF xMnrlcLoPXcl7CyGcuO1cK13R8PJiBYkrpzHm+MssGTZpOr4Y2RGdKgnyOJPqKpB TSHF0mr+vFlyQ9SbEoeNSDZM9KBQLmOFT9IKIFhnzs4K3Nwzr6n6ajTkqO2QyDuv UXTmPWQ0sHJsuC1GJ9+8ZSa7pIIo1xW30hoA1d+7AU6vr+ShgoMhrot/yOEjyOTP MwCp2XuMnFW2W6y7XvChZA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1740619779; x= 1740706179; bh=56PbN1PWfWZrg84DadkqA8VLSeg11Y4+Bx3IPOEyJNY=; b=O k+GwtpirpyQiaXOQRPAwCA1Pb32V5oVFiAXLgtNIi4bZ7MXsoxdp0k/wjp8+MXio u3qw18c9ZuJ2LdVlmyBlsYfKBPJnRxIzlojMeMX3lmsqyUbfFxFo241ZlumNoA0M zQb6nOqJGhxlx4H2vznmxb7MTcX8189CAz5TTlwEIwu4EEZL1nzw9Lu9jah8I9d0 2qpAgO4vE5KQPmwe0WnokF0/6mbl+Ee7f8L4MroZUu6J6CvvOsEx3H+iZED18sXq ogzORmdX1II92gU3wz6iIo/rPmKLsM3bDmQSdPV+nzkXLQ7SZl4EjyqZmyK6xtiv 0ZucxdYwZ5wx6khoa9s3g==
X-ME-Sender: <xms:AsC_ZyNlbW4S0SjcVJLaazSApYQlIg3dO5SrYaIH_B1wK64AIwvTZw> <xme:AsC_Zw-eqyvW6sn_513ABSokebvEEBfK0N4RmhDhIsP4s-n01iqQ9UbKH1DFKCBt1 OzO6ZUDMZVfdZUiAg>
X-ME-Received: <xmr:AsC_Z5QeSHfvkvz85fmhBNBfSTC6ZbE-Tu8EurFf12JTlOijxV805RD0qRCTHrxJPvJ5poCehs_VGGZYnp5HLVPFDZPySTcvlq-B6urQnYEsTbxQkU4TwCN7>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefvddrtddtgdekieduiecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpggftfghnshhusghstghrihgsvgdp uffrtefokffrpgfnqfghnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivg hnthhsucdlqddutddtmdenucfjughrpegtggfuhfgjffevgffkfhfvofesthhqmhdthhdt jeenucfhrhhomhepofgrrhhkucfpohhtthhinhhghhgrmhcuoehmnhhothesmhhnohhtrd hnvghtqeenucggtffrrghtthgvrhhnpeejuddtteevkeekuefhgfefudeugeetueffkeev udeukefhvdelgfelteelvdffgfenucffohhmrghinhepihgvthhfrdhorhhgpdhgshdurd horhhgpdhphhhilhgrrhgthhgvrhdrohhrghdphhhvughsohhmphdrihhnfhhopdhorhgt ihgurdhorhhgpdhmnhhothdrnhgvthenucevlhhushhtvghrufhiiigvpedtnecurfgrrh grmhepmhgrihhlfhhrohhmpehmnhhothesmhhnohhtrdhnvghtpdhnsggprhgtphhtthho pedvpdhmohguvgepshhmthhpohhuthdprhgtphhtthhopehphhhilhdrrghrtghhvghrse hgshdurdhorhhgpdhrtghpthhtohephhhtthhprghpihesihgvthhfrdhorhhg
X-ME-Proxy: <xmx:AsC_ZytpgWKb_BNcLjKJDeN14c-4IDPjUb6h-G1p748kmtF2CL-ofg> <xmx:AsC_Z6ctfq-IupupXSSxNeLPiGZSRhEslXsmt8uBj6PL01giGcQK4w> <xmx:AsC_Z20WmH6k0hZFBz_cQTl88IKum_OzQpG1Nj532Pt7zZhzlnV0gg> <xmx:AsC_Z-8LATAoQIwOYz3Rx4wkzzY48d5L4r1lpaFsG6wEEDpL4PIeYA> <xmx:A8C_Z6788Z0xatqwfYmydyAtBIk0O0bnNFHLHt-anOzFqw9A8hD5QH1R>
Feedback-ID: ie6694242:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 26 Feb 2025 20:29:37 -0500 (EST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.400.131.1.6\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <PH0PR08MB98621DFB70D95937C06C9958B7C22@PH0PR08MB9862.namprd08.prod.outlook.com>
Date: Thu, 27 Feb 2025 12:29:35 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <878DEFA7-8631-4055-83AB-B09B27B3B1AE@mnot.net>
References: <AF875164-4064-4AD0-8DBA-92869D18AEF3@mnot.net> <0C580CFF-982C-44C5-A255-768FF48AEC93@gmail.com> <PH0PR08MB98621DFB70D95937C06C9958B7C22@PH0PR08MB9862.namprd08.prod.outlook.com>
To: Phil Archer <phil.archer@gs1.org>
X-Mailer: Apple Mail (2.3826.400.131.1.6)
Message-ID-Hash: I352PMJVJAY7IBDD6NG2S4SY6CHEUBSW
X-Message-ID-Hash: I352PMJVJAY7IBDD6NG2S4SY6CHEUBSW
X-MailFrom: mnot@mnot.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "httpapi@ietf.org" <httpapi@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [httpapi] Re: Link Hint 02 feedback
List-Id: Building Blocks for HTTP APIs <httpapi.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/ySZNK5pE4Efpv8DouZ-OMy7pUPc>
List-Archive: <https://mailarchive.ietf.org/arch/browse/httpapi>
List-Help: <mailto:httpapi-request@ietf.org?subject=help>
List-Owner: <mailto:httpapi-owner@ietf.org>
List-Post: <mailto:httpapi@ietf.org>
List-Subscribe: <mailto:httpapi-join@ietf.org>
List-Unsubscribe: <mailto:httpapi-leave@ietf.org>
Hmm. RFC 6906 defines the profile link relation, but AFAIK there isn't any way to communicate this in HTTP. Since the scope of this effort is *HTTP* based hints, we should probably define how to do that first. I think the options are: 1) Just use the Link header field 2) Put a parameter on the media type 3) Define a new field (1) is problematic because it requires modelling all possible links as hints, and that adds complexity that we're trying to get away from. Web linking is great if you need to have integration between links expressed in content and headers (for example), but for protocol-level details (such as something you might use for lower-layer dispatch, like a media type) it really should be a primary protocol mechanism, not something buried down inside a generic mechanism like this. In particular you don't want to force someone to parse all of the links on a response just to get one bit of information out if it's on the critical path. (2) is problematic IIRC because it's effectively usurping individual media types' ability to control their own name space (would have to check with the media type folks to be sure) and parameters are stripped/dropped by some software (still?). That might just leave (3). I know that <https://datatracker.ietf.org/doc/html/draft-svensson-profiled-representations> started down this path; personally I'd go a bit further and a) define a Profile header rather than reusing Link, and b) making it a Client Hint (since we have that now). Cheers, > On 26 Feb 2025, at 11:15 pm, Phil Archer <phil.archer@gs1.org> wrote: > > Thanks very much for working on this, Mark. I can see the potential in GS1's implementation of RFC 9264 (Herbert and Erik W's work on Linksets). > > An issue that has been around for a long time is that a media type is often only half the story. An application will typically want content that is serialized as, say, application/json, but it wants JSON that uses a specific vocabulary/data model. A hint of 'profile', that takes a URI as value, would probably be sufficient for this? Then a service can offer links to the same data (I'm thinking product descriptions but could be anything), following different data models, all of which are serialized as JSON. > > Phil > > --- > > Phil Archer > Web Solutions Director, GS1 > https://www.gs1.org > > https://philarcher.org > +44 (0)7887 767755 > @philarcher.bsky.social > > -----Original Message----- > From: Herbert Van de Sompel <hvdsomp@gmail.com> > Sent: 26 February 2025 11:15 > To: Nottingham Mark <mnot@mnot.net> > Cc: httpapi@ietf.org > Subject: [httpapi] Re: Link Hint 02 feedback > > Hi Mark > > Thanks for the helpful clarification. > > I’m totally ok with simplification too. As you indicate, it’s about “hints”. > > Greetings > > Herbert > >> On Feb 26, 2025, at 09:08, Mark Nottingham <mnot@mnot.net> wrote: >> >> Hi Herbert, >> >> This draft is a transitional step away from using JSON as the base data model. What I'd like to do is to use a subset of JSON or Structured Fields data types, and then describe how to map them into another format. What I've done here is to start that process by removing the most complex structures (objects). >> >> It'd be helpful to know how people feel about this -- especially whether the constraint and loss of information is acceptable. Personally I'm OK with it, since 'hints' shouldn't be too detailed (IMO). >> >> Cheers, >> >> >>> On 26 Feb 2025, at 6:53 pm, Herbert Van de Sompel <hvdsomp@gmail.com> wrote: >>> >>> hi all, >>> >>> I was happy to see the publication of a new version of the Link Hints I-D. I do want to share some feedback: >>> >>> (1) From the outset of this effort, I have failed to understand the motivation for making JSON the canonical serialization format. I assume that boat has sailed but think that the draft would benefit from some extra wording to make it more accessible to those who are more familiar with HTTP/HTML links: >>> >>> (*) Given there is no formal definition of the canonical JSON structure for Link Hints, a description of the opening example provided in Section 2 would be helpful for those less familiar with expressing links in JSON. >>> >>> (*) Since Appendix A describes how JSON Link Hints are mapped to links in the HTTP header, it would be helpful to represent the examples provided there in a verbose manner that aligns with the opening example of Section 2: >>> - this would allow understanding where the rel="sample" comes from in >>> both examples >>> - this would allow understanding how the content of the second example relates to that of the Section 2 example. That is really not obvious to me, because the content of the second example is contained in square brackets that I can't seem to map to the opening example. >>> - use of a more realistic/intuitive complex example might also help. >>> >>> (*) It might be nice to include an example/appendix regarding representation of Link Hints in (JSON) Link Sets. >>> >>> (2) Section 5.1 lists some reserved names. Should "anchor" and "title*" be included there? It looks like title* would not be allowed on the basis of the restricted character set for Link Hints but maybe being explicit could be helpful? >>> >>> Greetings >>> >>> Herbert >>> >>> -- >>> ================== >>> Herbert Van de Sompel >>> https://hvdsomp.info >>> https://orcid.org/0000-0002-0715-6126 >>> -- >>> httpapi mailing list -- httpapi@ietf.org To unsubscribe send an email >>> to httpapi-leave@ietf.org >> >> -- >> Mark Nottingham https://www.mnot.net/ >> > > -- > httpapi mailing list -- httpapi@ietf.org To unsubscribe send an email to httpapi-leave@ietf.org > > CONFIDENTIALITY / DISCLAIMER: The contents of this e-mail are confidential and are not to be regarded as a contractual offer or acceptance from GS1 (registered in Belgium). > If you are not the addressee, or if this has been copied or sent to you in error, you must not use data herein for any purpose, you must delete it, and should inform the sender. > GS1 disclaims liability for accuracy or completeness, and opinions expressed are those of the author alone. > GS1 may monitor communications. > Third party rights acknowledged. > (c) 2020. -- Mark Nottingham https://www.mnot.net/
- [httpapi] Link Hint 02 feedback Herbert Van de Sompel
- [httpapi] Re: Link Hint 02 feedback Mark Nottingham
- [httpapi] Re: Link Hint 02 feedback Herbert Van de Sompel
- [httpapi] Re: Link Hint 02 feedback Phil Archer
- [httpapi] Re: Link Hint 02 feedback Mark Nottingham
- [httpapi] Re: Link Hint 02 feedback Herbert Van de Sompel
- [httpapi] Re: Link Hint 02 feedback Darrel Miller
- [httpapi] Re: Link Hint 02 feedback Herbert Van de Sompel