This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Interaction"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) (new page) |
Rene spronk (talk | contribs) |
||
| Line 3: | Line 3: | ||
*[[Trigger Event]] - each interaction will be associated with a single trigger event. The trigger event represents the “real-world” occurrence that creates a need to exchange information. Note that a given trigger event may fire multiple interactions. | *[[Trigger Event]] - each interaction will be associated with a single trigger event. The trigger event represents the “real-world” occurrence that creates a need to exchange information. Note that a given trigger event may fire multiple interactions. | ||
:Note that the semantic context of an interaction has to be defined by a domain. | :Note that the semantic context of an interaction has to be defined by a domain. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
*[[Composite Message Type]] – The set of static model definitions (wrappers and message types) that define the structures of the data that is transmitted by the interaction. Committees will explicitly identify all message types (transmission wrapper, control act wrapper and payload) associated with a particular interaction. | *[[Composite Message Type]] – The set of static model definitions (wrappers and message types) that define the structures of the data that is transmitted by the interaction. Committees will explicitly identify all message types (transmission wrapper, control act wrapper and payload) associated with a particular interaction. | ||
Revision as of 04:56, 30 November 2005
Interactions are defined as a triplet involving the following elements:
- Trigger Event - each interaction will be associated with a single trigger event. The trigger event represents the “real-world” occurrence that creates a need to exchange information. Note that a given trigger event may fire multiple interactions.
- Note that the semantic context of an interaction has to be defined by a domain.
- Composite Message Type – The set of static model definitions (wrappers and message types) that define the structures of the data that is transmitted by the interaction. Committees will explicitly identify all message types (transmission wrapper, control act wrapper and payload) associated with a particular interaction.
- In terms of structure an Interaction can be either a Message-based Interaction or a Batch-based Interaction. Interactions consist of:
- 1. a Batch Wrapper (conditional upon it being a Batch)
- 2. a Transmission Wrapper
- 3. a Trigger Event Control Act Wrapper (conditional)
- 4. Domain Content (optional)
- Receiver Responsibilities - will be defined for the target receiver of the message. The receiver responsibilities will be cast in terms of one of several interactions to be sent as a result of receiving the message and/or as one trigger event out of a set of trigger events the receiver will fire after receipt of the message. Implementers will need to take care that applications that can send an interaction are capable of receiving the ‘receiver responsibility’ interactions, and vice versa.
- Receiver Responsibilities are a set of mutually exclusive responsibility options that are triggered by the receipt of an interaction. Each responsibility option includes a description that describes the circumstances under which that option should be fired. These circumstances are all mutually exclusive, such that one and only one responsibility option fires in response to a given interaction.
- A responsibility option consists of:
- A) An optional trigger event the receiver should fire
- B) An optional interaction the receiver should return. (This is what's sent as an 'application acknowledgment')
- It is possible that the responsibility option interaction will itself have receiver responsibilities, resulting in a prolonged conversation between sender and receiver.
