Changes between Version 3 and Version 4 of NewCapDesign


Ignore:
Timestamp:
2009-07-15T08:03:36Z (15 years ago)
Author:
warner
Comment:

minor formatting changes

Legend:

Unmodified
Added
Removed
Modified
  • NewCapDesign

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