FpML Issues Tracker

1284: All elements MUST be associated with a globally defined type

February 6, 2023

closed

Tweak

Have not tried

Schema

5.13 Second Working Draft (Build 2)

AWG

JasonPolis

mgratacos

Summary

FpML Architecture Specification 3.1#s2.3.5

  • All elements MUST be associated with a globally defined type

5-12 and 5-13-WD-1 have 5 elements which define local anonymous types They should reuse or convert to global named types.

//xsd:simpleType[exists(parent::xsd:element)]

  • RegulatoryWithdrawal/ withdrawalReason

//xsd:complexType[exists(parent::xsd:element)]

  • DayCount/ currencySpecificDayCount
  • Rollover/ currentContracts,
  • Rollover/ newContracts
  • AdditionalData/ originalMessage

Notes:

  • JasonPolis

    02/06/23 3:43 pm

    change category to schema

  • mgratacos

    03/23/23 11:24 am

    AWG Meeting 2023-03-23 Agreed by the group. Type should be named as the element where possible. Contact Bhavik for loan changes.

  • mgratacos

    05/04/23 8:29 am

    Regarding withdrawalReason, the proposal is to create a new simple type Max255NormalizedString.

  • mgratacos

    05/04/23 8:53 am

    All issues have been solved and committed to SVN for release in the upcoming release of FpML 5.13. We still need to notify Bhavik for the loan changes.

  • jbaserba

    03/18/24 11:29 am

    Change published as part of FpML 5.13 Working Draft 2 on July 31st 2023:

    https://www.fpml.org/spec/fpml-5-13-2-wd-2/html/recordkeeping/index.html

    Marked as closed.

    • 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