FpML Issues Tracker

895: masterAgreementVersion not permitted in Validation example

December 11, 2008

closed

Crash

Always

Validation Rules

Admin

None

Summary

Many of the Validation Examples are schema invalid. It looks like a problem with masterAgreementVersion under masterAgreement. This is in the validation-rules branch.

The warnings I get from XML Spy are: File C:workingganny-wsvalidation-rulessrcvalidationexamplesvalid-testcasesvalid-cd-1-01.xml is not valid. Element is not allowed under element . Reason: The following elements are expected at this location (see below) Annotations of type 'fpml:MasterAgreement' (see below) An entity for defining the agreement executed between the parties and intended to govern all OTC derivatives transactions between those parties. Error location: FpML / trade / documentation / masterAgreement / masterAgreementVersion Details cvc-model-group: Element unexpected by type 'fpml:MasterAgreement' of element . cvc-elt.5.2.1: The element is not valid with respect to the actual type definition 'fpml:MasterAgreement'.

Notes:

  • matthewdr

    12/16/08 2:17 pm

    Agreed at VWG today that ISDA will fix the examples, so they all validate against the schema.

  • matthewdr

    02/03/09 2:21 pm

    Discussed at the VWG today. Irina offered to check the implementation of this issue.

  • iyermakova

    02/04/09 3:42 pm

    This issue is checked. All examples are correct in 4-6 (trunk) and 4-5 (branches).

  • matthewdr

    02/04/09 8:24 pm

    The issue has not been resolved. I just took a refresh of the validation-rules branch and it is still a problem.

    The issue states the problem is in the validation-rules branch. The comment on closing was that the trunk branch was checked. If the problem is in the validation-rules branch then that is the branch that should be checked.

  • mgratacos

    02/05/09 8:44 am

    This is simply a synchronization problem with the branch. The validation-rules branch didn’t contain the latest version of the 4.5 schemas (contained within the FpML-4-5 branch). I copied the schema files and the example validates fine now.

    From a management perspective, I don’t think we can keep all branches in synch with the appropriate versions. It should be the creators of those branches who should maintain them.

  • Leave an update

    You must be logged in to post an update.