Abstract: "SGML documents can be large and complex, composed of many parts in various formats. These parts may be entities, subdocuments, or other SGML documents that are linked to as part of the content of an enframing document."

"Such a compound document may consist of an SGML declaration, a DTD (which may be composed of modules stored in separate files), a document entity (where the DOCTYPE declaration appears and in which parsing begins), external entities, other SGML documents, and noncharacter data (such as pictures and sounds). Beyond that, a document may require style sheets, fonts, an SGML Open catalogue, a 'readme' file, a statement of conditions of use, digital signatures, authentication information, and on and on.

"In this paper I'll point out some circumstances under which one might need to package together some or all of the items comprising a full compound document, describe some advantages of and requirements for packaging, briefly mention some existing packaging schemes, and outline my own suggested solution."

"If SGMLlers want to control their own destiny in archival preservation, copyright, and commerce, it would be wise to take up the challenge of packaging specifically for SGML (and XML), or at least come to agreement on what requirements a packaging system must meet. If we don't figure out packaging, someone else may do so in ways we find painful. Our first attempt, MIMESGML, seems to have failed because it was too complex. I hope the simpler solution I've offered has the clarity necessary for success."

Abstract: "This paper examines the aspects of hyperlinking that are relevant to document management systems. Various standard mechanisms for hyperlinking -- XML, HyTime, and HTML -- are reviewed and their relative merits discussed. Ways in which document management systems can facilitate link creation, maintenance, and delivery are presented, along with their effect on integrated authoring and delivery systems."

"Traditionally, the topic of hyperlinking has been primarily discussed in the context of distribution, viewing, and display systems. This paper examines the requirements put on document management systems, and in turn, integrated authoring tools for creation and management of hyperlinks. One of the distinguishing characteristics of hyperlink management in a document management environment versus a display environment is the dynamic nature of the information to which the hyperlinks apply. Fixed linking schemes layered onto static information are no longer sufficient. Changes in information imply the need for linking mechanisms that can adapt to changed resources, ongoing validation that links are still valid, and the need for creation of additional links."

Abstract: "To provide report program developers [with] a single output format, while allowing multiple presentation formats, we are using an SGML language based on HTML tables. The reporting programs generate the SGML documents which are translated into HTML, LaTeX or ASCII depending on the needs of the users."

The project relates to a "myriad of reports" produced for Lucent Technologies': "5ESS-200 is a large telephone switch involving the work of thousands of developers. The ADEPT project tracking system records the work items, completion dates, quality records and other information to assure the project conforms to its processes. [...] Each report program generates a complete SGML document. These are then run through the sgmls parser. The parse tree that results is analyzed by a translation program that converts the SGML tags and their contents to the appropriate statements in the presentation language. [...] We use marked sections to hide the embedded SGML from the parser when the error file is processed. We have extended our definition of reports to include printouts of the forms customers fill out on the screen. The form printing system also generates SGML which passes through the translation system to be printed. We are examining how DSSSL and XML could alter our translation mechanism."

"Our project is different than many other uses of SGML as the SGML documents are transitory and limited in nature. Once the SGML is generated and translated, it is deleted. We believe that using SGML as a report writing language provides several benefits. It is easy to understand and write, it provides independence from the presentation mechanism and results in smaller, easier to understand report code."

Abstract: "Text has a special place in the digital library as the primary medium of human communication. While sometimes a picture may be worth a thousand words, more often, the best way to convey any complex thought is through text. The reason is simple; the richness of concepts, the detail, and the precision of ideas that can be expressed in words are remarkable. This talks looks at the role of text in digital libraries and attempts to place the various methods for managing text in context. A theme of the talk is the trade-off between generality and simplicity. Generality is the great strength of SGML and also its principal weakness. Simple formats are easier for the non-specialist to learn and easier for interoperability in distributed computing, but fail when asked to do too much. The early success of HTML is a fine example of simplicity; more recent troubles show what happens when simplicity is abandoned in a piecemeal fashion. Digital libraries are interested in both ends of the spectrum. At the high end, libraries must support every language and character set in the world, past or present. They must work with mathematics, music, chemical symbols, and special formats from every discipline. However, while accepting high-end formats, such as the encoding used by the Text Encoding Initiative, libraries ask questions about the long term [...] Unicode is emerging as the extended character set of choice, partly because the developers have been steadfast in providing compatibility with other standards, notably ASCII. The introduction of XML is paying close attention to these factors, thus greatly increasing the chance of broad acceptance."

