Abstract: "Document retrieval based on string searches typically returns either the whole document or just the occurrences of the searched words. What the user often is after, however, is microdocument: a part of the document that contains the occurrences and is reasonably self-contained."

"These microdocuments might, for instance, consist of several successive text paragraphs sharing a mutual subject. Single paragraphs, or corresponding close-to-leaf SGML elements, do not convey enough of the contextual information. On the other hand, sections or subsections of a text document, such as a book or an article, can discuss many heterogeneous topics, and thus be too large a unit for retrieval or assembly.

"We claim that such microdocuments are both suitable retrievable units and appropriate units for document assembly, and that they can be reasonably well located using automatic techniques.

"Optimal creation of microdocuments would require thorough semantic analysis of the text. However, it is possible to catch parts of the elementary semantic content by statistical term-frequency analysis.

"Term-frequency distributions enable us to determine the locations of possible topic changes in the text. Based on this information, we can measure the similarity of two successive elements, and decide whether we wish to have them in the same microdocument. On the other hand, existing markup, for example classifying attributes, can be used in boundary detection. The microdocument, again, can be attributed with content information.

"The results of our preliminary experiments show that the presented approach works well in user-assisted topic-oriented microdocument detection. We currently study the usefulness of this technique in document assembly, i.e., in generating new documents from a collection of existing text documents."

[...] "We consider a topical microdocument to be semantically motivated by the topic the microdocument discusses. Topical microdocuments might, for instance, consist of several successive text paragraphs. Single paragraphs, or corresponding close-to-leaf SGML elements, do not convey enough of the contextual information. On the other hand, sections or subsections of a text document, such as a book or an article, can discuss many heterogeneous topics. Furthermore, sections are often longer than desired with respect to the intended purpose, such as document retrieval or assembly.

In this article, we presented a method for detecting microdocuments based on term-frequency distributions. The detection process has two phases: similarity calculation and fragmentation. In general, the results of our preliminary experiments show that the presented approach works well in user-assisted topic-oriented microdocument detection. We currently study the usefulness of this technique in document assembly, i.e., in generating new documents from a collection of existing text documents.

Summary: "There is a growing consensus that healthcare records, including the individual patient record, will be gathered, managed, and distributed electronically, but there is little consensus on how this will be done. One study estimates that fewer than five percent of providers have determined how they will computerize patient records. In this climate, where our second largest industry has yet to establish an informational infrastructure, what does SGML (Standard Generalized Markup Language) have to offer? What are the prospects of large-scale use of SGML-based technology? How does use of SGML relate to other standards efforts?

"This paper examines the place of SGML within healthcare informatics, reports on some recent work demonstrating the application of SGML to healthcare records, and discusses the relationship between SGML-based standards for healthcare and other standards initiatives. It concludes with a brief discussion of one type of SGML architecture and applications envisioned for healthcare."

Abstract: "This paper examines whether (or not) HyTime is an essential feature of a document management system. Scenarios for the appropriateness (or inappropriateness) of indirect linking are reviewed. Ways in which a document management system can help (or hinder) management of links are examined. Should (or shouldn't) a document management system treat HyTime markup as more than ordinary SGML?

"With the addition to HyTime of several annexes in the Technical Corrigendum (TC), HyTime becomes a broader framework for describing generalized SGML-based architectures. The potential impact of these far-reaching topics on document management systems is discussed."

Abstract: "Caterpillar, Inc. has developed a new document information system that emphasizes the reusability of Information Elements (shared objects) in multiple documents, the automatic compilation of objects into a document, and the reusability of documents on multiple media. Based on ISO and military standards, the new information system will improve accuracy, consistency, efficiency, timeliness, and costs. This paper describes the issues that led to the system's design, pitfalls in its implementation and operation, and details the anticipated benefits."

"Caterpillar is the world's leading producer of earth-moving equipment and industrial gas turbine engines and a leading global supplier of diesel engines. Caterpillar sells over 300 products with a service life as long as fifty years or more. To support distributors in over 120 countries, Caterpillar communicates in 35 different languages. [. . .] The division implementing this new system is Caterpillar's Technical Information Division (TID) which has worldwide responsibility for producing the documentation needed to operate and service its products. TID's 300 authors and illustrators produce 800 new pages of English documentation every business day -- and Caterpillar routinely translates those 800 pages into as many as 14 languages. Today the TID group is made up of 15 groups with over 400 writers total, a total of 600 writers is expected by the end of 1997. [...]Caterpillar's New Authoring System is based on standards. They selected SGML for text and documents; TIFF, IGES, and CGM for graphics; and output specifications based on MIL-PRF-28001 for page composition. Through the use of these standards, Caterpillar was able to integrate tools from multiple vendors to support their ambitious goals.

"Enator Information Management has many years of experience in system solutions based on Enator Information Management has many years of experience in system solutions based on SGML and related standards, and carries out information analyses, information structuring, DTD design and construction as well as SGML-based system implementation.

"The necessity of using standards when trying to preserve the value of information in a changing business environment is quite well-known today, but the use of several standards simultaneously and the integration of them has not been discussed too much, even within the CALS initiative. This drama in one act will put emphasis on the benefits of integrating standards rather than choosing one of them, which in several cases is essential for success. The differences between the product model standard STEP (ISO 10303) and SGML, and thereby the strengths of each, will be illustrated by a fictive business scenario that focuses on the reasons why an integration of standards is essential for success."

Abstract: "This paper explains what is a Topic Map and describes how we have made it for the current CD-ROM.

"Topic Maps are a standard representation of navigational information that is intended to be used for interchanging such devices as indexes, thesauri, glossaries, on sets of heterogeneous documents (structured or not structured). It can be thought of as the equivalent of a neutral database scheme, that should allow its users to preserve the value added on their information repositories with semantic navigation.

"Typical users of Topic Maps include SGML users who need to maintain links accross living documents, while avoiding the overhead caused by maintenance of huge amount of data as systems evolve. Note that Topic Maps can also be used if source documents are not in SGML.

"The conceptual basis of the Topic Map architecture is based on the possibility standardized by HyTime to separate the semantic information of a link from the address of the (possibly multiple) anchors. The architecture that has been designed will be updated to take into account new standard formalism being defined for links. An XML representation is planned as well.

