MeetingCancellationV03

seev.002.001.03

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.

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
%% MeetingCancellationV03 recursion level 0 with max 0
MeetingCancellationV03 *-- "1..1" MessageIdentification1 : Identification
MeetingCancellationV03 *-- "0..1" AmendInformation1 : MessageCancellation
MeetingCancellationV03 *-- "1..1" MeetingReference5 : MeetingReference
MeetingCancellationV03 *-- "0..1" IPartyIdentification9Choice : NotifyingParty
MeetingCancellationV03 *-- "0..200" SecurityPosition6 : Security
MeetingCancellationV03 *-- "1..1" MeetingCancellationReason2 : Reason
  

Now, we will zero-in one-by-one on each of these building blocks.

Identification building block

Identifies the cancellation message. Identifies a message by a unique identifier and the date and time when the message was created by the sender. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% MessageIdentification1 recursion level 0 with max 1
class MessageIdentification1{
    Identification IsoMax35Text
    CreationDateTime IsoISODateTime
}
  

MessageIdentification1 members

Member name Description Data Type / Multiplicity
Identification Identification of the message. IsoMax35Text - Required 1..1
CreationDateTime Date of creation of the message. IsoISODateTime - Required 1..1

MessageCancellation building block

Information indicating that the cancellation of a message previously sent is requested (and not the cancellation of the meeting). Information specific to an amendment or cancellation. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% AmendInformation1 recursion level 0 with max 1
class AmendInformation1{
    ReconfirmInstructions IsoYesNoIndicator
}
AmendInformation1 *-- "1..1" MessageIdentification : PreviousReference
%% MessageIdentification recursion level 1 with max 1
class MessageIdentification{
    Identification IsoMax35Text
}
  

AmendInformation1 members

Member name Description Data Type / Multiplicity
PreviousReference Identifies the linked message which was previously sent. MessageIdentification - Required 1..1
ReconfirmInstructions Indicates whether instructions must be resent (in case of modification of the parameters of a meeting for which instructions have already been sent). IsoYesNoIndicator - Required 1..1

MeetingReference building block

Series of elements which allow to identify a meeting. Elements which allow to identify a meeting. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% MeetingReference5 recursion level 0 with max 1
class MeetingReference5{
    MeetingIdentification IsoMax35Text
    IssuerMeetingIdentification IsoMax35Text
    MeetingDateAndTime IsoISODateTime
    Type MeetingType2Code
}
MeetingReference5 *-- "0..1" IMeetingTypeClassification1Choice : Classification
MeetingReference5 *-- "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
}
  

MeetingReference5 members

Member name Description Data Type / Multiplicity
MeetingIdentification Identification assigned to a 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 a 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. MeetingType2Code - 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

NotifyingParty building block

Party notifying the cancellation of the meeting. Identification of a party. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% IPartyIdentification9Choice recursion level 0 with max 1
  

PartyIdentification9Choice members

Member name Description Data Type / Multiplicity

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
%% SecurityPosition6 recursion level 0 with max 1
SecurityPosition6 *-- "1..1" SecurityIdentification11 : Identification
SecurityPosition6 *-- "0..1000" EligiblePosition3 : Position
%% SecurityIdentification11 recursion level 1 with max 1
class SecurityIdentification11{
    Description IsoMax140Text
}
SecurityIdentification11 *-- "1..1" ISecurityIdentification11Choice : Identification
%% EligiblePosition3 recursion level 1 with max 1
class EligiblePosition3{
    AccountIdentification IsoMax35Text
}
EligiblePosition3 *-- "0..1" IPartyIdentification9Choice : AccountOwner
EligiblePosition3 *-- "0..10" HoldingBalance6 : HoldingBalance
EligiblePosition3 *-- "0..10" IPartyIdentification9Choice : RightsHolder
  

SecurityPosition6 members

Member name Description Data Type / Multiplicity
Identification Identification of a security, as assigned under a formal or proprietary identification scheme. SecurityIdentification11 - Required 1..1
Position Amount of securities that are eligible for the vote. EligiblePosition3 - 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

Extensibility and generalization considerations

To facilitate generalized design patterns in the system, the MeetingCancellationV03 implementation follows a specific implementaiton pattern. First of all, MeetingCancellationV03 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, MeetingCancellationV03Document implements IOuterDocument. Because MeetingCancellationV03 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type MeetingCancellationV03.

classDiagram
    class IOuterRecord
    MeetingCancellationV03 --|> IOuterRecord : Implements
    MeetingCancellationV03Document --|> IOuterDocument~MeetingCancellationV03~ : Implements
    class IOuterDocument~MeetingCancellationV03~ {
        MeetingCancellationV03 Message
     }
  

