You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tika.apache.org by Apache Wiki <wi...@apache.org> on 2012/04/25 18:13:53 UTC

[Tika Wiki] Trivial Update of "MetadataRoadmap" by JoergEhrlich

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Tika Wiki" for change notification.

The "MetadataRoadmap" page has been changed by JoergEhrlich:
http://wiki.apache.org/tika/MetadataRoadmap?action=diff&rev1=1&rev2=2

   Still no client changes needed.<<BR>><<BR>>
   I. '''Use XMP instead of Hashmap in Metadata class'''<<BR>><<BR>>
   The idea is to have just one data model which is able to faithfully store all metadata information. The XMP data model provides that. The Metadata API will be kept as is, just the internal representation of the data will be moved to XMP data model. To be able to map from the API to the internal data model, the static mapping table that has been introduced in step 2 will be used. (see picture 1)<<BR>><<BR>>
-  Any client provided that cannot be mapped to existing namespaces, will be stored in a special Tika namespace in XMP.<<BR>>
+  Any client provided data that cannot be mapped to existing namespaces, will be stored in a special Tika namespace in XMP.<<BR>>
   Add an access API to the internal XMP object to the Metadata API for clients or parsers who want to directly work on the XMP data model. The alternative would be to add a complete XMP API to the Metadata class, but it is the question whether that is feasible or worth the effort.<<BR>><<BR>>
   The XMP output handler can be declared deprecated.<<BR>><<BR>>
   Still no client has to change.<<BR>><<BR>>