Movatterモバイル変換

Abstract: "The World Wide Web has had over 5 years of intensive development, and has expanded from a text-only technical documentation system to a multimedia information base distributed across the planet. Although its tool for structural definition, the Hypertext Markup Language (HTML), has been under constant development throughout this period, most browsers have been slow to take advantage of all the facilities it offers. At a time when there is much debate over the public future of the Web, it is in danger of partial stagnation. Despite significant innovations in some areas, the field is still open for software developers who are capable of harvesting the benefits of SGML, the language in which HTML is written. This analysis of HTML Document Type Descriptions (DTDs) reveals where some opportunities may lie."

"Abstract: The evolution of document management systems towards compound documents makes necessary the use of rational representations of information. Rather than slowing down technology development, document standards offer a new way of using document management systems. They are not only search tools, but become communication nodes for documents between electronic media. By representing the logical structure of documents and being system independent, the SGML standard especially addresses this issue."

"Abstract: With support from four NSF awards we aim to develop a prototype digital library in computer science and apply it to improve undergraduate education. First, Project Envision, "A User-Centered Database from the Computer Science Literature", 1991-94, deals with translation, coding standards including SGML, retrieval/previewing/presentation/browsing/linking, human-computer interaction, and construction of a partial archive using text and multimedia materials provided by ACM. Second, "Interactive Learning with a Digital Library in Computer Science," 1993-96, supported by NSF and ACM with additional assistance from other publishers, focuses on improving learning through delivery of materials from the archive. Third, "Networked Multimedia File System with HyTime", funded by NSF through the SUCCEED coalition, considers networking support for distributed multimedia applications and the use of HyTime for description of such applications. Fourth, equipment support comes from the Information Access Laboratory allotment of the "Interactive Accessibility: Breaking Barriers to the Power of Computing" grant funded by NSF for 1993-98. We report on plans and work with digital video relating to these projects. In particular, we focus on our analysis of the requirements for a multimedia digital library in computer science and our experience with MPEG as it applies to that library."

"Abstract: As far as technical documentation or publishing is concerned, paper media is giving way to electronic media. The SGML exchange standard is gaining increasing importance. It is more particularly used to perform electronic technical publication exchanges between aircraft manufacturers and airlines. This standard allows the document tree logical structure to be described in a computer system-independent way. As the documents produced are usually of large size, highly structured and regularly updated, their manipulation calls for new systems: document management systems. In fact, a document repository and therefore an underlying database is necessary to support document utilization. An in-depth analysis of requirements allows this repository s main features to be defined. We focus on demonstrating how database technology, and more particularly object-oriented database technology, is helpful to develop such a system. We propose an object-oriented repository data model which allows most of the requirements to be met."

Abstract: "This paper proposes a model of a hypermedia repository based on both object technologies (specification method and Database Management System) and electronic document standards (SGML and HyTime).

"SGML is an ISO standard for document structuring. It guarantees document exchange capabilities, document longevity and document reusability. Object Database Management Systems fit well for complex document storage and access. However, every time a mapping between SGML and an object model is studied, many issues arise and only a part of them are solved. We propose a complete and generic object model of SGML which eliminates all the limits. Moreover, this model should stand for a universal model,i.e., it can be used as a standard API to plug any SGML visualizer or editor on top of an object repository.

"HyTime is also an ISO standard, based on SGML, so that it ensures exchange capabilities, longevity and reusability too. Moreover, HyTime goes beyond the SGML limits concerning the hyperlinking features by offering the semantics to model complex links, such as a link from a document to a very precise location inside another one. We describe how to extend our object model to the hyperlink features of HyTime. We give an overview of the prototype we have implemented to validate our approach."

"Abstract: SGML is an excellent tool or technology for implementing modular, reusable information and documentation - but technology and tools alone are not enough! Unless a new methodology is added, the end result of a typical SGML project may be that the users get instant access to enormous amounts of completely useless data (i.e. information pollution).

"The reason is that the basic units of information that we have been using for centuries - the chapter, the section, and the paragraph, are completely undefined in terms of what function and purpose the information has for the reader! Short and/or highly structured documents may be easy to describe in a meaningful way in a DTD - but if we are looking at typical business policies and procedures manuals they will often be just as structured as a bowl of spaghetti.

