FpML-VALU improve scheduledDate/assetReference model

["Marc Gratacos" <MGratacos@xxxxxxxx>]

Hi all,

 

Related to the issue http://www.fpml.org/issues/view.php?id=210

 

The assetReference element within scheduledDate can point to multiple places.

 

The current example that we have (based on the DSWG example for position reporting) shows pointers to trade and product leg (interest leg, equity leg,...). In order to improve the clarity of the model, I'd suggest creating a choice between legReference and tradeReference and deprecate the current assetReference element (leave it at the schema for backward compatibility reasons). This would clarify the targets of these pointers and the model for this structure.

 

Let me know your thoughts.

 

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