Abstract: "In 1986, the Standard Generalized Markup Language (SGML) became an international standard for the format of text and documents. SGML has withstood the test of time. Its popularity is rapidly increasing among organizations with large amounts of document data to create, manage, and distribute. However, various barriers exist to delivering SGML over the Web. These barriers include the lack of widely supported stylesheets, complex software because of SGML's broad and powerful options, and obstacles to interchange of SGML data because of varying levels of SGML compliance among SGML software products.

"Because mainstream Web browsers lack SGML support, most applications that deliver SGML over the Web convert the SGML to HTML. This down-translation removes much of the intelligence of the original SGML information. That lost intelligence virtually eliminates information flexibility and poses a significant barrier to reuse, interchange, and automation.

"The Extensible Markup Language (XML) is being developed to enable delivery of SGML information over the Web while overcoming the limitations of HTML. The momentum building behind the XML effort means that XML is inevitably destined to become the mainstream technology for powering broadly functional and highly valuable business applications on the Internet, intranets, and extranets."

Abstract: "This presentation aims at giving an understanding of the work with STEP and SGML/XML integration, the reasons for it and current status of work. It begins with a presentation of the STEP standard and its parts, and discusses what the relations between STEP and SGML/XML are, and what inter-operability between the two might provide.

"A few current initiatives or projects will also be covered, with the Hägglunds LOTS project presented in somewhat more detail, being one of the more advanced STEP and SGML projects so far. Finally, a status report of the current standardization efforts within the STEP and SGML/XML communities will be given."

"STEP is an international standard, ISO 10303 'Product Data Representation and Exchange'. The former name was 'Standard for the Exchange of Product Model Data', thereby the acronym STEP. The objective with the series of standards that together are called STEP is to define a common way to describe product model information for the product's complete life-cycle, independently from the software used. [...] Today, efforts are spent to make STEP more open, i.e., to permit STEP to cooperate with other standards. An example of that is the efforts to achieve inter-operability between STEP and SGML."

Abstract: "This presentation examines the benefits of structured data files, compares different file formats (SGML, HTML, PDF, and XML) and their suitability for various deliveries, and discusses criteria for selection of structured authoring tools from the perspective of the user of the tools, the technical writer. The presentation is intended for people new to structured authoring who may have become interested in the topic because of the popularity of the new XML standard, and would benefit from hearing about structured authoring environments in general and how SGML, HTML, PDF, and XML fit into the picture."

Abstract: "SGML information systems usually come into being in the form of small-scale prototype systems supporting a few users and a relatively small set of representative documents. After a successful proof-of-concept phase comes the time of production on a larger scale where the problems encountered are of a totally different nature from those uncovered during the prototyping phase.

"This paper addresses scalability of SGML authoring and dissemination systems. An area highlighted is the need to have a set of detailed production procedures taking into account human as well as automated operations."

"SGML information systems usually come into being in the form of small-scale prototype systems supporting a few users and a relatively small set of representative documents. After a successful proof-of-concept phase comes the time of production on a larger scale where the problems encountered while growing to a full-scale production system are of a totally different nature from those uncovered during the prototyping phase. For example there are the different and sometimes contradictory constraints of the authoring and dissemination systems, which often show up only in high-volume/high-update rate conditions. This paper addresses scalability. Neglecting the more obvious aspects of scalability it highlights some issues, which are not always considered when designing complex document management systems. One aspect highlighted is the need to have a set of detailed production procedures which are adhered to in order to avoid cascading effects of incorrectly entered data, among other potential problems."

