FpML Issues Tracker

1036: Schema annotation for ConfirmationStatus

February 7, 2011

closed

Major

Always

Business Process

Admin

mgratacos

Summary

Type ConfirmationStatus contains a choice model of the form:

(assertedEvent, proposedMatch*)|allegedEvent,

where assertedEvent and allegedEvent are both of type EventsChoice, proposedMatch is of type EventProposedMatch.

None of these elements is annotated, and there is no schema annotation to explain the circumstances in which assertedEvent and/or allegedEvent should be used, or the rationale for choosing between them.

There does not seem to be any specific documentation for the content of ConfirmationStatus in the html documentation set. This needs to be addressed as we are now seeing market initiatives which implement FpML 5-1 confirmation messaging.

Notes:

  • mgratacos

    02/10/11 3:45 pm

    I have added annotations to the elements:



    Message for sending matching results. Response message that returns the status of an event that have been submitted for matching.






    Defines the confirmation status of a trade or post-trade event (e.g. Matched, Mismatched, Unmatched, Alleged).






    Event (trade or post-trade event) asserted by one of the parties.




    “Other side’s” event (trade or post-trade event) that meets the minimimum matching criteria and is proposed as match to the event that is being asserted.





    Event (trade post-trade event) asserted by the “other side’s” party.







  • mgratacos

    09/27/11 9:24 pm

    I have added html documentation with a brief description and diagram for each message:

    3.4.3.6.1.1 requestConfirmation

    The confirmation process starts with the requestConfirmation message. The message may be used to request the confirmation of a new trade or any other event supported by FpML such as novation, terminations, amendments, etc.

    3.4.3.6.1.2 requestConfirmationRetracted

    A requestConfirmation message may be cancelled using the requestConfirmationRetracted message.

    3.4.3.6.1.3 confirmationAcknowledgement

    A business acknowledgement message to indicate that the previously sent message was sucessfully processed.

    3.4.3.6.1.4 confirmationException

    A message sent to inform another system that some exception has been detected.

    3.4.3.6.1.5 confirmationStatus

    The confirmationStatus message provides the status of the matching process: matched, mismatched, unmatched, or alleged. It may also provide the best fit trade(s) or event(s) as result of the matching process.

    3.4.3.6.1.6 confirmationAgreed

    The confirmationAgreed message is sent when the matching process returns a proposed match (trade or event) and the Confirmation Requester agrees with it.

    3.4.3.6.1.7 confirmationDisputed

    The confirmationDisputed message is sent when the matching process returns a proposed match (trade or event) and the Confirmation Requester disputes it.

  • Leave an update

    You must be logged in to post an update.