"The Topic Navigation Maps Project is a work done under the auspices of ISO WG8, the group responsible for SGML and related standards (Convenor: James Mason). The co-editors of this project are Martin Bryan (UK) and Michel Biezunski (France).

Abstract: "A new data modeling approach to producing SGML documents has been developed. Documents are assembled from content models, or information units, which are created and edited using common tools. These information units are collections of SGML elements, raw text, and processes, but less than whole documents. For this work, when an assembly of these objects or information units is made, then the DTD and FOSI are created for use with the output document. If the information objects conform to a given DTD (say the ATM 2100), then the assembled document will also conform. We start by describing some of the real issues that SGML systems face, then some of the approaches others have taken. Finally we detail our solution and the research that is ongoing.

Summary: The Topic Navigation Maps standard "provides a mechanism, based on techniques defined in ISO/IEC 10744:1992, for identifying information objects that share a common topic. It can also be used to define the relationships between sets of related topics. This standard can, for example, be used to define: 1) tables of contents and subject indexes for individual documents, or related sets of documents; 2) glossaries that can be shared by more than one document; 3) the relationship between topics within a thesaurus; 4) the relationships between multilingual thesauri, glossaries, etc."

Abstract: "Generation of SGML-coded documents as a result of database query processes is a commonly used practice. In most cases, however, the contents of such documents are entirely built from scratch as an SGML-formatted image of the query results. We present an extension to this practice, in cases when documents are made of a combination of human-generated parts and database originated parts. When such documents are updated, human-generated parts should remain untouched, while database originated parts (text, tables and graphics) should be regenerated or updated.

"The method used here is that of SGML templates, which embed links targeted to a database. Such a technique can be used in many application fields, ranging from Web applications to industrial catalog publishing, where complex, human-generated document structures coexist with database extracts."

Abstract: "Just as JAVA has brought an open, distributable way to enable users to interact with data by transferring applications in real time from server to client, so SGML can enable them to interact with persistent database objects by transferring, real time, the database schema for those objects. This talk explores the potential of SGML as a universal database definition language for reusable, distributable information objects and shows how existing technology is already turning that potential into reality."

Abstract: "Grupo Anaya is engaged in a 3 years project to create an educational encyclopaedia for the XXI century. The editorial work starts from scratch with no legacy information. From day one the encyclopaedia has been conceived as a product and media independent database, ready to be deployed in traditional paper based media as well as through any electronic media and channel (CD-ROM, Internet, cable services, etc.). Textual information is SGML coded, and hyperlinks are HyTime compliant; quantitative and perishable information is stored and maintained in relational databases linked to queries embedded into SGML structures.

"The editorial team, more than 100 authors, works in a distributed environment using internet, intranet and extranet technologies. All of them have access to the central encyclopaedia database (text and images), and also to an electronic library with hundreds of textbooks and reference sources available for documentation purposes. A detailed workflow has been designed to manage the editorial flow between authors, copy editors, documentalists, and managers.

"An evaluation of different SGML-based editorial systems has been undertaken (ASTORIA and SigmaLink among them) together with other standard solutions (Oracle InterOffice). The results of these evaluations together with the architecture of the solution finally adopted will be presented.

"On top of these SGML structures, a knowledge database is built in the form of an object network with semantic relations that will allow the creation of very sophisticated JAVA-based interfaces for Internet access and delivery of the encyclopaedic information. For this purpose, technology developed by GMD-IPSI in the context of MacMillan's Dictionary of Art, will be used.

Abstract: "Good quality documentation is identified by manufacturing industries as an important asset to push their products on the market. More and more companies sell their products all over the world and are requested to provide localized product documentation. In this context, controlling - through creation, translation and maintenance - the consistency of huge documentation produced in different places, on different tools by people with different skills is a real challenge. Moreover, reducing the effort of document creation and management by help of powerful software tools, will cut down the costs of complex products significantly.

"The goal of the DOCSTEP project, which is presented here, is the usage and integration of beneficial technologies and standards for product modeling, natural language processing and document management in order to improve the process of product documentation creation and management. The DOCSTEP approach is based on the integration between the product data standard ISO 10303 STEP and the documentation standard ISO 8879 SGML. It is the aim of the DOCSTEP project to develop an Authoring System where documents are based on the generic model of the product, with language independent semantic layer plus integrated tools allowing the end user to access document/product relevant information efficiently.

"The presentation shows the current results of the DOCSTEP project. DOCSTEP is promoted in the context of the Telematics Research Program (Language Engineering) of the Commission of the European Community.

Abstract: "In the context of Document Management Systems, the notion of document is becoming less and less preponderant. A document corresponds to an assembly of information objects -- SGML or non SGML objects -- that may be shared by several documents. Moreover, these information objects are interconnected by various kinds of links.

"The conventional SGML Databases offer a good support for storing and manipulating collections of independent SGML documents. They have to evolve for managing a network of SGML and non-SGML documents, i.e., hypermedia documents. SGML allows to define inter-document links by using id/idref attributes and entity sharing. HyTime goes beyond the SGML limits concerning the hyperlinking features by offering the semantic to model complex links, such as a link from a document to a very precise location inside an other one. In order to offer all the functionalities necessary for managing hypermedia documents, SGML Databases must then take into account all the above constructs. The schema of these SGML databases consists in a tree structure representing the mapping of the SGML meta-model. But it has to evolve towards a graph structure for representing the HyTime hyperlinking model. This paper presents the principles to extend an SGML Database to an HyTime Database and the functionalities of a web interface to access to the documents stored in the database."

This paper is the result of a current collaboration between Aerospatiale Aircraft Business and the Research and Development Division of Electricité De France. This collaboration concerns a study and research project in the structured electronic document database field. Although the specific industrial contexts are different, numerous common requirements may be identified in this particular field and a large benefit may be expected from a common study. Aerospatiale and Electricité De France are two big French companies which produce respectively, aircrafts (Aerospatiale Aircraft Business) and electricity. Both need to manage a large amount of documentation in their own industrial context. As a consequence, a significant benefit is expected from powerfully computerized documents. [...] After presenting this study's industrial contexts, we succinctly present our approach for specifying an SGML database. Then, we focus on our strategy for evolving towards an HyTime hypermedia database. We show how we have chosen to implement this SGML/HyTime Database. Finally, we conclude by giving the progress status of our work and the main issues which remain to be studied in depth.

