(last updated 2008-12-19) Registration Request: Type name: application Subtype name: cea-2018+xml Required parameters: none Optional parameters: none Note that (in contrast to application/xml) no charset parameter is defined since CEA-2018 specifies UTF-8 as the required file format. Encoding considerations: Same as encoding considerations of application/xml as specified in RFC 3023. Security considerations: All of the security considerations described in RFC 3023. Additionally, the inclusion of ECMAScript fragments (so-called "active content") in a CEA-2018 document bears risks in that a task-based application may execute malicious or erroneous ECMAScript code as part of a task model embedded condition or grounding statement. However, a task-based application will typically execute this code in sandbox and can thus prevent potential damage to local and other resources. Note that the embedded ECMAScript code fragments pose only minimal additional security risks for Web browsers since ECMAScript code is only embedded as content of XML elements other than