We could then build lean, database-less asset management applications, while the user data (i.e. the files and their metadata) would always be portable, across platforms.
Take for example:
J.M.W. Turner | Rain, Steam and Speed | ···· 1844.jpg
W. Blake ···· | Newton ·············· | 1795–1805.jpg
It’s just an idea for HN Idea Sunday; I did a somewhat more detailed write-up:
but some standard way of expressing it in the file name would be great, and nicer to parse out later. There are filesystems that allow metadata, but I've never seen one really being used for that purpose. You could make some associated command line tools that are equivalent to 'ls' that allow splitting/slicing the files down different parameters.
It has support for database-like extended file attributes, which can be custom attributes!
For example, a `person` file would have all of the normal fields you'd expect from an address book as file attributes: http://www.birdhouse.org/beos/byte/24-scripting_the_bfs/ https://www.haiku-os.org/docs/userguide/en/attributes.html
Though you seem to be against specific file systems due to non-portability and that is understandable.
Imagine managing a collection of photos (or a mixed collection of multiple file formats, like scans of receipts, and pdfs with invoices) in something like Dropbox: no access to hidden low-level metadata blocks, etc., let alone easy editing. Not to speak of cross-platform support.
File names are always visible and editable, and they’re easily parsable.
I discussed such objections here: https://gist.github.com/rhythmus/11118629#problem-metadata-p...