Abstract: "This case study describes the issues involved in managing a large body of SGML-based aircraft maintenance documentation. Principal topics covered are managing appropriate granularity; sharing document components; managing multiple configurations; managing revision cycles; and impact on publications. The presentation explains the reasons motivating the technical decisions, describes the tools used to manage multiple configurations and versions, and evaluates the resulting system."

"Sogitec has developed Industrial Documentary Systems (IDS) independent of the Document Type Definitions (DTD) handled and which are based on the concept of Data Modules. These systems benefit from our dual qualification as a supplier of aircraft documentation and computer system designer. For many years, Sogitec has been handling technical documentation for all Dassault aircraft, including the Mirage and Rafale fighters and the Falcon series of business aircraft. The systems can be adapted to different user profiles.

"The documentary database is broken down into a multitude of units of documentation (UD). The final documents are compiled by concatenating individual units of documentation. This strategy has been dictated by the often overwhelming size of documents combined with the need for fine grained control of the system. Each unit of documentation has contents, an identifier and an identity card. The contents of a unit of documentation is an SGML-format text based on a DTD. Almost any DTD is possible, but they sometimes use mark-up which needs to be displayed to identify links, effectivity or any other information useful for database management.

Abstract: "Forty Years of Generalized Markup. 1997 marks the start of the second decade of ISO 8879, the International Standard that defines SGML. It also marks the start of the fourth decade of the generic coding and Generalized Markup concepts on which SGML is based. In his traditional SGML Europe keynote, SGML's inventor fearlessly predicts where we will be ten years from now, with perspective and direction gleaned from where we have come during the last thirty."

Absract: "The growing complexity of automobiles, coupled with U.S. government requirements for emission-related information to be made available to independent repair technicians, is requiring major changes in the way technical information is delivered in the automobile industry. The European automotive industry also will benefit from implementation of automotive industry also will benefit from implementation of SGML, CGM, TIFF and other standards specified by the SAE J2008 task force, which was charged with developing the recommended organization of electronic service information. This presentation describes common problems U.S. automobile manufacturers have faced in creating electronic service bay systems, and the additional challenges that arise when some of the needed data resides in foreign countries in closed, proprietary systems.

"In the last few years, the 'Big Three' U.S. car companies (GM, Ford, Chrysler) have begun to introduce electronic service information into their dealerships. These systems differ widely in their look, feel, and user-friendliness, but they all use SGML and can produce information organized according to J2008. While a few importers, such as Hyundai, already have operational SGML systems, most are still developing viewing and authoring systems simultaneously with creation of an SGML/CGM database. Development of a J2008-compliant system is even more complex for companies where much of the service information required resides in foreign locations, sometimes in foreign languages, in proprietary, non-standard publishing systems."

Abstract: "One of the main barriers to those wishing to create SGML systems is the high 'cost' of authoring: the level of expertise necessary to author in a structured editor can be prohibitive, as can the cost of up-translating documents from traditional word-processing formats. While SGML editing tools are slowly improving, they are still a far cry from the sort of applications that would enable SGML to be adopted as a mainstream technology in settings where WYSIWYG word-processors are the norm. At the same time, emerging standards in the SGML world such as HyTime and DSSSL, as well as the demand for support of such features of the standard as LINK, SUBDOC, and the internal declaration subset (among a more technical audience) require that SGML editors fill a different role, but one that is currently neglected. This paper presents a practical look at how (and how far) these goals can be met, given the existing state of SGML technology and related standards."

"By examining the different authoring paradigms, and by looking at successful word-processors, code editors, HTML authoring tools, and structured editors, a set of requirements is developed for the 'ideal' SGML authoring tool(s). The design approaches that can be taken for meeting these requirements is then considered. Emphasis is placed on utilizing architectural forms as an enabling technology within software applications, and leveraging the DSSSL and HyTime standards to enhance both application functionality and the value of the documents produced.

"Features that would be desireable for ease of integration with SGML document management systems are also addressed. The impact of XML on the development of editing tools is examined, and some approaches recommended for dealing with the impending wave of 'para-SGML' documents this new 'standard' threatens to generate.

"While an SGML editor cannot do everything for the user, the real world demands that this class of applications be significantly improved, both in terms of usability and functionality. This paper focuses on where these improvements can realistically be made, and what approaches have become possible given advances in the implementation of SGML and related technologies. In a more traditional vein, an analysis of successful authoring paradigms shows how SGML applications could be improved without requiring new technologies. It is hoped that this paper will help users vocalize what they most want in their SGML editors, and help developers understand how these features might successfully be implemented."

Abstract: "Was SGML born too early? 10 years ago, very few people understood its potential. But, now-a-days, surfing on the Internet wave, a number of technologies have become trendy. Buzzwords like virtual reality (VRML) or active content (Java, activeX) have become fashionable. How are they related to SGML? Is it not the SGML approach that paved the way to such advanced technologies?

"This paper explores these issues, examining the results of a number of research projects launched by Eurostat to review cutting-edge and emerging information technologies and to evaluate, from a user's point of view and on the basis of concrete applications, how they could help Eurostat fulfil its mission, which is to provide the European Union with a high quality statistical information service.

Abstract: "Sun is 3 years into a large project that radically revamps its online document creation, management and delivery system, from a proprietary product to an open SGML system designed to meet all current needs, including XML and Java, as well as whatever the future might bring.

"The goals are deceptively simple: take the writers' documents and, with a minimum of processing, package them and make them available to all users; support links not only within the books but also between books, independently of where the books are ultimately located; execute context driven searches; support user manipulation of contents of book collections and installation wherever they wish; enable viewing books outside of the Solaris environment - and we want, finally, for anybody to be able to publish their own books within this environment.

"A decision was made, very early in the process, to migrate to an SGML-based delivery process, and, following consultations with others in the industry and our own research, we also decided to migrate our authoring environment and tools to SGML, rather than continue using a third party proprietary product, so as to avoid the painful problems associated with multiple conversions.

"Three processes were put in place: conversion/authoring, production, and delivery vehicles.

