seev.002.001.05
Scope The MeetingCancellation message is sent by the party that sent the MeetingNotification message to the original receiver. It is sent to cancel the previous MeetingNotification message or to advise the cancellation of a meeting. Usage The MeetingCancellation message is used in two different situations. First, it is used to cancel a previously sent MeetingNotification message. In this case, the MessageCancellation, the MeetingReference and the Reason building blocks need to be present. Second, it is used to advise that the meeting is cancelled. In this case, only the MeetingReference and Reason building blocks need to be present. This message definition is intended for use with the Business Application Header.
Message Construction
Every ISO20022 message has at the highest level what we call ‘building blocks’. Because the message is constructed as immutable records, the association is by composition. Below you can see the relationship between the message and its constituent building blocks: For comparison, see the ISO20022 official specification
classDiagram
direction LR
%% MeetingCancellationV05 recursion level 0 with max 0
MeetingCancellationV05 *-- "1..1" MeetingReference6 : MeetingReference
MeetingCancellationV05 *-- "0..200" SecurityPosition8 : Security
MeetingCancellationV05 *-- "1..1" MeetingCancellationReason2 : Reason
MeetingCancellationV05 *-- "0..1" SupplementaryData1 : SupplementaryData
Now, we will zero-in one-by-one on each of these building blocks.
MeetingReference building block
Series of elements which allow to identify a meeting. Identification of a meeting. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% MeetingReference6 recursion level 0 with max 1
class MeetingReference6{
MeetingIdentification IsoMax35Text
IssuerMeetingIdentification IsoMax35Text
MeetingDateAndTime IsoISODateTime
Type MeetingType3Code
}
MeetingReference6 *-- "0..1" IMeetingTypeClassification1Choice : Classification
MeetingReference6 *-- "0..5" PostalAddress1 : Location
%% IMeetingTypeClassification1Choice recursion level 1 with max 1
%% PostalAddress1 recursion level 1 with max 1
class PostalAddress1{
AddressType AddressType2Code
AddressLine IsoMax70Text
StreetName IsoMax70Text
BuildingNumber IsoMax16Text
PostCode IsoMax16Text
TownName IsoMax35Text
CountrySubDivision IsoMax35Text
Country CountryCode
}
MeetingReference6 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| MeetingIdentification | Identification assigned to the general meeting by the party notifying the meeting. It must be unique for the party notifying the meeting. | IsoMax35Text - Required 1..1 |
| IssuerMeetingIdentification | Identification assigned to the meeting by the issuer. It must be unique for the issuer. | IsoMax35Text - Optional 0..1 |
| MeetingDateAndTime | Date and time at which the meeting will take place. | IsoISODateTime - Optional 0..1 |
| Type | Specifies the type of meeting for which instructions are sent. | MeetingType3Code - Optional 0..1 |
| Classification | Classifies the type of meeting. | IMeetingTypeClassification1Choice - Optional 0..1 |
| Location | Place of the company meeting for the scheduled meeting date. | PostalAddress1 - Collection 0..5 |
Security building block
Identifies the security for which the meeting was organised. Identifies the securities for which the meeting is organised. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% SecurityPosition8 recursion level 0 with max 1
SecurityPosition8 *-- "1..1" SecurityIdentification14 : FinancialInstrumentIdentification
SecurityPosition8 *-- "0..1000" EligiblePosition5 : Position
%% SecurityIdentification14 recursion level 1 with max 1
class SecurityIdentification14{
ISIN IsoISINIdentifier
Description IsoMax140Text
}
SecurityIdentification14 *-- "0..0" OtherIdentification1 : OtherIdentification
%% EligiblePosition5 recursion level 1 with max 1
class EligiblePosition5{
AccountIdentification IsoMax35Text
}
EligiblePosition5 *-- "0..1" IPartyIdentification40Choice : AccountOwner
EligiblePosition5 *-- "0..10" HoldingBalance7 : HoldingBalance
EligiblePosition5 *-- "0..10" IPartyIdentification40Choice : RightsHolder
SecurityPosition8 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| FinancialInstrumentIdentification | Identification of the security, as assigned under a formal or proprietary identification scheme. | SecurityIdentification14 - Required 1..1 |
| Position | Amount of securities that are eligible for the vote. | EligiblePosition5 - Collection 0..1000 |
Reason building block
Defines the justification for the cancellation. Specifies the reason for cancelling a meeting. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% MeetingCancellationReason2 recursion level 0 with max 1
class MeetingCancellationReason2{
CancellationReason IsoMax140Text
}
MeetingCancellationReason2 *-- "0..1" IMeetingCancellationReason1Choice : CancellationReasonCode
%% IMeetingCancellationReason1Choice recursion level 1 with max 1
MeetingCancellationReason2 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| CancellationReasonCode | Reason for cancelling a meeting. | IMeetingCancellationReason1Choice - Optional 0..1 |
| CancellationReason | Provides more information on the reason for cancelling a meeting in free format form. | IsoMax140Text - Optional 0..1 |
SupplementaryData building block
Additional information that can not be captured in the structured fields and/or any other specific block. Additional information that can not be captured in the structured fields and/or any other specific block. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% SupplementaryData1 recursion level 0 with max 1
class SupplementaryData1{
PlaceAndName IsoMax350Text
}
SupplementaryData1 *-- "1..1" IsoSupplementaryDataEnvelope1 : Envelope
%% IsoSupplementaryDataEnvelope1 recursion level 1 with max 1
SupplementaryData1 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| PlaceAndName | Unambiguous reference to the location where the supplementary data must be inserted in the message instance. In the case of XML, this is expressed by a valid XPath. | IsoMax350Text - Optional 0..1 |
| Envelope | Technical element wrapping the supplementary data. | IsoSupplementaryDataEnvelope1 - Required 1..1 |
Extensibility and generalization considerations
To facilitate generalized design patterns in the system, the MeetingCancellationV05 implementation follows a specific implementaiton pattern. First of all, MeetingCancellationV05 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, MeetingCancellationV05Document implements IOuterDocument. Because MeetingCancellationV05 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type MeetingCancellationV05.
classDiagram
class IOuterRecord
MeetingCancellationV05 --|> IOuterRecord : Implements
MeetingCancellationV05Document --|> IOuterDocument~MeetingCancellationV05~ : Implements
class IOuterDocument~MeetingCancellationV05~ {
MeetingCancellationV05 Message
}
Document wrapper for serialization
The only real purpose MeetingCancellationV05Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:seev.002.001.05’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using MeetingCancellationV05.ToDocument() method. The returned MeetingCancellationV05Document value will serialize correctly according to ISO 20022 standards.
classDiagram
MeetingCancellationV05Document *-- MeetingCancellationV05 : Document
Sample of message format
This is an abbreviated version of what the message should look like.
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:seev.002.001.05">
<MtgCxl>
<MtgRef>
<!-- MeetingReference inner content -->
</MtgRef>
<Scty>
<!-- Security inner content -->
</Scty>
<Rsn>
<!-- Reason inner content -->
</Rsn>
<SplmtryData>
<!-- SupplementaryData inner content -->
</SplmtryData>
</MtgCxl>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_xDAOAVtcEeSwKe7KuKvXhg"
nextVersions="_yXBbUayREemMosWmlQ33EA"
previousVersion="_TlmIHtEwEd-BzquC8wXy7w_-1684108229"
name="MeetingCancellationV05"
definition="Scope
The MeetingCancellation message is sent by the party that sent the MeetingNotification message to the original receiver. It is sent to cancel the previous MeetingNotification message or to advise the cancellation of a meeting.
Usage
The MeetingCancellation message is used in two different situations.
First, it is used to cancel a previously sent MeetingNotification message. In this case, the MessageCancellation, the MeetingReference and the Reason building blocks need to be present.
Second, it is used to advise that the meeting is cancelled. In this case, only the MeetingReference and Reason building blocks need to be present.
This message definition is intended for use with the Business Application Header."
registrationStatus="Registered"
messageSet="_wRe70U2rEeG_I4xRYCA_7g"
xmlTag="MtgCxl"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<constraint
xmi:id="_xDAOA1tcEeSwKe7KuKvXhg"
nextVersions="_yXBbU6yREemMosWmlQ33EA"
previousVersion="_TlvSBdEwEd-BzquC8wXy7w_269200866"
name="Cancellation1Guideline"
definition="It is recommended to cancel a meeting by using MeetingReference/MeetingIdentification and Reason only. It is recommended to avoid the repetition of optional building blocks or components."
registrationStatus="Provisionally Registered" />
<messageBuildingBlock
xmi:id="_xDAOD1tcEeSwKe7KuKvXhg"
nextVersions="_yXBbVayREemMosWmlQ33EA"
previousVersion="_TlvSANEwEd-BzquC8wXy7w_-1689849520"
name="MeetingReference"
definition="Series of elements which allow to identify a meeting."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="MtgRef"
complexType="_bLQ9gVuPEeSmO6RkXg92Lg" />
<messageBuildingBlock
xmi:id="_xDAOE1tcEeSwKe7KuKvXhg"
nextVersions="_yXBbV6yREemMosWmlQ33EA"
previousVersion="_TlvSAtEwEd-BzquC8wXy7w_1987199986"
name="Security"
definition="Identifies the security for which the meeting was organised."
registrationStatus="Provisionally Registered"
maxOccurs="200"
minOccurs="0"
xmlTag="Scty"
complexType="_03CHAVthEeSwKe7KuKvXhg" />
<messageBuildingBlock
xmi:id="_xDAOFVtcEeSwKe7KuKvXhg"
nextVersions="_yXBbWayREemMosWmlQ33EA"
previousVersion="_TlvSA9EwEd-BzquC8wXy7w_-2140747415"
name="Reason"
definition="Defines the justification for the cancellation."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="Rsn"
complexType="_RCMa19p-Ed-ak6NoX_4Aeg_1000768570" />
<messageBuildingBlock
xmi:id="_kohz4VtoEeSwKe7KuKvXhg"
nextVersions="_yXBbW6yREemMosWmlQ33EA"
name="SupplementaryData"
definition="Additional information that can not be captured in the structured fields and/or any other specific block."
registrationStatus="Provisionally Registered"
minOccurs="0"
xmlTag="SplmtryData"
complexType="_Qn0zC9p-Ed-ak6NoX_4Aeg_468227563" />
<messageDefinitionIdentifier
businessArea="seev"
messageFunctionality="002"
flavour="001"
version="05" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.