About the edition

STUART LONDON TEAM

General Editor:
Dr Julia Merritt (University of Nottingham)
Technical Implementation:
The following have been responsible for managing XML markup as well as undertaking XML conversion, interface and search engine design.
Michael Pidd
Christiane Meckseper
Jamie McLaughlin
Ed Mackenzie
Katherine Rogers
Transcribers:
Wendy Field
Gwen Smithson
Tom Leng

Return to the topback to top


PUBLICATION DETAILS

This is version 1.0 of the online edition of John Strype's Survey of the Cities of London and Westminster (1720) and it was published in November, 2007 by hriOnline. The ISBN of this edition is 0-9542608-9-9.

Return to the topback to top


HOW TO CITE THIS EDITION

The material published in this edition remains the copyright of the Stuart London Project. It may be used, subject to the law of copyright relating to fair dealing, with citation as follows:

If you wish to cite particular text of Strype's Survey of London (1720), the acknowledgement should read:

e.g.

Strype, Survey of London (1720), [online] (hriOnline, Sheffield). Available from:--- [Accessed 9.9.2005].

If you wish to cite from the prefatory materials within this edition, the acknowledgement should read:

e.g.

J.F. Merritt, ‘The creation of Strype's Survey of London’, in Strype, Survey of London (1720), [online] (hriOnline, Sheffield). Available from: --- [Accessed 9.9.2005].

All images on this website which are marked with a Motco watermark are reproduced under licence from Motco Enterprises Limited. Any use of these images, other than personal use, should be accompanied by a reference to the source (Motco Enterprises Limited, www.motco.com). Fully indexed versions of the maps reproduced on this site are available, with large images, on CD from Motco Enterprises Limited (www.motco.com).

All other images on this site are made available for personal use only, and no other use should be made of these images without prior permission. Enquiries should be directed to hri@sheffield.ac.uk

Return to the topback to top


ACKNOWLEDGEMENTS

The Stuart London Project gratefully acknowledges the financial assistance of the following in the preparation of this edition:

The Project also gratefully acknowledges the assistance of the following in digitising images for this edition.

Professor Caroline Barron (RHUL) receives our special thanks for lending her personal copy of Stype's 1720 edition of the Survey of London for use by the project.

Return to the topback to top


TECHNICAL GLOSSARY

This Edition has developed a vocabulary to refer to various individual components of the editorial framework. These will mostly be self-evident or well-known terms, but it may be helpful to the user to define our terms here in order to avoid ambiguity.

Attribute

Attributes are used to associate name-value pairs with elements. They are most often used to define an element more closely through their attribute value. For example: <note type="gloss">. Here type is the attribute that more closely defines the element note though its attribute value gloss.

Attribute Value

A value given to an attribute that more closely defines an element. See example given under Attribute.

Catchword

The word that is echoed from the beginning of one page back to the end of its predecessor. Catchwords have been transcribed in the online edition.

DTD

The XML document type declaration contains or points to markup declarations that provide a grammar for a class of documents. This grammar is known as a document type definition, or DTD. For this edition we used the DTD of the Text Encoding Initiative (TEI), that was specifically developed to mark-up textual material and manuscripts. The texts were originally created in SGML (see below).

Element

Each XML document contains one or more elements, the boundaries of which are either delimited by start-tags and end-tags, or, for empty elements, by an empty-element tag. Each element has a type, identified by name, sometimes called its "generic identifier" (GI), and may have a set of attribute specifications (http://www.w3.org/TR/REC-xml).

Entity

Within the context of the edition, the term entity is most often used to refer to an entity reference of a literal character. Entity references are used in order to express the various letters used by early editions that cannot be easily typed using the standard western computer keyboard. Those letters have to be expressed in the text by using an entity reference. Entity references are made up of a numerical code preceded by an ampersand and a hash and followed by a semicolon.

Gloss

The marginal glosses, or accompanying marginal commentaries, play a particularly important role in the edition text. They have an important pedagogical function as well as serving as a means of citation. The gloss commentary notes changes to the position and content of each gloss.

Gutter

The gutter is the inner margin of the printed book that runs into the spine.

Page

The fundamental unit of the published text. It has been retained in the organization and display of this Edition. The pagination has been retained, even where it is in error. All citations should be to the page of the edition.

SGML

Structured Generalised Markup Language. The original encoding scheme of the Stuart London edition. SGML was originally devised in the 1960's. XML, a derivative of SGML is considered the current standard for document encoding.

TEI

The Text Encoding Initiative (TEI). "Initially launched in 1987, the TEI is an international and interdisciplinary standard that helps libraries, museums, publishers, and individual scholars represent all kinds of literary and linguistic texts for online research and teaching, using an encoding scheme that is maximally expressive and minimally obsolescent" (http://www.tei-c.org/).

URL

'Unique Resource Locator' : the fundamental address utilised by the world-wide web.

XML

The Extensible Markup Language (XML) is a subset of SGML. Its goal is to enable generic SGML to be served, received, and processed on the Web in the way that is now possible with html. XML has been designed for ease of implementation and for interoperability with both SGML and html (W3C). XML allows the markup of a document's content and structure, rather than the pure layout mark-up utilised by html.

Return to the topback to top