Two users, A and B are dealing with the task of “text answering” for the artwork X. A says that the EmotionEvent “crying” present in this artwork triggers in them the emotion “suffering”. B instead describes this emotion as “unhappiness”. Both suffering and “unhappiness” are then generalized to “Sadness”.
Both suffering and Unhappiness refer to the prototype emotion of Sadness.
Competency Questions
CQ1) Retrieve the prototype emotion from an emotion word.
CQ2) Retrieve the emotion event that triggered an emotional reaction.
CQ3) Retrieve all emotion events that trigger a particular prototype emotion (This question is a way to link different artworks, as to say that artwork might be linked because they portray emotion events that refer to the same prototype emotion).
Ontology/Ontology Design Patterns Relevant for the scenario
Shaver Emotion Ontology re-uses the DOLCE ODP, in particular the class EmotionEvent (In Shaver, emotions are a reaction to an Event) is created as a subclass to DUL.owl#Event. Moreover, the standard emotion module for spice is used as well, in particular the emotion:label data property to describe the emotion events and also the two classes: EmotionWord and PrototypeEmotion are subclasses to e:Emotion.
Used as a standalone, the ontology only describes the emotion knowledge theory of Shaver. In order to be correctly applied to spice project it also needs to import the EmotionInCulturalContext module.
SPARQL Questions
CQ1
PREFIX: shavem: <https://w3id.org/spice/SON/ShaverEmotions/>
PREFIX e: <https://w3id.org/spice/SON/emotion/>
SELECT ?protEm WHERE {
?unhappiness a shavem:Unhappiness ;
shavem:refersToPrototypeEmotion ?protEm .
} LIMIT 100
CQ2
PREFIX: shavem: <https://w3id.org/spice/SON/ShaverEmotions/>
PREFIX e: <https://w3id.org/spice/SON/emotion/>
SELECT ?emoevent WHERE {
?emoevent a shavem:EmotionEvent ;
shavem:triggers ex:unhappinessofA .
}
LIMIT 100
CQ3
PREFIX: shavem: <https://w3id.org/spice/SON/ShaverEmotions/>
PREFIX e: <https://w3id.org/spice/SON/emotion/>
SELECT ?emoevent WHERE {
?emoevent a shavem:EmotionEvent ;
shavem:triggers ?emotionword .
?emotionword a shavem:EmotionWord ;
shavem:refersToPrototypeEmotion shavem:Sadness .
}
LIMIT 100
Depends on
Independent
Description
Two users, A and B are dealing with the task of “text answering” for the artwork X. A says that the EmotionEvent “crying” present in this artwork triggers in them the emotion “suffering”. B instead describes this emotion as “unhappiness”. Both suffering and “unhappiness” are then generalized to “Sadness”.
Both suffering and Unhappiness refer to the prototype emotion of Sadness.
Competency Questions
CQ1) Retrieve the prototype emotion from an emotion word.
CQ2) Retrieve the emotion event that triggered an emotional reaction.
CQ3) Retrieve all emotion events that trigger a particular prototype emotion (This question is a way to link different artworks, as to say that artwork might be linked because they portray emotion events that refer to the same prototype emotion).
Ontology/Ontology Design Patterns Relevant for the scenario
Shaver Emotion Ontology re-uses the DOLCE ODP, in particular the class EmotionEvent (In Shaver, emotions are a reaction to an Event) is created as a subclass to DUL.owl#Event. Moreover, the standard emotion module for spice is used as well, in particular the emotion:label data property to describe the emotion events and also the two classes: EmotionWord and PrototypeEmotion are subclasses to e:Emotion. Used as a standalone, the ontology only describes the emotion knowledge theory of Shaver. In order to be correctly applied to spice project it also needs to import the EmotionInCulturalContext module.
SPARQL Questions
CQ1
CQ2
CQ3
Toy Dataset/SPARQL Endpoint
shaverscenario1.ttl