Harry McAllister — I note that, in both recordkeeping and transparency view, the annotation for element [Party]TradeInformation nonStandardTerms reads: Specifies whether the trade contain.When the clearing status changed to the current value. This is mostly useful if the clearing status messages could be delayed from when the status actually changes; this could be important if … Continued
Shared component type Address contains several elements of type xsd:string: . streetLine . city . state . postalCode None of these elements requires to be an unrestricted string e.g. it would be undesirable for an Address component to contain non-printing/control characters. Element ‘streetLine’ has multiple occurence, suggesting that a multi-line street address should be represented … Continued
In 5.0 the element ‘scheduledTerminationDateadjustableDate’ was removed from the schema when the type of ‘scheduledTerminationDate’ was changed to be an adjustable date. Rules cd-5, cd-8, cd-21, cd-21b, cd-27, cd-28 and cd-30 need to be updated with the new path.
This example does not appear to contain any element that would cause CD-19 to be triggered. This problem applies to earlier versions as well.
Hi. I find myself importing/including/redefining/extending/restricting the FpML 5.3 schema to build an internal OTC messaging standard. Since this entire exercise is driven by our DFA reporting and recordkeeping requirement we have chosen the recordkeeping view as the base model. Is there a reason why versionedTradeId is not available in partyTradeIdentifier of the recordkeeping view of … Continued
The definition of the ISDA1999Credit condition states the XPath as documentation/contractualDefinition but its missing an ‘s’ and should be documentation/contractualDefinitions
by garyjkennedy on 2012/2/11 18:47:04 There is a small typo in the following document Financial Date Calculations in FpML Validation Working Group Editor: Andrew Jacobs Updated: 2011-01-25 Page 10, the pseudo code for the function PeriodStartDates makes reference to a parameter “startDate” concerning the initial stub, probably it is meant to be “effectiveDate” which is … Continued
In fpml-reporting.xsd -> within “PositionActivityReport”, “terminatingEventsReport”, incorrect fromDateTime and toDateTime elements’ type. The type should be “xsd:dateTime” instead of “xsd:date”. This affects several reports in the reporting subschema (PositionActivityReport and TerminatingEventsReport), and changing the type from “xsd:date” to “xsd:dateTime” is a non-backward compatible change.
I noticed that some of the examples for terminations have a negative value in changeInNotionalAmount (see confirmation view/business-processes/confirmation) while other have a positive one (see execution-advice examples). Something is wrong. What is the correct approach? I thought it was a positive number always. This is how this field was implemented in 4.x versions, even though … Continued
All, On behalf of the HKMA-HKICL I have a request to change the naming of the “cleared” indicator inside PartyTradeInformation. The fact that the flag is named “cleared” while the trade may not be cleared yet is causing a lot of confusion among the HK TR users. The description of the element is correctly defined … Continued