Author: Admin

Should there one main identifier and potentially multiple alternates? Andrew Jacobs

What would this mean? How would you tell which was the primary one? Andrew Jacobs

Isnt it possible to define at least some field combinations that must be present? Andrew Jacobs

In other products we have changed the rules so allow components to be in any order. Andrew Jacobs

1. Why are DealIdentifier and FacilityIdentifier derived from Product? I cant see why they need to be as they are not used within a or structure and being derived this way creates an opportunity for accidental misuse. 2. DealIdentifier can be completely empty The design of the type does not force any component to be … Continued

There is no indication of whether dates are unadjusted or adjusted, or whether this matters (e.g. rateFixingDate, period [start|end]Date, feePayment /effectiveDate, /paymentDate, …) Harry McAllister (BNPParibas)

Failure to use schema to control association of related elements (conditionsPrecedent[Met|Comment]; interestRate|margin|MCR|allInRate, …) – basic architecture Harry McAllister (BNPParibas)

“Position” structures (loanContract-, facilityCommitment-) containing current- and prior-Amount components, without an explicit value date or event identifier which would allow the consumer to determine current-as-of-when – confusion between event notification and historical record Harry McAllister (BNPParibas)

payment structures lack [payer|receiver]PartyReferences (interestPayment, feePayment) – so it is questionable whether the model meets the FpML principle of party neutrality. Harry McAllister (BNPParibas)

Rule shared-4 is today: ” Context: RelativeDateOffset (complex type) shared-4 (Mandatory) If the dayType is Business then the businessDayConvention should be NONE. ” The rule needs two changes. 1. NONE is a string. 2. “is” should be “=” 3. dayType=string Business is a condition ” shared-4 (Mandatory) Context: RelativeDateOffset (complex type)[dayType= string Business] Rule: businessDayConvention … Continued