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

Nick Burch commented on TIKA-784:
---------------------------------

bq Is there code that needs to distinguish between these subtypes based on only 
the media type? 

I'd like to be able to tell the difference between them, so I can label them 
differently in the UI. While I think any application that works with DITA 
should normally be able to handle all the different files, editors and content 
stores may well want to display or filter them differently. So, I think being 
able to tell them apart is useful.

Reading through the registration document, as well as the issue for tracking 
registration, I think we can probably use the format parameter to distinguish 
the different DITA file types, such as "application/dita+xml;format=map" or 
"application/dita+xml;format=topic". (Can't see any evidence of anyone else 
doing this though, but it does look to be the suggested way to handle it)

If no-one spots a problem with this, I'll change to using those
                
> 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