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

Re: FpML-BP FW: AWG Teleconference June 3 at 9am NYC/2pm LON - spreadsheet with message names


I'm afraid the proposal does not work for me, mainly because of the apparent confusion of terms such as "Advice" and "Request".

Formerly in FpML, we recognised two basic patterns: Notification and Request/Response.

Notifications are "fire-and-forget" messages - the sender does not expect any response, and it is the responsibility of the receiver to decide what action to take on receipt of the message (if any), without any obligation to report back to the sender.

In a Request/Response pattern, the message sender expects to receive a defined response, which the receiver is obliged to produce (possibly asynchronously).

More recently, we have added the "Advice" pattern, which can be thought of as intermediate between pure notification and request/response. An Advice functions like a notification, but the receiver may return an acknowledgement, to indicate successful processing, or an exception message to indicate a processing fault. The acknowledgement may contain business content e.g. identifiers issued by the receiving system.

Lastly, some of our processes provide for intermediate acknowledgement/exception messages within a request/response pattern.

We have decided to make the messaging pattern explicit by adding an appropriate suffix to the message name e.g. -Notification, -Request, -Advice.

From this point of view, a construction such as "tradeChangeAdviceRequest" is ambiguous (is this an Advice message, which I might optionallly acknowledge, or a Request to which I am obliged to produce a strongly-typed Response?).

I suggest we construct a table detailing for each pattern, the suffixes used for process initiation, retraction and the various flavours of response (maybe we have such a table already ...?). For example, suffixes employed in the Advice pattern would be:

Initiation                -Advice
Retraction                -AdviceRetraction
Acknowledgement        -Acknowledgement
Exception                -Exception

- so we would use process-nameAcknowledgement, instead of process-nameAdviceAcknowledgement

Let's discuss further on the call ...
Best regards,
Harry





__________________________________________________________________________
Harry McAllister | Information Architect | Fixed Income Architecture | BNP Paribas
4R223 | 10 Harewood Avenue | London NW1 6AA
tel: +44 (0)20 7595 3416 | email : harry.mcallister@xxxxxxxxxxxxxx



Internet  
MGratacos@xxxxxxxx

Sent by: bpwg@xxxxxxxx

03/06/2010 09:46

Please respond to
bpwg@xxxxxxxx
To
awg@xxxxxxxx
cc
bpwg@xxxxxxxx
Subject
FpML-BP FW: AWG Teleconference June 3 at 9am NYC/2pm LON - spreadsheet with message names





See attached proposal from Irina (.xlsx)

________________________________________
From: Irina Yermakova
Sent: Wednesday, June 02, 2010 6:54 PM
To: Marc Gratacos
Subject: FW: AWG Teleconference June 3 at 9am NYC/2pm LON - spreadsheet with message names

Marc,

I attached updated 5-0-Messages-Naming patterns.xlsx with my messages naming proposal. Basically, I agree that the 5-0 messages naming needs to be corrected, but I against the first proposal only because it does not go far enough and creates more ambiguity in the naming of the message processes.

Let me know your thoughts about my proposal.

P.S. I added 3 comments as well (look for red triangle) could you review them too? It looks that two messages that are currently notifications needs to be a response instead.

Thank you,
Irina

-----Original Message-----
From: owner-awg@xxxxxxxx [mailto:owner-awg@xxxxxxxx] On Behalf Of Marc Gratacos
Sent: Monday, May 31, 2010 6:25 AM
To: awg@xxxxxxxx
Cc: bpwg@xxxxxxxx
Subject: FpML-AWG AWG Teleconference June 3 at 9am NYC/2pm LON - spreadsheet with message names
Importance: High

As agreed in the previous AWG call, next Thursday will continue the discussion around the FpML 5.0 messaging issue reported by LCH.Clearnet. See attached a spreadsheet with the list of messages and their names with the current and proposed patterns. Please propose alternative patterns if you want.

Members of the BPWG interested in this issue please join the call.

US: 888 481 3032
Intl: 617 801 9600
UK: 0800 904 7961
Participant Code: 8682747

Agenda.

1. Message Naming Issue
2. AOB


Thanks,
Marc

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 <mailto: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.

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 <mailto: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.
[attachment "Message Naming Issue.docx" deleted by Harry MCALLISTER/UK/EUROPE/GROUP] [attachment "5-0 - Messages - Naming patterns.xlsx" deleted by Harry MCALLISTER/UK/EUROPE/GROUP] 
___________________________________________________________
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is prohibited.

Please refer to http://www.bnpparibas.co.uk/en/information/legal_information.asp?Code=ECAS-845C5H  for additional disclosures.