On Feb 9, 2009, at 9:41 AM, Jukka Zitting wrote:
Because they are useful pieces of metadata that are already accurately
defined in the respective XMP schemas. I for example didn't propose
changing the MIDI metadata key "patches", as AFAIK there is no
standard schema that covers that piece of information.
Thats what I realized after I slept on it.
You create a new class that takes the raw key-value pairs that
stored in
Tika::Metadata and translates them to something else. Call it
Metadata2XMP
or whatever. That can be packaged within Tika as a convenient class
that does least common denominator mapping in a well defined way.
Having such a mapping class within Tika is an alternative, but as
discussed in the Dublin Core thread [1] in December, I'm not sure if
it's worth the added complexity. My proposal covers the use case with
much less extra code or documentation.
Storing the raw metadata in Metadata according to its native ontology
is most important thing. Which seems to be a consensus from the
December thread you linked to.
--
Jonathan Koren
jonat...@soe.ucsc.edu
http://www.soe.ucsc.edu/~jonathan/
