[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

FpML-BP minutes June 27



Participants

Christian Unger (BBH)

Lucio Iida (BGI)

Marie-Paule Dumont (SWIFT)

Banu Apers (SWIFT)

John Booth (Northern Trust)

Brian Lynn (GEM)

Mike Fitzgerald (SWIFT)

Gary Brown (Hattrick)

Henri Pegeron (DTCC)

Andrew Jacobs (HandCoded)

Irina Yermakova (ISDA)

Marc Gratacos (ISDA), chair

 

Regrets

Francoise Massin (SWIFT)

 

1. Review of actions

> IY to propose a message or messages for responding to a request or a notification, with the ability to:

- indicate that the message was received (but not necessarily processed)

- indicate that the message was processed successfully.

>> There was a discussion on this. This proposal could be applied in different business processes and a request message could have a flag to receive a response (ack). Andrew Jacobs expressed the concern that the introduction of a message accepted at the same level as the existing business messages would blur the distinction between the different layers. There should be a complete business process definition with messages for not continuing the process. FpML assumes reliable message delivery. We should look at WS-Reliability standards to see if this could be used in conjunction with FpML for adding this extra layer of messaging.

 

> MG Check with validation working group on rationale for not including validation rules for product type scheme.

>> TO DO.

 

2. Generic product (see updates from Brian)

There was agreement on the group to publish the generic product representation. We’ll send a call for comments to publish it in version 4.4.

 

3. Confirmation Choreography (Steve Ross-Talbot; see email with materials sent by Steve. Please review them before the meeting)

Gary and Steve took the Confirmation process as defined in the messaging specifications and translate it into CDL. Marc asked the group to review it and send any comments to the mailing list. Gary stated that there are some open questions regarding the use of token identifiers and defining the combination of elements that constitute a primary identifier: conversation id + Event id + Trade id? There was no decision on this.

 

4. AOB

None

 

Kind Regards,

-Marc

+13472846531

 

 

************************************************************************************************************************** The information contained in either this email and, if applicable, the attachment, are confidential and are intended only for the recipient. The contents of either the email or the attachment may not be disclosed or used by anyone other than the addressee. If you are not the intended recipient(s), any use, disclosure, copying, or distribution is prohibited and may be unlawful. If you have received this communication in error, please notify us by e-mail at isda@xxxxxxxx then delete the e-mail and all attachments and any copies thereof. This communication is part of an ISDA process and is not intended for unauthorized use or distribution. **************************************************************************************************************************