Request for review of EmotionML media type: application/emotionml+xml

Kazuyuki Ashimura <> Thu, 10 May 2012 16:30 UTC

Received: from (localhost []) by (8.14.5/8.14.3) with ESMTP id q4AGU4BF019258 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 10 May 2012 09:30:04 -0700 (MST) (envelope-from
Received: (from majordom@localhost) by (8.14.5/8.13.5/Submit) id q4AGU4td019257; Thu, 10 May 2012 09:30:04 -0700 (MST) (envelope-from
X-Authentication-Warning: majordom set sender to using -f
Received: from hamachi ( []) by (8.14.5/8.14.3) with ESMTP id q4AGU2u1019252 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for <>; Thu, 10 May 2012 09:30:04 -0700 (MST) (envelope-from
Received: from ([] helo=[]) by hamachi with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <>) id 1SSWFc-0006AI-Qk; Fri, 11 May 2012 01:30:00 +0900
Message-ID: <>
Date: Fri, 11 May 2012 01:28:48 +0900
From: Kazuyuki Ashimura <>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
Subject: Request for review of EmotionML media type: application/emotionml+xml
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
List-Archive: <>
List-ID: <>
List-Unsubscribe: <>

Dear list,

W3C has just published a Candidate Recommendation for "Emotion Markup
Language (EmotionML)" at:

I am sending this request to ask the Ietf-types list for comments on
the Media Type section of the EmotionML specification following the
procedure defined at:

The Media Type section of the EmotionML specification is available

and a plain text copy is also available below.

MIME media type name:

MIME subtype name:

Required parameters:

Optional parameters:

         This parameter has identical semantics to the charset parameter 
of the application/xml media type as specified in [RFC3023] or its 

Encoding considerations:
     By virtue of EmotionML content being XML, it has the same 
considerations when sent as "application/emotionml+xml" as does XML. See 
RFC 3023 (or its successor), section 3.2.

Security considerations:
     EmotionML elements may include arbitrary URIs. Therefore the 
security issues of [RFC3986], section 7, should be considered.

     In addition, because of the extensibility features for EmotionML, 
it is possible that "application/emotionml+xml" will describe content 
that has security implications beyond those described here. However, if 
the processor follows only the normative semantics of this 
specification, this content will be ignored. Only in the case where the 
processor recognizes and processes the additional content, or where 
further processing of that content is dispatched to other processors, 
would security issues potentially arise. And in that case, they would 
fall outside the domain of this registration document.

Interoperability considerations:
     This specification describes processing semantics that dictate the 
required behavior for dealing with, among other things, unrecognized 

     Because EmotionML is extensible, conformant 
"application/emotionml+xml" processors MAY expect that content received 
is well-formed XML, but processors SHOULD NOT assume that the content is 
valid EmotionML or expect to recognize all of the elements and 
attributes in the document.

Published specification:
     This media type registration is extracted from Appendix B of the 
"Emotion Markup Language (EmotionML) 1.0" specification.

Additional information:
     Magic number(s):

         There is no single initial octet sequence that is always 
present in EmotionML documents.

     File extension(s):

         EmotionML documents are most often identified with the 
extensions ".emotionml".

     Macintosh File Type Code(s):


Person & email address to contact for further information:
     Kazuyuki Ashimura, <>rg>.

Intended usage:

Author/Change controller:
     The EmotionML specification is a work product of the World Wide Web 
Consortium's Multimodal Interaction Working Group. The W3C has change 
control over these specifications.

Normative References:

RFC 3023
  XML Media Types, M. Murata et al., Editors. IETF RFC 3023, January 2001.



Kaz Ashimura, W3C Staff Contact for Web&TV, MMI and Voice
Tel: +81 466 49 1170