- From: Michael Toomim <toomim@gmail.com>
- Date: Tue, 19 Nov 2024 17:18:15 -0800
- To: Julian Reschke <julian.reschke@gmx.de>, ietf-http-wg@w3.org
Received on Wednesday, 20 November 2024 01:18:21 UTC
On 11/2/24 12:54 AM, Julian Reschke wrote:
> On 02.11.2024 03:12, Michael Toomim wrote:
>> Julian Reschke wrote:
>>> At the end of the day, the question is: do you want the version to be
>>> bookmarkable and retrievable by user agents that do not know your
>>> protocol? If yes, it needs an HTTP(s) URL.
>>
>> I do not want those features to be provided within the scope of this
>> spec.
>>
>> I understand that they are useful features, but I think this is a
>> separate concern that can be deliberated separately.
>
> How would that work if the version doesn't have a URI? You can't change
> how bookmarks function on the web...
To get bookmarkable versions, a separate spec would define a set of URIs
U that map to versions V of a resource R.
It might say something like:
> Doing a GET request on URI U is equivalent to a GET request on R
plus the header "Version: V"
This would be in a separate spec.
Received on Wednesday, 20 November 2024 01:18:21 UTC