811: fx-2 change to use exists() as a function.

fx-2 requires changing to follow the specification guidelines to use exists() as a function. The rule today is: ” fx-2 (Mandatory) Context: ExchangeRate (complex type) [exists(forwardPoints)] spotRate must exist. ” The rule should be: ” fx-2 (Mandatory) Context: ExchangeRate (complex type) [exists(forwardPoints)] exists(spotRate) “

810: ref-6 is incorrect

The rule says: ref-6 (Mandatory) Context: InterestCalculationReference (complex type) The @href attribute = the @id attribute of an element of type InterestCalculation. But The InterestCalculation type does not have any attributes so it can’t be referenced. From examining the examples the correct referenced type is Rate which has an associates RateReference type an is validated … Continued

809: SensitivitySet/definitionReference has the wrong type (SensitivitySetReference)

The valuation schema defines a two referencable data containing types ‘SensitivitySetDefinition’ and ‘SensitivitySet’ but one only reference type ‘SensitivitySetReference’ which is defined as a ‘Reference to a sensitivity set’ but used by the SensitivitySet/definitionReference as ‘A reference to a sensitivity set definition’. The use of the same type to reference elements of two different types … Continued

808: pr-ex06-option-sens-on-scenario-request

The data content of this file fails validation rule ref-1 (an AssetReference’s @href must refer to an Asset’s @id). Within the block there is an href to a defintion but YieldCurve type is not derived from Asset so this is an invalid target for the link. USD Swaption Vol Matrix USD 3M-LIBOR USD The example … Continued

807: ref-26 & ref-39 are the same

These two rules have the same definition. Remove ref-39. ref-26 (Mandatory) The @href attribute must match the @id attribute of an element of type BusinessCenters. ref-39 (Mandatory) The @href attribute must match the @id attribute of an element of type BusinessCenters.

806: use of Xpath vs English [exists() vs “exists” / not(exists()) vs “does not exist”]

The valwg agreed (8/26/2008) to implement exists (and others) tests as Xpath expressions within Conditions (see issue 613, closed) e.g., [exists(xyz)] vs “xyz exists” [not(exists(xyz))] vs “xyz does not exist” [count(xzy)>1] vs “at least 2 xzy elements exist” There are a number of new issues raised to expand the implementation throughout rule definitions. If we … Continued