Collaboration: At the Extremities of Extreme
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Abel Avram on Jul 30, 2010
W3C has published the first public working draft of the Emotion Markup Language (EmotionML), a language meant to express emotions in three main ways in today’s computer-based communication: annotating data, the recognition of emotional-based states, and generating emotion-related system behavior.
According to the language authors, EmotionML can have applications in various fields like:
- Opinion mining / sentiment analysis in Web 2.0, to automatically track customer's attitude regarding a product across blogs;
- Affective monitoring, such as ambient assisted living applications for the elderly, fear detection for surveillance purposes, or using wearable sensors to test customer satisfaction;
- Character design and control for games and virtual worlds;
- Social robots, such as guide robots engaging with visitors;
- Expressive speech synthesis, generating synthetic speech with different emotions, such as happy or sad, friendly or apologetic;
- Emotion recognition (e.g., for spotting angry customers in speech dialog systems);
- Support for people with disabilities, such as educational programs for people with autism.
The basis of an EmotionML document is represented by the <emotion> element, having as children one of the following elements: <category>, <dimension>, <appraisal>, <action-tendency>. There are various emotion category sets, the shortest one being Paul Ekman’s, containing six basic emotions having facial expressions: anger, disgust, fear, happiness, sadness, and surprised. Other sets are more elaborate like Fontaine, Scherer, Roesch and Ellsworth’s, having 24 categories. The dimension element can also have various values depending on the author(s) studying it, an example being: pleasure, arousal, and dominance. The same goes for appraisal and action-tendency, detailed in the document.
The EmotionML draft contains several examples, including annotating an image:
Another example shows how a system can express the information collected by three different affective sensor devices:
Yet another example demonstrates the third usage intended for EmotionML, the behavior of a robot with batteries running out and looking for a power outlet and avoiding to pick up boxes which would drain the batteries even more:
EmotionML can be used in conjunction with other markup languages like EMMA, and extensible multi-modal annotation language, and SSML, a speech synthesis language.
Mobile and the New Two-Tiered Web Architecture
18 agile and lean practices for effective software development governance
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
Agile Development: A Manager's Roadmap for Success
Agile Practices to Improve Project Management Organization (PMO) Effectiveness
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).
Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
1 comment
Watch Thread Reply