News for hackers. Stuff that matters.
Re:Trusty URIs: Verifiable, Immutable, and Permanent Digital... by tkuhn on Friday October 17, 2014 @12:25PM (#8471722)
I am the main author of the paper. Happy to discuss and clarify if needed.
Re:Trusty URIs: Verifiable, Immutable, and Permanent Digital... by edwintorok on Friday October 17, 2014 @04:43PM (#8473251)
What happens to other URLs embedded in the document that you link to with trusty URLs (other than self-references?). For example your document could include images, and javascript that could completely the meaning of the document, while keeping the hash of the document the same.

Do you require all URLs contained in the document to be trusty URIs too?

Re:Trusty URIs: Verifiable, Immutable, and Permanent Digital... by tkuhn on Saturday October 18, 2014 @06:22AM (#8475068)
No, there can be contained URIs that are not trusty (probably the majority of contained URIs will be of that type). You can verify the entire reference tree as long as you follow trusty links, but of course this cannot go on indefinitely. Furthermore not all resources have the form of what I call a "digital artifact" (e.g. foaf:knows does not stand for a digital artifact), but they reach out to the real world (these URIs might not even return a representation, i.e. they might not be URLs).
Re:Trusty URIs: Verifiable, Immutable, and Permanent Digital... by ac2u on Friday October 17, 2014 @02:01PM (#8472380)
Could this be combined with JSON Web Tokens as a hybrid implementation that would be compatible with existing JWT/HMAC libraries?
Re:Trusty URIs: Verifiable, Immutable, and Permanent Digital... by tkuhn on Saturday October 18, 2014 @06:10AM (#8475058)
I cannot really answer this, as I am not familiar at all with JWT/HMAC...