XML output from SearchRequest contains XML entities valid only in XML 1.1

One of our customers answered to JIRA notification using e-mail seemingly with a binary data (attachment?) (see ). Then when we in Atlassian Connector retrieve all issues matching some filter (with $applicationContext/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml) we get XML file which contains XML entities (escaped characters) which are invalid in XML 1.0, and valid only in XML 1.1 - e.g. https://studio.atlassian.com/secure/attachment/10674/SearchRequest-10021.xml

My quick research showed that XML 1.1 was not really widely adopted (e.g. newest FireFox and Opera browsers, Java JDOM) don't parse correctly XML 1.1 files.
Only IE and J-Xerces passed my tests.

People in the industry (e.g. here claim that it's better to stick to XML 1.0 whenever we can and generally than XML 1.1 is a new unnecessary standard.

I think that JIRA should generate valid XML 1.0 instead of XML 1.1 files.
Quick dive into JIRA sources revealed that responsible code for escaping characters in search request XMLs is here.

One more thing: JIRA does not include proper

<?xml version="1.1" ?>

header in generated XMLs, so anyway such data by default will be parsed as XML version 1.0 which fails (even with Xerces).

You may refer to real scenario at https://studio.atlassian.com/browse/PL-863