Document wrapper for serialization

The only real purpose MeetingCancellationV03Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:seev.002.001.03’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using MeetingCancellationV03.ToDocument() method. The returned MeetingCancellationV03Document value will serialize correctly according to ISO 20022 standards.

classDiagram
    MeetingCancellationV03Document *-- MeetingCancellationV03 : 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.03">
    <MtgCxl>
        <Id>
            <!-- Identification inner content -->
        </Id>
        <MsgCxl>
            <!-- MessageCancellation inner content -->
        </MsgCxl>
        <MtgRef>
            <!-- MeetingReference inner content -->
        </MtgRef>
        <NtifngPty>
            <!-- NotifyingParty inner content -->
        </NtifngPty>
        <Scty>
            <!-- Security inner content -->
        </Scty>
        <Rsn>
            <!-- Reason inner content -->
        </Rsn>
    </MtgCxl>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_TlSmJNEwEd-BzquC8wXy7w_-1183208887"
  nextVersions="_TlmIHtEwEd-BzquC8wXy7w_-1684108229"
  previousVersion="_TlJcItEwEd-BzquC8wXy7w_-976963352"
  name="MeetingCancellationV03"
  definition="Scope&#xD;&#xA;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.&#xD;&#xA;Usage&#xD;&#xA;The MeetingCancellation message is used in two different situations.&#xD;&#xA;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.&#xD;&#xA;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."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="MtgCxl"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <constraint
    xmi:id="_TlcXFtEwEd-BzquC8wXy7w_-835966089"
    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" />
  <constraint
    xmi:id="_TlcXGdEwEd-BzquC8wXy7w_-835966059"
    name="Cancellation2Guideline"
    definition="It is recommended to cancel a meeting notification message by using MessageCancellation, MeetingReference/MeetingIdentification and Reason only. It is recommended to avoid the repetition of optional building blocks or components."
    registrationStatus="Provisionally Registered" />
  <constraint
    xmi:id="_TlcXHNEwEd-BzquC8wXy7w_-835966028"
    name="MeetingIdentificationAndPreviousReference1Guideline"
    definition="If MessageCancellation is not present, then the meeting has been cancelled by the issuer."
    registrationStatus="Provisionally Registered" />
  <constraint
    xmi:id="_TlmIEtEwEd-BzquC8wXy7w_-835965997"
    name="MeetingIdentificationAndPreviousReference2Guideline"
    definition="If MessageCancellation is present, then the MeetingNotification message is cancelled however the meeting itself is not cancelled."
    registrationStatus="Provisionally Registered" />
  <messageBuildingBlock
    xmi:id="_TlcXENEwEd-BzquC8wXy7w_558997340"
    name="Identification"
    definition="Identifies the cancellation message."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Id"
    complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
  <messageBuildingBlock
    xmi:id="_TlcXEdEwEd-BzquC8wXy7w_1330137199"
    name="MessageCancellation"
    definition="Information indicating that the cancellation of a message previously sent is requested (and not the cancellation of the meeting)."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="MsgCxl"
    complexType="_RVa40tp-Ed-ak6NoX_4Aeg_-1270467118" />
  <messageBuildingBlock
    xmi:id="_TlcXEtEwEd-BzquC8wXy7w_1445576923"
    name="MeetingReference"
    definition="Series of elements which allow to identify a meeting."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="MtgRef"
    complexType="_Tk62R9p-Ed-ak6NoX_4Aeg_-8393617" />
  <messageBuildingBlock
    xmi:id="_TlcXE9EwEd-BzquC8wXy7w_1723554265"
    name="NotifyingParty"
    definition="Party notifying the cancellation of the meeting."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="NtifngPty"
    complexType="_QRUXhtp-Ed-ak6NoX_4Aeg_967984948" />
  <messageBuildingBlock
    xmi:id="_TlcXFNEwEd-BzquC8wXy7w_1760496175"
    name="Security"
    definition="Identifies the security for which the meeting was organised."
    registrationStatus="Provisionally Registered"
    maxOccurs="200"
    minOccurs="0"
    xmlTag="Scty"
    complexType="_QTaCNdp-Ed-ak6NoX_4Aeg_-582916783" />
  <messageBuildingBlock
    xmi:id="_TlcXFdEwEd-BzquC8wXy7w_1802979520"
    name="Reason"
    definition="Defines the justification for the cancellation."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Rsn"
    complexType="_RCMa19p-Ed-ak6NoX_4Aeg_1000768570" />
  <messageDefinitionIdentifier
    businessArea="seev"
    messageFunctionality="002"
    flavour="001"
    version="03" />
</messageDefinition>

ISO Building Blocks

The following items are used as building blocks to construct this message.