Be Careful Where You Put Your Commas
May. 11th, 2012 09:02 amIn Osmium Shipping v Cargill the High Court has ruled that the placement of a comma was crucial in deciding whether or not seizure by pirates fell within a crucial clause of the shipping contract*.
The clause provided that if the vessel should “be put back whilst on voyage by reason of any accident or breakdown, … or capture/seizure, or detention or threatened detention by any authority including arrest, the hire shall be suspended”.
The Charterers said that 'capture/seizure' stood alone as one of a number of events that would suspend hire. The Owners said that it was qualified by the 'any authority' wording afterwards, and that as Somalian pirates were not any sort of authority, the clause had not come into effect.
Not surprisingly, when the matter went to arbitration it was held that the Charterers' interpretation was correct, and on appeal to the High Court Mr Justice Cooke agreed. This sort of thing is why I am sympathetic to my friend T's views (based on his experience as a programmer) that laws and legal documents ought to adopt a structured programming approach and clearly indicate by their layout which parts apply to what. I often have to draft Orders of Court recording decisions or agreements regarding matters such as child contact with separated parents, and it can take a lot of care and sub-paragraphs to ensure that what you end up with is clear and unambiguous.
The full judgment is here, with the relevant discussion being at paragraphs 16 onwards. However, I must note the mention at paragraph 6 of Clause 16 of the contract:
"…The act of God, enemies, fire, restraint of Princes, Rulers and People, and all dangers and accidents of the Seas, Rivers, Machinery, Boilers and Steam Navigation, and errors of Navigation throughout this Charter Party, always mutually excepted."
I rather suspect that clause was drafted quite a long time ago and may have been copied as standard wording since the days of, oh, Queen Victoria?
* Yes, I know the correct term is 'charterparty', but I assume that most of my friends haven't done a module in shipping law.
The clause provided that if the vessel should “be put back whilst on voyage by reason of any accident or breakdown, … or capture/seizure, or detention or threatened detention by any authority including arrest, the hire shall be suspended”.
The Charterers said that 'capture/seizure' stood alone as one of a number of events that would suspend hire. The Owners said that it was qualified by the 'any authority' wording afterwards, and that as Somalian pirates were not any sort of authority, the clause had not come into effect.
Not surprisingly, when the matter went to arbitration it was held that the Charterers' interpretation was correct, and on appeal to the High Court Mr Justice Cooke agreed. This sort of thing is why I am sympathetic to my friend T's views (based on his experience as a programmer) that laws and legal documents ought to adopt a structured programming approach and clearly indicate by their layout which parts apply to what. I often have to draft Orders of Court recording decisions or agreements regarding matters such as child contact with separated parents, and it can take a lot of care and sub-paragraphs to ensure that what you end up with is clear and unambiguous.
The full judgment is here, with the relevant discussion being at paragraphs 16 onwards. However, I must note the mention at paragraph 6 of Clause 16 of the contract:
"…The act of God, enemies, fire, restraint of Princes, Rulers and People, and all dangers and accidents of the Seas, Rivers, Machinery, Boilers and Steam Navigation, and errors of Navigation throughout this Charter Party, always mutually excepted."
I rather suspect that clause was drafted quite a long time ago and may have been copied as standard wording since the days of, oh, Queen Victoria?
* Yes, I know the correct term is 'charterparty', but I assume that most of my friends haven't done a module in shipping law.
no subject
Date: 2012-05-11 09:31 am (UTC)A-hem. "International Trade" at Oxford - taught by pretty much the entire editorial board of Chitty of Contracts, from what I could tell - was pretty much a module in advanced shipping.
And, incidentally, I think a lot too much fuss is made about commas. Even without the comma, it seems clear to me that "capture/seizure" has to be construed against redundancy, and that the only reasonable meaning to give it which adds to "detention/arrest" is that one is a lawful detention and the other is not.
no subject
Date: 2012-05-11 09:44 am (UTC)I took the shipping law module on the BVC in part because it was relevant to many other areas of international trade, but also because it was not an area of law I was likely to pick up in the normal course of pupillage or early practice. It was quite fun, and I'm glad I did it, although I have yet to see anything resembling a CIF contract or Bill or Lading, or apply the Carriage of Goods by Sea Act 1971. Which is a pity, as a canal runs right underneath my flat...
no subject
Date: 2012-05-11 09:47 am (UTC)no subject
Date: 2012-05-11 09:45 am (UTC)no subject
Date: 2012-05-11 09:51 am (UTC)When programmers realise what it would take to have each software drop go through two houses of Parliament and committee on each iteration of bug-testing, it might be a feasible proposition.
no subject
Date: 2012-05-11 10:08 am (UTC)no subject
Date: 2012-05-11 10:13 am (UTC)a) Tunnel vision; that is, identifying a problem, deciding that the law must catch every single instance of this problem which appears in future, not working out what else you'll catch if you apply that approach to drafting.
b) Not respecting the professionals on the team; ie ditching things parliamentary draughters have put in for good technical reasons in pursuit of some chimaera of "plain English".
c) The need for MPs to be seen to have made a mark; interference from committee members just, apparently, for the sake of it.
no subject
Date: 2012-05-11 08:36 am (UTC)no subject
Date: 2012-05-11 08:55 am (UTC)On a related point, I once showed by CV to a non-technical person, who handed it back with the comment that she did not understand any of the (industry- and role- specific) jargon and I should rewrite it without. Which if I had done would of course guaranteed I would not get interviews for any of the jobs it was written to get.
no subject
Date: 2012-05-11 08:56 am (UTC)no subject
Date: 2012-05-11 10:18 am (UTC)no subject
Date: 2012-05-11 10:28 am (UTC)Didn't it use to be the case that some legal documents had to be drafted without commas, because they were printed/typed on low quality paper, and you didn't want a blemish being mistaken for a comma.
no subject
Date: 2012-05-11 12:42 pm (UTC)no subject
Date: 2012-05-11 10:34 am (UTC)no subject
Date: 2012-05-11 10:37 am (UTC)Apparently it was made into a TV series, which I never knew. Very pleased to see I remembered the McGuffin correctly.
no subject
Date: 2012-05-12 10:41 am (UTC)no subject
Date: 2012-05-22 09:52 am (UTC)no subject
Date: 2012-05-11 01:31 pm (UTC)if (some_comparison)
perform(step);
perform_another(step);
Instead of:
if (some_comparison) {
perform(step);
perform_another(step);
}
The eye is so easily fooled by so many things.
no subject
Date: 2012-05-11 06:51 pm (UTC)no subject
Date: 2012-05-22 09:51 am (UTC)