Hi, On Wed, Dec 3, 2008 at 1:05 PM, Robert Burrell Donkin <[EMAIL PROTECTED]> wrote: > should be simple enough to support minimal subclassing eg > tika:content-type -> dc:format
We could do that, but what's the use case? The primary use case I'm thinking of is having a clear set of metadata fields that I can easily map to specific fields in a search index. For this use case it doesn't really matter what metadata schema we use as long as it's clear enough and we are consistent in using it (e.g. all dc:format values produced by Tika would be MIME types, all dates of a specific format, etc.). A secondary use case is being able to easily use those fields when integrating with external metadata-aware applications. Here I think Dublin Core is the best alternative as I believe it's the most widely used and best understood (relatively speaking) metadata schema there is. Currently I don't see where using subclasses or alternative schemas would bring enough value to counter the added complexity, but I'd be happy be proven wrong. BR, Jukka Zitting
