83,229
edits
Template:M comp disc IETA Force Majeure: Difference between revisions
Template:M comp disc IETA Force Majeure (view source)
Revision as of 15:55, 11 July 2023
, 11 July 2023no edit summary
Amwelladmin (talk | contribs) No edit summary |
Amwelladmin (talk | contribs) No edit summary |
||
| Line 3: | Line 3: | ||
Let us speculate: the IETA was written first, is independent of the {{isda}} universe, and for reasons best known to IETA’s {{Cds}}, they decided to call this a Force Majeure. Being beyond the reasonable control of the affected party this is not entirely unreasonable. | Let us speculate: the IETA was written first, is independent of the {{isda}} universe, and for reasons best known to IETA’s {{Cds}}, they decided to call this a Force Majeure. Being beyond the reasonable control of the affected party this is not entirely unreasonable. | ||
{{icds}} was, as usual, late to the “novel asset class” party and, as it couldn’t find a spot, decided to park its tanks on IETA’s lawn, borrowing much of the | {{icds}} was, as usual, late to the “novel asset class” party and, as it couldn’t find a spot, decided to park its tanks on IETA’s lawn, borrowing much of the technology wholesale but unable to call this event a {{ietaprov|Force Majeure}} because the {{isdama}} ''already has a {{isdaprov|Force Majeure Event}}'', this is quite different, and that would confuse people even beyond ISDA’s tolerance for confusing people.<ref>Seeing as the {{ietama}} borrows a bit of technology from the {{1992ma}} is is conceivable that IETA’s {{cds}} didn’t realise there was a {{isdaprov|Force Majeure Event}} in the {{2002ma}}, as there was not one in the {{1992ma}}. I am guessing. </ref> | ||
So {{icds}} went with its product specific “stuff happens” label, {{euaprov|Settlement Disruption Event}}. | So {{icds}} went with its product specific “stuff happens” label, {{euaprov|Settlement Disruption Event}}. | ||