"This paper will introduce the Information Mapping(reg.trade mark) method. The method provides a complete hierarchy of information types or classes that can be used to produce modular, reusable information objects - all with a precisely defined purpose and function for the information users."

Abstract: "The Internet provides a medium to combine human and computational entities together forad hoc cooperative transactions. To make this possible, there must be a framework allowing all parties (human or other) to communicate with each other. The current framework makes a fundamental distinction between human agents (who use HTML) and computational agents, which use CORBA or COM. We propose domain-specific languages (DSLs) as a means to allow all kinds of agents to 'speak the same language'. In particular, we adopt some ideas (and syntax) from SGML/XML, especially the strict separation of syntax and semantics, so each agent in a collaboration is capable of applying a behavioral semantics appropriate to its role (buyer, seller, editor). We develop the example of a card game, where the syntax of the language itself implies some of the semantics of the game."

See also the following entry.

Abstract: "We consider the syntax and semantics of the TL (Transformation Language)in the DSSSL (Document Style Semantics and Specification Language) specification (DSSSL96). At present TEs (Transformation Expressions) are less than first-class language objects - they must all reside at the top level, and cannot be manipulated like other DSSSL/Scheme objects. In particular, there is no means of passing information among TEs, so one TE cannot take advantage of information derived by another, such as passing data about parent nodes to direct the transformation of child nodes. We propose extending the DSSSL syntax to allow a DSSSL program to better exploit the tree-like nature of the source grove by providing a semantics for nesting query expressions, allowing information to be passed around while retaining DSSSL's functional nature. The TEs would also come closer to being first-class objects. We suggest these extensions will make DSSSL programs easier to write and probably easier to optimize."

"Abstract: Several research document manipulation systems have combined an interactive direct-manipulation style of use interface with a grammatically-specified structured document representation. These systems have demonstrated that the two concepts can be combined, but have not yet demonstrated that the resulting systems are usable when manipulating large or complexly-structured documents. The paper discusses some of the characteristics of such complicated documents and suggests possible approaches for handling the resulting issues. Primary attention is focussed on structurally complex documents, with additional discussion on the management of large-sized documents and on the handling of specification errors."

Abstract: "Integrated Editor/Formatters merge the document editing and formatting functions into a unified, interactive system. A common type of Integrated Editor/Formatter, the Exact-representation Editor/Formatter (also known as WYSIWYG), presents an interactive representation of the document that is identical to the printed document. Another powerful metaphor applied to documents has been to describe the document as abstract objects -- to describe the document's logical structure, not its physical makeup. The goal of the research reported here is to merge the flexibility found in the abstract object-oriented approach with the naturalness of document manipulation provided by the Exact-representation Editor/Formatters. A tree-based model of documents that allows a variety of document objects as leaves (e.g., text, tables, and mathematical equations) has been defined. I suggest a template-oriented mechanism for manipulating the document and have implemented a prototype that illustrates the mechanism. Further work has concentrated on handling user operations on arbitrary, contiguous portions of the display."

Abstract: "During the period of time since the inception of MIL-PRF-87269 and MIL-PRF-87268, vendors have been developing and delivering 'MIL-PRF-87269 compliant' SGML instances to the DoD (Department of Defense) as line item deliverables under various system acquisition/maintenance contracts. Many of these SGML instances have been developed with a limited understanding of the specific information engineering requirements set forth in MIL-PRF-87269. In the absence of this understanding non-conforming IETM (Interactive Electronic Technical Manual) instances have been or are being accepted by the DoD. This has happened partially because there has been no contractual basis to support rejection. This in turn has led to some IETM providers believing that they are creating a fully conforming product when in fact their offerings may have fallen short of what the specification intended.

"It should be noted that the problems encountered with IETM implementation do not stem from any major deficiency in the MIL-PRF-87269 specification. On the contrary, MIL-PRF-87269 and its accompanying implementation guide clearly express a simple but elegant IETM traversement concept.

