-
Key: MDMI_-115
-
Legacy Issue Number: 12723
-
Status: closed
-
Source: SWIFT ( Frank Vandamme)
-
Summary:
Current text
The messageModelName property is a string that is usually similar to the name of the message format it is modeling.
New text
SEE QUESTIONS & COMMENTS IN NEXT COLUMN
Rationale
How does this work with messages that are multi-functional and where you may need to have a separate model for each function it supports? (e.g. because the meaning of the fields is different for each function). -
Reported: MDMI 1.0b1 — Tue, 8 Jul 2008 04:00 GMT
-
Disposition: Resolved — MDMI 1.0b2
-
Disposition Summary:
Discussion:
You have only one MessageModel per message format. Different purposes are handled because SemanticElements can only have one semantic meaning. Thus, one field in a message format can have numerous associated SemanticElements
Disposition: Closed, no change -
Updated: Sat, 7 Mar 2015 04:57 GMT
MDMI_ — page 10 section 8.1.3 1st bullet
- Key: MDMI_-115
- OMG Task Force: Model Driven Message Interoperability (MDMI) FTF 2