RE: Call for Implementations of EmotionML published

Felix et al,

Implementation report for EMLPy library that generates EmotionML compliant documents is included.

Is there an interest in having a technical report available for the site? 

Thank you,
From: []
Sent: Monday, September 17, 2012 5:58 AM
Cc:;;; Begoli, Edmon;;;
Subject: AW: Call for Implementations of EmotionML published

Thanks Roddy,
That's good news.
Now the next step, as described in [1],
would be to deliver the report in form of an XML file with the format:

<system-report name="YOUR-SYSTEM-NAME-HERE">
        <assert id="100" res="pass|fail|not-impl">OPTIONAL-NOTES-HERE</assert>

What the assert-ids mean is described in [2], e.g.

<assert id="221" res="pass "> </assert>
means, in your implementation all dimension elements contain a "name" attribute

Or, another example
<assert id="118" res="not-impl "> </assert>
means, your implementation ignores appraisal-sets (and elements)

I attach as sample my report, from the Speechalyzer, if that helps.
If done, this file should be submitted to



-----Ursprüngliche Nachricht-----
Von: Roddy Cowie []
Gesendet: Samstag, 15. September 2012 16:16
An: Burkhardt, Felix;
Betreff: RE: Call for Implementations of EmotionML published

Dear all,
              We have uploaded a version of our trace program, Gtrace, which generates EmotionML outputs, to meet the revised deadline. The program and a manual can be downloaded from

Below is a sample output, which I have to say looks more intelligible than our old format.
Roddy Cowie

<emotionml version="1.0"



<emotion dimension-set="">
        <dimension name="potency">
                        samples="0.475 0.527 0.710 0.902 0.932 0.937 0.530 0.163 0.091 0.122 0.628 0.645 0.639"/>
        <reference uri="Bear.wmv#t=0.200,1.500"/> </emotion>


From: []
Sent: Tuesday, August 28, 2012 1:55 PM
Cc:;;; Roddy Cowie;;;
Subject: AW: Call for Implementations of EmotionML published