Abstract: The purpose of this paper is to present some of the issues involved in taking advantage of the current advances in Web new technologies, in the aim of distribute linguistic resources in an opened client/server environment. The paper is organized as follows: First, we describe our experiment within the first season of the SILFIDE (Serveur Intéractif pour la Langue Française, son Identité, sa Diffusion et son Étude) Server Project currently under development at the CRIN (Centre de Recherche en Informatique de Nancy) a laboratory associated with the CNRS (Centre National de la Recherche Scientifique) and INRIA Lorraine (Institut National de Recherche en Informatique et en Automatique). We developed a first SILFIDE Server prototype implementing the TEI guidelines, the CGI (Common Gateway Interface) and Java technologies. Next, we sketch the new directions within a second season of the SILFIDE Server Project concerning new related topics: (1) managing linguistic resources encoding in XML/TEI, (2) distributing linguistic resources over a SILFIDE network using the possibilities given by new technologies for a Web information server and (3) integrating and standardizing linguistic tools in a distributed environment."

Abstract: "Mathematical Markup Language (MathML), designed by the W3C HTML Math working group, is a XML application for describing mathematical expression structure and content. The goal of MathML is to enable mathematics to be served, received and processed on the Web.

"This paper discusses the particular problems posed by the representation of mathematics on the web and outlines the XML-based solution proposed. This solution supports both presentation and semantic models of mathematics. The paper looks at the relationship between MathML and some existing mathematical representations which have contributed significantly to its development.

"Initially MathML will be processed and rendered by helper applications. An overview of the browser interface and techniques for embedding of MathML in HTML pages will be presented. The requirements on tools for the creation, editing and viewing of MathML are reviewed. An outline of MathML support in applications, under development or planned, will be given."

Abstract: "The editorial process of the budget of the European Union provides a good example of a production environment that is entirely SGML-based, and meets severe constraints in terms of production time, quality, and costs."

"As such, it illustrates the fact that SGML realizes its full potential when used as a means of manipulating structured documents. It also highlights certain aspects of SGML, usually considered as advanced, making their significance apparent through a concrete example of their use."

"[Conclusion:] We have described a complex SGML-based client-server system that is used for the creation and maintenance of the European Union's budget, a huge 11-language document, revised three times a year. We have shown that an SGML system can be much more than just having SGML instances as input and output. We have described and illustrated how SGML is used in every aspect of the system, ranging from the server modules, over SGML based processing modules to an SGML-formatted messaging scheme between clients and server. Finally, we have outlined how at the very heart of the system presented here is SIT, the SGML Technologies Group's fully-featured SGML parser and integrated application language."

Abstract: "This paper studies, from an historical perspective, the relationship between SGML and data modeling concerns. SGML did not the invent the concept of structural document models, or 'schemata'. Nevertheless, through the notion of DTDs, it made this powerful concept available and understandable to a large number of people with little or no data modeling experience.

"With the evolutionary trend towards 'content oriented' DTDs, the emergence of well-described methodologies to design them and the appearance of specialized 'case' tools to manipulate them, the potential of SGML as a data modeling methodology became clear, and some SGML enthusiasts suggested to use it as a general purpose tool.

"However, because an SGML DTD intimately mixes the notion of a 'grammar' and that of a 'schema', these two concepts remained partly confused, at least in the 'orthodox' SGML approach. This original characteristic caused some misunderstandings and raised many suspicions from the 'traditional' data modeling world. This largely precluded, so far, the use of SGML as a general data modeling tool outside the restricted arena of structured documents.

"By introducing a simplified syntax with a fixed grammar, XML isolated the role of DTDs as 'pure schemata', and also made them unnecessary for pure recognition of the 'de facto' document structure.

Finally, recent proposals such as MCF and XML-data suggest to use the XML syntax itself to encode document schemata, therefore making 'traditional' DTDs obsolete. At the same time, they propose several extensions to the SGML data modeling semantics, by incorporating object-oriented concepts. Will such an evolution allow XML to become the official, well-accepted and ubiquitous way to exchange structured data and associated models, and bring SGML power much beyond its original application niche?"

