Logo
Unionpedia
Communication
Get it on Google Play
New! Download Unionpedia on your Androidâ„¢ device!
Download
Faster access than browser!
 

Bazley v Curry and Tort

Shortcuts: Differences, Similarities, Jaccard Similarity Coefficient, References.

Difference between Bazley v Curry and Tort

Bazley v Curry vs. Tort

Bazley v Curry, 2 SCR 534 is a Supreme Court of Canada decision on the topic of vicarious liability where the Court held that a non-profit organization may be held vicariously liable in tort law for sexual misconduct by one of its employees. A tort, in common law jurisdictions, is a civil wrong that causes a claimant to suffer loss or harm resulting in legal liability for the person who commits the tortious act.

Similarities between Bazley v Curry and Tort

Bazley v Curry and Tort have 2 things in common (in Unionpedia): Strict liability, Vicarious liability.

Strict liability

In criminal and civil law, strict liability is a standard of liability under which a person is legally responsible for the consequences flowing from an activity even in the absence of fault or criminal intent on the part of the defendant.

Bazley v Curry and Strict liability · Strict liability and Tort · See more »

Vicarious liability

Vicarious liability is a form of a strict, secondary liability that arises under the common law doctrine of agency, respondeat superior, the responsibility of the superior for the acts of their subordinate or, in a broader sense, the responsibility of any third party that had the "right, ability or duty to control" the activities of a violator.

Bazley v Curry and Vicarious liability · Tort and Vicarious liability · See more »

The list above answers the following questions

Bazley v Curry and Tort Comparison

Bazley v Curry has 9 relations, while Tort has 208. As they have in common 2, the Jaccard index is 0.92% = 2 / (9 + 208).

References

This article shows the relationship between Bazley v Curry and Tort. To access each article from which the information was extracted, please visit:

Hey! We are on Facebook now! »