* Present
Marc Gratacos, ISDA
Owen King, MarkitSERV (Chair)
Farzad Moshfeghi, Barcap
Irina Yermakova, ISDA
William Wise, MarkitSERV
* Apologies
Peter Stockman, DTCC
* Review outstanding actions
>> MG to clarify the intended use of RelativeDates/scheduleBounds
MG had not been able to do this. FM said he would also be able to
investigate the use of this element.
To summarise the original question, what is the intended use of the
scheduleBounds element within RelativeDates type? It would appear to be
of use in defining the start and end of the date sequence but since
RelativeDates contains the mandatory dateRelativeTo element and neither
unadjustedFirstDate nor unadjustedLastDate have an id attribute that
could be referenced by it, dateRelativeTo will have to reference an
external date.
>> RI to try and provide a confirmation for a daily expiring
physically-settled option
RI has supplied an example confirm.
[Closed]
>> FM to propose an alternative structure for physically settled options
that uses the existing commodityOption type
OK noted that the proposed schema had changed significantly since this
action was assigned and FM said that he was broadly in agreement with
the current proposal.
[Closed]
>> DM to propose an alternative structure for physically settled options
that uses the existing commodityOption type
DM was not on today's call [Carried forward]
* Minutes
1. Physical Options
- Review of feedback received for physical options survey
+ OK said that he had received feedback directly from one transactor
who indicated that they did trade options with quantities or strike
prices that varied during the term of the trade. Further validation from
other firms would be appreciated.
+ The group was broadly comfortable with the schema (pending further
feedback to the survey). OK will complete outstanding items and
distribute the schema and a test trade to the group.
2. Addition of optional totalPrice element to CommodityFixedPrice.model
- FM asked whether this meant the final price is known at the time of
execution. OK explained that for many physical commodities this would be
the case when a trade is "Firm". It is not anticipated that this element
will be widely used as the total price is simply the product of the
total quantity and fixed price. However, for very bespoke power trades
where the price differs by load shape and by period, counterparties may
include the total price on a confirmation due to the relative complexity
of the calculation.
- OK asked when this change could be included. MG noted the WD1 of
FpML 4.7 should be available next week and the change could be added to
these schemas for inclusion in the subsequent release.
3. Total Return Swaps on Commodity Indices
- OK asked the group for their thoughts on modelling TRS on commodity
indices in FpML and expressed the hope the returnSwap element could be
used for this. FM suggested that the initial area of focus should be on
the underlyer.
- OK explained that the ISDA Commodity Index Working Group were aiming
to produce standardised documentation in this area but had not yet
produced a confirmation template.
* Actions
[New] FM to clarify the intended use of RelativeDates/scheduleBounds
[Carried Forward] MG to clarify the intended use of
RelativeDates/scheduleBounds
[Carried Forward] DM to propose an alternative structure for physically
settled options that uses the existing commodityOption type
* Next meeting 15:00 UK / 10:00 US Fri 2nd October 2009
Attachment:
FpML Physical Commodity Options Survey.doc
Description: FpML Physical Commodity Options Survey.doc