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

Sebastian Nagel commented on TIKA-2744:
---------------------------------------

Hi Martin,
afaics, the MIME type detection works for the Jira issue RSS exports:
{noformat}
% java -jar tika-app-1.19.1.jar -d 
https://issues.apache.org/jira/si/jira.issueviews:issue-xml/TIKA-2744/TIKA-2744.xml
...
application/rss+xml
{noformat}
... and also for the attached test document:
{noformat}
% java -jar tika-app-1.19.1.jar -d ./rsstest.xml
application/rss+xml
{noformat}

Parsing of rsstest.xml fails but that's ok given that the content is ill-formed 
XML.

Could you share more details how you are testing?

> rss+xml doesnt accept files with .xml extension
> -----------------------------------------------
>
>                 Key: TIKA-2744
>                 URL: https://issues.apache.org/jira/browse/TIKA-2744
>             Project: Tika
>          Issue Type: Bug
>            Reporter: Martin
>            Priority: Major
>         Attachments: rsstest.xml
>
>
> Hello, 
> if i try to validate application/rss+xml file with .xml extension and it 
> fails. 
> I would say, that is a bug.
> I think the .RSS extension is only until version 1.0. From 2.0 is rss xml 
> based and it should(could) have .xml extension:
> Source:
> https://www.w3schools.com/xml/xml_rss.asp 
> "Get Your RSS Feed Up On The Web
> Having an RSS document is not useful if other people cannot reach it.
> Now it's time to get your RSS file up on the web. Here are the steps:
> 1. Name your RSS file. Notice that the file must have an .xml extension."
> or specification on Harvard university:
> https://cyber.harvard.edu/rss/rss.html
> there is example:
> "Its value is the name of the RSS channel that the item came from, derived 
> from its <title>. It has one required attribute, url, which links to the 
> XMLization of the source.
> Example of file:



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to