FpML Issues Tracker

1230: Incorrect documentation on Simple Types

February 19, 2016

closed

Tweak

Always

Schema

andrew

lyteck

Summary

In confirmation view fpml-5-9-shared.xsd the documentation on the simple types 'String', 'NormalizedString' and 'Token' says 'A xxx that may not be empty' but none of these types has a minLength 1 constraint so they will accept an empty string.

Either the generation is incorrect or the documentation needs to be changed.

Notes:

  • lyteck

    05/16/18 4:32 pm

    assigned.

  • lyteck

    05/16/18 4:34 pm

    assigned /

  • lyteck

    10/03/18 10:23 am

    Andrew,

    First, apologies for the delay. We are catching up with the issues and will make sure we respond/or at the very minimum acknowledge in a timely fashion (<1 week) going forward.

    Looking at the schema:

    1. String – “A string. FpML may define lenght restrictions in some views.” (a restriction of xsd:string with maxLength=255. We need to correct typo “lenght”.)
    2. NormalizedString – “A normalized string” (a restriction of xsd:normalizedString with minLength=0)
    3. Token – “A token. FpML redefines this type so that in some views it can enforce that it may not be empty” (minLength=0 but overriden to 1 in Transparency, Recordkeeping)

    It seems all these definitions are correct in the latest 5.10/5.11 schema. (They may have been wrong earlier, not sure.) If no objections, I will close the issue but feel free to reopen if not satisfactory.

    Thanks and again sorry for the delay, Lyteck

    • 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