Imported from previous forum
[ original email was from Jim Northey - jnorthey@jandj.com ]
The current FIXML Schema nor the FIA Extensions schema supports validation of user defined values. Not sure if this was intentional or not. To get around this for the SecurityIDSource field, I used a union of the enumerations with a type that uses a pattern so that both the enumerations and the values 100 and greater could be supported.
Was wondering if anyone had thoughts on us adopting this approach or know of a better approach.
A XML SimpleType definition with modifications for user types can be found at:
The current FIXML Schema nor the FIA Extensions schema supports validation of user defined values. Not sure if this was intentional or not. To get around this for the SecurityIDSource field, I used a union of the enumerations with a type that uses a pattern so that both the enumerations and the values 100 and greater could be supported.
Was wondering if anyone had thoughts on us adopting this approach or know of a better approach.
As this is an XSD snippet - it will not display in a browser - just view the source in your browser or download the XML to view
I think our original thought was to have counterparties actually document their new enumerations in the impl files of the schema - as a way of providing self documenting extensions. However, the limitations imposed by tools, escpecially code generation tools has made this impractical.
Any thoughts?
[ original email was from George Kledaras - george@fixmlflyer.com ]
Looks reasonable to me, as long as we try to keep non-proprietary SecurityIDSources documented and public. This will be a fast compare. Note that your regex gets you from 100 to 999.
The current FIXML Schema nor the FIA Extensions schema supports
validation of user defined values. Not sure if this was intentional or
not. To get around this for the SecurityIDSource field, I used a union
of the enumerations with a type that uses a pattern so that both the
enumerations and the values 100 and greater could be supported.Was wondering if anyone had thoughts on us adopting this approach or
know of a better approach.A XML SimpleType definition with modifications for user types can
be found at:The current FIXML Schema nor the FIA Extensions schema supports
validation of user defined values. Not sure if this was intentional or
not. To get around this for the SecurityIDSource field, I used a union
of the enumerations with a type that uses a pattern so that both the
enumerations and the values 100 and greater could be supported.Was wondering if anyone had thoughts on us adopting this approach or
know of a better approach.http://www.fixprotocol.org/documents/1684/SecurityIDSource_Proposal_For-
_UserDefinedEnumerationSupport.xmlAs this is an XSD snippet - it will not display in a browser - just view
the source in your browser or download the XML to viewI think our original thought was to have counterparties actually
document their new enumerations in the impl files of the schema - as a
way of providing self documenting extensions. However, the limitations
imposed by tools, escpecially code generation tools has made this
impractical.Any thoughts?