489: pr-2 context should be complexType not an element

pr-2 states: ” Context: PaymentCalculationPeriod pr-2 (Mandatory) If paymentCalculationPeriod/@href attribute is present, it must match the @id attribute of PricingInput type ” It should state: ” Context: PaymentCalculationPeriod (complex type) pr-2 (Mandatory) If paymentCalculationPeriod/@href attribute is present, it must match the @id attribute of PricingInput type ” PaymentCalculationPeriod is a complex type not an element.

488: pr-1 incorrect XPath statement

pr-1 states: ” Context: PricingDataPointCoordinate pr-1 (Mandatory) generic/@href must match the @id attribute of Asset type. ” There is no element(*, Asset) within the context of PricingDataPointCoordinate. It does not event exist within the descendants of PricingDataPointCoordinate. Please correct the XPath statement to identify the field the @id must be in.

487: Add an example for pr-1

Add a valid and invalid example for rule pr-1. Today are there are no examples to test. This compounds and masks the separate issue that the rule refers to an element when it should refer to a type.

486: Rule pr-1 should be on complexType not an element

Rule pr-1 states: ” Context: PricingDataPointCoordinate pr-1 (Mandatory) generic/@href must match the @id attribute of Asset type. ” It should be changed to: ” Context: PricingDataPointCoordinate (complex type) pr-1 (Mandatory) generic/@href must match the @id attribute of Asset type. ” PricingDataPointCoordinate is a complex type not an element. This is always indicated in the rules, … Continued

484: Representation of time in FpML

The coordination committee is currently discussing how the trade execution time should be represented in FpML. This comes from MiFID regulations. Some architectural questions were raised while discussing how we should represent time in FpML: 1. Should Parties have different views of time? 2. Should the clock issuing the time be identified? 3. Can we … Continued

483: valid-cd-1b-01.xml is not a credit index

The example file valid-cd-1b-01.xml does not exercise rule cd-1b because the example is not a credit index and does not meet that precondition. “Precondition: CreditIndex creditDefaultSwap/generalTerms/indexReferenceInformation is present and creditDefaultSwap/generalTerms/indexReferenceInformation/tranche is not present.” There is no indexReferenceInformation on the example, only /FpML/trade/creditDefaultSwap/generalTerms/referenceInformation

481: Example valid-cd-1-02.xml is invalid

Rule cd-1 does not apply to example valid-cd-1-02.xml because it does not meet the Single Name Precondition of “fn:exists(//creditDefaultSwap/generalTerms/referenceInformation)” Instead it is based on an index, not a single name. It has element: /FpML/trade/creditDefaultSwap/generalTerms/indexReferenceInformation

480: Same Currency precondition has incorrectly specified rule

“Precondition: SameCurrency All instances of currency values must be identical.” Instead the rule should be: “count(distinct-values(//element(*, Money)/currency)) le 1” or in plain English “Evey Money element should have the same currency”. At the moment this reads that the amount must be identical i.e. 5USD and 5GBP are valid.