Glossary

A field set created by a consume/reply operation.

As opposed to an initial field set, which starts a new transaction, a consequent field set starts a new sequence.

An input event that forms a goal.

An operation that a service can use to receive input from other services (via SPARKL).

An operation that comprises a consume and a reply event. The consume forms a goal event, while the reply of a consume/reply creates a new (consequent) field set.

An edge is an element of the Sequencing Graph. It is generated by a reply event and is used to connect vertices.

Fields contain the data being carried by the events, except for flag fields. Fields are sent to and from operations.

A set of fields. A field set usually grows in terms of fields contained as it moves through the Sequencing Graph.

A field that does not contain data. It is used only for sequencing purposes. For example YES or NO flag fields.

Response and consume events form a goal which services provisioned using the Sequencer extension try to satisfy. A transaction can have one or more goals.

The field set that starts a transaction. An initial field set is created by a solicit or notify event.

Islands are bunches of vertices disjoint from other vertices existing on the same mix. Each island makes a different transaction possible on the same Sequencing Graph.

Labels are added to vertices. A label identifies the operations that generated the vertex by listing the fields associated with the operations.

A mix is a SPARKL configuration used for handling interactions between services. A mix comprises services, operations supported by these services, and fields sent to and from the operations.

An output event that starts a transaction. This event carries an initial field set.

An operation that a service can use to start a transaction and to send output to SPARKL.

Operations are mix components used to generate the Sequencing Graph. Operations are made up of events, which carry the fields of the operations between the services. Four operations are possible in SPARKL: solicit/response, notify, request/reply, consume(/reply).

A field set that satisfied the consume goal event on a consume/reply and contributed to the creation of a new (consequent field set by the reply.

Each SPARKL extension has a priv directory where user assets are kept. The location of the extensions is decided at installation time. By default, the extensions' are at: /usr/local/lib/sse/lib.

An input event that forms a goal.

An operation that a service can use to generate additional data and then send it to SPARKL.

An output event that adds fields to a field set (or in the case of a consume/reply creates a consequent field set).

An input event that forms a goal.

A transaction is made up of sequences. Each field set processed by SPARKL forms a sequence. Only an initial field set starts a new transaction. Consequent field sets start new sequences.

The Sequencing Graph is derived from all the operations in a mix. It is built once per mix and is used for all transactions on that mix.

An output event that starts a transaction. This event carries an initial field set.

An operation that a service can use to start a transaction and to send output to SPARKL. The service then waits until SPARKL sends a response.

The system configuration file. It is located within each nodes' folder, along with a directory containing system logs, a backup of your SPARKL resources, and a directory that contains your machine key and TLS/SSL certificate.

A process in SPARKL started by the Sequencer upon receiving an initial field set, and stopped by the Sequencer upon having nothing more to do with the field sets present in the transaction.

A vertex is an element of the Sequencing Graph. It is generated by a certain operation of a mix. Vertices are connected by edges.