As agreed in the 4.x series (see AWG minutes, issue #161 resolution, and 4.x schema), the MessageAddress attribute partyIdScheme should be renamed messageAddressScheme in the 5.0 release. fpml-msg.xsd ” The data type used for identifying a message address. It includes a partyIdScheme for keeping the type backward compatible with the PartyId complex type. In the … Continued
Today the definition of NotificationMessage is: 1. NotificationMessage extends Message and mixes in NotificationMessageHeader. 2. Message does not contain MessageHeader. 3. NotificationMessageHeader extends MessageHeader. I suggest instead: 1. Message contains a Message Header. 2. NotificationMessage extends Message. The same is also true for RequestMessage and ResponseMessage. I propose the same for them also. This would … Continued
Attached is a proposal to bring the FpML FRA model into line with the ISDA 2006 Definitions.
The invalid validation examples invalid-ird-32-00.xml is schema invalid. The validation examples should be schema invalid. The example invalid-ird-32-00.xml should be fixed. The offending piece of XML is: Standard ACT/360 It is missing an element.
The validation rule ird-35 doesn’t take into account schema optionality. The correct behaviour is for the validation rule to take into account the schema. The rule today is: ” Context: PaymentDates (complex type) ird-35 (Mandatory) firstPaymentDate < lastRegularPaymentDate. " The problem is that both firstPaymentDate and lastRegularPaymentDate are not required elements. A good example of … Continued
The validation invalid example invalid-ird-38-00.xml is schema invalid. The validation rule examples should all be schema valid. The problem is that the //fpml:initialStub and //fpml:finalStub are missing. Below is the offending snippet of XML.
The validation rule ird-46 doesn’t take account of the optionality of elements. The current rule is: ” Context: OptionalEarlyTermination (complex type) ird-46 (Mandatory) In cashSettlement/cashSettlementValuationDate/dateRelativeTo, the @href attribute must point to the @id attribute of cashSettlement/cashSettlementPaymentDate. ” A good example is valid-ird-46-01.xml. In this example, supposedly valid for this rule, the path //element(*, OptionalEarlyTermination)/cashSettlement/cashSettlementPaymentDate/relativeDate/dateRelativeTo/@href does … Continued
ird-47 doesn’t use XPath for axis. The Validation Architecture requires paths to be given using XPath for axis in the body of the rules. The rule should be changed to use XPath for axis. The rule today: ” ird-47 (Mandatory) In cashSettlement/cashSettlementPaymentDate/relativeDate/dateRelativeTo, the @href attribute must point to the @id attribute of americanExercise, bermudaExercise or … Continued
The invalid example invalid-cd-38-01.xml is valid. The example should be invalid for rule cd-38. The /FpML/trade/creditDefaultSwap/generalTerms/basketReferenceInformation/referencePool/referencePoolItem/constituentWeight/basketPercentage sum to 1. 0.60 Agrium Inc. 008HA7 008916AB4 0.077 2017-02-01 NorthAmericanInvestmentGrade 0.40 Tenet Healthcare Corporation 8G836J 88033GAT7 0.06 2011-12-01 NorthAmericanInvestmentGrade
The example valid XML document valid-cd-38-02.xml is not valid against the rule. Rule cd-38 states today: ” Context: ReferencePool (complex type) cd-38 (Mandatory) The sum of referencePoolItem/constituentWeight/basketPercentage is equal to 1 or no referencePoolItem/constituentWeight exists. ” If any of the //constituentWeight is described using //constituentWeight/openUnit or //constituentWeight/basketAmount then it will not equal the value “1” … Continued