FpML Issues Tracker

Agree there is an issue.

I suggest the solution is to give the explicit namespace of the context (view) for each Validation rule. One of the results of views is that we now have namespaces to refer to them by.

So instead of:
“Context: InterestRateStream (complex type)
ird-1 (Mandatory)
resetDates must be present if and only if a floatingRateCalculation or inflationRateCalculation is present in the calculationPeriodAmount/calculation element.”

This would remain exactly the same except you would get at the top of the document the XQuery syntax:
declare default element namespace “http://www.fpml.org/FpML-5-0/pretrade”;

If you need to refer to the namespaces explicitly you can do that with:
declare namespace pre=”http://www.fpml.org/FpML-5-0/pretrade”;

Agreed at the VWG for Irina to document the progress on adding VWG rules to FpML 5.

The “next couple of weeks” is elapsed. What is the current status?

Discussed at the VWG today. Irina stated she is working on this for the Confirmation ‘view’ and the Reporting ‘view’.

Irina stated the plan is not to have any rules on the Master schema. Instead all rules will apply to a specific View schemas. Each View has a namespace, so does each rule, which allows the rules to be associated to a specific view.

There is no link between the same rule in different contexts.

Views now have different validation rules. Issue no longer needed.