FpML Issues Tracker

1101: invalid-shared-19-1 does not exercise the rule

April 1, 2012

closed

Minor

Always

Examples/Test Cases

Admin

mgratacos

Summary

shared-19 detects cases where two account structures exist for the same logical instance. In the test case the two accounts have unique Ids (differing in thier scheme URI) so can not trigger the rule.

12345PartyA 12345PartyAB

Change the scheme URI for the second account to match the first.

Attachments

  • invalid-shared-19-01.xml

    • Notes:

  • andrew

    11/02/12 4:24 pm

    The attached file does generate the error when tested with the HandCoded toolkit.

  • mgratacos

    04/30/19 10:56 am

    Assigned to me.

  • rabad

    05/03/19 5:49 am

    Attached invalid-shared-19-01.xml which solves the issue.

    Changes:

    /dataDocument/account[2]/accountId[1] from ‘12345PartyAB’ to ‘12345PartyA’ to equal /dataDocument/account[1]/accountId[1]

    /dataDocument/account[2]/accountId[1]/@accountIdScheme from “http://partyB/accountId” to”http://www.partyA/accountId” to equal /dataDocument/account[1]/accountId[1]/@accountIdScheme

    /dataDocument/trade[1]/documentation[1]/contractualTermsSupplement[1]/type[1]/@contractualSupplementScheme from “http://www.fpml.org/coding-scheme/contractual-supplement-8-0” to “http://www.fpml.org/coding-scheme/contractual-supplement”. To use a CanonicalUri instead of a previous CanonicalVersionUri.

    The first 2 changes makes the two accountIds the same so it triggers the rule.

    The third change uses canonical URI instead of outdated version for an scheme.

  • mgratacos

    05/15/19 5:30 am

    This will be available in the next release of 5.11.

    • Leave an update

    You must be logged in to post an update.

    Report an Issue

    The FpML Issues Tracker is designed to facilitate public interaction in the standard.

    By registering you will be able to submit corrections and comments, generate reports, and view the complete issues archive for FpML.

    Report Issue