2001-12-18 15:18:20 +0000 <sjanes71> maybe not realizing that they had something important...
2001-12-18 15:18:39 +0000 <sjanes71> or more often, just not knowing where the files are without a search
2001-12-18 15:19:16 +0000 <sjanes71> the metadata on files has shrunk and shrunk to the point where it's not really useful for the user anymore
2001-12-18 15:19:43 +0000 <sjanes71> it's just there to tell the operating system which application to use to "open" the file
2001-12-18 15:19:55 +0000 <sjanes71> or who's allowed to open the file, etc.
2001-12-18 15:20:15 +0000 <sjanes71> this metadata isn't extensible at all by the user, or if it is, it's really not easy to do
2001-12-18 15:21:16 +0000 <sjanes71> if you right-click on a file in W2K Pro, there's a tab called "Summary"
2001-12-18 15:21:38 +0000 <sjanes71> which has some fields like "Title", "Subject", "Keywords"
2001-12-18 15:22:13 +0000 <sjanes71> there's no way to add new kinds of metadata
2001-12-18 15:22:38 +0000 <sjanes71> things like... a "Role"-- aka "Why" you're interested in the dat.
2001-12-18 15:22:40 +0000 <sjanes71> data.
2001-12-18 15:23:32 +0000 <sjanes71> so I imagine a computer should have some kind standard way of associatig metadata with data... that combines all the needs
2001-12-18 15:23:33 +0000 <shapr> what would you like to add other than Role?
2001-12-18 15:24:30 +0000 <sjanes71> Role, Task, Goal, When, Where, How, Disclosure, Permanance
2001-12-18 15:25:25 +0000 <sjanes71> ... but more importantly, the user has to be able to create new kinds of metadata as they need it... and the operating system should just be able to index it as if it were "core metadata"
2001-12-18 15:25:28 +0000 <shapr> have you tried to put together a mockup with a separate file holding metadata?
2001-12-18 15:26:09 +0000 <sjanes71> I have tried to do it with some shell scripts, but I haven't gotten it to a point where I really like it
2001-12-18 15:26:27 +0000 <sjanes71> it could be simulated with files and directories
2001-12-18 15:26:57 +0000 <sjanes71> it just gets messy because filesystems really want to be hierarchical
2001-12-18 15:27:04 +0000 <sjanes71> boxes within boxes
2001-12-18 15:27:55 +0000 <shapr> the extra bits could be done with the recursive boxes just fine
2001-12-18 15:28:00 +0000 <shapr> for example, streams in ntfs
2001-12-18 15:28:09 +0000 <shapr> they're parts of the file that most programs can't see
2001-12-18 15:28:13 +0000 <sjanes71> hmm
2001-12-18 15:28:37 +0000 <shapr> the extra bits you've suggested still sound like they're attached to files
2001-12-18 15:29:01 +0000 <sjanes71> they're really attached to streams in the end
2001-12-18 15:29:12 +0000 <sjanes71> streams of data that have a type
2001-12-18 15:30:12 +0000 <sjanes71> in my mind this o/s should also make versioning of data a core service... ala cvs.. you can eventually tell the o/s to "purge" the data...
2001-12-18 15:30:36 +0000 <sjanes71> but otherwise, all applications then inherit the ability to rollback bad changes
2001-12-18 15:31:10 +0000 <sjanes71> instead of having to do it by themselves
2001-12-18 15:32:02 +0000 <sjanes71> By hand I'm simulating it with a directory called "My Roles"
2001-12-18 15:32:25 +0000 <sjanes71> where I've made subdirectories of various roles... "Webmaster", "SysAdmin", "Home Owner".. etc.
2001-12-18 15:32:40 +0000 <sjanes71> so I collect bookmarks and files and documents in those directories
2001-12-18 15:33:05 +0000 <sjanes71> When I want to put on the "Webmaster" hat, I just find that Webmaster directory
2001-12-18 15:33:50 +0000 <sjanes71> but because of the directories, there's no easy way of showing myself a timeline across everything I've bee doing