Hi, On Mon, Mar 10, 2008 at 12:18 PM, Jeremias Maerki <[EMAIL PROTECTED]> wrote: > Of course, some properties might be missing which Tika might need. But > they can be defined by Tika in your own schema [...]
Instead of missing some properties, I'm more concerned about the fact that the wide variety of XMP properties will put off a number of potential users and that we have little chance of enforcing consistency across parser implementations. > [...] you can provide your own adapter class for easy, type-safe access. That sounds like a good approach. We could make the Tika Metadata class be an XMPMeta adapter that provides simple getters and setters for the most commonly used types of metadata. Parsers and clients that produce or need more detailed metadata can directly access the underlying XMP model, while others can ignore the underlying complexity. BR, Jukka Zitting
