[ 1 ] International Organization for Standardization, ISO 8879: Information processing --Text and office systems -- Standard Generalized Markup Language (SGML), ([Geneva]: ISO, 1986)
[ 2 ] Examples include Bryan (1988), van Herwijnen (1990) and Goldfarb (1991).
[ 3 ] Originally published as part of Greenstein, D.I. (ed) Modelling Historical Data(Göttingen, Max-Planck-Inst. für Geschichte, 1991)
[ 4 ] De Rose (1990)
[ 5 ] I do not discuss here the possibility of using variant character sets within an SGML document; though possible this does not of course solve the general case
[ 6 ] The use of the ampersand and semicolon to delimit the acronym is an example of the SGML reference concrete syntax, discussed briefly below. It is not a necessary part of the SGML solution; merely a conventional one.
[ 7 ] The semicolon is not in fact strictly necessary in all situations: the end of an entity reference is signalled by the first character encountered which cannot form part of a name. A space is therefore sufficient; since however entity references are often found within words, rather than between them, the semicolon is often necessary to indicate where the entity name ends and the word within which it is embedded resumes.
[ 8 ] Categorization of this kind could equally well be achieved by using a different tag -- say biblicalName. The decision as to whether to use an attribute or a distinct element type is often a difficult one, involving more detailed technical and design skill than it is appropriate to consider here.
[ 9 ] For clarity of discussion, more specific element names have been used here than are proposed in the basic TiEI scheme.
[ 10 ] More exactly, a name token, that is a sequence of alphanumeric characters of which the first is a letter
[ 11 ] It must also be enclosed in quotation marks if it is not a name token