Subject: Re: A common VFS and a Common conf-system (Was: namespacing)

[Sean Middleditch]

On Tue, 2005-03-01 at 13:38 +0100, Timo Stuelten wrote:
>Hi!
>
>> Sean Middleditch <elanthis at awesomeplay.com> wrote:
>> Target profile for Desktop VFS 1.0:
>> * Read whole documents including meta-data
>> * Read just document meta-data
>> ...
>> Also note that I didn't define the data items in the vfs_metadata_t
>> type, although doing so is very important.  I'll get to those later.
>
>What type of metadata do you have in mind? Some sort of key-value-pairs 
>(like xfs-xattrs or ogg), with or without special named keys and strings 
>or somehow typed values? 
>So some sort of "Give me the name, type, .time and some other 
>cheap to get data of 'some:uri'" or some "metadata-resolver-mechanism 
>which can be used to get automatic playlists for spoken-word-audiofiles 
>heard in the last 3 weeks"?

I'm open to suggestions.  ;-)  The main things are of course file size,
MIME type, etc.  It would be nice to be able to get a list of key/value
pairs that map to EAs or DAV properties.  If a backend wants to add
additional "magic" values, it would make sense to provide a namespace
for that as well.  Then a Storage backend could do its magic, or
whatever.

>
>(All desktops would benefit from some sort of reasoner support and query 
>mechanism on metadata (this RDF/OWL/Weltformel thingy) -- but I think this 
>type of (support for) metadata is not what is meant by this lib, is 
>it? :)
>
>-Timo-
>
-- 
Sean Middleditch <elanthis at awesomeplay.com>