"This paper reviews the powerful information modeling and information exchange concepts contained in MIL-PRF-87269, and describes how well they fit with existing object-oriented analysis and design methodologies. The MIL-PRF-87269 generic layer architectural forms are discussed in terms of Class 2,3,4 and 5 ETM, ICW and IETM development and their relationship to procedural traversement data modeling. An object-oriented analysis and design approach is offered for interoperable ETM, ICW and IETM content data modeling beginning with the analysis of the users' existing old physical model, the construction of logicalized content data model object classes, the enhancement of logicalized content model object classes with inherited traversement behavior, and finally the implementation of the traversement rules enhanced content data model for ETM, ICW and IETM development. Configuration management and version control issues are addressed as an essential and embedded part of the object-oriented content data modeling approach. The proper use of parameter entities in the creation of re-usable modular DTDs is explained. Issues are raised and strategies are offered regarding the creation and/or adoption of mnemonics and nomenclature related to the naming and name space management and cataloging of information objects and rich content tagged general entities. Finally, the benefits of the object-oriented content modeling approach are revealed in terms of IETM instance acquisition, development and acceptance quality, and in terms of the interoperability that can be achieved among instances through a consolidated ETM, IETM and ICW information server."

Abstract: "Nortel is a large, international telecommunications company, with 68,000 employees, whose documentation needs are diverse and changing. Implementation of SGML in a cross-corporate fashion introduces the difficulty of meeting separate user requirements while still maintaining a level of control over document structures. Using SGML architectures confronts this by defining the relationships between diverse document types, allowing for more effective interchange of cross-corporate information. This information interchange is further enabled by generic tools that can operate on documents conforming to specific classes. This paper highlights the activities of a team tasked with implementing SGML architectures, and describes some of the technical challenges involved. In particular, we show how implementation of architectures relates to the broader area of object-oriented design. We also describe a generic transformation tool written to facilitate interchange."

Abstract: "In this paper we report the use of SGML for the documentation of highly structured engineering data in the telecommunication area. These structures are built by using a method, called Macro Modeling Technique. Macro Modeling Technique provides means for structuring the information about complex technical domains in a most unambiguous and nonredundant way. Models built by using Macro Modeling Technique are highly modular and can be refined and aggregated without overlap. The models also allow very precise access to engineering information because of their elaborated detailed structures.

It was a challenge to use the SGML language to map structures of the Macro Models onto document structures and support certain operations on a model within a document. For this purpose we have defined an unambiguous mapping from our models to content-oriented DTDs. We have developed a systematic approach to construct specifically tailored DTDs by combining parts of various model-based DTDs.

We have successfully applied this approach to the documentation for large systems in the telecommunication area and we implemented a prototype version of the required operations."

Abstract: "We use SGML to bridge the gap between early specification documents and analysis models in an object-oriented software development process. Introducing content-oriented DTDs for the specification documents it is possible to define a tool-based transformation from the specification documents to an initial object-oriented analysis model. Our methodology OOSDM (Object Oriented Structuring and Description Method) which structures specification documents in a canonical way and our tool OMC (Object Model Creator) which converts those specification papers to an initial object-oriented analysis model are a first step towards a seamless integration of the early specification and analysis phases into the software development and the documentation process."

"We have implemented the conversion tool OMC which converts an input document (OOSDM based SGML document) to an initial object model in the Case Tool Software through Pictures (StP) from Aonix. The user interface is integrated completely into the user interface of StP. OMC uses the OMCT+Booch notation which is supported by StP. OMC runs under UNIX (SUN OS and HP UNIX) and is implemented as an user customization to StP (using a StP specific programming and query language and C++). We have defined a default rule file tailored for the DTD of our specification documents which we use as the input files for OMC. Our customer has started to use OMC for pilot applications."

"Abstract: The Kurdish language presents specific problems for the lexicographer. Being the language of a people without a state, it has attracted less interest than the other languages of the Middle East, and it is only recently that lexicographic studies and bilingual dictionaries of Kurdish have been published. It lacks standardization (division in dialects, and above all, use of three different writing systems). It also presents further problems in the field of computing (encoding). Paradoxically, this complicated situation means the computer may be especially useful for lexicographic work on the Kurdish language."

"This paper deals with Direji Kurdi, a project for the development of a lexicographic software environment specifically geared towards Kurdish. The different phases of the project, the reasons for the technical choices made by the author, its current state of development, the problems encountered and the planned extensions (linking with CD-ROM dictionaries, corpora, compliance with TEI-SGML) are introduced."

