I'd recommend picking a specific file extension for richmedia+xml, because "svg" will already be pre-configured in most Web servers to map to the image/svg+xml media type. You might also want to talk about when it is/isn't appropriate to use image/svg+xml under "interoperability considerations". Also, the descriptions of the parameters should be included in the registration rather than implicitly referencing the specification. It also seems there's some security considerations to their use, so that should be documented here. Mark. On Fri, Jan 9, 2009 at 10:37 AM, Hall, Edward, VF-Group <Edward.Hall@vodafone.com> wrote:
Dear IETF Types list,
I am writing to you as the OMA MCE Interim Chairman. We have recently approved the Rich Media Environment (RME) v1.0 as a candidate enabler at the OMA. As a result, we would like to socialise the registration of the associated MIME types for this specification. We would appreciate any comments you may have on this registration information.
Please feel free to review the specification linked for further details about the use of these potential MIME types, or contact me (or the copied OMA List) directly.
If you see any problems, please let us know.
Many thanks,
Eddy Hall
Edward Hall Standards Engineer II&S, Vodafone Group Technology - R&D
Mobile: +44 (0) 7717424404 E-mail: edward.hall@vodafone.com
Vodafone Group Services Limited Registered Office: Vodafone House, The Connection, Newbury, Berkshire RG14 2FN Registered in England No 3802001
For RME Initial Scenes:
Type name:
application
Subtype name:
richmedia+xml
Required parameters:
none
Optional parameters:
charset
useFullRequestHost
pathComponents
Encoding considerations:
Same as for application/xml. See [7]RFC3023 , section 3.2.
Security considerations:
The media type defines a Rich Media scene viewed by an end user.
It is possible for content to surge computational and memory resources from the receiver.
Therefore user confirmation is recommended before consuming this media type.
Interoperability considerations:
none
Published specification:
OMA Rich Media Enabler Technical Specification
The published enabler specification can be found at:
http://www.openmobilealliance.org/Technical/release_program/rme_v1_0.aspx
Applications that use this media type:
Applications implementing the Rich Media Enable Technical Specification.
Typically these are rich media environments on mobile devices.
Additional information:
Magic number(s): None
File extension(s): svg
Macintosh file type code(s): None
Person & email address to contact for further information:
Edward Hall, Vodafone Group
edward.hall@vodafone.com
Intended usage:
COMMON
Restrictions on usage:
none
Author:
The author of this specification is the Open Mobile Alliance working group Mobile Client Environment. See http://www.openmobilealliance.org/Technical/mobile_client_environ.aspx
Change controller:
Change control of this specification is done by the Open Mobile Alliance working group Mobile Client Environment. See http://www.openmobilealliance.org/Technical/mobile_client_environ.aspx
For RME Commands:
Type name:
application
Subtype name:
richmediacommand+xml
Required parameters:
none
Optional parameters:
charset
useFullRequestHost
pathComponents
Encoding considerations:
Same as for application/xml. See [7]RFC3023 , section 3.2.
Security considerations:
The media type defines update commands to data viewed by an end user.
Updates from an malicious source can perform harmful changes to the image viewed by the end user.
A specific form of updates consists of scripts executed by the receiver of the media type. If the scripting language so permits access to data
can be given allowing this data to be disclosed to unintended parties.
It is also possible for content to surge computational and memory resources from the receiver.
Therefore user confirmation is recommended before consuming this media type.
Interoperability considerations:
none
Published specification:
OMA Rich Media Enabler Technical Specification.
The published enabler specification can be found at:
http://www.openmobilealliance.org/Technical/release_program/rme_v1_0.aspx
Applications that use this media type:
Applications implementing the Rich Media Enable Technical Specification.
Typically these are rich media environments on mobile devices.
Additional information:
Magic number(s): None
File extension(s): scg
Macintosh file type code(s): None
Person & email address to contact for further information:
Edward Hall, Vodafone Group
edward.hall@vodafone.com
Intended usage:
COMMON
Restrictions on usage:
none
Author:
The author of this specification is the Open Mobile Alliance working group Mobile Client Environment. See http://www.openmobilealliance.org/Technical/mobile_client_environ.aspx
Change controller:
Change control of this specification is done by the Open Mobile Alliance working group Mobile Client Environment. See http://www.openmobilealliance.org/Technical/mobile_client_environ.aspx
Edward Hall Standards Engineer II&S, Vodafone Group Technology - R&D
Mobile: +44 (0) 7717424404 E-mail: edward.hall@vodafone.com
Vodafone Group Services Limited Registered Office: Vodafone House, The Connection, Newbury, Berkshire RG14 2FN Registered in England No 3802001