To view parent comment, click here.
To read all comments associated with this story, please click here.
Aaron already answered this, but just a bit more detailed: the acquired relation data is stored in an relation database separate from the file. Thus the file itself remains "clean".
For some kind of data it might make sense to also store it in the file or in extended file system attributes. This is currently not implemented AFAIK and as Aaron pointed out, would be subject to policies.
For some kind of data it might make sense to also store it in the file or in extended file system attributes. This is currently not implemented AFAIK and as Aaron pointed out, would be subject to policies.
IMHO all such metadata information should be stored per-file, ie. in extended attributes cos then it could be shared by all users. And I don't really like the idea of a single database with all the metadata cos it could get corrupted, or if it got deleted one way or another you'd lose ALL metadata. But to have public and private metadata saved per-file would most likely require modifications to existing filesystems, or a completely new one. Hopefully this will happen, I'm sure a lot of people would find such a thing useful even if I can't imagine myself gaining much from that.







Member since:
2006-02-15
I just started thinking about something..If you f.ex. save a file from an email, and the saved file automatically acquires metadata such as the sender's email address, couldn't this be considered potentially a threat if there's several users on the same computer? If the file's metadata is readable by other users and they have read-access to even some of your files, they could learn email addresses of the people you stay in contact with etc. In that case it'd help if the metadata was accessible only by the owner of the file, but what if sooner or later f.ex. system files are populated with metadata? The only way I can think of how to fix that would be to have two kinds of metadata: private and public.