Abstract: "During development of our first-generation online documentation conversion and delivery system, we addressed most of the obvious problems and requirements we foresaw. After the system was in place, we discovered other less obvious areas for improvement. We implemented the changes in a second-generation system and are planning additional changes in a third-generation system. This paper addresses the plans and realities of each of these systems."

Abstract: "This paper discusses, from a corporate point of view, the maintenance of an internally developed SGML environment, continual training for the maintenance team, and training and support of users. These are the practical aspects of an SGML system implementation that are quite often overlooked when making implementation decisions. The author recognizes that external SGML consultants normally provide ongoing maintenance and support of systems they design, as well as ensuring that users of the system are properly trained. However, as a user of, and trainer for, an internally developed SGML environment, the author observes that maintenance, support, and training are items that often occur as afterthoughts because of sudden need, rather than checklist items planned for from the beginning as strategic parts of any SGML system implementation."

Abstract: "Lately it seems that everyone is talking about HTML. Some of you SGML `96 attendees may believe that this hot topic has nothing to do with SGML. Some of you may believe it has everything to do with SGML. And the rest of you may not be sure whether it's relevant or not.

Whether you consider HTML as a critical element of your information delivery strategy or not, you are probably reacting to .... thinking about ... being asked to put your SGML content on an intranet. This brings up many challenges: how to track revisions, how to manage relationships and links between objects, how to reuse information effectively and efficiently, and how to retain your investment without transforming to HTML.

Getting the most out of your SGML source means exploiting your investment by using that source as the same source for your intranet delivery needs. There's a big payoff in combining HTML, SGML, document component management and internet technologies to achieve a diversity of document products, increase quality of customer service, and ensure accuracy and timeliness. Imagine automatically assembling pieces of information which exactly matches a customer's need, and delivering the most up-to-date information in the form and format requested. Achieving this is possible today.

To help you achieve this 'jackpot' of capabilities, this presentation will:

• describe the need and business case for intranets
• identify a roadmap for exploiting SGML
• list key capabilities of such a system
• identify key technologies that should be integrated

This presentation, aimed at a managerial audience, will examine the aspects, value and impact of several real-world intranet applications. It will describe the relevant technologies and offer guidance on enabling your current technology investment to drive this new type of information delivery. It will also discuss critical features and functions of such a system. You will leave this presentation with a deep understanding of how to build a complete information delivery strategy."

"Abstract: Over the past ten years, SGML has achieved great popularity. But not without some bad publicity. Comments heard in the past include: "We're glad we did it, but it did take us longer than we thought"; "We had to change our DTD late in the project and that cost us quite a bit"; "The product didn't work the way we had thought it would, so we had to redesign part of the system"; and so on. SGML is a relatively new tool, so it is still highly vulnerable to being implemented in ways that confound rather than assist the user. Because it is so vulnerable, it is important to continuously monitor project activities against business requirements and keep focused on the project's ultimate objectives. The use of SGML can yield great rewards. As business people, we must decide how much we are willing to pay for those rewards."

Abstract: "Literate Programming is a documentation method that attempts to maintain consistency among the various design and program documents of a software system. Unfortunately the majority of the literate programming tools do not have appropriate user interfaces and require the users to learn complicated and cryptic tagging languages. SGML is a metalanguage used to specify markup or tagging languages that can be used to encode the structure of documents. Since SGML is an ISO standard and is being widely used by both industry and government, the number of applications that use SGML as the underlying document representation language is growing rapidly. This paper describes how a markup language defined using SGML can be used as the basic method for structuring literate programming documents and can be made independent of the programming language. Furthermore, with SGML and tools to browse and edit SGML documents, literate programs can benefit from WYSIWYG editing and hypertext capabilities, and can even include pictures and other graphics. In addition, syntax-directed editors that support SGML can hide the markup tags and thus, remove the need to learn a markup language. Text databases that use SGML can also be used to store literate programs. As a result, literate programs can be browsed and queried using complex search expressions, a capability beyond most text editors. For example, the searches can involve combinations of structural and textual information. Because SGML is a popular and emerging standard, we can expect to have more powerful tools to manipulate many different forms of design and program documentation."

"This paper describes the issues involved in the development of a literate programming environment that uses SGML as the storage model."

"Abstract: Standards, if widely accepted, encourage the development of tools and techniques to process objects conforming to that standard. The paper describes a number of experiments using available tools to process text containing Z specifications adhering to the existing Z Interchange Format. The experiments resulted in tools that could be used in specific programming environments where Z was used to describe software systems."

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.

