Latest Posts

783: ln-10 facilityIdentifier doesn’t exist

By

ln-10 refers to the element facilityIdentifier. This element does not exist anywhere in FpML. Please correct ln-10. The rule today: ” ln-10 (Mandatory) Context: FacilityNotice (complex type) [facilityIdentifier/originalCommitmentAmount exists] [facilityCommitmentPosition/loanContractPosition/loanContractSummary/originalAmount exists] [same-currency((facilityIdentifier/originalCommitmentAmount,facilityCommitmentPosition/loanContractPosition/loanContractSummary/originalAmount)) = True] facilityIdentifier/originalCommitmentAmount/amount >= facilityCommitmentPosition/loanContractPosition/loanContractSummary/originalAmount/amount. “

782: FpML needs to consider creating merge all sub-schema together

By

FpML include paths in most of the cases are indirect. For example, “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 is Legal in XML Schema 1.0, but illegal in XML Schema 1.1 Tools should support XML Schema 1.0 fully, but unfortunately not … Continued

781: FX schema must use the currency type in fpml-shared for currencies

By

The FX schema must use the currency type in fpml-shared for currencies. This is affecting validation rules. The type of /FpML/trade/fxSingleLeg/exchangeRate/quotedCurrencyPair/currency1 is xs:normalizedString. This is wrong. Either this should be an IDREF within the document to refer to a currency ID or it should be of type “Currency”. Currency is defined in fpml-shared as: ” … Continued

780: Define xs namespace

By

The Validation Rules use the xs namespace but it is not defined. Add the definition of xs namespace to each page’s namespace definition. ln-8 is an example of using the xs namespace: ” ln-8 (Mandatory) Context: InterestAccrualSchedule (complex type)[MultipleLenderLoanContractPeriod(.)] Rule: every $startDate in $interestAccrualSchedule/lenderLoanContractPeriod[startDate > min($interestAccrualSchedule/lenderLoanContractPeriod/startDate)]/startDate satisfies $startDate – xs:dayTimeDuration(“P1D”) = $interestAccrualSchedule/lenderLoanContractPeriod/endDate Comment: Each lendLoandContractPeriod … Continued

779: shared functions section

By

The valwg agreed (2008-08-12) to create a new HTML page to list common functions which can be shared and reused across validation rules. Product specific validation rules will only list the names of reused functions and provide links to the function definitions located in the new HTML page (rules-functions.html)

778: Not all unique contexts listed

By

There is a problem in the XSLT that generates the “Unique Contexts” for the Validation Rules. An example is eqd-20: ” eqd-20 (Mandatory) Context: EquityOption (complex type) EquityOptionTransactionSupplement (complex type) ” There is no EquityOptionTransactionSupplement listed in the unique contexts. ” Unique contexts: * Trade (complex type): eqd-2 eqd-4 eqd-12 eqd-13 eqd-14 eqd-23 eqd-31 * … Continued

777: Parameters need $ to prevent them being confused with XPaths

By

As per the specifications, parameters need $ symbols to prevent them being confused with XPaths. This may need clarifying in the specification. Current example: ” Function: different-BusinessCenters The combination of businessCenter and businessCenter/@businessCenterScheme must be distinct for each businessCenter. * parameter: businessCenter (fpml:BusinessCenter) (cardinality: min=1) * test: All businessCenter must not be the same and … Continued

776: Meaningful title to HTML rules pages

By

Please add a meaningfule title to the HTML pages for rules. For example today’s rules-english-shared.html is: ” FpML 4.4 Validation Rules – 2008-06-09 ” This could be changed to: ” Shared Rules – FpML 4.4 Validation Rules – 2008-06-09 ” The key part is the “Shared Rules” so I can tell the different rules web … Continued