- From: Liam R. E. Quin <liam@fromoldbooks.org>
- Date: Sat, 23 Feb 2019 20:05:28 -0500
- To: Melvin Carvalho <melvincarvalho@gmail.com>, Dimitri Zagidulin <dzagidulin@gmail.com>
- Cc: W3C Credentials Community Group <public-credentials@w3.org>
On Sun, 2019-02-24 at 01:00 +0100, Melvin Carvalho wrote: > > "EquihashProof2017": "sec:EquihashProof2017", [...] > Look at all these year specific references. That indicates that the > vocab is likely to change at least once a year. I think here it's just from the convention to include the year a resource was published in the URI, and should not be taken to reflect stability (or otherwise). And > also what happens when one hash changes to another (also the hash of > what exactly!)? A hash (checksum) of the linked resource. > > None of this is necessary if you put URIs inline, On the contrary, that's a security problem, because then you don't find out there's been an update to patch a vulnerability. So, there's tradeoffs here. For sure there shouldn't be a single point of failure in a distributed system. That's a good catch. Liam -- Liam Quin, https://www.delightfulcomputing.com/ Available for XML/Document/Information Architecture/XSLT/ XSL/XQuery/Web/Text Processing/A11Y training, work & consulting. Web slave for vintage clipart http://www.fromoldbooks.org/
Received on Sunday, 24 February 2019 01:06:12 UTC