XMP, Krita, KFileMetaInfo and Strigi

[Sebastian Trüg]

Hi guys,

my 2 cents from the Nepomuk point of view:

XMP seems to be a pseudo-standard already in use so there is no point in 
trying to replace it with a Nepomuk ontology. In addition the XMP data is 
stored in the file itself (right?). That is why I thought Nepomuk could not 
solve the problem right away. What would be of interest however, would be to 
also store the data in Nepomuk to make it searchable and linkable. maybe for 
this we need a bridging ontology that links XMP data with data specified in 
Nepomuk ontologies.

But as far as KFileMetaData is concerned I also think it would be good to make 
it powerful enough to handle the metadata used in Krita. However, since the 
KDE API is frozen, how about you, Cyrille, model your xmp lib very closely to 
kfilemetadata so it can easily be merged in KDE 4.2 or 5.0 or whatever.

Cheers,
Sebastian


On Friday 22 June 2007 10:21:52 Jos van den Oever wrote:
> Hi Cyrille,
>
> I read your post on metadata in Krita and would like to point you to
> the KDE4 way of handling metadata to make sure all applications
> benefit from your efforts.
>
> - getting metadata
>   For retrieving metadata, one should write a strigi analyzer. Doing
> so makes the data available for indexing in Strigi and Nepomuk and
> KFileMetaInfo. There's a tuturial on techbase and plenty of example in
> the strigi codebase.
>
> - writing metadata
>   For this there are two possibilities which should be merged at some
> point. You can write data into a file by implementing a KFileWritePlugin.
> This allows you to write into the file via the KFileMetaInfo
> interface. You can also annotate data via the Nepomuk interface.
>
> I'd love to help you with this effort, since obviously XPM is an
> important file format. We can even add the analyzers directly in
> Strigi so all apps benefit from the get go.
>
> Cheers,
> Jos