This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Composite Message Type (new wrapper mechanism)"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) |
Rene spronk (talk | contribs) |
||
| (5 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{INM Workitem}} | {{INM Workitem}} | ||
| − | ''Note: this pages describes new wrappers, these are still being discussed by the INM committee. This work is related to [[Interaction (new dynamic model)]].'' | + | ''Note: this pages describes new wrappers, these are still being discussed by the INM committee. This work is related to [[Interaction (new dynamic model)]]. This page also assumes that "top half RIM" classes are used for all models.'' |
| + | |||
| + | [[Image:New wrapper struc.jpg|200px|right|thumb|Wrapper structure]] | ||
The '''Composite Message Type''' is 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 associated with a particular information exchange. | The '''Composite Message Type''' is 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 associated with a particular information exchange. | ||
| − | |||
In terms of structure the information exchange consists of: | In terms of structure the information exchange consists of: | ||
| − | # | + | #one [[Transmission Wrapper (new wrapper mechanism)]], which contains |
| − | # | + | #zero or more [[Behavioral Contract Wrapper (new wrapper mechanism)]], which in turn contains |
| − | #[[Domain Content]] | + | #zero or more [[Domain Content|payload]] models. (Note: a [[Query Definition (new wrapper mechanism)]] is an example payload model). |
| − | + | ==Details== | |
| − | + | *The [[Behavioral Contract Wrapper (new wrapper mechanism)|Behavioral Contract Wrapper]] contains a BehavioralContract act which has a 1..1 relationship with a ControlAct in Event mood. As such the Behavioral Contract Wrapper contains the identification of the [[Trigger Event]]. | |
| + | *The BehavioralContract Act has a recursive Act Relationship to allow for nesting. This can be used (amongst other things) to support a transactional grouping (a.k.a. transactional batching) mechanism. | ||
| + | *The Transmission Wrapper may contain multiple Behavioral Contract Wrappers. This can be used to support a "transmission batching" mechanism. | ||
| − | In the future, additional levels of wrappers may be supported. For example, a "claims" message might be | + | ==Additional notes== |
| + | *In the future, additional levels of wrappers may be supported. For example, a "claims" message might be defined as a wrapper which itself wraps an Act representing the billable act for which an insurance claim is being made. | ||
Latest revision as of 13:05, 5 October 2006
This page documents an INM Workitem, i.e. an issue within scope of the INM Committee that either is still being discussed, or the resolution of which has not yet been included in an INM ballot.
Note: this pages describes new wrappers, these are still being discussed by the INM committee. This work is related to Interaction (new dynamic model). This page also assumes that "top half RIM" classes are used for all models.
The Composite Message Type is 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 associated with a particular information exchange.
In terms of structure the information exchange consists of:
- one Transmission Wrapper (new wrapper mechanism), which contains
- zero or more Behavioral Contract Wrapper (new wrapper mechanism), which in turn contains
- zero or more payload models. (Note: a Query Definition (new wrapper mechanism) is an example payload model).
Details
- The Behavioral Contract Wrapper contains a BehavioralContract act which has a 1..1 relationship with a ControlAct in Event mood. As such the Behavioral Contract Wrapper contains the identification of the Trigger Event.
- The BehavioralContract Act has a recursive Act Relationship to allow for nesting. This can be used (amongst other things) to support a transactional grouping (a.k.a. transactional batching) mechanism.
- The Transmission Wrapper may contain multiple Behavioral Contract Wrappers. This can be used to support a "transmission batching" mechanism.
Additional notes
- In the future, additional levels of wrappers may be supported. For example, a "claims" message might be defined as a wrapper which itself wraps an Act representing the billable act for which an insurance claim is being made.
