RE: FpML-VALU TradeValuationItem

Brian,

Any thoughts on this? See below.

Thanks,

Marc

From: prwg@xxxxxxxx [mailto:prwg@xxxxxxxx] On Behalf Of Marc Gratacos
Sent: Thursday, August 31, 2006 12:38 PM
To: prwg@xxxxxxxx
Subject: RE: FpML-VALU TradeValuationItem

Brian,

Maybe I am missing something but I am looking at the content of TradeValuationItem and I don't understand its content model. Why do we have trade with maxOccurs="unbounded"? Shouldn't we have a single trade element only?

In addition, shouldn't we have a choice between partyTradeIdentifier and trade?

<xsd:complexType name="TradeValuationItem">
  <xsd:annotation>
   <xsd:documentation xml:lang="en">A type used in trade valuation enquiry messages which relates a trade identifier to its current value.</xsd:documentation>
  </xsd:annotation>
  <xsd:sequence>
   <xsd:element name="partyTradeIdentifier" type="PartyTradeIdentifier" minOccurs="0" maxOccurs="unbounded">
    <xsd:annotation>
     <xsd:documentation xml:lang="en">One or more trade identifiers needed to uniquely identify a trade.</xsd:documentation>
    </xsd:annotation>
   </xsd:element>
   <xsd:element name="trade" type="Trade" minOccurs="0" maxOccurs="unbounded">
    <xsd:annotation>
     <xsd:documentation xml:lang="en">Fully-described trades whose values are reported.</xsd:documentation>
    </xsd:annotation>
   </xsd:element>
   <xsd:element ref="valuationSet">
    <xsd:annotation>
     <xsd:documentation xml:lang="en">The trade valuation.</xsd:documentation>
    </xsd:annotation>
   </xsd:element>
  </xsd:sequence>
</xsd:complexType>

From: prwg@xxxxxxxx on behalf of Brian Lynn
Sent: Wed 8/23/2006 18:30
To: prwg@xxxxxxxx
Subject: RE: FpML-VALU TradeValuationItem

The issue says that the TradeValuationItem should probably have only one partyTradeIdentifier, or there should be a rule that if there is more than one partyTradeIdentifier, it should refer to the same trade.

The existing documentation on that item says, “One or more trade identifiers needed to uniquely identify a trade.” This implies that the multiple trade IDs are for the same trade. I’m not sure if it’s possible to create a rule that enforces this.

Should we update the documentation on the element to make this more explicit?

- Brian

From: prwg@xxxxxxxx [mailto:prwg@xxxxxxxx] On Behalf Of Marc Gratacos
Sent: Tuesday, August 22, 2006 5:20 AM
To: prwg@xxxxxxxx
Subject: FpML-VALU TradeValuationItem

Brian,

See question posted in the issues list: http://www.fpml.org/issues/view.php?id=204

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