On Donnerstag 02 Oktober 2008, Jason Tackaberry wrote:
> Ultimately the question comes down to: where should authoritative
> user-created metadata be stored?
>
> The two obvious responses are 1. keep user-generated metadata in an fxd
> file, and have beacon parse it and duplicate it in its database
> (updating the db when the fxd changes), or 2. store the user-generated
> metadata directly in beacon's db and treat it as authoritative.
>
> It would be a useful exercise to enumerate the pros and cons of each
> approach.

Yes, that's what I wanted to discuss.  Thinking about it, this discussion is 
absolutely not new.  In fact, this is the typical filesystem/metadata 
discussion, which appeared on all OS'es and desktop environments again and 
again, and which has lead to a lot of nice concepts and extended 
attributes/metadata-supporting filesystems (and a lot of vaporware a la WinFS 
or Reisers' vision).

I think freedesktop.org has lead to some standardization in this respect, and 
one might find libraries (I am thinking of what KDE4 etc. use) that allow 
dealing with such metadata without knowing where it is stored.  That may 
allow taking advantage of filesystems that support attaching such data 
directly to files (best option) and provide a transparent fallback solution 
for those that don't.  Actually, I was thinking about Nepomuk, but that does 
not seem to use extended attributes at all right now. :-/
http://nepomuk.semanticdesktop.org/

Nevertheless, using such libraries could be a 3rd option, but I don't want to 
imply at all that I believe this to be the best option.

> Cover images for readonly media would be stored in the overlay
> directory, which beacon does support directly.

Yes, that would obviously be the appropriate solution.  I'll eventually have a 
look at that, too (for now, I won't care about cover images).

-- 
Ciao, /  /                                                    .o.
     /--/                                                     ..o
    /  / ANS                                                  ooo

Attachment: signature.asc
Description: This is a digitally signed message part.

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Freevo-devel mailing list
Freevo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freevo-devel

Reply via email to