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)
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
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
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
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
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
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
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.