[Gzz-commits] gzz/Documentation/Manuscripts/URN5 urn5.rst

[Benja Fallenstein]

CVSROOT:        /cvsroot/gzz
Module name:    gzz
Changes by:     Benja Fallenstein <address@hidden>      02/11/14 14:30:18

Modified files:
        Documentation/Manuscripts/URN5: urn5.rst 

Log message:
        comments

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/gzz/Documentation/Manuscripts/URN5/urn5.rst.diff?tr1=1.1&tr2=1.2&r1=text&r2=text

Patches:
Index: gzz/Documentation/Manuscripts/URN5/urn5.rst
diff -u gzz/Documentation/Manuscripts/URN5/urn5.rst:1.1 
gzz/Documentation/Manuscripts/URN5/urn5.rst:1.2
--- gzz/Documentation/Manuscripts/URN5/urn5.rst:1.1     Thu Nov 14 14:07:30 2002
+++ gzz/Documentation/Manuscripts/URN5/urn5.rst Thu Nov 14 14:30:17 2002
@@ -10,7 +10,7 @@
 ABSTRACT
 ========
 
-Our research group has recently registered the informal {\tt urn-5} namespace
+Our research group has recently registered the informal ``urn-5`` namespace
 with IANA. We discuss the rationale behind the namespace and
 possible applications of this open namespace.
 
@@ -22,6 +22,11 @@
 how globality has become important now that the net makes places around
 the world accessible.
 
+Benja says:
+    Hmm... how to present this in an interesting way? Can we sketch
+    some kind of "timeline of identification"? Where to go to find
+    the relevant facts?
+
 - snailmail addresses
 - IP addresses
 - DNS
@@ -50,6 +55,21 @@
 **And** you need a domain name, which has all the problems
 of hierarchy, DNS abuse etc.
 
+Benja says:
+   We need to get the point across that we're not saying
+   "here are the other namespaces and here is what ours
+   does better"; I don't even want to say "and here is
+   why ours is better for these applications." I want it
+   to be more like, "Here is what applications tag URIs
+   are better for, and here is what urn-5 is better for."
+
+   (E.g. tags are domain name based, but are arguably much
+   better when humans mint identifiers themselves. I think
+   that even applies to Gzz-- it would not be too bad if
+   some core dimension names were tag URIs, so that
+   you could actually *see* what they are when browsing
+   the file format.)
+
 Should we go through all the urn types briefly?
 
 
@@ -144,12 +164,40 @@
 to create havoc. This problem is really no different from the corresponding
 one with digital signatures: you have to trust the software you use.
 
-Another: no way to verify an index. Anyone may spoof an id easily.
-Therefore, you can't really refer to an id outside the current context:
-too easy to substitute another document for it.
+Tuomas once said:
+    Another: no way to verify an index. Anyone may spoof an id easily.
+    Therefore, you can't really refer to an id outside the current context:
+    too easy to substitute another document for it.
+
+Benja notes:
+    As was clarified in the following discussion, Tuomas' statement above
+    *makes no sense*. urn-5s, by themselves, *never* refer to documents.
+    They are not resolvable. Documents may only state that they have
+    something to do with a urn-5, and a search may be performed and return
+    that; but that doesn't mean that you can make a reference,
+    'show the document identified by this urn-5, here.'
+
+    We have to be really careful to get this point across correctly,
+    beca
 
 Coupling urn-5 with digital signatures?
 
+Benja says:
+    This needs an own URI type, if we want to take this approach,
+    combining an identity (a person) with a urn-5 or tag URI.
+    I.e., something like::
+
+        urn:pointer:<person>:<sub-uri>
+
+    where ``<person>`` is some way to identify an entity (public key
+    won't suffice, because public keys can change), and ``<sub-uri>``
+    could be a urn-5.
+
+    It's an open research problem how to associate ``<person>`` 
+    identifiers with entities in a way that doesn't require central
+    assignment and does allow changing an entity's public key.
+    (Freenet gets around the problem by identifying entities
+    by unchangeable public keys; not nice.)