[Extract from the section "The Dual Nature of DTDs"]: "With the benefit of hindsight, after ten years of practice, the design of SGML appears as an unlikely and unique mixture of many brilliant ideas and a few mistakes, and strikes [one] by its total lack of references to data modeling or language design theories which had already emerged in computer science at the time it was designed. A major point of originality is the central SGML DTD concept itself: a DTD is both a generative grammar for the markup language which will be used to tag corresponding instances, and a schema which characterizes a document class: it assigns names to things and defines rules stating what structural patterns shall or shall not be not possible/required in an SGML document (modeled as a tree of typed nodes with attributes) which belongs to the class. In the same set of statements, one is instructed that 'the end tag for AUTHOR can be omitted' and that 'the document must have a title and a single one', although these two pieces of information admittedly belong to totally different areas of concern. This dual nature of DTD should not necessarily lead to confusing the two notions. Unfortunately, this is largely what happened in the SGML community..."

Abstract: "The Canadian Department of National Defence requires suppliers to produce technical manuals for equipment supplied to project offices within the department. DND now requires suppliers to support the Standard Generalized Markup Language (SGML).

"The DND CALS Assembly Information Model is the content-oriented SGML structure mandated to markup information about equipment. The technical manuals are typically presentation-oriented, based on a book paradigm.

"A preliminary publishing system architecture along with Document Type Definitions (DTDs) to support this architecture were designed to address the transformation requirements necessary to produce the technical manuals from the information model as well as future requirements that may arise for electronic-based information products. This paper describes the evolution of this architecture, based on feedback from multiple field trials which validated various segments of this preliminary architecture.

"Version 2.0 of the DND CALS DTD with extensive documentation, applications and scenarios based on this architecture is now available from the DND CALS Office."

Abstract: "This presentation discusses the ways in which SGML is being used to build prototypes of scholarly editions for distribution on the Internet. Based on the Text Encoding Initiative (TEI), the sophisticated markup offers greater intellectual access as well as sophisticated frameworks on which to build editions. Chesnutt will review the work of the consortium and its plans to create an American Documentary Heritage Database encompassing documentary editions drawn from all fields of the arts and sciences."

Abstract: "Some of the information processed through SGML systems should never be stored in a document instance. In particular, tabular data may already be maintained and stored in a relational database. This paper discusses the alternatives and outlines a strategy for integrating relational data in an SGML instance, and for automating the process of updating and delivering the information content."

[Conclusion:] "We have seen that not all information contained in documents should be stored there. Graphic elements provide one obvious example of this principle, which we can easily extend to tabular data. Using relational database technology and SQL, the data can be managed appropriately; while SGML provides the mechanism for delivery. This paper has offered a simple strategy for integrating these systems, through the storage of SQL queries in the SGML instance and scripts to intelligently process those queries."

Abstract: "Standard Generalized Markup Language (SGML) allows the creation of content to be separated from the formatting or delivery of information. The ability to deliver data authored once in several different formats is one of the major benefits organizations site when stating their reasons for moving to SGML. However, few organizations have the foresight to understand how SGML will be spread across their organization. In this paper, I will discuss the two basic adoption models of SGML in corporations and how these two different models can sometimes create the same problem and may have the same solution.

"SGML has always allowed you to define a group of elements and reuse those elements in multiple DTDs. Many companies that have to manage a group of DTDs that are reused in multiple other DTDs use this modularity of SGML to their advantage. However, not until recently was there a way to enforce and express formally these reusable components. The use of the meta-DTD was first defined by ISO/IEC 10744 (HyTime) and defines the structure and semantics of a class of documents which conform to an 'SGML architecture'.