This presentation was the text of a keynote address at SGML '96, and is printed in the Introductory section of the proceedings volume.

From the Conclusion: "I like to think of the history of SGML as - what else - a tree structure. One root - from Rice to GML to my basic SGML invention - joined at the base of the trunk by the other - Tunnicliffe to Scharpf and GenCode. The trunk, of course, is the extraordinary 8-year effort to develop ISO 8879, involving hundreds of people from all over the world. The products and tools that came after are the branches, the many applications the leaves, and they are all still growing.

And in all these 30 years, while the technologies of both computers and publishing have undergone overwhelming and unpredictable changes, the tree continues to bear the fruit that I described in 1971:

The principle of separating document description from application function makes it possible to describe the attributes common to all documents of the same type. . . [The] availability of such 'type descriptions' could add new function to the text processing system. Programs could supply markup for an incomplete document, or interactively prompt a user in the entry of a document by displaying the markup. A generalized markup language then, would permit full information about a document to be preserved, regardless of way the document is used or represented."

Abstract: "This article is a commentary -- over a quarter-century after the fact -- on the first published paper to summit the need for (and hint at the existence of) what is now the Standard Generalized Markup Language. It was presented at the 33rd Annual Meeting of the American Society for Information Science in Philadelphia, October 15, 1970, and published in Volume 7 of theASIS Proceedings. The editors of this Special Issue ofJASIS felt that that meeting was worth remembering here because of its hitherto unpublicized connection with the origin of SGML. In addition, it is also worth remembering because of its closing banquet, which featured an erudite and witty speech by a professor with two doctorates, a piece balalaika orchestra, the entire Philadelphia Mummers band (replete with banjos, saxophones, and feathered headdresses), and a middle-eastern belly dancer who worked on the table tops! I've spoken at some hundred conferences since then and none of them has even come close."

The paper discusses the use of SGML to structure texts in a medical database for full text retrieval. The paper has two themes: (1) an overview of the concept of an online reference work (ORW) as defined by the Online Reference Works in Medicine, a collaborative program between the National Library of Medicine (NLM) and the William H. Welch Medical Library, Johns Hopkins Medical Institutes (JHMI), and (2) an overview of the evolving concepts of full text and object-oriented retrieval from structured texts. The article addresses the concepts and general observations on the implementation of an ORW, the efforts to extend the present model, and a brief description of the object-oriented full text retrieval methodology to be applied.

Abstract: "There are many hypertext authoring tools available for specific outputs. For example, software that enables HTML or Windows Help authoring. These tools provide easy to use solutions for specific outputs, but they lack the benefit of a tailored, structured environment, and of course they do not allow the creation of multiple outputs from raw content stored as SGML -- a requirement we have at Novell.

However, these tools provide distinct advantages to the author that an SGML-based authoring system should strongly consider. To ignore these capabilities is to risk the SGML system being unusable, or incapable of handling large hypertext projects. These advantages center around the management of small information objects we call topics, and the links between them that are inherent in hypertext systems. To combine the power of SGML with the advantages of off-the-shelf authoring tools, Novell has developed a hybrid, named HelpWise. Novell's goal with HelpWise is to leverage the benefits of a structured SGML authoring system, and retain the link management that is crucial while creating hypertext documentation."

Abstract: "Using simple examples concentrating on five characters from an exotic character set, the author shows techniques for describing a document's character set in the SGML Declaration and how different document character sets are treated by the parser. The presentation concludes with examples of how the techniques are used in real life."

In the category of "Free SGML Transformation Tools" are free software packages "for transforming an SGML instance into something else, be that another SGML instance or a file in some other format." Graham discusses "the criteria for selecting an SGML transformation processing tool."

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: "Book publishing is a conservative industry that relies on a tried-and-true process, characterized by a strong division between 'editorial' functions (obtaining and preparing manuscript) and 'production' functions (turning manuscript into printed books), a division commonly known as 'the wall'. SGML has been relegated to the production side in most implementations. While there is much to be gained here, this limited approach also involves a considerable sacrifice of potential benefit. This paper presents a blue-print for maximizing the benefits of SGML in a commercial book-publishing setting by showing how SGML can be leveraged on both sides of the wall, with consideration of practical implications for both process modification and the implementation of technology.

