For me a basic tag based file system needs several things: A unique ID for files (a strong cryptographic hash of the contents is probably best), a name for each file, and a list of tags for each files. And of course, a number of logical volumes on which the files are "located". Where a directory structure is actually needed, files could have special names, like "/os/glad/file_42" (that's a name, not a path).
A variation on this theme would be to do away with explicit names altogether, and only use tags. The "name" of the file would just need to be reasonably unique. That one is probably best.
Now, when you search for a file, you just query for tags. Can also be done through the shell: it's just that those two commands would have the exact same effect:
cd /foo/bar
cd /bar/foo
As for the volume, you need them to transfer files between your USB key and your computer.
Oh, thinking of using cryptographic hashes to name files… When you modify the file, the ID changes as well… that's a
new file! By default, the old version should still be around. Imagine that: Git for the masses.
A variation on this theme would be to do away with explicit names altogether, and only use tags. The "name" of the file would just need to be reasonably unique. That one is probably best.
Now, when you search for a file, you just query for tags. Can also be done through the shell: it's just that those two commands would have the exact same effect:
As for the volume, you need them to transfer files between your USB key and your computer.Oh, thinking of using cryptographic hashes to name files… When you modify the file, the ID changes as well… that's a new file! By default, the old version should still be around. Imagine that: Git for the masses.