[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gzz] Simple Storm again
From: |
Tuomas Lukka |
Subject: |
Re: [Gzz] Simple Storm again |
Date: |
Wed, 2 Apr 2003 11:36:44 +0300 |
User-agent: |
Mutt/1.4.1i |
On Wed, Apr 02, 2003 at 12:56:20AM +0200, Benja Fallenstein wrote:
>
> Hi all,
>
> please have a look at the 'simple storm' PEG again. If nobody's opposed,
> I'd like to start using this soon, in order to get on with Storm.
Couple of clarifications and questions below, will accept once
these are resolved.
> - Won't dropping headers make it harder to include metadata?
>
> RESOLVED: MIME headers are a non-extensible form of metadata
> anyway; if we allow ``X-`` headers, we have problems with
> permanence. We can still put metadata into another block
> refering to this one; alternatively, many file formats
> allow inclusion of metadata in the file itself (e.g. PNG).
Clarification:
Or also you can use blocks of a mime type that is metadata + another
block reference.
> I suggest that we may look at the header issue again
> related to pointers. Instead of having pointer URIs,
> we might have 'reference' URIs which give the hash
> of a metadata block used to retrieve the actual data.
> This metadata block could be used to implement the HTTP
> features as well as pointers and CC licenses.
How are headers of a stable block related to pointers? I don't understand.
Maybe just remove this paragraph for now?
> - Why bitzi bitprint? What is it? Why not SHA-1?
>
> RESOLVED: Bitprints are a combination of a SHA-1 hash with a
> Merkle hash tree based on the Tiger hash algorithm.
> Hash algorithms get broken; when one of the above
> is broken, you have a transitional period before
> the other is, too, in which you can e.g. sign blocks,
> ensuring you can still use them when the other
> is broken too.
Heh... AJK, remember my reductio ad absurdum? ;)
Tuomas