Changes between Version 3 and Version 4 of NewCapDesign

Timestamp:

2009-07-15T08:03:36Z (15 years ago)

Author:

warner

Comment:

minor formatting changes

NewCapDesign

@@ -19 +19 @@
    vs non-hierarchical segments. What's magical about a leading double-slash?
    Do we need one?
- * according to #683, a URI !!!identifies!!! a resource, but does not
+ * according to #683, a URI '''identifies''' a resource, but does not
    necessarily provide enough information to actually access it (i.e. if you
    have a URI and somebody pointed you at a file, you could confidently tell
    them whether or not it was the right file, but if you only have the URI,
-   nyou might not be able to find the file without additional information). If
+   then you might not be able to find the file without additional information). If
    the cap has both identifying and location information, it's called a URL.
  * Tahoe filecaps are meant to be URLs (they are intended to provide location
@@ -53 +53 @@
    non-word-breaking string. The next best will be to have a large
    non-word-breaking string at the start and end, with smaller segments (if
-   necessary) in the middle.
+   necessary) in the middle. Note that {{{tahoe:}}} is an easy target, but
+   {{{x-tahoe:}}} is not (you'd have to double-click on the "x").
  * Usable in a browser. Specifically, it should be easy to actually use a
    filecap that you get in email or IM, and many email/IM clients will look
@@ -116 +117 @@
    {{{tahoe://grid1234/D/MR/cryptobits}}} should reference
    {{{tahoe://grid1234/MR/cryptobits}}}. (#403)
- * #102 has notes on dircaps
+ * #102 and #217 have notes on dircaps