Please review "application/richmedia+xml" and "application/richmediacommand+xml"

Hall, Edward, VF-Group Edward.Hall at vodafone.com
Fri Jan 9 16:37:54 CET 2009


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 at vodafone.com <mailto:edward.hall at 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.asp
x
<blocked::http://www.openmobilealliance.org/Technical/release_program/rm
e_v1_0.aspx>
<blocked::http://member.openmobilealliance.org/ftp/public_documents/bt/M
AE/Permanent_documents/OMA-TS-RME-V1_0-20071123-D.zip> 

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 at vodafone.com <blocked::mailto:edward.hall at 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
<blocked::http://www.openmobilealliance.org/Technical/mobile_client_envi
ron.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
<blocked::http://www.openmobilealliance.org/Technical/mobile_client_envi
ron.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.asp
x
<blocked::http://www.openmobilealliance.org/Technical/release_program/rm
e_v1_0.aspx>
<blocked::http://member.openmobilealliance.org/ftp/public_documents/bt/M
AE/Permanent_documents/OMA-TS-RME-V1_0-20071123-D.zip> 

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 at vodafone.com <blocked::mailto:edward.hall at 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
<blocked::http://www.openmobilealliance.org/Technical/mobile_client_envi
ron.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
<blocked::http://www.openmobilealliance.org/Technical/mobile_client_envi
ron.aspx> 

 
 
Edward Hall
Standards Engineer 
II&S, Vodafone Group Technology - R&D
 
Mobile: +44 (0) 7717424404

E-mail: edward.hall at vodafone.com <mailto:edward.hall at vodafone.com> 

 
Vodafone Group Services Limited 
Registered Office: Vodafone House, The Connection, Newbury, Berkshire
RG14 2FN Registered in England No 3802001

 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.alvestrand.no/pipermail/ietf-types/attachments/20090109/fdb5dcc9/attachment-0001.htm 


More information about the Ietf-types mailing list