The FpML Issues Tracker is designed to facilitate public interaction in the standard.
By registering to the Issue Tracker you will be able to submit corrections and comments, generate reports, and view the complete issues archive for FpML.
| Anonymous | Login | Signup for a new account | 2010-09-09 14:09 UTC |
| Main | My View | View Issues | Change Log | Docs |
| Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
| 0000682 | [FpML] Validation Rules | minor | always | 2008-05-02 16:29 | 2010-08-18 12:06 | ||||
| Reporter | matthewdr | View Status | public | ||||||
| Assigned To | apparry | ||||||||
| Priority | normal | Resolution | fixed | ||||||
| Status | closed | Target Version | 4.8 First Working Draft 2010-04-16 (build 1) | Product Version | 4.4 Recommendation 2008-08-20 | ||||
| Summary | 0000682: eqd-17 fix broke the context | ||||||||
| Description |
The context for eqd-17 doesn't take into account optional fields. The rule today is: " Context: EquityOption, EquityDerivativeShortFormBase (complex type) eqd-17 (Mandatory) equityExercise/equityAmericanExercise/equityMultipleExercise/maximumNumberOfOptions * equityExercise/equityAmericanExercise/equityMultipleExercise/integralMultipleExercise >= numberOfOptions. " This is a change. The rule was changed in issue 0000457. This fixed one problem but removed the handling of optional fields from the context. The correct form of the rule in XQuery is: (for $equityOption in (//element(*, EquityOption)|//element(*, EquityDerivativeShortFormBase))[equityExercise/equityAmericanExercise/equityMultipleExercise][numberOfOptions] return <result constraint="eqd-17" valid="{($equityOption/equityExercise/equityAmericanExercise/equityMultipleExercise/maximumNumberOfOptions * $equityOption/equityExercise/equityAmericanExercise/equityMultipleExercise/integralMultipleExercise) le $equityOption/numberOfOptions}"></result>) The solution is to rewrite the rule as: " Context: (EquityOption (complex type), EquityDerivativeShortFormBase (complex type))[equityExercise/equityAmericanExercise/equityMultipleExercise][numberOfOptions] eqd-17 (Mandatory) equityExercise/equityAmericanExercise/equityMultipleExercise/maximumNumberOfOptions * equityExercise/equityAmericanExercise/equityMultipleExercise/integralMultipleExercise >= numberOfOptions. " NB This uses the FpML way to write out contexts which doesn't use XPath. |
||||||||
| Additional Information | |||||||||
| Tags | No tags attached. | ||||||||
| XML Tool Type | |||||||||
| Attached Files |
|
||||||||
|
|
|||||||||
Relationships |
|||||||||||
|
|||||||||||


