Template:M summ EUA Annex Registry Operation: Difference between revisions

From The Jolly Contrarian
Jump to navigation Jump to search
No edit summary
Tags: Mobile edit Mobile web edit
(Replaced content with "{{Emissions Registry Operation summ|euaprov}}")
Tag: Replaced
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
[[Registry Operation - Emissions Annex Provision|If]] ever there were a sign of the half-heartedness of these accursed definitions, this is surely it. The definition of {{euaprov|Registry Operation}}, as a piece of ''syntax'', doesn’t make sense. It is not a complete logical statement.
{{Emissions Registry Operation summ|euaprov}}
 
This is somewhat ameliorated in that the definition only appears once in the document — knee-deep in the clunge of the {{euaprov|Suspension Event}} — in a context that makes it clear what it is meant to say, but still. We think it could be fixed by deleting the words: “{{strike|, other than by reason of the occurrence of an Administrator Event|}}”, and adding that into the already leaden phrasing of the {{euaprov|Suspension Event}} paragraph.
 
This is what our nutshell version does. There: ''better'' than ISDA.

Latest revision as of 11:13, 16 October 2023

One of those definitions that appears to make little sense when viewed in isolation. The unhappy news is it doesn’t make a great deal more sense — at least as a piece of elegant draftspersonship — when you zoom out and view it in context. Parables of farmers and sheep come to mind.

What on earth could “Other than by reason of an Administrator Event” mean? typically, an Administrator Event would lead to a Registry non operation, you would think. As it turns out the definition “Registry Operation” is only used once, as an example of a Suspension Event, where it is used in the negative:

“(i) absence of Registry Operation; or”

Which then makes you think there is a curious, nested double negative: i.e., a Suspension Event is the absence of the Relevant Registry, EUTL or the link between them unless that was caused by an Administrator Event. Why would you exclude those, you wonder? Well, if you follow the rabbithole long enough, you get to a satisfactory answer — you don’t — because any Administrator Event, whether causing an absence of Registry Operation or not, is independently listed as a Suspension Event.

Seeing that “Administrator Event” itself (which is only used in the same context) is concerned with “the suspension of some or all of the processes of a Relevant Registry” you would like to think all of this could have been tidied up quite a bit.

In other words, this epically rubbish drafting from one of the carbon squads, which the other Carbons Squads have blindly adopted wholesale, which makes you glad to be alive.