Latest Posts

831: ref-38 needs a more specific context

By

The rule ref-38 needs a more specific context. A second issue is that the element //element(*, MandatoryEarlyTermination)/cashSettlement/cashSettlementValuationDate is an optional element. The rule today is: ” ref-38 (Mandatory) Context: MandatoryEarlyTermination (complex type) The cashSettlement/cashSettlementValuationDate/dateRelativeTo/@href attribute = the @id attribute of an element mandatoryEarlyTerminationDate. ” The rule should probably be: ” ref-38 (Mandatory) Context: MandatoryEarlyTermination (complex … Continued

830: ref-18 requires optional element to be present

By

The rule ref-18 requires an optional element to be present. If the element is not present the rule will fail. The rule today is: ” ref-18 (Mandatory) Context: PricingStructurePoint (complex type) The coordinate/generic/@href attribute = the underlyingAsset/@id attribute ” The element “coordinate” is optional within PricingStructurePoint. One potential solution is to add a guard on … Continued

829: ln-27 “BreakageFee” is a value not an XPath

By

The value “BreakageFee” currently looks like an XPath, not a value in ln-27. Rule today: ” ln-27 (Mandatory) Context: OneOffFeeNotice (complex type) [feePayment/feeType = BreakageFee] loanContractSummary must exist. ” There are two things I need to know: 1. “BreakageFee” is a value. 2. The type of “BreakageFee”. If we wrote it out like the other … Continued

828: Define how to use a function

By

The FpML Validation Architecture specifies how to define a function, but not how to use a defined function. Please add this definition.

826: reference rules could be made more succinct

By

The Reference Rules are wordier than the Rules Specification directs us. The form of the the rules could be shrunk. The rule today: ” ref-1 (Mandatory) Context: AssetReference (complex type) The @href attribute = the @id attribute of an element of type Asset. ” First proposed form: ” ref-1 (Mandatory) Context: AssetReference (complex type) @href … Continued

824: repo-1 and repo-2 refer to complex types that don’t exist

By

The rules repo-1 and repo-2 refer to complex types that don’t exist: ” repo-1 (Mandatory) Context: Repo (complex type) [repo/duration = Open] repo/forwardLeg must not exist. ” ” repo-2 (Mandatory) Context: Repo (complex type) [RepoForwardLeg] spotLeg/buyerPartyReference/@href = forwardLeg/sellerPartyReference/@href, and spotLeg/sellerPartyReference/@href = forwardLeg/buyerPartyReference/@href. ” The complex type Repo is not in the schema.