Hello,

I have started to implement the new metadata engine for Krita2 (a replacement 
of the Exif engine which was, well, tied to Exif), the new one is designed 
around XMP and RDF (some RDF features are not in XMP, and are not supported 
yet by the framework) which is much more extensible. But it shouldn't be tied 
to any storing backend.

Here is the page where I put my thought on handling metadata : [1], it's very 
specific to Krita.

And the starting implementation here : [2] and the editor [3] (it's a page 
dialog whose page are created from UI file which allows to get extension)

I don't think metadata is handled differently in other applications than in 
Krita, unless OASIS decide not to go the XMP/RDF road for ODF, but reading 
[4] I think it will. So if there is an interest, I am ready to share the 
framework.

While the design was conceived to be adapted to krita's need, I accept 
constructive comments to make the framework usuable by other application, 
including:
 - comments on the API, especially I am not very happy with my use of 
QVariant, I need the Value class because of the need to associate a 
PropertyQualifier, but I wonder if there isn't a better way to handle this, 
maybe Q_DECLARE_METATYPE, but it looks worse to me)
 - and if you need more (but not less)

Don't forget to CC me if you want me to see your answer.

References:
[1] http://wiki.koffice.org/index.php?title=Krita/Metadata
[2] http://websvn.kde.org/trunk/koffice/krita/image/metadata/
[3] 
http://websvn.kde.org/trunk/koffice/krita/plugins/viewplugins/metadataeditor/
[4] Metadata Use Cases for ODF 
http://www.oasis-open.org/committees/download.php/19226/Metadata_UseCases14July2006.pdf
-- 
Cyrille Berger
_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel