FpML Issues Tracker

Summary

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 the existence of the element: " ref-18 (Mandatory) Context: PricingStructurePoint (complex type) [exists(coordinate)] The coordinate/generic/@href attribute = the underlyingAsset/@id attribute "

The second problem is that coordinate is a repeating element, and so is generic underneath it. This requires the form of the rule to change: " ref-18 (Mandatory) Context: PricingStructurePoint (complex type) every $generic in coordinate/generic satisfies id($generic/@href) is underlyingAsset "

NB I use "is" instead of "=" because I am testing for identity equivalence, not value equivalence. In other words - it needs to be the exact same element, not just contain the same value.

A further complication is that underlyingAsset is optional. This requires a guard on the underlying asset.

" ref-18 (Mandatory) Context: PricingStructurePoint (complex type) [exists(underlyingAsset)] every $generic in coordinate/generic satisfies id($generic/@href) is underlyingAsset "

It is completely unclear how to interpret coordinate/generic/href if underlyingAssetReference is present.