"This case study will concentrate on: 1) how we arrived at our DTD; 2) how SunSoft decided on an editing tool; 3) how inter-book linking in the absence of standard URNs is accomplished; 4) how books are delivered over the Net, including multiple HTML formats; 5) print-on-demand; 6) I18N/L10N. [Finally], what is the relationship between all of the above and the so-called 'production process', which controls both the automatic production of collections, and the repository/database where all meta-information is maintained?"

Abstract: "When making a business case for SGML, one of the key arguments is justifying the cost for the transition to SGML. This presentation is designed to help you justify the cost of implementing SGML whether your objective is to support multiple outputs or to re-engineer your information production processes. This presentation covers the measurable benefits in detail, discusses the unmeasureable benefits of SGML, and provides suggestions for preparing your argument."

"A cost justification proposal is more than just a series of line items with related costs. It is an important sales tool - one that will help ensure your success as you compete against others for funding. Authors of successful cost justification proposals have three things in common. First, they have a clear understanding of their company's short- and long-term goals and objectives. Second, they have identified areas where new practices (or processes) and new technologies can contribute to reaching these goals. Third, they have adopted a production process vocabulary set to describe the changes and how these changes will benefit their customers."

Abstract: "SGML has celebrated 10 years as a standard, and although the standard is only now being revised, the use of SGML has evolved over time. This paper explores some of the features that has made SGML successful, the importance of adopted conventions, and speculates on future applications as SGML transitions into the next century."

"As an international standard, SGML is subject to orderly, voted-upon change. Already a decade in adoption, it is due to be revised. In many ways, the standard was farsighted in its design -- a fact confirmed by it being applied well beyond its original publishing design intentions, and in becoming the foundation of promising standards such as ISO 10744 HyTime. Even the long delay in completing the companion standard ISO 10179 DSSSL has not significantly slowed SGML's rise to prominence. However, even if the standard itself has yet to change, the use of SGML has made a number of transitions.

Abstract: "Two key measurements of the success of any SGML system are cost reduction and user satisfaction. This paper examines implementation details that can affect ease of training, ease of use, and overall productivity; and suggests various techniques for enhancing both productivity and user satisfaction. It also looks at how to take advantage of emerging technologies to provide additional capabilities for leveraging and reusing information."

Abstract: [for the Closing Keynote address] "With developments like the World Wide Web, intranets, and increased focus on standardization by major software vendors, SGML and its related standards are being revised and enhanced to reflect new technologies and new requirements. This presentation looks at recent events--including the publication of the DSSSL standard, the HyTime Technical Corrigendum, and the XML specification--and projects the trends they represent into the future of SGML. The major trends are more functionality at a lower cost of entry, providing greater overall value."

Abstract: "This presentation describes how the information repository of a publishing house was integrated into the environment of the company. The attempt was made to combine the entity relationship approach of an SQL database and the document-driven approaches of SGML. This led to more than one SQL database with an identical microdocument architecture to store the information elements. This presentation closes with a view to the future plans of integrated composing of products with the microdocuments of the database."

"Introducing SGML to a conservative publishing house is a long way to go. In the case of C. H. Beck, the leading company for legal publications in Germany, the efforts were driven by the demands of a continuous growing market for electronic publications, on line as well as CD-ROM.

"Since information is the main business of a publishing company, to create an effective information repository was the first step to go. The efforts were driven into two different directions.

"On one hand the information, the sources and the publication process was structured in classic entity relationship models. The analysis brought three different information models (legislative documents, court decisions and intellectually authored texts) implicating three different databases. Two of three databases represent an entity relationship model of the information. The third database (storing the authored texts like books) is document driven and mirrors the structure of the source publication. To enable the best flexibility and an easy handling of the data, in each case the documents were broken apart into micro documents of almost the same class.

"On the other hand the source documents and the resulting publications where examined in order to create a DTD. The resulting DTD is divided into several modules, that represent overall document structures (books, journals, sections etc.) and modules to indicate detailed information (tables, highlighting etc.). the overall DTD is intended as an abstract model in order to derive various different process specific DTDs. Thus the detailed element model corresponds with the micro documents of the information repository. The global document structures are created by the export function of the databases.

"In the future there will be a combining project management system, which will enable the product manager to create publications containing micro documents of all three databases and an overall structure.

Summary: "This session will address the central role that identification and analysis of document components plays in the selection, design, and deployment of document management systems. The key to success in installing such a system is a thorough analysis of your information model. The SGML document analysis process is the cornerstone of this effort. The total effort should be no less rigorous than that used for designing and deploying any database management system. Additionally, information analysis should be independent of the deliverables such as paper documents that traditionally inform the design of a document management system."

"SGML is today's most powerful comprehensive object model for document information, and as such is an ideal mechanism to migrate the underlying document structure need to change to move from a file based to a component based DBMS system. The SGML document analysis process is the starting place for the information analysis required for successful component management."

Abstract: "Brunei Shell Petroleum (BSP) has developed a system to support the production operators in their day-to-day activities on the Platform. This system (named 'Ajaib' which is Malay/Arabic for Miracle) breaks away from the traditional Operations Manual and instead delivers all information required by the Operator in support of his day-to-day activities from a single, commodity desktop Web browser. The information is managed in its native format (e.g., SGML, AutoCad) and is presented in a variety of formats including animation and graphics; this session aims to provide insight into the development and acceptance of a corporate Intranet solution."

"BSP decided that the core information for the system should utilise SGML to manage the various information content types and relationships. BSP chose to re-use DTDs specifically developed for Shell Expro to capture the information. This information consisted of asset information (e.g., equipment descriptions for specific platforms, pipelines and systems), organisation information (e.g., description of BSP personnel and their responsibilities), and activity information (e.g., descriptions of maintenance tasks that operators perform each day). Furthermore, the system should also contain additional explanatory information, as is usually contained in training manuals. The new system had to provide all the information that operators require from a single point of delivery, in a format that would be appealing to the operators. The decision was made to use Web technology and standard products to deliver the specially created content in a textual and graphical form. The textual information would be converted from SGML to HTML prior to delivery of the final system."

