[ 
https://issues.apache.org/jira/browse/TIKA-784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152985#comment-13152985
 ] 

Jukka Zitting commented on TIKA-784:
------------------------------------

bq. For now, I've invented mimetypes for the subtypes, but we might decide we 
want to have them all use the official type with parameters instead?

Is there code that needs to distinguish between these subtypes based on only 
the media type? The DITA type registration document seems to imply that all 
applications that process DITA should be able to deal with all subtypes, so 
having separate media types for them all is not needed.

I didn't quite understand how the "type" and "format" parameters of the type 
are supposed to be used. If they map to these separate kinds of DITA files, 
then using those to distinguish between the subtypes sounds like the correct 
approach.

If we do invent new media types, I would recommend that we stick with the 
.../x-tika-... pattern to make it clear that these are not generally used types.
                
> Mimetype entry for DITA
> -----------------------
>
>                 Key: TIKA-784
>                 URL: https://issues.apache.org/jira/browse/TIKA-784
>             Project: Tika
>          Issue Type: Improvement
>          Components: mime
>    Affects Versions: 1.0
>            Reporter: Nick Burch
>
> Currently, we don't have mimetype entries for DITA. There is a provisional 
> mimetype
> According to 
> http://docs.oasis-open.org/dita/v1.2/cs01/spec/non-normative/DITA-mime-type.html
>  there is a provisional mimetype of "application/dita+xml" for DITA files
> There are then three kinds of DITA file, which apparently all use the same 
> mimetype:
>  DITA Topic - .dita
>  DITA Map - .ditamap
>  DITA Conditional Processing Profile - .ditaval
> DITA is XML based, so we should be able to do XML detection in addition to 
> filename matching

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to