340: define ProblemLocation
What is ProblemLocation? Is it text, an XPath, a line number? What may it be? How should I interpret it? Please add a definition.
Latest Posts
339: Add a definition of ConversationId in fpml-msg.xsd
Add a definition of ConversationId in fpml-msg.xsd
338: Add a definition for IndexAdjustmentEvents in fpml-eq-shared.xsd
Add a definition for IndexAdjustmentEvents
337: Add definition for MarketDisruption in fpml-eq-shared.xsd
Add definition for MarketDisruption in fpml-eq-shared.xsd
336: add definition for AdjustableDateOrRelativeDateSequence in fpml-eq-shared.xsd
Add a definition for the complex type AdjustableDateOrRelativeDateSequence in fpml-eq-shared.xsd
335: Element governingLaw is undocumented
file: fpml-doc-4-2.xsd TBA Coding scheme file “governing-law-1-0.xml” associated with type “GoverningLaw” contains the description “Identification of the law governing the transaction”
334: custodian receives trade twice
Custodians sometimes receive the same trade twice, once for each trade side. How can a custodian tell who the message was on behalf of? They can’t look at sender as it may be ent by an agent or proy. Is receiving the same message twice a business process bug I suggest adding a party reference … Continued
333: partial novation
Provide partial novation in the contract messages. This came out of the SWIFT CUG.
332: make tradeId version mandatory
tradeId version should be made mandatory. This issue arose from the SWIFT CUG, and Andrew Parry and Marc Gratacos.
331: master agreement message
Add support for sending the master agreement to set up the master defaults. This is necessary for people such as custodians who need a copy of the Master Agreement.