Abstract: "The SGML (Standard Generalized Markup Language) world has concentrated on solving the problems of textual documentation. SGML and other information standards are rather complex to take into wide use. SGML alone is not enough to implement working solutions. There are a large number of methods, models and naming conventions developed for different application areas: microdocuments, components that contain bigger element hierarchy, etc.

"This paper describes a keep-it-simple model as a base for interactive electronic applications. The model keeps the data in life-cycle safe format (SGML), but still gives the end-user any possible view to the data and interaction with it. One design goal of the model was to separate information, functionality and user interface from each other.

"Information is managed in SGML, HyTime (Hypermedia-Time-based Structuring Language, ISO 10744), and DSSSL (Document Style Semantics and Specification Language) formats. The information packages, that travel between client and server (and between applications), are modeled with information standards. Functionality is achieved with engines on client and/or server side. The user interface language is HTML (HyperText Markup Language) and Java applets.

"XML (Extensible Markup Language) brings lightness and data format independence when HTML provides a common user interface description language. Java applets are a modular solution for interface functionality and platform independence. HyTime is the way to link the information chunks together in a standard way. Data is stored in databases that are part of the application or part of the information infrastructure.

"This presentation contains models for putting SGML and other information standards to work for wide range of interactive electronic multimedia applications.

Abstract: "The Alabama State Legislature has begun an extensive re-engineering effort to improve the process and technologies used to craft and enact legislation and to improve the means through which the public can be directly involved in the legislative process. When this project is completed, the State will have an information system that provides repository based authoring and publishing, client/server legislative operation systems with a 'real-time' Internet interface. SGML is an important component of this complex application.

"In this session we will present an overview of the application and we will discuss in more detail how we used object oriented information engineering analysis and document analysis to develop a robust information model. We will discuss the design challenges we faced integrating SGML with traditional database technologies, mult-tiered client server technologies and the Internet. Most important, we will share valuable lessons learned about designing and building repository based SGML systems."

Abstract: "Publishing to the Web introduces a new set of challenges, especially when added to the requirement to produce traditional documents using the same data, at little extra cost or manpower. To the casual observer, the problem seems one of converting data from its presentation format into HTML. However, the problem is much more complex. Although converting your data into HTML is one part of the solution, issues such as modularization of your data, establishing links for traversing through the information, search aids, and adding additional data that might not be found in your traditional (paper) publications (such as navigation aids) must all be considered. This presentation explains how, through the use of SGML and document management technology, publishers can create highly automated processes for using the same data to produce paper documents, a Web Product, and possibly other electronic deliveries."

Abstract: "PCIS DSSSL-O Stylesheet (PDoS). PCIS - The Pinnacles Component Information Standard is an ISO 8879 application designed to meet the markup needs of the semiconductors industry. It was designed under the auspices of the Pinnacles Group, a consortium consisting of major companies in the semiconductors industry. The PCIS tag-set is the de-facto standard in the semiconductors industry. DSSSL-O is a subset of ISO/IEC 10179 (DSSSL), designed the address formatting requirements in the area of online-display (rendering) of SGML/XML data using DSSSL.

PDoS is a first attempt to create a DSSSL stylesheet for the PCIS DTD. This paper discusses a variety of aspects encountered/addressed during the development of this prototype stylesheet, such as modular stylesheet design and user configerable stylesheet architectures. Testing and development of the presented concepts has been done using James Clark's DSSSL engine Jade and the authors Java based DSSSL renderer Yade.

Abstract: "A method to develop an SGML diff is presented. The extendible approach is based on a change-oriented model for structured documents containing objects of type 'data', 'element', 'attribute', or 'link'. The difference between two documents, A and B, is computed and expressed as a sequence of changes that must be incrementally performed on the objects in A in order to obtain the state B.

"Companies that must handle huge amounts of technical documentation can use SGML to mark up their documents in order to process, interchange, and archive them independently of any particular proprietary format. An author often faces different versions and variants of a document. In case these are two SGML document instances that are similar, but where the relation between them is not clear, he needs a meaningful description of their differences.

"As SGML is used to encode additional information about the structure of a document an SGML diff should reflect the data structure of the documents it compares. It is not enough to get a description of differences between two SGML document instances on the basis of their unstructured textual contents. [...] The aim of this paper is to propose a method to build an SGML diff that computes the difference between two SGML document instances A and B as the sequence of changes that would produce B if incrementally performed on A. The task of developing such an SGML diff is threefold: first, the object types of an SGML document must be determined, and second the possible changes for those objects have to be specified. Finally an algorithm is needed to compute the delta between two documents."

Abstract: "RAFHS produce the Aircraft Manuals and Flight Reference Cards required by the aircrew of all three United Kingdom services -- Army, Navy, and Airforce. Members of the RAFHS team are specialists in the aircraft types flown by the Forces. They are not computer professionals and therefore the system acquired had to be intuitive, modern, and have an excellent user interface. The RAFHS system provides an integrated solution including SGML author/editing, document management, revision tracking to provide future-proofed data, an airworthiness audit trail, and finally output formatting and pagination by a composition engine."

"RAFHS (ROYAL AIR FORCE HANDLING SQUADRON) produce the AM (Aircrew Manuals) and FRC (Flight Reference Cards) required by the aircrew of all three United Kingdom services -- Army, Navy and Air Force. Members of RAFHS are specialists in the aircraft types and roles flown by the forces. The mix is approximately 50/50 serving officers and retired officers. The retired officers, in general, are over 55 and only just computer literate having moved in 1989, reluctantly, from a cut and paste editorial system. A system that owed its genesis to advanced technological change much earlier in the century; essentially coloured pencils, scissors and glue.

"AM are substantial documents covering the handling of the aircraft under normal and abnormal flight conditions, the description of the aircraft structure and systems and their operation under normal and failure modes and the limitations that apply to all phases of flight. Extensive use is made of A3 and A4 illustrations in both black and white and colour. FRC are, for most modern aircraft, large documents in A5 format and can be as large as 160 sheets. The contents are checks and drills to be carried out by the crew during the period they occupy the flight deck or cockpit and include normal and emergency procedures.

"Moving to SGML provides considerable benefits, many well documented which need not be rehearsed again here, others less well known like the focusing, within our organisation, of the authors' energies. To achieve these benefits cost effectively and efficiently many lessons can be drawn from our, initially quite naive, but ultimately very successful change to the standard. [...] We now have the basis of a system which will protect our information in the long term.

