[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gzz-commits] storm/doc/pegboard/simple_storm--benja peg.rst
From: |
Benja Fallenstein |
Subject: |
[Gzz-commits] storm/doc/pegboard/simple_storm--benja peg.rst |
Date: |
Thu, 03 Apr 2003 03:20:18 -0500 |
CVSROOT: /cvsroot/storm
Module name: storm
Changes by: Benja Fallenstein <address@hidden> 03/04/03 03:20:18
Modified files:
doc/pegboard/simple_storm--benja: peg.rst
Log message:
update simplestorm issues
CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/storm/storm/doc/pegboard/simple_storm--benja/peg.rst.diff?tr1=1.2&tr2=1.3&r1=text&r2=text
Patches:
Index: storm/doc/pegboard/simple_storm--benja/peg.rst
diff -u storm/doc/pegboard/simple_storm--benja/peg.rst:1.2
storm/doc/pegboard/simple_storm--benja/peg.rst:1.3
--- storm/doc/pegboard/simple_storm--benja/peg.rst:1.2 Tue Apr 1 17:55:14 2003
+++ storm/doc/pegboard/simple_storm--benja/peg.rst Thu Apr 3 03:20:18 2003
@@ -4,8 +4,8 @@
:Author: Benja Fallenstein
:Date: 2003-02-16
-:Revision: $Revision: 1.2 $
-:Last-Modified: $Date: 2003/04/01 22:55:14 $
+:Revision: $Revision: 1.3 $
+:Last-Modified: $Date: 2003/04/03 08:20:18 $
:Type: Architecture
:Scope: Major
:Status: Current
@@ -40,6 +40,9 @@
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).
+ We could also devise a MIME type or something that is
+ some RDF metadata plus a reference to the actual body block--
+ so we might simulate the old system when we need it.
Content types are now included in the block id (different
content type -> different block).
@@ -68,20 +71,10 @@
header blocks, making for a much more complex system
and separating namespaces in the Storm world.
- 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.
-
- I think that the best route for now is to have these
- two layers-- the simple, but in itself useful method
- of identification by mime type plus content hash;
- and, to be built, the more complex and potentially
- extensible system of refering to metadata that can
- point to the actual data in more complex ways
- (or simply include additional metadata like a CC license).
+ I think the best route is to have the simple system
+ specified here for now, and possibly extend it later
+ by another kind of reference which points to
+ a metadata block that then points to the actual body.
- What about the hash tree vulnerabilities mentioned in
<http://zgp.org/pipermail/p2p-hackers/2002-November/000993.html> /