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

RE: FpML-BP meeting tomorrow June 27


I raised two separate issues:
  1. Observable conversation completion
  2. Message accepted as the happy path alternative to Message rejected in the business process definition

I can see how this solves the second issue, but not the first. Yet, the document references the first. How is that?


The lessons from SWIFT, FIX, and 20022 should not be rediscovered:
  1. The separation of transport and business layers (session and application in FIX parlance). This is necessary otherwise the transport business process definition (accept, reject), has to appear in the business process definition. How would this layering work in FpML?
  2. The message transport characteristics. This is a series of requirements of the transport which must be known to understand the transport process definition and the business process definition. Marc Gratacos distributed an early draft of the ISO20022 standard for these. What should these be for FpML?

I support the proposal and it is an improvement in itself, but it is not a complete solution because we must also implement the separation of layers and define the message transport characteristics.

I suggest all 3 changes are needed.

Matthew Rawlings
+44 7917 596 827


"Irina Yermakova" <IYermakova@xxxxxxxx>
Sent by: bpwg@xxxxxxxx

27/06/2007 14:37

Please respond to
bpwg@xxxxxxxx
To
<bpwg@xxxxxxxx>
cc
Subject
RE: FpML-BP meeting tomorrow June 27





Attached is a proposal for a response message to a request or a
notification, with the ability to indicate that the message was received
successfully (but not necessarily processed).

Regards,
Irina Yermakova

-----Original Message-----
From: bpwg@xxxxxxxx [mailto:bpwg@xxxxxxxx] On Behalf Of Marc Gratacos
Sent: Tuesday, June 26, 2007 6:08 AM
To: bpwg@xxxxxxxx
Subject: FpML-BP meeting tomorrow June 27

The next BPWG meeting will be on Wednesday June 27 from 10:30 to 11:30
New York Time.

Agenda
------
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.
>>> MG Check with validation Working group on rationale for not
including validation rules for product type scheme.

2. Generic product (see updates from Brian)
3. Confirmation Choreography (Steve Ross-Talbot; see email with
materials sent by Steve. Please review them before the meeting)
4. AOB

Call details:

US: 1 888 481 3032
UK: 0 800 904 7961
Intl: 1 617 801 9600
Code: 8682747

Best Regards,
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 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 Accepted Proposal.doc" deleted by Matthew D Rawlings/JPMCHASE]

This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates. This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to UK legal entities.