Abstract: "Only a few markets around the globe can mandate the universal use of a single language for documentation. Further, it was once the case that the author had some sight of the user of the information. With global markets this luxury has all but vanished. Today authors have little sight of the intended user of the information. It is more than likely the user will work in a different culture, a different language, using different media. Organisations must be cogniscent of these conditions of entry into the market, and in most cases the requirement to provide localised, translated information must be absorbed as part of the cost of entry. Such costs can rapidly exceed the original startup costs for production of the source language version. Today the pressure is on to find ways to reduce startup and ongoing costs and time frames whilst maintaining or improving quality.

"The presentation discusses such initiatives. The key argument presented will be that translation activity and management of information encoded in SGML (Standard Generalized Markup Language) can provide reductions in cost and timescales whilst offering real opportunity to improve the quality and consistency of the content. The advantages offered by the SGML context when applied against technologies and concepts such as Translation Memory, SGML Element-level management and Controlled Terminology will be presented and discussed. The application of these capabilities will then be presented as part of a Component Based Document Management System providing a concurrent translation processing environment."

"Within the presentation references will be made to ongoing initiatives to implement such systems, providing an analysis of the issues to be addressed, and the savings generated have provided towards the justification for the use of SGML."

[No abstract available.]

Abstract: "The World Wide Web is fast becoming the de facto repository of preference for on-line information, yet the technology of the Web has inadvertently created barriers for people with disabilities. Worldwide, more than 750 million people with disabilities (more than 100 million in Europe alone) are affected by the emergence of the Web, directly or indirectly. In order to 'push the envelope' of information access and truly realize the full potential of the Web, the World Wide Web Consortium (W3C) intends to take a leadership role in removing accessibility barriers by launching the Web Accessibility Initiative (WAI, pronounced 'WAY').

"Mr. Paciello, creator of the WAI, will discuss the initiative's goals and mission and how SGML plays a major role in the advancement of information accessibility."

Abstract: "A significant economical objective at Norsk Hydro is to reduce the time and cost of maintaining equipment used in oil production.

"According to NORSOK (NORsk SOkkels Konkuranseposisjon, or in English the competitive standing of the Norwegian offshore sector), 50% of the development cost of an off-shore installation is related to information. NORSOK is the Norwegian initiative to reduce development and operation cost for the off-shore oil and gas industry. An important part of this effort is to develop cost efficient standards to replace individual oil company specifications.

"In this case study we will explain the implementation of an interactive system to improve the accessibility of technical supplier documentation by utilising the SGML standard."

Abstract: "SGML was designed in an environment where other-than-8-bit character representations were only vaguely known and not understood. The designers did not differentiate between (abstract) characters and the bit-patterns by which they are represented in machines. This resulted in a character-handling model that is no longer adequate in many respects. In addition, there have surfaced differences of opinion as to how the current SGML standard (ISO 8879 as amended in 1988) should be interpreted with respect to the handling of the characters that make up the SGML documents it describes.

"A new character and character-string model has been adopted by the SGML Rapporteur Group within WG8 [now WG4], where the ISO 8879 revision is being prepared. The new model encompasses handling of variable-width-character string representations such as Shift-JIS, and outside-the-document specification of character representations, as well as the traditional 'document character set' specification.

"A Technical 'Correction' to ISO 8879 was made official in 1996, which made it more feasible to use SGML with very-large-character-set languages such as Japanese and Chinese, for use on SGML systems not constrained to an 8-bit character set.

"This presentation will explain the distinction between (abstract) characters and the computer representations of characters, and will explain the new character handling model in terms thereof. It will further explain the relationship to the old character-handling model of 1986, and how older systems may be upgraded, and what is possible when still running under the old (1986/88) rules. This involves the relationship of the 'document character set' to the way systems may actually represent characters, and the use or non-use of the 'shunned character numbers' specification."

Abstract: "This presentation provides an overview of four techniques that combine the principles of data storage and generalized markup into database publishing systems. These four techniques are ordered by increasing document structure flexibility. Their effects are illustrated by a simple yet realistic example. The conclusion argues in favor of document structure independent data modeling.

"Consider a class of database publishing systems that exploit the principles of generalized markup. Each system in this class encompasses three main subsystems: a data storage subsystem, processes that transform the stored data into SGML, and processes that transform the SGML documents into final publication form.

"We are interested in the impact that the chosen style of storing data has on the structural flexibility of the database publishing system. In other words, we wonder how much effort, and of what kind, is involved in adding a DTD (Document Type Definition) to the publication domain, or in altering an existing DTD.

"Four styles of data storage are beforehand, namely: 1) storing text files containing the SGML; 2) a database whose schema has been designed after one or more DTDs; 3) a generally applicable SGML database; and 4) databases designed independently of document structure. Each of these approaches has its own advantages and disadvantages, but regarding structural flexibility, document structure independent data modeling is the winner by far."

Abstract: "A panel of experienced users (including Marcy Thompson, Neil Bradley, Roger Boncoeur, Alan Burrows, François Chahuneau, Louis Nahas, Steve Newberry) discusses the pros and cons of using industry DTDs. Avoiding the over simplification of two polar positions (drastic or no modification of an existing DTD), the panel members discuss the numerous decisions facing implementers in between these poles. Questions posed to the members include: When a DTD is so large that an organization only uses part of it, what does interchange mean? Do different organizations interpret elements (or attributes) differently? Does any organization implement the entire DTD? How accepted is it to use a different DTD for editing and the industry-standard one for 'interchange'?

"The term industry-standard DTD refers to a DTD, designed by participants from several unrelated companies or other organizations, for use with documents on similar topics produced by these organizations. Despite the word 'standard,' industry-standard DTDs are not necessarily produced by recognized standards authorities. Often, they are intended for interchanging documents rather than for creating new ones. This panel brings together two groups of users of such DTDs -- end users and vendors (or SGML service providers) -- for a discussion of practical issues in the implementation of SGML projects based on such DTDs.

