You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Tim Allison (Jira)" <ji...@apache.org> on 2021/05/26 17:11:00 UTC
[jira] [Commented] (TIKA-3421) Obsoleted mime types
[ https://issues.apache.org/jira/browse/TIKA-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17351944#comment-17351944 ]
Tim Allison commented on TIKA-3421:
-----------------------------------
My personal pref would be to keep everything as long as the definition is precise/unique. I _think_ we have digital preservation folks who might use Tika, and they may come across old files.
That definition troubles me...
[~nick] and fellow devs, what say you?
> Obsoleted mime types
> --------------------
>
> Key: TIKA-3421
> URL: https://issues.apache.org/jira/browse/TIKA-3421
> Project: Tika
> Issue Type: Improvement
> Components: core
> Reporter: Gannon McGibbon
> Priority: Minor
>
> We're currently using Tika's `tika-mimetypes.xml` to detect mime types for files based on extensions and magic in [rails/marcel|https://github.com/rails/marcel]. I'm wondering what Tika's stance is on retiring deprecated/obsolete mime types.
> In [an issue|https://github.com/rails/marcel/issues/4], someone reported that the [message/news|https://www.iana.org/assignments/media-types/message/news] type was matching on any text file beginning with "Article". While this magic rule seems a little aggressive to me, the type has also been [deprecated by the IANA|https://www.iana.org/assignments/media-types/message/news] since 2009. Does Tika ever plan on removing support for deprecated types such as this? If not, I can change our XML parsing rules to reject certain types.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)