Definition
Functional Requirements
Syntax
Semantics
Conformance Testing
Performance Assessment
Definition
Functional Requirements
- Header: The Data shall have Header “PGM-CFN-V1.0”.
- Identification: The Data shall carry a unique identifier and a time (CommunicativeFunctionsID, CommunicativeFunctionsTime) and may carry the identifiers of the M‑Instance, of the U‑Environment, of the session and of the Final Response whose Text the functions go with.
- Level: The Data shall state its Level: 0, no functions; 1, functions without Behaviour; 2, functions, each of which may carry the Behaviour that realises it.
- Function: Each function shall have an identifier unique in the Final Response (FunctionID), a Function from the closed list, an Anchor and a Requirement; it may have a Target, an Intensity, a Behaviour (Level 2) and Times (given by Behaviour Planning only).
- Target: The Target is the User, or an Item or an M‑Location that the PC Prompt gives; it is absent when the Function has no target.
- Anchor: The Anchor is the first and the last word of the Text with which the function goes (words separated by white space, counted from 0), or Before or After the utterance.
- Requirement: A Required function is realised by A‑User Formation or reported as not realised with the reason; an Optional function may be left out.
- Behaviour: A Behaviour shall be one of those allowed for its Function (Table 2).
- Metadata: The Data may include DataXMData and DescrMetadata.
Syntax
https://schemas.mpai.community/PGM1/V1.0/data/CommunicativeFunctions.json
Semantics
Table 1 – Semantics of Communicative Functions
| Label | Description |
| Header | Header of the Data Type, with the version. (required) |
| MInstance | Identifier of the M-Instance. |
| UEnvironment | Identifier of the U-Environment. |
| SessionID | Identifier of the A-User session. |
| CommunicativeFunctionsID | Identifier of this instance. (required) |
| CommunicativeFunctionsTime | Time at which the Data was produced. (required) |
| FinalResponseID | Identifier of the Final Response whose Text the functions go with. |
| Level | One of: 0 (no functions), 1 (functions without Behaviour), 2 (functions, each of which may carry the Behaviour that realises it). (required) |
| Functions | The functions. (required) |
| – FunctionID | Identifier of the function, unique in the Final Response; A-User Formation reports on it. (required) |
| – Function | What the A-User means to do with its body. One of the Functions of Table 2. (required) |
| – Target | Towards whom or what. Absent when the Function has no target. |
| –– Kind | One of: User, Item, MLocation. (required) |
| –– ID | Identifier of the Item or of the M-Location, as the PC Prompt gives it. |
| – Anchor | Where in the utterance the function goes. (required) |
| –– Position | One of: During, Before, After. (required) |
| –– FirstWord | The first word of the Text with which the function goes, counted from 0. Required when Position is During. |
| –– LastWord | The last word of the Text with which the function goes. Required when Position is During. |
| – Intensity | How marked the function is, from 0 to 1. |
| – Requirement | One of: Required (A-User Formation realises it or says why not), Optional (A-User Formation may leave it out). (required) |
| – Behaviour | Level 2 only. The Behaviour that realises the function. |
| –– Name | One of the Behaviours of Table 3 allowed for the Function in Table 2. (required) |
| –– BodyPart | One of: Eyes, Head, Face, Shoulders, LeftHand, RightHand, BothHands, Torso, WholeBody. |
| –– TowardsTarget | Whether the Behaviour is directed towards the Target. |
| –– Amplitude | From 0 to 1. |
| –– Repetitions | Number of repetitions (at least 1). |
| –– PeakWord | The word of the Anchor on which the peak of the Behaviour falls. |
| – Times | Given by Behaviour Planning only: start, peak and end of the Behaviour, in seconds from the start of the Machine Speech. |
| –– Start | Start of the Behaviour. (required) |
| –– Peak | Peak of the Behaviour. |
| –– End | End of the Behaviour. (required) |
| DataXMData | Data Exchange Metadata of MPAI-PTF: provenance, authorisation, security and confidence of the Data. |
| DescrMetadata | Descriptive metadata (plain text, at most 2048 characters). |
Table 2 – The Functions and the Behaviours that may realise them
| Function | Meaning | Behaviours |
| Gaze | looks at the Target. | LookAt, TurnTowards |
| Deictic | indicates the Target. | Point, HeadPoint, LookAt |
| Greeting | greets or takes leave of the Target. | Wave, Nod, Bow, Smile |
| Affirmation | says yes or agrees. | Nod, Smile |
| Negation | says no or disagrees. | HeadShake, Frown |
| Beat | marks the words of the Anchor as important. | Stroke, Nod, RaiseEyebrows |
| Iconic | depicts the shape, size or movement of what the Anchor names. | Trace, Frame |
| Metaphoric | gives a concrete form to an abstract idea. | PalmUp, Frame, Trace |
| Uncertainty | shows doubt. | Shrug, HeadTilt, PalmUp |
| Attention | shows that it listens to or attends to the Target. | LookAt, LeanForward, HeadTilt, Nod |
| Invitation | invites the Target to act or to speak. | PalmUp, HoldOut, Nod, LookAt |
| Stop | asks the Target to stop or to wait. | StopPalm, HeadShake |
Table 3 – The Behaviours
| Behaviour | Meaning |
| LookAt | eyes, and head if needed, towards the Target. |
| TurnTowards | head, torso or whole body towards the Target. |
| Point | index finger towards the Target. |
| HeadPoint | a short head movement towards the Target. |
| Nod | head down and up. |
| HeadShake | head left and right. |
| HeadTilt | head tilted to one side. |
| Wave | open hand moved side to side. |
| Bow | torso bent forward and back. |
| Smile | a social smile. |
| RaiseEyebrows | both eyebrows raised. |
| Frown | brows drawn together. |
| Shrug | shoulders raised and dropped. |
| PalmUp | open hand, palm up. |
| HoldOut | hand held out towards the Target, as when offering. |
| StopPalm | hand raised, palm towards the Target. |
| Stroke | a short downward hand movement on the peak word. |
| Trace | the hand draws a shape or a path. |
| Frame | two hands show a size or a boundary. |
| LeanForward | torso leaning towards the Target. |
Conformance Testing
Data conforms with Communicative Functions if it validates against the schema of Section 3. If a schema contains references to other schemas, conformance of data for the primary schema implies that any data referencing a secondary schema shall also validate against the relevant schema.
Performance Assessment
Not part of this specification.