New answers tagged


It would be remiss to neglect the original Mac HFS with its core support of the Resource Fork. A normal Macintosh file had two forks: the data fork, and the resource fork. The resource fork was a key/value store, with the values typically being large binary blobs (most notably icons, code, sounds, etc.). The data fork was where typical "read" and &...


I'll admit to not quite understanding their jargon, but it looks like IBM's AS/400 (1988) and to a certain extent, System/38 before it (1978) relied on object or database-style single-level storage rather than hierarchical files.


The BeOS used extended attributes heavily. In OS/2, rexx scripts are tokenised into extended attributes, and all sorts of things like icons and whatnot used them. There were a decent arrangement of tools to access and edit the ea's. 4os2 could store its descriptions in ea.


The Sinclair QL's file system has a 64-byte "File header" providing metadata for the file. Among system-owned fields like modified/access dates, file length, type and name, it also holds 8 bytes of so-called "type-dependent data" that can be used by specific file types for their own metadata. Due to the structure of QDOS I/O, that header ...


AmigaOS, first released in 1985, made extensive use of key/value attributes that could be defined by the user in a GUI and recognized by any tool. (e.g. an application/program). This was done using a metadata system implemented through "Tool types" that were embedded within the .info file. Every Tool or Project (e.g. a document) had an icon and ...

Top 50 recent answers are included