This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Domain Payload"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) m (add Wrapper link) |
|||
| Line 3: | Line 3: | ||
The domain payload typically consists of an [[R-MIM]] as defined by the appropriate domain comittee. Example: the Laboratory SIG has defined an R-MIM for "Notification of a Lab Result". This Domain Payload in encapsulated in wrappers to form a [[Composite Message Type]]. | The domain payload typically consists of an [[R-MIM]] as defined by the appropriate domain comittee. Example: the Laboratory SIG has defined an R-MIM for "Notification of a Lab Result". This Domain Payload in encapsulated in wrappers to form a [[Composite Message Type]]. | ||
| − | In the future, a domain payload may itself be a | + | In the future, a domain payload may itself be a [[Wrapper]], which contains its own domain payload (or potentially multiple payloads). |
Revision as of 00:22, 15 December 2005
The payload part of a Composite Message Type. In other words: the subject of the ControlActProcess class as contained in the Trigger Event Control Act Wrapper.
The domain payload typically consists of an R-MIM as defined by the appropriate domain comittee. Example: the Laboratory SIG has defined an R-MIM for "Notification of a Lab Result". This Domain Payload in encapsulated in wrappers to form a Composite Message Type.
In the future, a domain payload may itself be a Wrapper, which contains its own domain payload (or potentially multiple payloads).
