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

FpML-AWG minutes 2007-11-08



Participants

=========

Jason Pouflis (BGI)

Brian Lynn (GEM)

Andrew Jacobs (HandCoded), chair

Scot Baldry (Goldman Sachs)

Daniel Dui (Barcap)

Irina Yermakova (ISDA)

Lyteck L. (ISDA)

Marc Gratacos (ISDA)

Simon Heinrich (IONA)

Ketur Shah (DTCC)

 

 

  1. Updates
    1. Agreement to publish 4.3 Second Last Call Working Draft. The coordination committee expressed some concerns regarding the documentation of changes in the equity side. This has been resolved.
  2. 5.0
    1. Participants agreed to improve the documentation describing:

                                                               i.      Annotations that are being used in the Master Schema.

                                                             ii.      XSLT Transformation

                                                            iii.      Example of how to make extensions using the Master Schema.

    1. XSLT Transformation: Brian will check whether XSLT Transformation can be extended to cover extensions.
    2. There was some discussion about whether the transformation should be available in other languages, such as Java or C#, and generalized to be applicable to other vocabularies. In the short term it will be available in XSLT only and it will be simplified if possible.
    3. Views Schemas are the normative artifact. Master and transformation are non-normative technical artifacts released to help people understand the generation of views.
    4. People should have access to the transformation and Master Schema through Subversion and the Views Schemas should be published in the website. Access to Subversion is available to everybody. Requesting access to subversion may help filtering the people using transformation and Master Schema.
    5. All this documentation should be published in the Architecture 3.0 or as Technical Note. Publishing initially as a technical note may give us more flexibility to make changes. In the long term it should be part of the Architecture 3.0.
    6. Should the Working Groups create products for all views? WG can include products for specific views without necessarily having to cover all views.

 

 

Let me know if I missed anything.

 

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. **************************************************************************************************************************