Abstract: "Croner Publications Ltd's experiences with SGML over the last three years have been both exciting and traumatic! In this presentation, Mr. Rankin describes how and why Croner considered SGML to be the answer to many of their problems and details the difficulties encountered along the way. The presentation emphasizes the need to have the courage to press ahead and 'open the envelope'. Finally, he plots the future strategy his company will adopt and the role SGML is set to play over the next decade."

"Croner Publications is a successful publishing company based in London and is market leader in the UK in areas of publishing information relating to tax, employment law, transport, education, health & safety and the environment. The publications interpret the law for business managers and directors and the text of the publications is mainly in the form of commentary. Today, Croner publish over 100 loose-leaf books, 75 newsletters, 40 special reports, 70 bound books and 50 electronic products. Publications are updated frequently, including weekly, fortnightly, monthly and quarterly. [...] The presentation will be in the form of a case study and will look at how Croner Publications tackled the whole issue of adopting the SGML standard. Covering the period 1993 to 1997, the presentation will highlight some of the problems encountered, how the business benefits of SGML were perceived and how the business case for SGML was sold to the publishers at Croner. The future is also addressed and an outline of Croner's future strategy will be given. The theme of the presentation is simply that it took courage to finally grasp the nettle and 'open the envelope'!

Abstract: "This report describes our experience with a conversion project involving IBM BookMaster and HTML.

"Credit Suisse, a large Swiss Bank, has an existing document processing infrastructure based on IBM host. They use IBM BookMaster -- a markup language based on GML (Generalized Markup Language). Their BookMaster documents are traditionally distributed on paper. The content is the documentation of bank-internal software applications -- everything from user manuals to technical descriptions for audit purposes. The document size varies from about five to several hundred pages.

"To improve the accessibility of their documents the bank wants to publish and keep these documents in a corporate intranet in the future. While this intranet is currently coming into existence the old paper publishing process must be maintained. The coexistence of the old and the new 'world' will be necessary for several years. Conversion tools are therefore needed to ease the way from BookMaster to HTML and back. This paper is a description of the current status of the ongoing project.

Abstract: "Increasing requirements in development documentation for automotive manufacturers such as the number of world-wide development sites (leading to the support of different languages); the speed of the development cycle; and the number of variants of products (re-use of base documentation), has led to the definition of exchange formats for information. This paper examines how SGML technology can be a good solution for problems in this area." [from the published program]

"The development of ECU (electronic control unit) for cars is a highly parallel and complex job. Requirements from different parts of an automotive manufacturer have to be fulfilled. The interfaces between correlated persons are not defined in a way, that an exchange of information is done easily. Business process reengineering activities discovered a big potential for enhancements by using SGML technology as an overall exchange format in these areas.

"Several projects were started, to implement a new process model. This article describes our experiences in projects we realized since the beginning of 1995. The biggest project deals with diagnosis data that is needed to describe parameters to communicate with ECUs. Today you can get many informations about the actual state of internal and external variables of ECUs (for example a coolant temperature). These informations are used to guide a diagnosis process to determine erroneous behaviour of components of a car. The diagnosis data is used in different parts of the company (development, production, service). Even companies that deliver ECUs can be involved in this process. We started a case study to determine the best format for the description of structures. As a result we decided to take SGML. The Document Type Structure (DTD) is presented to the ASAM/ASAP consortium for standardization. This consortium represents the German automotive industry, suppliers and tool companies.

"The system is now in use by 10 to 15 users and will grow in 1997 to 30 to 50 users. There is a process of standardization of diagnosis data in the moment in a consortium called ASAM/ASAP. Our DTD is a proposal to that committee and we think it will be fixed till the end of 1997. Our experience with the technologie SGML are quite good. We can transport the concept very easily to the users.

Abstract: "The aviation industry has a long tradition for information interchange standardization. The first generation of on-line documentation was a paper document duplicate based on SGML. In the future, documentation has to move from the document paradigm to an information paradigm. Then the user will get an 'Information Web' and exactly the information he is looking for. This presentation looks at the challenges and trends in aircraft maintenance documentation."

"In aircraft maintenance and operations documentation structure and form are well defined by the ATA SPEC 100 specification. It was a good foundation bringing that documentation into electronic form using SGML. SGML is today the foundation for ATA SPEC 2100, the aviation standard for electronic document interchange. [...] Tagged information at a well defined granularity makes incremental revisions easy. Taking advantage of the progress in electronic networks, an on-line document update will be possible and leads to totally new worksharing concepts between aircraft manufacturers product support organization and airline engineering."

Abstract: "Most Document Management System architectures can be categorized by the ability to handle and organize information of different kinds. Supporting information based on the Standard Generalized Markup Language (SGML) involves unique requirements that bear on the tasks of managing structured documents."

"This report overviews approaches to support SGML documents in a number of Document Management System architectures that were candidates to be used in an actual publishing system supporting the publishing and re-purposing of shared information for technical manuals. This publishing system supports content- and presentation-oriented SGML documents for a supplier of military equipment to a Canadian Department of National Defence (DND) Project Office."

Abstract: "The abilities to deliver vast amounts of corporate information on-line in real time, with sophisticated hypertext navigation aids, and the accelerating system complexity of products and corporate processes have converged to drive a new paradigm: component-based documentation development. The microdocument architecture is a vendor-independent hybrid of SGML and RDBMS methodologies that enables the delivery of personalized virtual documents. Illustrations of successful virtual document implementations and an overview of business and project leader implementation issues are provided."

Abstract: "Authoring in SGML is difficult and time consuming. Creating SGML documents is costly and complex. Although many of the SGML authoring tools available provide superior SGML functionality, many are not intuitive. This paper will discuss Novell's approach to creating structured hypertext documents intuitively and efficiently by integrating and customizing current database and SGML authoring technologies. The main goal of the system Novell developed is to optimize the authors ability to create and manage structured content.

"The focus of the presentation will be a demonstration of the tool Novell developed to solve many of these problems.

Abstract: "The new paradigm of information objects has recently emerged that replaces the old one of documents. The new view on information concentrates on smaller bits of information which may be connected in different contexts and that are linked and webbed together under multiple perspectives."

"This paper focuses on the techniques and applications that are available already to produce and maintain information webs. We discuss the fact that many authors and publishers are writing books as they have been doing for the last 500 years. Partly it seems to us to be the publishers and authors turn now to redefine their methods, their products and their markets. What are the new opportunities, what abilities and skills are needed, and what are the problems in the shift to a new way of writing and publishing?

