[jira] Resolved: (TIKA-308) Improve supertype handling in type registry

["Jukka Zitting (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TIKA-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting resolved TIKA-308.
--------------------------------

         Assignee: Jukka Zitting
    Fix Version/s: 0.8
       Resolution: Fixed

Done in revision 955959. The type registry now uses the full set of both built-in and configured type hierarchy information.

> Improve supertype handling in type registry
> -------------------------------------------
>
>                 Key: TIKA-308
>                 URL: https://issues.apache.org/jira/browse/TIKA-308
>             Project: Tika
>          Issue Type: Improvement
>          Components: mime
>    Affects Versions: 0.4
>            Reporter: Ken Krugler
>            Assignee: Jukka Zitting
>             Fix For: 0.8
>
>
> When processing tika-mimetypes.xml, additional supertype information should be set so that the right parser gets called if there's no explicit parser for that mime-type.
> Jukka suggested:
> The type registry could do with some implicit supertype settings like the following (in order):
> * a type with an explicit <sub-class-of/> setting is a specialization
> of the specified type
> * a type with parameters is a specialization of the same type without parameters
> * all */*+xml types are specializations of application/xml
> * all text/* types are specializations of text/plain
> * everything is a specialization of application/octet-stream

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.