"The proposed approach for taking full advantage of SGML in a publishing setting involves the mark-up of manuscript not at the stage when it is traditionally keyboarded for typesetting, within production, but at the intake stage. Because there is no way to enforce author compliance with an SGML authoring strategy, it must be handled on submission by an 'intake unit' that is under the control of the editorial departments. This association allows those responsible for DTD creation and initial tagging of manuscript to be in direct contact with those whose job it is to dictate the structure of the documents, and who are most familiar with its content.

"Further, this connection makes the editors in charge of decisions regarding repurposing (electronic versions of existing titles on Web or CD-ROM) and reuse (ancillaries, subsequent editions) directly aware of the potential of SGML to help ease the costs of these (often low-profit) publications. If properly implemented, they also avoid the need to learn the more arcane and unfamiliar aspects of SGML; they can rely on their own staff (NOT answerable to the head of production) to supply them with the necessary technical guidance. The 'structured manuscript' allows the automation of repetitive and labor-intensive tasks in the development process, while making sample material readily available for delivery in print or on the Web for early promotion efforts and expert review.

"By the time the manuscript passes to production, many time-consuming production chores (typecoding, identification of ambiguous structural elements, consistency checks) have already been performed. The editorial departments are brought into closer touch with the realities of scheduling (a constant bone of contention between editorial and production arms), while the production department can now create the printed book at a much accelerated rate, again through automated processes enabled by SGML.

"The introduction of the SGML 'intake unit' into what is traditionally a non-technical branch of a publishing company could be a difficult change to implement; through the proper use of conversion and authoring technology for both initial tagging and subsequent development (and with appropriately designed document types), many of these challenges can be overcome. The gains realized in giving the power of SGML to those who can best make use of it will also help to enable the success of this tricky aspect of implementation.

"The antagonism between editorial and production units within a commercial publishing company has many negative effects. The proper implementation of SGML in this setting could actually help to ease these antagonisms, by adjusting the responsibilities and power that accompany the use of this technology. At the same time, such an implementation would allow publishers to realize the full promise of SGML, in terms of reuse, repurposing, and in faster time-to-market, not just in the final phases of book publication, but throughout the publication process."

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: "There are two common, but unfortunate, responses when companies are confronted by a need to do a legacy data conversion to SGML: freezing in fear and doing nothing, or jumping in head-first and creating a disaster. Obviously, there are better ways to react. This presentation discusses how to develop an effective and realistic data conversion strategy. Among the issues considered are whether to do it inhouse or to outsource, selecting a DTD, developing a workable conversion schedule, writing a conversion specification, conversion methodologies, and arriving at a realistic conversion plan."

Abstract: "The XML language is a profile of the full SGML language optimized for use on the Web. XSL -- the Extensible Style Language -- is the name being given to the language designed to be used to specify a stylesheet for an XML document.

"In the original conception of the XML project, its stylesheet language was expected to be a subset of DSSSL. However, the syntax of DSSSL as defined in the 1996 version of the standard -- based on the Scheme programming language -- was seen by many as suboptimal for average use. The current XSL proposal is basically a mapping of a subset of DSSSL into what is mostly a declarative (rather than programming) language.

"The official XSL work being done under the auspices of the World Wide Web Consortium (W3C) is very much in progress. This talk mostly discusses XSL described in the joint proposal made by ArborText, INSO, and Microsoft to the W3C, acknowledged by the W3C in September 1997. Updates on the latest work will be provided at the talk."

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 three 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: "Information is the raw material from which information products are produced. Nowadays, new information products are needed, including CD-ROM, online databases, World Wide Web pages, and electronic browsers, in addition to printed documents, which impacts production processes. The reasons why SGML is ideal for supporting multiple outputs are discussed. Because of the many process changes involved, it is important to cost justify your SGML project. The three keys to a successful cost justification proposal are: 1) understanding your company's goals, 2) understanding your contribution, and 3) understanding your readers. Return on investment and cost/benefit analysis approaches to a cost justification proposal are discussed. Some formulas for associating cost savings with some tangible SGML benefits are presented."

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, theuse 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: "ADAPT is a document processing system that automatically builds full-text databases from document images. The major components of the process are scanning, image segmentation, optical character recognition (OCR), layout object identification, and database building. A retrieval system and user interface completes the functionality. The system features a general document representation that includes the document image and an SGML tagged version. Standards are adhered to where applicable."

