Jump to ContentJump to Main Navigation
Roman Law, Scots Law and Legal HistorySelected Essays$
Users without a subscription are not able to see the full content.

William Gordon

Print publication date: 2007

Print ISBN-13: 9780748625161

Published to Edinburgh Scholarship Online: September 2012

DOI: 10.3366/edinburgh/9780748625161.001.0001

Show Summary Details
Page of

PRINTED FROM EDINBURGH SCHOLARSHIP ONLINE (www.edinburgh.universitypressscholarship.com). (c) Copyright Edinburgh University Press, 2021. All Rights Reserved. An individual user may print out a PDF of a single chapter of a monograph in ESO for personal use.date: 18 September 2021

The Actio de Posito Reconsidered☼

The Actio de Posito Reconsidered☼

Chapter:
(p.43) 4 The Actio de Posito Reconsidered
Source:
Roman Law, Scots Law and Legal History
Author(s):

William M Gordon

Publisher:
Edinburgh University Press
DOI:10.3366/edinburgh/9780748625161.003.0004

The action de posito (vel suspenso) is found among the Roman quasi-delicts and imposed liability on someone who had something placed on a building in a dangerous position. It appears along with the actio de effusis vel deiectis which imposed liability on the occupier of a building from which something was poured or thrown to the damage of a passer-by but it is not clear whether the actio de posito lay against the occupier also or against the owner and whether liability was strict or depended on knowledge of the placing. That it lay against the owner who knew seems possible but corruption of the texts makes a definite conclusion difficult.

Keywords:   Action de posito, Actio de effusis vel deiectis, Quasi-delict, Strict liability

Edinburgh Scholarship Online requires a subscription or purchase to access the full text of books within the service. Public users can however freely search the site and view the abstracts and keywords for each book and chapter.

Please, subscribe or login to access full text content.

If you think you should have access to this title, please contact your librarian.

To troubleshoot, please check our FAQs, and if you can't find the answer there, please contact us.