Fwd: HTML Catalogue File?

which group / CG would deal with this sort of issue?

one embodiment,

some standard means to identify the date the hyperlink was produced and the
option to either get the latest or the version that was available then (if
its available).  File needs to be supported by the web-server.  web-server
needs to know what file to deliver.  browser may need some method to
provide UX in how to navigate between an older version and a newer one.

https://chrome.google.com/webstore/detail/wayback-machine/fpnmgdkabkmnadcjpehmlllkndpkmiak
seems to do it via archive.org.

Theory would be to built this into WWW & file-system.

Perhaps there's an easier / better way to do it?

I also like the idea of using HTTP-Signatures to sign the various versions
(optionally perhaps rather than mandatorily).

Tim.H.


---------- Forwarded message ---------
From: Timothy Holborn <timothy.holborn@gmail.com>
Date: Sat, 4 Nov 2017 at 00:01
Subject: HTML Catalogue File?
To: public-rww <public-rww@w3.org>


Was thinking about version control.  One idea was to have some form of
catalogue file that stores previous versions, latest and various date
signatures, et.al.

point being that if someone references an uri sometimes the content on that
URI that was expected to be static; has changed.

wikipedia is a very good example.

tim.h.