26.03.2013 Views

Appendix CASE ONE - Collection Point® | The Total Digital Asset ...

Appendix CASE ONE - Collection Point® | The Total Digital Asset ...

Appendix CASE ONE - Collection Point® | The Total Digital Asset ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

20 Legal History in the Making<br />

case. Initial failure was clearly the result of inaccuracy in presentation, and the<br />

degree of error was too significant for the court to either overlook, or modify<br />

during process - that is, the case could not go forward on the original bill.<br />

<strong>The</strong> necessity of presenting an accurate case to the court of chancery is<br />

confirmed by eight other bill-pairs in which a failed bill is altered and resubmitted.<br />

<strong>The</strong> nature of the errors they contain of course varies with their<br />

substance. While it is not possible to ascertain precisely what degree of error<br />

would lead the court of chancery to dismiss a bill - for there was certainly no set<br />

rule to guide such a determination - these cases do give us some understanding<br />

of the type of inaccuracy that was required before this would happen.<br />

Inaccuracy concerning a will governing the devolution of certain goods and<br />

chattels caused failure in the first of these eight examples. <strong>The</strong> petitioner initially<br />

described the central document as a last will sealed with the seal of the testator,<br />

and complained of the subsequent forgery of a new will, the removal of the seal<br />

and its affixation to the forgery. Unfortunately for him, although the specific<br />

document in question was indeed a last will, it was in fact sewn to the testator's<br />

testament and the two were sealed not with the testator's seal, but with that of<br />

the archdeacon of Norwich. It is this seal that the respondents had removed and<br />

placed on the forgery. Thus while the petitioner may have been correct about a<br />

forgery having been made and a seal having been misused, his errors with regard<br />

to the details of the matter caused his case to fail. 16<br />

Several bills concerning enfeoffments to use failed on substantive grounds<br />

for a number of reasons. In one example the cause was a mistake as to whether<br />

the feoff or had been seised alone, or with another person, for this significantly<br />

affected the subsequent claim of failure to re-enfeoff. 17 Another bill concerning<br />

a use failed not only because of a number of simple errors, such as describing<br />

feoffees as feoffors, but also because of outright contradiction with respect to<br />

the petitioner's role in selling the property in question. 18 A third case involving<br />

a use also failed upon error in the description of a sale. This time, the petitioner<br />

presented himself initially as the preferred buyer, whereas the correct provisions<br />

governing the use allowed him the property as of right and for a sum such as<br />

might be accorded with the executors. So again, we see here a petitioner who<br />

was apparently well and truly in the right in terms of the crucial issue at stake,<br />

but who mis-stated the facts of his position. 19<br />

In a category of its own, outright error in the identification of the respondent<br />

was in one case clearly sufficient for dismissal. 20 More complex reasons may,<br />

however, be discerned for cases concerning copyhold and coparcenery. In the<br />

copyhold case, the error lay in presenting the lord as having seized the holding<br />

permanently, and in asking for his summons as respondent. This was rectified<br />

16 Fraunceys v. Gayrstang (C1/9 nos.285,286).<br />

17 Dawe v. Tanner, Monke, Balhorn, Ede (C 1/9 nos.270, 269).<br />

18 Godfray v. Middelton, Shippe, London (C 1/9 nos.103,102).<br />

19 Besyles v. Somerton (C 1/9 nos.128,127).<br />

20 Abraham v. Abraham (C 1/9 nos.193,192).

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

Saved successfully!

Ooh no, something went wrong!