Verona Interfaces Specification "Editor" 4.2.0

This is one part of the Verona Online Assessment Standards. All messages are sent via the postMessage function of the html page. The editor takes the page root of its parent as target (parent.window), and the application binds the function call to the iframe element of the editor. Most important, the message body carries as first parameter the operationId of the message. The html page MUST contain a

Operations

  • SUB voeReadyNotification

    Ready Notification

    The editor announces that it's code is loaded and initialized so the communication can start.

    Operation IDvoeReadyNotification

    Accepts the following message:

    voeReadyNotification
    object

    Examples

  • PUB voeStartCommand

    Start Command

    The application sends parameters for editing the unit and commands the start of user interaction.

    Operation IDvoeStartCommand

    Accepts the following message:

    voeStartCommand
    object

    Examples

  • SUB voeDefinitionChangedNotification

    Definition Changed Notification

    The definition of the unit has changed.

    Operation IDvoeDefinitionChangedNotification

    Accepts the following message:

    voeDefinitionChangedNotification
    object

    Examples

Schemas

  • SessionIdString
    string
    uid: SessionIdString

    The session id flags all communication. If a message has no or empty session id, it's not processed. The session id is unique and was generated by the application. Any simple algorithm would work. The session id helps to link the correct unit with the data of the message. Using the id of the editor hosting html element is less reliable, because the element could be reused with another unit.

  • object
    uid: EditorConfig
  • object
    uid: Dependency
  • array<object>
    uid: https://w3id.org/iqb/responses/variable-list/variable-list.json

    Data structure produced by verona editors, consumed by schemer etc.