|
http://www.fpml.org/issues/view.php?id=560 two
steps… 1. I had an action item
to identify messages in which FirstPeriodStartDate can exist: NotificationMessage\novation
(of type ContractNovation which uses ContractNovationDetails.model) 1. ContractNovated 2. ContractNovatedCancelled NovationResponseMessage\NovationMessage.model 3. NovationConsentGranted 4. NovationConsentRefused NovationRequestMessage\NovationMessage.model 5. NovationConsentRequest 6. RequestNovationConfirmation 7. NovateTrade NovationNotificationMessage\NovationMessage.model 8. NovationAlleged 9. NovationConfirmed 10. NovationMatched 11. TradeNovated These
11 messages use FirstPeriodStartDate indirectly through: ·
NovationMessage.model\novation\firstPeriodStartDate
(of type FirstPeriodStartDate) ·
NovationDetails.model\firstPeriodStartDate
(of type FirstPeriodStartDate) ·
ContractNovationDetails.model\firstPeriodStartDate
(of type FirstPeriodStartDate) (see
attached message object model PDF for an overview of the messages) ·
Other unrelated local elements FYI o PeriodicPayment\firstPeriodStartDate
(of type xsd:date) (fpml-cd-4-4.xsd) o CalculationPeriodDates\firstPeriodStartDate
(of type AdjustableDate) (fpml-ird-4-4.xsd) 2. As discussed in today’s
call, The plan is to deprecate ref-5 and create bp-2 with 11 contexts
(is that actually possible to create 1 validation rule with multiple contexts?)
which states: bp-2 Context: ContractNovated, ContractNovatedCancelled, NovationConsentGranted,
NovationConsentRefused, NovationConsentRequest, RequestNovationConfirmation, NovateTrade,
NovationAlleged, NovationConfirmed, NovationMatched, TradeNovated Rule: The novation/firstPeriodStartDate/@href attribute must match the party/@id attribute. Please
review/confirm. If there are no objections by the end of the week, I will execute. Lyteck
|
Attachment:
FpML_ObjectModel_Messaging_v4.4WD.100a_2007-10-19_8.5x14.pdf
Description: FpML_ObjectModel_Messaging_v4.4WD.100a_2007-10-19_8.5x14.pdf