Thanks Abe
Yes please, submit to the list
Cite Kaz:
>Could you please send your implementation report to the MMI public list ( as the EmotionML Candidate Recommendation announcement [1] says?


And interesting point you raise about the "no space" requirement, I myself was not aware of this and there is an example ("being hurt") in the official WD by Marc and Catherine [2] that includes a space.
Also it says in the spec [3]:

name: a name for the item, used to refer to this item. An <item> MUST NOT have the same name as any other <item> within the same <vocabulary>.

So, I don't see a problem with spaces in names for the vocabulary.



Von: [] Im Auftrag von abe kazemzadeh
Gesendet: Dienstag, 28. August 2012 09:07
An: Burkhardt, Felix
Betreff: Re: Call for Implementations of EmotionML published

Hi Felix and all,
Here's an implementation report for the EMO20Q agent that you demoed.
I'm not sure if this is the right format for the report... Let me know if it need any fixing. I also have a human readable version (pdf) as well as the xml format given in .
The only issue is that there were a few words in our vocabulary with spaces (eg, "let down"). As a computer readable format, it is possible to record this as "letDown", but if the no space requirement is not strongly motivated, I think it might make sense to accept spaces (e.g., "pissed off", "culture shock", or maybe "deja vu". It seems like multiword emotions eventually get lexicalized, like "homesick" or "carefree", but one could make the case for containing space in order to make the format more general).
I wasn't sure if I should submit this report to the list mentioned on the specification site,  I haven't been following this list, so please let me know if should join and submit via the list or if the organizers here are collecting them off several threads, like this one.
I'll be on vacation and traveling for the next 3 weeks but I should be able to get to email mostly within a day or so.
On Thu, Aug 23, 2012 at 9:23 AM, abe kazemzadeh <> wrote:
> Hi Felix,
> On Thu, Aug 23, 2012 at 1:18 AM, <> wrote:
>> Congratulations, I just played it and it only took 12 questions to guess my emotion (jealousy). There was only one strange situation, when I first answered "no" on the question "is it like sadness?" and the next question was "is it sadness?".
> Thanks for playing the emo20q demo! I'm glad it guessed correctly, but
> you're right, there are some non-sequitur responses. I'm still trying
> to decide whether more data or an improved algorithm will be the best
> way to fix these...
>> So when will you send the report? Are you clear on the format?
> I hope to send it soon. I've reviewed the report requirements
> ( ). It seems clear, so
> no questions at the moment, but if there are any example reports
> available that might help.
>> You're all aware we extended the deadline to mid September?
> I wasn't aware of the extension, but that's great.
>> I'll be on the Eusipco conference in Bukarest next week in case anyone is also there and we could meet.
> Have a good trip. I just checked with Shri, unfortunately no one from
> SAIL is going to be at Eusipco this year.
> Take care,
> Abe
>> -----Ursprüngliche Nachricht-----
>> Von: abe kazemzadeh []
>> Gesendet: Mittwoch, 22. August 2012 22:08
>> An: Burkhardt, Felix
>> Cc:;;
>> Betreff: Re: Call for Implementations of EmotionML published
>> Hi Felix,
>> I'm sorry that I was delayed with the implementation report for my
>> use of EmotionML. I just recently made a usable demo and if I could
>> still submit a report, I would be very glad if I could help with the
>> EmotionML effort. The demo is at
>> . It basically uses the
>> EmotionML vocabulary idiom with a list of 110 emotion words for
>> implementing emotion twenty questions (EMO20Q). After each question,
>> the agent updates the probabilities/potentials associated with each
>> word and hopefully the belief update will narrow down the candidate
>> words (lower the entropy of the categorical distribution over the
>> vocabulary) so that the agent can guess the emotion word in less than
>> 20 questions.
>> I would have submitted the report earlier, but it just wasn't ready.
>> Actually the EmotionML helped make the emo20q demo practically usable because earlier I had been serializing a big object in between the http requests, but now I only serialize an EmotionML vocabulary (with associated weights) and a dialog turn history.
>> Thanks,
>> Abe
>> On Mon, Jun 18, 2012 at 2:37 AM, <> wrote:
>>> Hi prospective implementers of EmotionML This is a reminder to
>>> deliver Implementation Reports until 10th August, I attach my own implementation report as a sample.
>>> Marc has sadly left us and I'm the new editor of EmotionML, so if you have any questions I'd be happy to assist you.
>>> It would be great to get some feedback on who actually works on implementation reports and when you think you can deliver.
>>> Regards,
>>> Felix
>>> I include Marc's last mail(s)
>>> -----Original mail-----
>>> Von: Marc Schroeder []
>>> Gesendet: Freitag, 11. Mai 2012 09:16
>>> An: Burkhardt, Felix;;
>>> Betreff: Call for Implementations of EmotionML published
>>> Dear prospective implementors of EmotionML 1.0,
>>> the W3C has published the Candidate Recommendation and the Call for Implementations of EmotionML yesterday:
>>> The specification as such has not changed much since the previous version, just some clarifications here and there:
>>> The most relevant bit for you guys will be the Implementation Report Plan, in which we have basically listed as verifiable assertions the various properties that an implementation of different aspects of EmotionML should guarantee:
>>> A key issue here might be to clarify whether you are implementing a "producer" and/or a "consumer" of EmotionML. In the Introduction of the Implementation Report Plan, e have tried to give clear descriptions what it means for a producer and a consumer to "pass", "fail" or "not-impl" a given assertion.
>>> I'll be happy to work with you in the next few weeks to clarify what needs to be done so that your implementation reports can help move EmotionML forward. Simply get back to me with any questions you have.
>>> I'd say if you think the question is of relevance to other prospective implementors, it should be OK to "reply all" to this email.
>>>>I have just completed an implementation of an EmotionML checker in java, which performs a full validation of input documents with respect to all assertions in the IRP. Aspects of the specification that cannot be >verified through schema validation are verified through java code.
>>>>This means that if the tool accepts any given document (or document fragment), I am reasonably confident it can be treated as valid EmotionML.
>>>>I have placed the code in the public domain:
>>> Mit freundlichen Grüßen / Viele Grüße / Best Regards
>>> Felix Burkhardt
>>> Deutsche Telekom AG
>>> T-Labs (Research & Innovation)
>>> Dr. Felix Burkhardt
>>> Winterfeldtstr. 21, 10781 Berlin
>>> +4930835358136 (Tel.)
>>> +4952192100512 (Fax)
>>> E-Mail:
>>> Erleben, was verbindet.
>>> Deutsche Telekom AG
>>> Aufsichtsrat: Prof. Dr. Ulrich Lehner (Vorsitzender)
>>> Vorstand: René Obermann (Vorsitzender), Dr. Manfred Balz, Reinhard
>>> Clemens, Niek Jan van Damme, Timotheus Höttges, Claudia Nemat, Prof.
>>> Dr. Marion Schick
>>> Handelsregister: Amtsgericht Bonn HRB 6794 Sitz der Gesellschaft:
>>> Bonn WEEE-Reg.-Nr. DE50478376
>>> Große Veränderungen fangen klein an - Ressourcen schonen und nicht jede E-Mail drucken.

Received on Thursday, 20 September 2012 14:30:37 UTC