The next BPWG meeting will be on Wednesday June 6 from 10:30 to 11:30 New York Time. Agenda ------ 1. Review of actions >>> MG to document scenarios where lack of message rejected/timeout for cash flow matching messages this is required. >>> 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. >>> Action: BL/MG to document that generic product is intended to be used only for portfolio composition reporting and reconciliation >>> BL Update generic product representation. >>> MG Check with validation Working group on rationale for not including validation rules for product type scheme. 2. Confirmation Choreography (Steve Ross-Talbot; see email with materials sent by Steve today) 3. Generic product (see updates from Brian) 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. **************************************************************************************************************************
--- Begin Message ---
- To: <bpwg@xxxxxxxx>
- Subject: RE: FpML-BP amended minutes 5/23 - generic product
- From: "Brian Lynn" <brian.lynn@xxxxxxxxxxxxxxxxxxx>
- Date: Thu, 31 May 2007 08:59:53 -0400
- In-reply-to: <B7C16C1424A7CE40981DA74035F88A8001D1E243@xxxxxxxxxxxxxxxxxxxxx>
- References: <B7C16C1424A7CE40981DA74035F88A8001D1E243@xxxxxxxxxxxxxxxxxxxxx>
- Reply-to: <bpwg@xxxxxxxx>
- Sender: <bpwg@xxxxxxxx>
- Thread-index: Aceh3Bj9bX6N3WtISO6E9JiKaCLtUAAH5hQAAGG+jdA=
- Thread-topic: FpML-BP amended minutes 5/23 - generic product
I've updated the generic product as discussed last week. Main changes included: - add a couple of missing fields from the portrec spreadsheet - removed a number of the option details fields (and the entire structure). I've attached a diagram and the schema files (the main one to look at is fpml-generic-4-2.xsd). - Brian -----Original Message----- From: bpwg@xxxxxxxx [mailto:bpwg@xxxxxxxx] On Behalf Of Marc Gratacos Sent: Tuesday, May 29, 2007 10:16 AM To: bpwg@xxxxxxxx Subject: FpML-BP amended minutes 5/23 Present ======= Brian Lynn (GEM) Irina Yermakova (ISDA) Michael Fitzgerald (SWIFT) Pierre Lamy (GS) Vinod K Jain (Bank of New York) Christian Unger (BBH) John Booth (Northern Trust) Steve Ross-Talbot (Hattrick) Marc Gratacos (ISDA), chair Minutes ======= Review of Actions 1. Review of actions >>> Action (OPEN): MG to document scenarios where lack of message rejected/timeout for cash flow matching messages this is required. >>> Action (OPEN): 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. >>> Action: BL/MG to document that generic product is intended to be used only for portfolio composition reporting and reconciliation (deferred to Generic Product discussion) >>> Action (DONE): BL to identify the new fields that would be required to meet the list in the spreadsheet for the portfolio reconciliation data standards (attached) >>> Action (DONE): IY circulate the existing portfolio reconciliation Documentation 2. Product types: disagreement on the fact that the Validation Working doesn't agree to include product type rules as validation rules. These rules should applicable to the FpML scheme. If it is not included, it can be published as separate document with links from the values description. 3. Generic product: GS uses a very skinny representation for complex products. Agreement that there are benefits on including this generic product. There is an open question on whether a more optional representation based on the confirmation view is better than a generic representation. Brian mentioned that from his experience, in some cases, the data is so poor that it is even hard to fill out the elements that you'd require for generic product. Agreement to include generic product for reconciliation. Need to update elements based on the analysis that Brian did. AOB Issues with choreography and fixing identities. We'll talk about it in the next meeting. People can continue discussions in the mailing list. Actions ======= MG Check with validation Working group on rationale for not including validation rules for product type scheme. BL Update generic product representation. 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. ************************************************************************ ************************************************** ------------------------------------------------------------------------ ------- To unsubscribe: Email majordomo@xxxxxxxx with a blank subject line In the body include the line: unsubscribe bpwg youremail@address To view archives: http://www.fpml.org/_wgmail/_bpwgmail/threads.html ---------------------------------------------------------------------------- --- To unsubscribe: Email majordomo@xxxxxxxx with a blank subject line In the body include the line: unsubscribe bpwg youremail@address To view archives: http://www.fpml.org/_wgmail/_bpwgmail/threads.htmlAttachment: generic_product.jpg
Description: generic_product.jpgAttachment: fpml-valuation-base-4-2.xsd
Description: fpml-valuation-base-4-2.xsdAttachment: fpml-asset-4-2.xsd
Description: fpml-asset-4-2.xsdAttachment: fpml-enum-4-2.xsd
Description: fpml-enum-4-2.xsdAttachment: fpml-generic-4-2.xsd
Description: fpml-generic-4-2.xsdAttachment: fpml-shared-4-2.xsd
Description: fpml-shared-4-2.xsd
--- End Message ---
--- Begin Message ---
- To: <bpwg@xxxxxxxx>
- Subject: FpML-BP Choreography model for FpML 4.3 Confirmations
- From: "Steve Ross-Talbot" <steve.ross-talbot@xxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 5 Jun 2007 09:42:47 -0400
- Reply-to: <bpwg@xxxxxxxx>
- Sender: <bpwg@xxxxxxxx>
- Thread-index: Acend4Kpf0HUqDNLQ1mrqykoTAQtVw==
- Thread-topic: FpML-BP Choreography model for FpML 4.3 Confirmations
If you download the eclipse environment at: http://www.pi4tech.org/tiki-index.php?page=pi4soa+Downloads There is a single click download in the section entitled: " Installing a standalone version" Pick the big one with BPMN and UML generation. Create a workspace folder to put things in and then unzip the model zip file into that workspace folder. In eclipse set your workspace to point to the newly created workspace folder and create a simple java project named: Confirmations-FpML4.3 This should pick up the enclosed project which you can then look at. When you create the project do not take the default perspective, when the dialogue comes up say no. The project is structured as follows: src src/choreography src/choreography/models which is where the Confirmations.cdm choregraphy description is located. Double click on it and it should come up. You should have three panels on the left called Roles and Relationships, Base Types and Choreography Flows. src/choreography/bpmn which is where the BPMN rendering is located. src/choreography/html which is where the html rendering of the choreography is. I would use this for review. You can right click on the html file and Open With a browser. src/choreography/uml which is where the xmi representation is. We use MagicDraw Enterprise to look at it.Attachment: Confirmations-FpML4.3.zip
Description: Confirmations-FpML4.3.zip
--- End Message ---