|
Hi Bhavik
Are you back in NY – let’s catch up soon. I would like to introduce you to our new COO Bill Buble (formerly JPM).
Can you add him to FpML distribution list? Thanks and give me a call to set up lunch/drinks, Elaine Elaine E. Davis Managing Director- Special Projects Trade Settlement Inc. Tel: 212.463.9763 Cel: 917.270.0769 Customer Support: 212.463.7801
From: loanwg@xxxxxxxx [mailto:loanwg@xxxxxxxx]
On Behalf Of Bhavik Katira Right. Also, it seems that the loan group want to participate in the design effort – ensuring that we have a solution that will
work for all. To this end, we would not introduce the event id for this version and include it within v4.5. FYI – ISDA would like to tag and build v4.4 this week, so we are aiming to finalize the documentation/schema by end of day today. Thanks, BK From: loanwg@xxxxxxxx [mailto:loanwg@xxxxxxxx]
On Behalf Of Marc Gratacos There is currently a discussion within the FpML Modeling Task Force about this topic and I think it’s going to a similar direction as
Derek is pointing at with eventIdentifier, having a similar structure as ContractIdentifier. The modeling group is also looking at ways to explicitly indicate the primary identifiers from a list of ids. It probably makes sense to pursue this direction, but
the only issue is that this is a general problem in FpML currently in discussion that affects all business processes so it will take some time to solve it and I think it won’t be ready for 4.4. Since the current processes modeled by this group don’t require
the use of eventId, I’d suggest not introducing the concept of eventId in this version yet and wait for an appropriate solution in a later phase. Best regards, Marc
From: loanwg@xxxxxxxx [mailto:loanwg@xxxxxxxx]
On Behalf Of derek.n.lasalle@xxxxxxxxxxxx Something we have modeled internally leverages the concept of causalEvents and resultantEvents. Each resultantEvent has an idRef to the causalEvent that initiated it. Both the causalEvent
and resultantEvent can be of various event types either explicitly (rolloverEventId) or a scheme/typeEnum combined generic structure to model events not known apriori in the model for extensibility. ----- Original Message ----- Agree on the need for multiple event id’s for integration etc. But the other design point I am thinking about is whether the event ids really belong at the notice level or whether they belong
within the body of the business event fields. Thinking forward, when we start to combine some of these ‘business events’ together (e.g. in a rollover), we may want to specify each of the business events separately (rollover has a repayment, interest payment
etc)…? Of course, the alternative is that when we combine these events into a rollover… they are all considered to be ONE event. ? BK From: loanwg@xxxxxxxx [mailto:loanwg@xxxxxxxx]
On Behalf Of derek.n.lasalle@xxxxxxxxxxxx Highly recommended that a similar model for event identifier is taken from trade identifiers with versionedEventIdentifer containing a version in cases of amends. Since identifiers of events
are assigned by originating systems and other participating parties/applications, the requirement is to inject their own event identifiers into the same <eventIdentifiers> parent collection. Each <eventIdentifier eventIdScheme="urn or uri of id source"> has
a scheme. This a crucial structure for integration. Event id's are separate from message id's which are different for each message sent. ----- Original Message ----- A follow up question to this is whether people think that we should have the ability to store multiple event id’s…? I.e. different vendors may want to store their own id’s in the messages… Any feedback on this from anyone…? _____________________________________________ All, It came to our attention that in previous discussions we spoke about introducing a business event id to all of our notices.
In the current design, there is a “message id” in the header section, which is unique for every single message sent out. However, if for any reason there are multiple messages sent out all referring to the same business event then they should all have the same “event id”. This event id has been
introduced at the Facility Notice and Loan Contract Notice levels. It is a required field and the sender of the message would populate the id based on their own scheme definition. Please take a look at the attached and provide any feedback ASAP. Note: The event id type used is inherited from an existing FpML structure. Thanks, BK << File: eventid.doc >>
Generally, this communication is for informational purposes only and 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. In the event you are receiving the offering materials attached below related to your interest in hedge funds or private equity, this communication may be intended as an offer or solicitation for the purchase or sale of such
fund(s). 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 ************************************************************************************************************************** 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. ************************************************************************************************************************** Generally, this communication is for informational purposes only and 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. In the event you are receiving the offering materials attached below related to your interest in hedge funds or private equity, this communication may be intended as an offer or solicitation for the purchase or sale of such
fund(s). 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 IMPORTANT NOTICE: The message and any attachments (the "message") is intended solely for the addressee(s) and is confidential. If you receive this message in error, please delete it from your computer immediately and notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except with formal approval. |