shared-6 is currently:< " shared-6 (Mandatory) Context: AmericanExercise (complex type) earliestExerciseTime/hourMinuteTime < latestExerciseTime/hourMinuteTime, if latestExerciseTime exists. " The existence of latestExercisTime is a condition to firing the rule. Solution: " shared-6 (Mandatory) Context: AmericanExercise (complex type)[exists(latestExerciseTime)] earliestExerciseTime/hourMinuteTime < latestExerciseTime/hourMinuteTime "
shared-7 is currently: ” shared-7 (Mandatory) Context: BermudaExercise (complex type) earliestExerciseTime/hourMinuteTime < latestExerciseTime/hourMinuteTime, if latestExerciseTime exists. " The existence of latestExercise should be a condition on firing the rule. Solution: " Context: BermudaExercise (complex type)[exists(latestExerciseTime)] shared-7 (Mandatory) earliestExerciseTime/hourMinuteTime < latestExerciseTime/hourMinuteTime "
The rule shared-9 is today: ” shared-9 (Mandatory) Context: BusinessDateRange (complex type) businessDayConvention is NONE or NotApplicable if and only if neither businessCentersReference nor businessCenters exists. ” This needs a condition and a more simple expression. ” shared-9 (Mandatory) Context: BusinessDateRange (complex type)[iff(exists(businessCentersReference), exists(businessCenters))] Rule: businessDayConvention = (string “NONE”, string “NotApplicable”) “
Rule shared-11 should use XPath for axis as per the specification for writing rules. Also the rule should have an additional condition. The rule today: ” Context: Trade (complex type) shared-11 (Mandatory) If businessDateRange exists within any descendant element of the trade, then businessCentersReference/@href, if present in any descendant element of the trade, must match … Continued
Rules shared-13 and shared-14 having the following issues related to compliance with the specification on writing rules: 1. They use the phrase “anywhere in the document”. The term “document” needs defining as to whether it is an element, document-node, etc.. Also all of these definitions are outside the current context. The term “anywhere” should be … Continued
shared-15 today is: ” shared-15 (Mandatory) Context: Offset (complex type) dayType must only exist if and only if period is D and periodMultiplier is non-zero. ” To comply with the specification on writing rules this should be changed to: ” shared-15 (Mandatory) Context: Offset (complex type)[exists(dayType)] Rule: iff((period = string ‘D’), (offset/periodMultiplier != 0)) ” … Continued
ln-16 and ln-17 refer to “tradeSide element” which is undefined. The rules today: ” Context: TradeSide (complex type) shared-16 (Mandatory) For party/@href anywhere within the tradeSide element, href shall match the @id attribute of an /FpML/party element. Context: TradeSide (complex type) shared-17 (Mandatory) For account/@href anywhere within the tradeSide element, href shall match the @id … Continued
Rule ln-4 has “mandatoryCostRate” misspelt as “mandatoryCostRatet”. Remove the final “t”.
Rules shared-13 and shared-14 should have a context of “Document(complex type)” just like shared-12. Please see issue #582.
The file invalid-ln-9-01.xml is failing on ln-3 twice. According to the VWG Specification Rules the example should only fail on ln-9. The example needs fixing so this is the case. See issue 0000746.