Search results

SGML, or Standard Generalised Markup Language, is an international standard (ISO 8879) allowing the logical structure of electronic documents to be represented rigorously and independent of applications. This article does not discuss the actual standard, but rather proposes a strategy libraries can consider when implementing SGML applications on top of existing products, or when embedding these in innovative end‐user services. Experiences of SGML within the VUBIS‐Antwerpen Library Network (Belgium) are discussed VUBIS‐Antwerpen has adopted SGML as a key standard for the exploitation of its bibliographical data (union catalogues, document ordering online contents, current awareness, publishing on the World Wide Web). With the move towards electronic publication and distribution of documents, SGML tends to become a crucial standard for digital libraries. Projects such as TEI, ELSA, DECOMATE and ELVYN now focus on access to and delivery of full‐text electronic documents, using SGML to manipulate, process and transform the document for the purposes of full‐text searching or hypertext navigation.

The abbreviation SGML stands for Standard Generalized Markup Language. Markup refers to adding style and formatting information to text prior to publication. It is a Standard because SGML has been accepted and published by the ISO, and is not owned by any manufacturer or software vendor. It is Generalized because SGML is powerful and flexible, allowing it to be used in many applications. And it is a Language that embodies a specification for creation of a set of rules to define the structure of a document. SGML has been designed to easily cross incompatible computer platforms, and its “open” nature allows for relatively simple access and manipulation of an SGML conforming document by both people and computers. Above all, SGML proposes a new way of thinking about document creation and presentation, by shifting document style considerations to the publication process rather than the creation process. This is done by dividing the document into named, logical elements, to which any style can be later applied. A by‐product of this approach is the effective creation of a flexible database, providing further access to the data for information retrieval or for re‐publication.

Working with documents in electronic format is inherently different from dealing with materials in print; nor can all electronic formats be considered equivalent. Processing and presenting SGML is not the same as processing and presenting materials in other markup or word processing formats. To maximize flexibility and extensibility, SGML is highly modular, which complicates implementation. Its emphasis on content structure rather than appearance enhances searchability but makes consistent and precise display difficult. Mechanisms used to maximize platform and software independence (e.g., entities, link protocols), though effective, can be used incorrectly or in ways difficult to implement on some systems or using certain software. Difficult questions remain for libraries planning to implement SGML.

Project ELSA is examining the use of documents encoded in SGML (Standard Generalised Markup Language) for the delivery of information to library end users and to librarians acting as information intermediaries. A partnership of industry providers and an end user working together within the Third Framework of the CEC Libraries programme, is constructing a delivery system using SGML encoded journal articles which will be used to investigate technical issues and to examine the potential for offering new and improved services. The development of document delivery is discussed briefly followed by some background on SGML and comment on progress within the ELSA project. Some possible applications of such a system are discussed.

SGML is in its second decade of existence but if it weren't for its most famous application, HTML, then few outside specialist circles would have heard of it. SGML of course has far more applications than HTML on its own: it is a meta‐language for defining, identifying and using the structure and content of documents in general. It has also become far easier to implement in recent years with the latest generation of editors, but still the basic task of setting up Document Type Definitions can require expert help. Meanwhile, for all its limitations, HTML is still what makes text able to be displayed via the World Wide Web, so something many would find ideal is a way of combining the flexibility of one markup language with the Web suitability of the other.

Within the library world, there is a growing interest in the use of XML in journals, not least because of its implications for e‐journal archiving. But what is actually happening in the commercial journals market? How far have XML and its related standards permeated the production of real commercial journals and how do publishers and other providers of journals see this area developing? This paper looks at the activities and future plans of a selection of publishers and aggregators in the STM journals market, although many of the comments relate to the entire journals arena.

This article describes the system used for the introduction of textual data into the CELEX full‐text document databases. The solution implemented is based on the establishment of a text production database for the management and validation of texts before introducing them into the CELEX dissemination databases, and the management of structured documents described with the help of an SGML syntax.

All of us in the library community are familiar with the impact of the MARC (machine‐readable cataloging) record on library operations. Whether we specialize in administrative, systems, public, or technical services, we recognize the MARC record as a standard data storage format that has made it easier to produce, store, and retrieve data. Few disagree that widespread adoption of the MARC record has enabled libraries to realize the full benefits of automation.

Imagine a document you want to read is available on disk. The publisher can readily supply it to you with no concern for computer system compatibility. If the publisher doesn't happen to have your brand of computer, they can send it to you over the phone lines without losing any of its format. Once you get it, the format is immediately obvious. You can identify all the headings, you can instantly find the tables and lists, and you have no doubts about italics or other font changes. If you want a braille edition, you don't have to worry about stripping out control characters or changing some word processor's commands to those appropriate for braille. If you're using a large print display system, you needn't worry about how the text is broken into lines.

The eventual adaptation of archives to new technological possibilities could begin with the creation of digital versions of archival finding aids, which would allow the international diffusion of descriptive information. The Standard Generalized Markup Language (SGML), document type definition (DTD) for archival description known as encoded archival description (EAD) is an appropriate tool for this purpose. Presents a methodological strategy that begins with an analysis of EAD and the informational object to be marked up, allowing the semiautomatic creation of a digital version.