...
The global structure of the XML-schema for the script configuration is as follows:
The Title
key is an optional identifier for the script.
The start and end date/time for the script have to be specified using attributes date
and time
in the format YYYY-MM-DD
and hh:mm:ss
, respectively.
The NextEventButton
key can be set to true
or false
and indicates whether or not a button for proceeding to the next event in the script must be included in the user interface.
The configuration of events (or stories) and the forecast table for a script are explained below.
Stories
In the section Stories
of the script configuration, an arbitrary number of stories can be specified.
Two types of stories can be specified:
Inbox
is optional and may be specified only once. In the inbox storyline you define the messages that appear in the inbox, which can be selected by the user.Story
is optional and can be specified an arbitrary number of times. Each story corresponds to a "Communication" button in the user interface that can be activated by the user. The content of story buttons can be dynamic, i.e. different events may be triggered by pushing the story button at different times.
Each story must have a title by specifying the Title
key (but the title for the inbox is optional). This title will be used as the title of the story button. The title can be different for various languages. If the language attribute for Title
is specified and it corresponds to the preferred language in the application configuration, then this title is used in the script. If no language attribute is found that corresponds to the preferred language, then the default Title
for which no language attribute was specified will be used.
Code Block | ||||
---|---|---|---|---|
| ||||
<Story>
<Title lang="NL">Telefoongesprek</Title>
<Title lang="GE">Anruf</Title>
<Title>Telephone call</Title>
</Story>
|
Frames
A story may consist of an arbitrary number of frames according to the following schema:
...