591: Definition of the semantics of optionality

I was exchanging messages with a counterparty and we couldn’t agree on the meaning of an optional element. The element is //element(*, Trade)/documentation. It is an optional element. What does it mean when the field is present or not present? Is it: – Whether it is known or not by the sender? – Whether it … Continued

590: example-extension.xsd is invalid

https://dedicated.fpml.org/svn/fpml/branches/FpML-5-0/src/schema/example-extension.xsd The example extension is invalid XSD. It contradicts: http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/#src-import. The imported schema has no namespace.

587: Validation Rule documentation lists a Namespace – what is its purpose?

In 4.4 documentation (e.g. http://www.fpml.org/spec/fpml-4-4-4-wd-3/html/validation-rules/rules-english-shared.html#namespace) a namespace section has been added for the 1st time and has a value of: ‘http://www.fpml.org/spec/fpml-4-4-4-wd-3’. What is the purpose of this? It does not correspond to the namespace of the 4.4 release.

586: add maximumClockVariation

Add maximumClockVariation to the MessageTransportMode. FpML adopted the Message Transport Mode settings from ISO 20022, and is having them registered at ISO 20022, such as the “Bulk Mode” proposed by Marc Gratacos. ISO 20022 now includes maximumClockVariation in the Message Transport Mode. This is defined as: “Clocks must maintain a maximum (inclusive) variance from UTC … Continued

585: Disambiguate the term “precondition”

There is a divergence between logic and computer programming on the definition of the term “precondition”. Please read the Wikipedia entry on a precondition: http://en.wikipedia.org/wiki/Precondition We use the term “precondition” widely in the FpML Validation Rules and it is causing confusion. The programmers interpret the term in its computer programming sense, whereas FpML uses the … Continued

584: FpML-5-0 at rev: 3238 does not build

Marc Gratacos confirms that the FpML-5-0 trunk source code is being kept in the branch “FpML-5-0” within Subversion Source Control. This code does not build C:svnfpmlbranchesFpML-5-0>do-all confirmation > do-all-confirmation.log a copy of the build log is attached to this issue

582: FpML context is not a type

Section 4.6.1 states: “For the purposes of precision, extensibility, and robustness to change the structure of the Validation Rules is profiled. The rules of the profile are: * The context for a validation rule must always be a type. …” This contradicts this context because the context is not a type: Context: FpML shared-12 (Mandatory) … Continued