Latest Posts

The FpML annotation namespace is “http://www.fpml.org/declaration”. The problem with this is everything in a schema is declarative, so what does calling it a “declaration” distinguish it from? Why not just call it: “http://www.fpml.org/annotation”, or “http://www.fpml.org/arch/2007”, or “http://www.fpml.org/arch/2007/FpML” By comparison the Ecore namespace is “http://www.eclipse.org/emf/2002/Ecore” xmlns:dec=”http://www.fpml.org/declaration” value=”Forward” dec:deprecated=”true” dec:deprecatedReason=”The optionType is to be used if the … Continued

Add a rule in the architecture specification that bans circular includes of schemas. Certain editors persistently add these back in just before each release!

Please provide a .spp file in the Zip download. This would be identical to the .spp file in the Subversion folder. This allows people to open up a release as an XML Spy project.

The validation rules call the classes “data types”. They are not data types. Either call them “complex types” or “classes”. Currently = Context: EquityAmericanExercise (data type) Future = Context: EquityAmericanExercise (complex type)

All elements should have their context provided, even if it is a any context. Look at this example: Preconditions The following preconditions are always to be executed relative to the root of the FpML document being validated. The context of the rule is NOT carried through to the precondition. Precondition: ISDA1999 The documentation/contractualDefinitions element or … Continued

52 examples files for validation contain examples from the previous, rather than the current version of FpML. Bring the example files up to version 4.3

Define precisely what deprecated means. Deprecated needs defining for: – Business Processes (such as A2A) – Validation Rules (such as the deprecated rule) – Schema constructs

In document fpml-4-3-intro-4.html change the text on line 561: Old == Applications that receive FpML for processing may want to check the validation rules to ensure that the data they are receiving represent a valid FpML trade. Processing applications are not obliged to reject invalid trades. Instead, the implications of rule normativity are that the … Continued

Add a rule that all HTML artefacts should be valid XHTML. This allows more of us to edit the files with more tools.

Convert the html files to xhtml. I am having problems processing many of the FpML HTML files because they are quite ‘loose’ HTML. For example invalid-cd-1-0-1-fragment.html contains an unclosed tag of . In xhtml this would show as invalid. The problem is the html is targeted at the browsers, when it should be valid regardless … Continued