"Declaring an architecture is easy. If you've ever written a DTD, you already know almost everything you need to know how to do it. The SGML Extended facilities describes a new markup declaration type called an AFDR (Architectural Form Definition Requirements). Documents can conform to one or more enabling architectures such as HyTime and SMDL. The declaration consists of two parts, a list of architectures to which the document conforms and a declaration for each architecture in the list. The list of architectures used is declared using a processing instruction that starts with the keyword ArcBase and is followed by a list of architectures used in the document. This processing instruction should precede any architecture declarations for base architectures. You can have more than one ArcBase processing instruction. Architectures are 'connected' to elements via their attribute declaration. If an element in a user DTD is derived from a corporate architecture, that fact is recorded in the user DTD. If two different user DTDs use the same architecture, information can be seamlessly interchanged between the two user DTDs by simply 'deriving' the user DTD content model back to its architectural form. This allows the best of both worlds in SGML. Users can have application specific DTDs that meet their particular needs while the corporation can have a standard base from which to create processing systems, training materials, and develop new authoring DTDs."

Abstract: MCG has developed an SGML database system with a view to information reuse. The system integrates workflow, an SGML editor, and an SGML database. The system implements extensive metadata about the SGML objects.

"MCG worked from a few concepts to build a complete environment: 1) There is only a certain amount of useful information concerning a given product; 2) The information can be divided into distinct, identifiable components; 3) The information components can be implemented in such a way that they can be gathered into myriad deliverable collections and in various media; 4) Handling information in this manner saves time and effort over the long run by reducing noncreative work.

"This paper describes: 1) the methods we used to analyze our information requirements, 2) translating those requirements into a DTD that supports modular information structures, 3) defining metadata requirements so a database supports the information structures, 4) and the application functions and features we integrated into the environment."

Abstract: "The ATA has been developing interchange DTDs since 1989 and several maintenance, training, and operations documents are currently being delivered in SGML. With the introduction of XML ( eXtensible Markup Language ) as a draft standard for web applications of SGML, the ATA must review their interchange DTDs to determine the impact of supporting web delivery of XML documents in the future. This paper will explore the impact of XML on the ATA interchange model. The conference presentation will demonstrate, using a representative ATA document, the steps required to move from SGML to XML for a typical industry interchange and will demonstrate how a data model might be used to facilitate this interchange."

Abstract: "This paper describes the use of XML in a Lotus Notes publishing project at the Bureau of National Affairs, Inc. (BNA). The paper reviews the current batch publishing environment available with the Lotus Notes Newsstand product and describes the new process that utilizes XML. It also covers the advantages of using a well-formed XML over RTF, data conversion issues, and the development of an XML processor to import XML into Lotus Notes."

Abstract: "The SGML community has had increasing interest in the capability of assembling document displays from multiple referenced parts. Elements in such documents reference other elements or objects that are retrieved on the fly and transparently displayed much as if their content had actually occurred inline. This is commonly called 'dynamic document assembly' or 'boilerplating' and traces back to the older notion of transclusion (dynamic data inclusion). Transclusion has previously been very theoretical, but is becoming less so daily, especially with the coming use of XML. This presentation looks at reasons for transclusion, possible problems, and some proposed solutions."

"XML rules out most of the constructs that make it hard to implement transclusion with SGML, such as asynchronous entities and document portions that can parse differently depending on where they are referenced. This makes truly dynamic transclusion processors more feasible. Also, XLL provides a powerful convention for referring to subtrees of documents on the fly (based on TEI extended pointer notation), making it very easy to transclude very specific document portions as required for quotation. XLL also provides transclusion semantics as a specific property that can be set for individual links: a link can be declared to require on-the-fly retrieval and display, or inline display on demand, or new-window display on demand, and so on, thus allowing all the needed combinations of behavior."

Abstract: "Architectural forms were developed in conjunction with HyTime, but you can take advantage of them without using HyTime. As a bonus, once you get used to them, HyTime will be much easier to understand. This article describes the creation of a simple DTD based on architectural forms defined in another DTD. It also shows how to use James Clark's sgmlnorm program to process a document conforming to the new DTD, and then describes the possibilities opened up by the use of architectural forms."

