The MTF is streamlining the implementation of Booleans in 5.0 and is asking each WG to go through the attached list of booleans in an attempt to consolidate: Optional Booleans of type xsd:Boolean Optional Booleans of type Empty The meaning of optional Boolean fields is not always being clear and consistent; Some were made optional … Continued
fpml-fx.xsd” uses enumerated types such as PayoutEnum, but does not directly include the file “fpml-enum.xsd”, where enumerated types are defined. This causes some XML Schema aware tools to fail.
The current rule says: If facilityIdentifier/originalCommitmentAmount and facilityCommitmentPosition/loanContractPosition/loanContractIdentifier/originalAmount/amount exist, then facilityIdentifier/originalCommitmentAmount >= facilityCommitmentPosition/loanContractPosition/loanContractIdentifier/originalAmount/amount. It should say instead: If facilityIdentifier/originalCommitmentAmount and facilityCommitmentPosition/loanContractPosition/loanContractIdentifier/originalAmount exist, then facilityIdentifier/originalCommitmentAmount/amount >= facilityCommitmentPosition/loanContractPosition/loanContractIdentifier/originalAmount/amount.
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)