1081: review rule shared-29: need to use also account element

Rule shared-29 (not published yet) compares buyerPartyReference/@href and sellerPartyReference/@href The rule can be seen in the attached image. We need to check if this rule should also compare the account fields and check what context the rule should have.

1074: review Context of msg rules

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.

1071: Multiplicity of onBehalfOf element

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

1017: shared-27 should it be kept? modified?

shared-27 currently reads as follows: Context: Document (complex type) All timezones must be the same. +00:00, -00:00, and Z are considered equivalent. Comment: This rule ensures that date and datetime comparisons behave as expected because they’re expressed in the same timezone. NB That the XSD specification uses the term “timezone”, but that they are not … Continued

984: Unused isFloating and hasInitialStub in IRD rules

The IRD rules define two conditions: isFloating and hasInitialStub, but they are not used in the rules themselves. I am looking at FpML 4.6.4 LCWD-1. For example, I suggest to change rule ird-59 from: XPath Description: Context: InterestRateStream (complex type) [exists(resetDates)] id(resetDates/calculationPeriodDatesReference/@href) is calculationPeriodDates to: XPath Description: Context: InterestRateStream (complex type) [isFloating] id(resetDates/calculationPeriodDatesReference/@href) is calculationPeriodDates … Continued