FpML Issues Tracker

488: pr-1 incorrect XPath statement

September 6, 2007

closed

Minor

Always

Validation Rules

Admin

None

Summary

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.

Notes:

  • mgratacos

    09/14/07 8:17 am

    The rule has been deprecated in 4.4 and replaced by a new rule (ref-18)

    Context: GenericDimension (complex type)
    The @href attribute must match the @id attribute of an element of type Asset.

    The rule has been corrected accordingly in version 4.3.

  • matthew

    09/14/07 10:33 am

    The new rule is incorrect. There is no “element of type Asset” within the “Context: GenericDimension (complex type)”.

    You either need to relax the context or explicitly break out of it for the “element of type Asset”.

  • matthew

    09/14/07 10:33 am

    Reopening because the resolution contains an error.

  • mgratacos

    10/23/07 2:20 pm

    VWG 2007-10-23: Agreement to fix it.

  • sheinrich

    11/12/07 10:42 am

    I will write a section for the spec on how validation rules should be expressed.

    We will review this issue once that spec is agreed upon.

  • matthew

    03/10/08 7:18 pm

    This issue is being reopened because it was resolved without a resolution.

    Closing the issue was a breach of FpML practise because:
    1. Issues must be resolved before being marked as resolved.
    2. Resolution must record exactly what the agreed resolution was.
    3. To prevent misunderstanding the raiser of the issue must be consulted for explanations of a potentially misunderstood issue, and should be invited as a guest to the WG meeting to discuss the issue.

    The VWG agreed at its meeting 2007-10-23 to fix the outstanding issue. The outstanding issue has not yet been fixed.

    The VWG agreed at its meeting 2007-11-12 to write a specification of how rules should be expressed. The specification has not yet been written, agreed, or applied.

    The rule remains open until resolved, either by completing the two actions or by resolving using another solution.

  • matthewdr

    04/15/08 1:43 pm

    Agreed at the VWG.

    This needs to be raised up a couple of context levels, so it has visibility of Asset. The issue is assigned to Lyteck.

  • lyteck

    04/16/08 2:16 pm

  • lyteck

    04/21/08 8:47 pm

    fixed as discussed in previous note.

  • matthewdr

    04/29/08 2:32 pm

    Accepting Lyteck’s fix.

  • Leave an update

    You must be logged in to post an update.