Need to review context and text of msg rules. Use the context colleciton() and document() generally means that the description of a rule needs to be updated. colleciton() and document() are Xquery function. They should be documented better.
Abstract global element underlyingAsset (instance of Asset), declared in fpml-asset-5-3.xsd, is documented in the schema annotation as: “Define the underlying asset when it is a listed security.” This is not strictly accurate, as underlyingAsset is substitutable with instruments (bond, cash) which are not necessarily listed securities (definitely not, in the case of cash). Recommend that … Continued
Values of coding scheme asset-class-1-0 (http://www.fpml.org/coding-scheme/asset-class-1-0.xml) mix singular and plural forms inconsistently e.g. Credit, ForeignExchange; but InterestRate*s*, Equit*ies*, Commodit*ies*. The singluar form is preferred and should be used consistently: Credit, InterestRate, ForeignExchange, Equity, Commodity.
Email from Lyteck: Request from the BPWG/RPTWG to develop a new messaging rule to handle the Multiplicity of the onBehalfOf field the BPWG evaluated and approved a request from the RPTWG to allow multiple on-behalf-of elements in a message to an SDR. We wrote down an action to ask the VALWG. – >> We discussed … Continued
ComplexType YieldCurveMethod has a redundant nested sequence at the top level of its content model, which is present at all FpML versions (see text below). This should be resolved to a single xsd:sequence (there is no impact on instance documents).
Reviewing the 5.2 schema I noticed that the abstract Product element has been modified and the documentation associated with the elements has been changed. I don’t believe the changes where necessary to match the requirements of the proposed regulation. 1. It is not necessarly to add an explicit element to contain the asset class it … Continued
Purely by chance I spotted another example of an untyped element – similar to http://www.fpml.org/issues/view.php?id=1065 In this case additionalCommoditySwapLeg should be of type Leg as an abstract base. Although seen in 4-9 – it goes further back to at least 4-8, possibly 4-7 (not present in 4-6)
Scheme http://www.fpml.org/coding-scheme/collateral-response-reason-code has been renamed to: http://www.fpml.org/coding-scheme/collateral-response-reason In doing so the CanonicalVersionUri has not been correctly edited. http://www.fpml.org/coding-scheme/collateral-response-reason-code-1-0 should now be: http://www.fpml.org/coding-scheme/collateral-response-reason-1-0
The current definition of PartyRoleType seems specific to the reporting views but it is available in the Confirmation view too. The current scheme only has two values: AllPositions and SomePositions, which only make sense in position report context. I’d suggest making the type element within RelatedParty available only to the Reporting view.
In confirmation view the Events.model has an additionalEvent element defined as This in turn is defined as: Is this meant to be a sustitution point? None of the other ‘Events’ are built from any sort of abstract event model.