Latest Posts

– Fails to validate empty elements while debugging (only for debugging, workaround is to include whitespace in instance docs).

– The presence of two or more elements with the same name within a xsd:choice or xsd:group structures is not supported. The issue doesn’t allow to fix non-deterministic content models within a xsd:choice. – anyAttribute is not supported in AttributeGroup. – Type restriction does not properly generate diagrams or validate. – Optional occurrences of xsd:group … Continued

– Restriction of complex Types is not supported

– complex Content restriction is not supported – Substitution groups are unsupported – Elements and attributes with the same names are not supported – xsd:any is not supported

– Doesn’t support type substitution (xsi:type) – Does not properly recognize namespace-based wildcards (xsd:any Math type in equity)

Multiple xyzReference data types are synonyms for Reference Examples include PartyReference, SensitivitySetDefinitionReference, … xzyReference data types should be removed All element of type xyzReference should be changed to type Reference

IdentifiedDate and TradeDate are data type synonyms ( as below ) TradeDate should be removed All elements currently of type TradeDate should be changed to type IdentifiedDate ++++++++++++++++++++++++ File locations +++++++++++++++++++++++++++++++++++++ C:cvsrootfpml41srcschema>grep -n ‘name=”IdentifiedDate”‘ *.xsd fpml-shared-4-1.xsd:1015: C:cvsrootfpml41srcschema>grep -n ‘name=”TradeDate”‘ *.xsd fpml-doc-4-1.xsd:418: ++++++++++++++++++++++++ Data type synonyms ++++++++++++++++++++++++++++++ A date which can be referenced elsewhere. The type … Continued

I’ve been looking through the FX portion of the DTD (3.0) and schema (4.0 + 4.1) and there seems to be a problem with the definition of the routingId element. In the examples the routingId elements is used to hold a BIC code for a bank. As such you would expect the qualifying scheme to … Continued

SwapsWire would like to propose the addition of a value to the TimeTypeEnum enumeration in the FpML 4.1 Trial Recommendation for use in equity derivatives. This need has been identified as a result of using FpML to model trades documented under the European interdealer equity option master confirmation. This enumeration is used in the equityOptionTransactionSupplementequityExercise\equityExpirationTimeType … Continued

The fpml-enum-4-1.xsd had no declaration of elementFormDefault, attributeFormDefault. I couldn’t think of a reason for not defining that explicitly. So I added elementFormDefault=”qualified” attributeFormDefault=”unqualified” to the schema root element in the enum file. In pr-shared-4-1.xsd the xsd:group QuoteLocation didn’t have the “.model” suffix at the end. I have added it. quotableProduct global element should be … Continued