"Abstract: The relatively new international HyTime standard (ISO 10744) introduced the notion of architectural forms. With architectural forms, SGML elements can be classified by means of #FIXED attributes as belonging to some class. In HyTime, architectural forms are used as a basis for processing hypermedia documents, but their use is not limited to that.

"The International Committee for Accessible Document Design (ICADD) was formed to help in making printed materials accessible to people with print disabilities (eg. people who are blind, deaf-blind, or otherwise reading impaired). The ambition of ICADD is that documents should be made available for people with print disabilities at the same time as and at no greater cost than they are made available to people who can access the documents in traditional ways (usually by reading them on pages of paper). This ambition presents a significant technological challenge.

"ICADD has identified the SGML standard as an important tool in reaching their ambitious goals, and has designed a DTD that supports production of both "traditional" documents and of documents intended for people with print disabilities (eg. in braille form, or in electronic forms that support speech synthesis).

"ICADD is aware that it is unrealistic to expect document producers and publishers to use the ICADD DTD directly for production and storage. Instead a "document architecture" has been developed that permits relatively easy conversion of SGML documents in practically any DTD to documents that conform to the ICADD DTD for easy production of accessible versions of the documents. The architecture is based on ideas that are quite similar to those of HyTime architectural forms."

"The approach of ICADD is interesting, not least because it illustrates that document portability and exchange in SGML can be achieved by other means than standardizing on a single DTD in the exchange domain. In ICADD, portability is achieved by specifying mappings onto a standardized DTD."

Abstract: "Information Providers add value by enabling access to information. On-line Information Providers add value by adding markup which enables access via a search engine. Improving search precision and recall is directly related to the match between the language used in a search query and the collection of searchable information. Markup that enables construction of the search query using the language of the collection is lexical and semantic not structural. SGML parsers allow us to validate structural markup but cannot be used to determine the quality of lexical and semantic markup.

"Natural language is powerful because the rules regarding lexical and semantic information are flexible and mutable. However, the recognition and marking of lexical and semantic information is more difficult, and will be less robust than the recognition of structural and syntactical information. We, as Information Providers, need to make sure that our markup systems maintain a high level of quality.

"The manufacturing industry uses Statistical Process Control to monitor and maintain the quality of their products. This paper demonstrates how Statistical Process Control can be used within an information manufacturing system to monitor and maintain the quality of the processes adding search enabling markup."

Abstract: A frequently cited problem with the Standard Generalized Markup Language (SGML) is that applications using the standard have been slow in arriving. Part of this delay is because of the instability of the standard and part because of constructs of the language that are functionally redundant and/or add unnecessary complexity to both machine and human processing. This paper is based on our experience implementing an SGML parser using commonly available tools for building programming language translators. It describes the problems we encountered and suggests modifications to SGML to eliminate those problems. The modified language can be implemented using well tested tools and will be more stable and more amenable to both computer and human processing while maintaining all of the fundamental strengths of SGML.

"Abstract: In this paper we outline how the use of design principles had a benificial impact on the modelling of the hierarchy of information, object information, meta-information and shape-information in electronic documents."

Abstract: The author provides a "discussion of practical experiences in using SGML and HyTime for publishing to different media (hardcopy, browser, HTML) using software such as Synex ViewPort and FrameMaker+SGML."

"Abstract: Guidon is OCLC's graphical interface to Electronic Journals Online. The World Wide Web (WWW) is a system that OCLC and many other institutions use to offer services over the Internet. We have extended a prototype version of Guidon so that it can display HyperText Markup Language (HTML) documents and function as a WWW browser. In addition to letting Guidon view Web pages, HTML offers several powerful features that could be integrated into OCLC's electronic journal services, such as a flexible forms capability."

"Abstract: Virginia Tech is one of the universities participating in Elsevier's TULIP project. OCLC is supplying the software to electronically distribute the collection to their campus. For this purpose, we have modified the Guidon electronic journal interface client software to display page images and have written a program to load Elsevier's data into OCLC's Newton text retrieval program. To make working with image databases as natural as possible, we have made a number of enhancements, including "thumbnail" page images and a magnifying option in Guidon."