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

FpML-RPTWG FpML Reporting minutes, Feb. 1, 2009



Attendees

========

Irina Yermakova, ISDA

Marcelle Van Wendland, Fincore

Sreedhar Segu, DTCC

Lucio Iida, Blackrock

Chris Funck, Chatham

Martin Sexton, London Market Systems

Brian Lynn, GEM

Ludvig Henriksson, Trioptima

Marc Gratacos, ISDA

 

 

1) Review status of actions

a)  Chris to provide additional sample data and Brian to convert to XML
>> done, provided with invitation

b)  Brian to update party model (change partyInfo type to group)
>> done, provided with invitation

c)  Brian to provide draft aggregate reporting requirements

>> done, provided with invitation

d)  d) Irina to update coding schemes for credit ratings and industry sector – in progress still, needs some feedback from Jai S. from GS.

e)  e) Marcelle V. will distribute a list of ECB party roles this week, to be discussed next meeting.

 

 

2) Review entity model and example, discuss refinements

>> we should review the model to try to make sure that at least one document type is there (if possible force using schema)

>> we should adjust the model slightly to make a distinction between related parties to a transaction vs. party relationships

>> should we add the ability to record status information about parties, e.g is in default? liquidation?

>> could indicate which asset class is in default?

>> Marcelle suggests keeping this in sync with the trigger conditions in a cds, use credit events e.g. from CEN

>> We should add an onBehalfOf element to represent who the report is being sent on behalf of.

 

 

3) Review aggregate reporting requirements

>> We reviewed the document briefly.  It was well received.  There were a few adjustments, such as:

-  at VAR as a reportable aggregate risk measure

- look at terminology when the report is from a central counterparty  (do we call it counterparties?)

 

 

Next meeting

===========

Monday,  Feb . 8, 11 am NY time – review updates to entity model, aggregate reporting requirements.