"Architectural forms give you a way to base a DTD's element types on element types defined in another DTD. You can define an element type of the new DTD as being the equivalent of one in the existing DTD and then give the new one a different element type name, additional attributes, and different names for existing attributes. A processing application that supports architectural forms can then treat elements conforming to the new DTD's declarations as if they conformed to the corresponding declarations in the original DTD (also known as the 'baseDTD' or 'base architecture'). All this can be done using a base DTD designed by someone who has never heard of architectural forms. If the base DTD was designed by someone who knew that it would be used as a base architecture, the new DTD's designer has even more flexibility, potentially being able to revise the content models of the base DTD's element types."

Abstract: "This paper presents the result of an investigation designed to show the possibility of producing an IETM (Interactive Electronic Technical Manual) by means of World Wide Web technology. For the needs of our investigation, we used an SGML document base, relating to the maintenance of an aircraft. This base, enhanced with techniques set forth in this paper, allowed us to build a WEB browser prototype meeting IETM class 3 and higher requirements. An important point shown by our work is that the semantic richness of an SGML base can be kept and used even when using HTML (HyperText Markup Language) as a browsing format."

Abstract: "The decision to go with SGML is only the first step toward complete SGML integration. There are issues and twists that make every implementation of SGML unique. This particular project involved creating and deploying a system that handled multiple configurations of documents customized for specific clients. This presentation discusses the steps necessary to implement fully an SGML authoring environment and SGML repository given a limited budget and challenging set of requirements."

"FSI International is a capital equipment manufacturer for the semiconductor manufacturing industry. The corporation has over $300M annual sales with corporate offices in [5 locations]. The Technical Communications Department is a technical writing and information coordination department for the design and sustaining engineering department of the Chemical Management Division. Our department produces technical operations and maintenance manuals for our product line as well as other technical, safety, and customer service communications. There are three direct employees, one contract employee, and two dotted-line direct employees in Hollister, California. With an annual budget of $350K for fiscal 1997, the group created 5,000 new or revised pages and 176CD ROMs. We are forecasting 5-6,000 pages and 538 CD ROMs for fiscal 1998."

Abstract: "This case study chronicles the successes and shortcomings of an ongoing SGML implementation for electronic publishing from a legacy data conversion at a technical society. A commitment to SGML is most often couched in dollar terms; most implementors are aware of the tremendous costs in data conversion, DTD development, and editorial tools. However, implementors at this technical society realized that an additional level of commitment was needed to successfully publish using SGML. This commitment escaped notice perhaps because implementation planning most often focuses on easily measurable costs. For this quintessential 'content provider,' the need for technically skilled people was one of the unforeseen aspects of its embrace of SGML."

Abstract: "The Electronic Library Project was lunched to study the limits of new technologies like ODBMS (Object Database Management System), SGML (Standard Generalized Markup Language) / HyTime (Hypermedia/Time-based Structuring Language) structuring and a Web access interface. The result is better than any estimation we could have made. Interactive XML (EXtensible Markup Language) generation is feasible. The submitted talk is as much oriented towards a concrete demonstration as towards the conceptual explanation of the prototype."

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: "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: "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: "The SGML Extended Facilities, part of ISO/IEC 10744:1997 (HyTime Second Edition) add significant functionality to SGML." Thus "HyTime Two" represents two standards in one document: 1) SGML Extended Facilities and 2) Enhanced HyTime architecture, where "SGML Extended Facilities will become part of ISO 8879: SGML." The presentation by Goldfarb covers: SGML Extended Facilities Overview, Architectural Form Definition Requirements (AFDR), Key AFDR Concepts, Architecture Benefits, Property Set Definition Requirements (PSDR), Graph Representation Of property ValuEs (GROVE), General Architecture, Formal System Identifier Definition Requirements (FSIDR), Lexical Type Definition Requirements (LTDR), HyTime Architecture Enhancements, Foundation for Future of SGML and XML, For Further Information ... (see the HyTime User's Group Web Site).

See also the ISO 8879 Review Index Page maintained by Charles Goldfarb, where a summary of HyTime Two and SGML Extended Facilities is available online, and in outline format substantially represents the content of the published paper; [local archive copy]. In this connection, see also the online paper "What You Need to Know About the New HyTime,", by Steven R. Newcomb, of TechnoTeacher Inc..

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."