Abstract: "There are at least three reasons why separating markup from the material marked up ('standoff annotation') may be an attractive proposition: 1) The base material may be read-only and/or very large, so copying it to introduce markup may be unacceptable; 2) The markup may involve multiple overlapping hierarchies; 3) Distribution of the base document may be controlled, but the markup is intended to be freely available.

"In this paper, two kinds of semantics for hyperlinks are addressed to facilitate this type of annotation, and describe the LT NSL toolset that supports these semantics. The two kinds of hyperlink semantics that are described are (a) inclusion, where one includes a sequence of SGML elements from the base file; and (b) replacement, where one provides a replacement for material in the base file, incorporating everything else. The speakers address the issue of different kinds of (HyTime and TEI) addressing schemes by means of SGML identifiers, URLs, and character offsets into non-SGML data. We also address the issues of indexing large files to improve the speed of accessing SGML elements in the base files."

Abstract: "This document presents the European Aquarelle project and the missions and the documentation system of the General Inventory. It then examines one of the first applications of this research project with Aquarelle project and the missions and the documentation system of the General Inventory. It then examines one of the first applications of this research project with SGML tagging of a digital version of Inventory archive folders dealing with France's monuments and art treasures."

"The technical and documentary specifications and standards selected are TCP/IP for internal and external networks, HTML for pages of text, SGML (Standard Generalized Markup Language (ISO 8879) for digitised content folders and the Z39.50 request protocol for access to data bases, standards ISO 2788 and 5964 for drawing up monolingual and multilingual thesauri, and the CIMI (Consortium for the Computer Interchange of Museum Information) DTD and the Inventory DTD for applications respectively relating to museums/art galleries and monuments

Abstract: "ISO 10303, Standard Exchange for Product Data (STEP), is being developed by a broad range of industries to provide extensive support for modeling, automated storage schema generation, life-cycle support, plus many more data management facilities. ISO 8879, Standard Generalized Markup Language (SGML), and the SGML family of standards, including HyTime (Hypermedia-Time-based Structuring Language, ISO 10744) and DSSSL (Document Style Semantics and Specification Language), is used for the documentation of products. These two standards, STEP and SGML, are used in the same industries and companies. STEP is used during product development and manufacturing, where as SGML products are usually created during the final processes of product development.

"This paper will discuss current initiatives in industry and government organizations for incorporating SGML product information during the beginning of the product development cycle. Several different initiatives from various corporations will be discussed. The benefits of each of the different methodologies will be discussed and analyzed.

"The STEP standard task group, Product Documentation (ISO 184/SC4/WG3/T14) is currently tasked with the responsibility for creating a methodology for the cooperation of the STEP and SGML standards. Information will be provided about how current corporate initiatives could impact and provide pertinent input in the T14 Working Group.

Abstract: "This presentation reviews the advantages of using the Extensible Markup Language (XML) in the context of legacy data conversion. This exciting application of SGML solves numerous conversion problems. By reviewing the advantages of XML in converting legacy data, this presentation shows a never before possible migration strategy towards valid SGML information."

"Converting legacy documents to XML is the most economical way to add intelligence to your documents and make them immediately 'consumable'. It also allows you to implement an SGML system for any future document and to use the 'hybrid' technology to slowly convert the legacy data to SGML."

Abstract: "In spite of its name, SGML (Standard Generalized Markup Language) is, at its core, a data schema language, not just a markup language.

"Its role as a markup language for text presentation is well understood. As such, it is one of the pillars of the WWW (World Wide Web) phenomenon. To limit SGML to text markup, however, is to do a disservice to its power. Textual presentation schemas, while important, constitute but one domain in which SGML can be applied. SGML can be used to specify schemas for many types of data and even for behaviours.

"SGML has two separate and distinct roles. The first role is for document (that is, text document) interchange. The second, more interesting role, is as a data schema language that supports structural semantics: that is, how do objects relate to other objects. It is this use of SGML that allows it to play a fundamental role in managing complex systems.

In this paper we will consider: (1) SGML as text encoding technology; (2) SGML as a data schema language; (3) The future of SGML; (4) Attaining the future.

Abstract: "The RAF (Royal Air Force) have traditionally supported their in-service fleet exclusively with either hard-copy publications or microfiche. This is changing. Recently placed contracts for the Attack Helicopter, EuroFighter 2000 and the Replacement Maritime Patrol Aircraft mandate electronic delivery of Descriptive, Maintenance, Parts Catalogue and Training publications data. This data is destined for delivery to LITS (Logistics Information Technology Strategy, the RAF's Logistic IT System). LITS is being developed by the RAF and IBM to receive and electronically distribute this data in an SGML-based Data Module form as defined by AECMA 1000D and the UK (United Kingdom) Def-Stan 00-60.

"This project is scoped to include over 60,000 pages of Technical Manuals (including Descriptive, Procedural and Parts Catalogue data) for conversion from its current production methods and specifications to SGML-based Data Module production and delivery.

"The project will challenge Consultants, Applications Developers, Authors, Editors and Document Conversion specialists to deliver this data in a new form and structure whilst continuing to support the operation of this front line Fighter Aircraft."

Abstract: "Many of those who use HTML are realising that they need the added flexibility of XML for their applications. This talk discusses how to get your data and systems from HTML to XML, including conversion and authoring."

"Interest in XML is growing, particularly now that major browser vendors are showing some interest in XML. There is an opportunity for people to add the richness they need to their documents, getting away from the restrictions of HTML. The best methods to do this will depend on the systems you currently have in place, as well as what you want to do with the documents.

"In general, you don't need to convert your SGML DTDs to use XML syntax. Many applications will only need the document, not the DTD. The advantage is that you can use the more complex SGML syntax that may be in your system, such as marked sections. What matters is that the document coming out is XML-compliant, not that the system that produced it is XML-compliant. Even if you need to provide a DTD, because the processing application on the other side of the Web uses the DTD, it may be possible to provide an XML-compliant DTD that matches the documents, but isn't the DTD you use for authoring." [extracted]

[Abstract unavailable.]