12.07.2015 Views

the travaux préparatoires hague rules hague-visby rules - Comite ...

the travaux préparatoires hague rules hague-visby rules - Comite ...

the travaux préparatoires hague rules hague-visby rules - Comite ...

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

PART II - HAGUE RULES 431Article 4 (3) - Responsibility of <strong>the</strong> shippercauses. In <strong>the</strong> case of <strong>the</strong> receiver of cargo you strike it out and you give him a generalcause. I think that is not <strong>the</strong> way [480] to treat it. I think <strong>the</strong> fair and proper way isto give equal treatment to both sides on this matter. If you are going to give <strong>the</strong>shipowner <strong>the</strong> particular exceptions, I think you ought to give exceptions to <strong>the</strong> shipper.I understand - Sir Stephen will correct me - that this matter was discussed and <strong>the</strong>clause was inserted at <strong>the</strong> direct request of <strong>the</strong> shippers involved, because <strong>the</strong>y thoughtit was very important that <strong>the</strong>y should have equal protection with <strong>the</strong> shipowner if <strong>the</strong>shipowner claims exemptions. One of <strong>the</strong> greatest objections that <strong>the</strong> traders of <strong>the</strong>country have made, is to <strong>the</strong> very wide range of exemptions and we thought it was onlyfair that <strong>the</strong> traders should have equal exemptions, and in my opinion, I may bewrong, of course, <strong>the</strong> clause as worded will not protect <strong>the</strong> receiver to <strong>the</strong> same extentas <strong>the</strong> shipowner is protected.The Chairman: My own impression about it is that <strong>the</strong> words framed here havebeen designed to give <strong>the</strong> shipper <strong>the</strong> largest protection that could be devised for him.I may be wrong about it, but I must take <strong>the</strong> judgment of <strong>the</strong> Conference upon <strong>the</strong> subject.Is it <strong>the</strong> sense of <strong>the</strong> Conference that <strong>the</strong> words which have been read be insertedin <strong>the</strong> clause? (Agreed).Text adopted by <strong>the</strong> Conference(CMI Bulletin No. 65 - Go<strong>the</strong>nborg Conference)[381]3. THE SHIPPER SHALL NOT BE RESPONSIBLE FOR LOSS OR DAMAGE SUSTAINED BYTHE CARRIER OR THE SHIP ARISING OR RESULTING FROM ANY CAUSES WITHOUT THE ACT,FAULT OR NEGLECT OF THE SHIPPER, HIS AGENTS OR HIS SERVANTS.Conférence Diplomatique -Octobre 1923Séances de la Sous-CommissionTroisième Séance Plénière -7 Octobre 1923[63]M. Bagge propose la suppression duparagraphe 3 à l’article 4 qui lui paraîtpeu clair; il semble n’être que la reproductiond’une règle générale suivant laquellele chargeur n’est pas responsabledes pertes ou dommages causés par samarchandise s’il n’y a pas faute de sa partou de ses agents.Sir Leslie Scott croit, en effet, quecette clause n’est qu’une simple constatationd’une règle générale insérée à la demandedes chargeurs.M. Bagge conclut que, dans la loi nationale,cette stipulation pourra être omise.Diplomatic Conference -October 1923Meetings of <strong>the</strong> Sous-CommissionThird Plenary Session -7 October 1923[63]Mr. Bagge proposed <strong>the</strong> deletion ofarticle 4(3), which seemed to him to bera<strong>the</strong>r unclear. It appeared to be only areproduction of a general rule underwhich <strong>the</strong> shipper was not liable for lossor damage caused by his goods if <strong>the</strong>rewas no fault on his part or that of hisagents.Sir Leslie Scott believed, in effect,that this clause was only a simple statementof a general rule inserted at <strong>the</strong> requestof <strong>the</strong> shippers.Mr. Bagge concluded that in nationallaw this stipulation could be omitted.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!