Request: Report queries should treat a xmltype column as a xmlelement

Question

In the shared components you can define a report query for creating PDF reports for example.
APEX will transform the results of the defined sql query to xml on runtime.
Each column of the query becomes a xmlelement. The values of the column will be the text data of the xmlelement.
In the current APEX versions a xmltype column in the sql query is not supported sadly enough.
I would like to see that if a column is a xmltype that APEX treats its values as a xmlelement and not as text.
This way it makes it possible to construct more meaningful xml structures using sqlx functions (xmlelement, xmlagg, etc...)
For example:
Report query
select xmlelement("USER",xmlattributes(u.user_id as "ID")
,xmlelement("NAME",u.username)) users
from all_users u
where rownum < 3
will now be transformed in
<?xml version="1.0" encoding="UTF-8"?>
<ROWSET>
<ROW>
<USERS>[unsupported data type]</USERS>
</ROW>
<ROW>
<USERS>[unsupported data type]</USERS>
</ROW>
</ROWSET>
It should be:
<?xml version="1.0" encoding="UTF-8"?>
<ROWSET>
<ROW>
<USERS>
<USER ID="0">
<NAME>SYS</NAME>
</USER>
</USERS>
</ROW>
<ROW>
<USERS>
<USER ID="5">
<NAME>SYSTEM</NAME>
</USER>
</USERS>
</ROW>
</ROWSET>
Or make it an option that it is possible to define a xml query instead of a sql query.
APEX doesn't have transform the query results in to xml on runtime, because the result is already a xml.
For example:
XML query
select sys_xmlagg (sys_xmlgen (xmlelement ("USERS"
,xmlelement ("USER"
,xmlattributes (u.user_id as "ID")
,xmlelement ("NAME"
,u.username)))))
users
from all_users u
where rownum < 3
results in:
<?xml version="1.0"?>
<ROWSET>
<ROW>
<USERS>
<USER ID="1">
<NAME>SYS</NAME>
</USER>
</USERS>
</ROW>
<ROW>
<USERS>
<USER ID="5">
<NAME>SYSTEM</NAME>
</USER>
</USERS>
</ROW>
</ROWSET>

Answer 1

Thank you for a quick response, but I am really surprised/confused by your answer.
User-agent already reports operating system. Adding the width/height of the device is not really any more private than that and is definitely not a personally identifiable information. What does it have to do with privacy?
We are not asking to report any device capability that Javascript does not already have access to. So if somebody wanted to gather the information s/he could already gather it by making an Ajax request through Javascript. The only difference is: that won't help images or Responsive Web efforts in a clean way.
Bottomline: this information is already available and is not of a Private Identifiable category. We just need to make it available in a manner in which it can be used for good.