UKERNA JEDI Project - Style Sheet analysis report UKERNA JEDI Project Deliverable 3 Style Sheet analysis report in the context of the DMU-JEDI project Version: 1.0 Date: March 1996 Authors: A Gartland, D Houghton UKERNA Atlas Centre Chilton, Didcot, Oxfordshire OX11 0QS This document, or parts of it as appropriate may be freely copied and incorporated unaltered into another document subject to the source being appropriately acknowledged and the copyright preserved. Trademarks: `JANET','SuperJANET' and 'UKERNA' are registered trademarks of the Higher Education Funding Councils for England, Scotland and Wales. Disclaimer: The JNT Association cannot accept any liability for loss or damage resulting from the use of the material contained herin. The information is believed to be correct but no liability can be accepted for any inaccuracies. Availability: Further copied of this document may be obtained from the JANET Liaison Desk, UKERNA, Atlas Centre, Chilton, Didcot, Oxfordshire, OX11 0QS Copyright © The JNT Association, 1996 Contents * The Joint Electronic Document Interchange Project (JEDI) o Introduction o Background o The project and its aims o Final Results * JEDI Project Status o Work to Date o Future Strategy + DMU Activities + UCL Activities * Introduction * The Document Type Definitions o General specification o The TEI DTD o The TEI Lite DTD o The Rainbow DTD o HTML 3.0 o SEMA Group's WRITE-IT * Style Sheets o Panorama + Attaching Style Sheets o Cascading Style Sheets + Why style sheets for HTML? + Methology + CCS support o DSSSL Lite o Others * Panorama the product o Panorama PRO o The Free Viewer * Arena the product * Conclusions * Glossary and expansions * About this document ... Executive Summary This report provides an introduction into the use of style sheets for use with SGML documents. The report concentrates on the practical application of style sheets that are in common use and studies in detail the style sheet mechanisms that are used by Panorama and Arena HTML 3.0. The report defines the SGML DTDs to be used in the study. These are :- * The Text Encoding Initiative * Electronic Book Technologies (Rainbow) * Internet Engineering Task Force (HTML 3) The products to be employed to provide SGML viewing have been identified as :- * Panorama from SoftQuad * Arena from WWW Organisation The report introduces these products and highlights the key features of style sheets that are used with these packages. The report also mentions the Document Style Semantics and Specification Language (DSSSL) standard as being the desired target for style sheet standards. The Joint Electronic Document Interchange Project (JEDI) Introduction There is increasing concern in the research community of the need to standardise on formats for electronic document interchange. There are a growing number of word processing formats that complicate an already complex array of proprietary and de facto multi-media standards. The JEDI project proposes to identify and investigate the leading word processing formats and conversion tools with an aim of providing a solution to multi-format and multi-platform document interchangeability. The aim is not only to study possible packages, but also to demonstrate such interchangeability both in electronic mail and database access environments. We are providing a common introductory section to each deliverable. The introductory section will summarise the background and aims of the project, its progress to date, and plans for future work. The last two will be updated with each deliverable. The bibliography and glossary will be cumulative; hence they may refer to references not in that deliverable and will be out of order. Background As modern publishing, editing and authoring has become influenced by the advances in information technology there is a growing realisation that there is a need for standardisation for electronic document interchange. The word processing tools have become many and varied. The manufacturers of such products apply whatever principles they see fit in order to make their product the market leader and henceforth the dominant standard. As a result, it is very difficult to get real industry impetus behind such common standards. There have been many attempts to introduce such standards in electronic text processing and information interchange; three examples are the Office Document Architecture (ODA; ISO 8613) activities [1], those towards a Standard Generalised Mark- up Language (SGML) [2], and the HyperText Mark-up Language (HTML) [3], used in the World Wide Web (WWW) [3]. The dominant providers of word processors (e.g. MicroSoft WORD [4] and Novell WordPerfect [5]), have often provided tools to allow the import of others' standards, but have done little to promote easy interoperability of their documents with those of others. Other formats in common use are LaTeX [6] and Rich Text Format (RTF) [7]. There are yet others, but they are not being considered in this project. One aspect of compound document interchange is the format of the document; another is the mechanism for interchange and its relationship to the format. In the context of document interchange there are two particularly popular methods of interchange - electronic mail and database access. For the first, we will consider the problems raised by integrating the formats above with the Multipurpose Internet Mail Extension (MIME) [8]. Electronic document delivery from a database involves an author generating documents in a proprietary format and providing the electronic form to organisations running a database service. These will then provide the documents to the users by storing them in a database in the original format or in a popular used format by the community. The customer for these documents will require them in one of two ways. Either they will be requested in their original format; then they will need the tools of the originator of the documents for reading and browsing. Alternatively, they will wish to search against a collection of documents, using some kind of query mechanism, and then browse or read the articles that were found. It should be possible also that a reader browse the document in his favourite format using the tools available in-house. An on-line database of Electronic Documents offers many advantages over the conventional paper-based Documents; many of these advantages fall into the areas of search and access. Electronic searching texts for information is much easier than manual searching. The Word Wide Web (WWW) [3] is the largest information service on the Internet. WWW is a client-server system with both clients and servers throughout the world. A WWW server is a program running on a computer that listens on a TCP port for incoming connections from WWW clients. It expects a connecting client to speak in a protocol called Hypertext Transfer Protocol (HTTP) [3]. The documents in the WWW are written in HTML (Hypertext Mark-up Language) format, and delivered from WWW servers to the Clients in this form. The technology in the WWW is evolving incredibly rapidly; many more proprietary format to HTML converters are available already, and many more are coming. Hence the importance of WWW access to documents.. It is also essential to be able to search a database, and then retrieve documents found. Here there is an International Search and Retrieval Standard (Z39.50) [9], and a particular widely used implementation, the Wide Area Information Servers (WAIS) [10]. These will be used in the project. The project and its aims The Joint Electronic Document Interchange (JEDI) project emanates from the call for proposals by UKERNA in September 1994 for Electronic Document Interchange projects. JEDI is studying the popular formats for word processing that exist in both academic and commercial environments. The project aims to identify format conversion methods for popular de facto standards and their relationship with internationally recognised standards such SGML and ODA. The work on SGML converters is being performed at De Montfort University (DMU), while the work on ODA, WWW, electronic mail, and database access is being performed at University College London (UCL). This explains the Joint part in the project title's acronym. The general aims of the project are as follows :- * Analyse the current international and industry standards used for electronic document creation; * Analyse the current tools and methods available for text processing and electronic document interchange; * Study the use of SGML, ODA and HTML as means for Electronic Document interchange * Evaluate the interoperability of some of the implementations available with such converters - including HTML converters from SGML, ODA and RTF, and the LaTeX -> SGML converters; * Design and implement a multi-mode converter, which will convert documents in recognised formats to SGML * Evaluate the UCL SGML-ODA converters * Investigate the transfer of such documents by the MIME e-mail technique. * Investigate the storage and retrieval of compound documents in a searchable form by the use of WAIS. * Set up of a user-friendly interface for editing documents from any format to HTML form and storing it on a database in that format. The DMU work consists of identifying known format conversion techniques and establishing methods by which popular word processing formats can be converted to SGML and related style sheet formats for presentation. It was hoped to utilise the Document Style Semantics Specification Language (DSSSL) Lite standard [11], but delays in its release and its limited support by computer software manufacturers have prevented this. In order to demonstrate the concepts of word-processing conversion to SGML the project has chosen the style sheet language of Panorama from SoftQuad [12]. The UCL work consists of three basic activities: * Investigating the current status and suitability of ODA, HTML, and WWW implementations - and converters between them; * Investigating the suitability of MIME for interchange, and WAIS for storage and retrieval, of such multi-mode documents; * Developing a testbed system which will allow documents prepared in one format to transferred, stored and retrieved in another. This system uses the mail system MH [13] with MIME support. UCL will implement a system which acts as an automated testing and storage tool for different format documents. The system automatically processes SMTP and MIME messages with specific headers, and acts on information in the header. It can STORE, RETRIEVE and RETURN original or converted documents. Any documents which are added to the Automatic Mail System (AMS) database will also be indexed and stored in WWW for further search and retrieval by a WWW Client using tools from the WAIS software. For the automatic conversion UCL will modify UCL SGML>ODA converters to work with the DTD produced by DMU, UCL will install different converters on the users' request. Final Results By the end of the project (Mid 1996), the project partners are expected to demonstrate the following: * Tools for creating SGML, ODA and HTML documents; * Interoperability of documents prepared with either SGML and ODA tools,and re-process by the other; * Conversion of documents in standard formats to HTML ones; * Provision of a complete package for WWW services for a typical conference proceedings; * Allowance of search of several databases by a search engine with automated document retrieval; * Demonstration of the tools for creating and converting ODA, HTML and SGML documents. JEDI Project Status Work to Date There have been five Deliverables of the project up to now. In [14] DMU considered the numerous document converters that are available within the public domain. The study concentrated on the conversion of the following popular formats :- LaTeX, RTF - Rich Text Format, SGML/HTML, MicroSoft Word, Novell WordPerfect, PDF - Portable Document Format [15], ODA - Open Document Architecture. In [16] there is a brief description of the packages available along with information on obtaining and setting up each package. The report also describes a set of important parsers, document viewers and related tools for document delivery, as well as the WWW document servers. In its first Deliverable [17], UCL reported on the interoperability of two ODA converters and discusses the advantages and drawbacks of these converters. The report also investigates the problems in converting from the SGML to the ODA format. It also looked at different Public Domain versions of converters which are available for converting SGML, ODA, and RTF to HTML. Finally, the report discusses the commercial package of WAIS and WAISgate for creating a searchable document database which can be retrieved using WWW clients. In its second Deliverable [18], UCL evaluated the interoperability of RTF and ODA. There exists an ODA tool for viewing ODA documents on the WWW [3]. Storing documents and retrieving the search result would be an advantage to the project. UCL will test the public and commercial versions of such tools. UCL have studied both storage and retrieval systems and several WWW gateways for retrieving documents from the database; one of these, WAISGATE [10] has been set up. For document transfer, UCL have set up a Mail system with MIME body parts of different formats viz. SGML, ODA, HTML, RTF and LaTeX. Document retrieval via mail messages is also useful; in [18], we also specified an Automatic Mail System for the originator of the document to store the proprietary format in the database or to request a conversion procedure. DMU-JEDI D2 [27] looked at document format analysis for the popular word processing packages and identified the SGML DTDs that are to be used in further project work. Future Strategy All parties realise that the formats, tools and developments in EDI are changing rapidly due to the technologies used within the WWW, the Internet and commerce. The activities in the project are concentrating on tools usable in these environments. Any reference to the past work is quickly overtaken by events. For this reason, the most recent information on the project is kept in the WWW itself in [19]. DMU Activities SGML [2] is a general mark-up language; its layout semantics are defined in SGML Document Type Definitions (DTDs), and its presentation properties in Style Sheets, With these general ideas in mind, DMU will continue the investigation into existing document formats in order to try and provide a method for generating SGML DTDs for a set of common document types. The final aim is to have a set of DTDs and Style Sheets for all occasions. The project will identify methods for users to reach this goal. To this aim, the work done by groups such as the Text Encoding Initiative and Electronic Book Technologies [20] will be of immense value. It is also encouraging to note that Novell WordPerfect have recently brought out WordPerfect 6.1, SGML Edition. First indications are that this product is very good. MicroSoft have not yet brought out an SGML version for Word although one has been promised. Such converters do exist from other suppliers, but they are normally imperfectly integrated into the editors. DMU will concentrate on studying how SGML documents can be generated easily from within popular text processing environments. The project will study the following DTDs :- HTML 3.0 [21], Rainbow 2.5 [22], TEI Lite [23]. Using these DTDs, suitable style sheets will be developed for use with SoftQuad's Panorama PRO [12]. A style sheet converter will also be developed to allow migration to the DSSSL standard [11]. DMU will investigate the suitability of the above DTDs for electronic document interchange. UCL Activities UCL will install and test an ODA viewer tool. UCL will also evaluate the interoperability of other converters available in the market. As the result of the DMU investigation on creating SGML documents, UCL will modify the UCL SGML-ODA documents to work with different SGML DTDs. UCL will finalise the work with implementing an Automatic Mail System (AMS) which acts as an automated testing and storage tool for different format documents. The system automatically processes SMTP and MIME messages with specific headers, and acts on information in the header. It can STORE, RETRIEVE and RETURN original or converted documents. Any documents which are added to the AMS database will also be indexed and stored in the WWW server for further search and retrieval by WWW Clients. Many converters will be used in the AMS system, e.g UCL modified SGML->ODA, RTF->HTML. LaTeX->HTML, and others as they become available. UCL will work on an extended AMS specification to have a complete automated system for storage, conversion, retrieval and indexed databases. In [15] DMU identified what documents formats are being used by the information providers and what documents tools are currently available for the conversion from one format to another format e.g SGML->ODA, RTF->HTML, LaTeX->HTML, RTF->LaTeX and Text-> HTML. Documents which are stored in the database will be automatically converted into HTML and stored in the WWW server for retrieval by WWW Client. Using the Automatic mail system documents attached to the originators request will be added to the index system to create a database. Project status and work to date can be found in [19]. Introduction This document discusses the use of style sheet languages with reference to the JEDI project. The style sheet system to be used within the scope of this project will provide the mechanism by which documents written using Standard Generalised Markup Language, SGML (ISO 8879) [2] may be presented. The JEDI project initially intended to utilise the ISO 10179 standard Document Style Semantics and Specification Language (DSSSL) [11] but support for this standard has been slow to materialise. Instead, the project will concentrate on the Panorama style sheet language which is a popular, widely available alternative. The Document Type Definitions General specification The DTDs to be used in this study were discussed in DMU JEDI Deliverable D2 [27] and included :- * The Text Encoding Initiative * Electronic Book Technologies (Rainbow) * Internet Engineering Task Force (HTML 3) * SEMA Group's WRITE-IT The TEI DTD The DTD from the Text Encoding Initiative is available from http://info.ox.ac.uk:80/~archive/teij31/index.htm#toc The TEI DTD is a comprehensive guideline for document markup that is sponsored and funded by numerous bodies that include the Directorate General XIII of the Commission of the European Communities. Further information may be obtained from http://www.uic.edu/orgs/tei/#Description The TEI Lite DTD Another DTD from the Text Encoding Initiative is available from http://info.ox.ac.uk:80/~archive/teilite The TEI Lite DTD is an abbreviated version of the TEI DTD. Further information may be obtained from http://info.ox.ac.uk:80/~archive/teilite/teiu5.html#ID1 The Rainbow DTD The Rainbow DTD has been written by Electronic Book Technologies (EBT) and is available from :- ftp://ftp.ebt.com The Rainbow DTD is an attempt to solve the problem of conversion from popular word processing package formats, such as RTF, to SGML. EBT provide a software package known as Rainbow Maker that is designed to perform this conversion and is available from the above address. HTML 3.0 The HTML 3.0 DTD may be obtained from http://www.w3.org/hypertext/WWW/MarkUp/html3/CoverPage.html The HTML 3.0 DTD is an attempt by the Internet Engineering Task Force to provide a standard HTML for use on the World Wide Web. SEMA Group's WRITE-IT The WRITE-IT DTD was used in DMU JEDI Deliverable D2 to produce a simple example of how to markup a letter. It is available from numerous sites. The European mirror site is ftp://rs104.hrz.th-darmstadt.de/pub/text/sgml/DTDwrite-it.dtds.tar.Z Style Sheets The concept of style sheets is a simple one that is often misunderstood by users. This misconception is due to the term "Style Sheet" being used by different manufacturers to mean different things. The JEDI project uses the term Style Sheet to mean that defined in (ISO 10179.2) DSSSL, i.e. a set of attributes associated with a DTD that defines presentation markup for elements and entities of that DTD. That is to say, potentially, for each element and entity in the DTD there is a set of information that defines such aspects as font, colour, emphasis, size, position etc. The presentation markup is clearly related to the ability of the viewer/browser to display the requested "style". If the user requests a font family that the viewer does not support, then it is bad luck. However, all is not lost. The style sheet information associated with the DTD is independent of the browser and so the information is retained as the publisher and author would wish. In this section we shall discuss style sheet languages and methods and provide examples of their use with particular emphasis on usefulness for Electronic Document Interchange. Panorama Panorama style sheets provide publishers with control over the presentation of SGML documents. Style sheets provide control over display attributes such as font, size, weight, colour, indents, spacing and automatic numbering. Text can be made larger so that users can see the text from the same terminal, or add colour to make important text stand out. * Add colour to text and graphics to highlight important information. * Adjust font type according to the font availability on the client machine. * Change margins and adjust the text size to suit the needs of different users. * Add more white space to documents to increase readability and improve the overall look of the document. Attaching Style Sheets The mechanism used to attach style sheets to a DTD involves several steps. Firstly, a style sheet file is created using any editor. The file extension is SSH and it must contain information relating to the required DTD. For example :- The text that refers to MY-OWN.DTD is the important bit. Secondly, the file must contain information about those DTD Elements that are to be 'presented'. For example The tag in this example is TITLE and it will be centre justified with a font size of 14pt that will be bold and Navy blue in colour. The break information means that a new line is created before and after the text and the Z-Ruler indicates that a horizontal line will follow the text. The next step in the set up is to place the style sheet file in a place that Panorama can get it. The style sheet and DTD may reside locally or on a remote server. If locally, The DTD must be placed in the CATALOG directory and the style sheet in the ENTITYRC. If remotely on the server, the style sheet and DTD must be in the directory with the data. For a more detailed example of Panorama style sheets see Appendix C. Cascading Style Sheets Cascading Style Sheet (CSS) terminology is based around that of the desk top publishing industry. Work in producing Cascading Style Sheets drafts is currently being carried out by Håkon W Lei and Bert Bos of the W3 consortium. Cascading style sheets are the favoured style sheet coding mechanism to be used with future WWW browsers. Style sheets could be included into HTML documents in the following ways. title</TITLE$> <LINK REL=STYLESHEET TYPE="text/css" HREF="http://style.com/cool"> <STYLE TYPE="text/css"> @import "http://style.com/basic" H1 { color: red } </STYLE> </HEAD> <BODY> <H1>Headline is red</H1> <P STYLE="color: blue">While the paragraph is blue. </BODY> </HTML> * The <LINK> tag in the documents `head' could be used to link the HTML page to an external style sheet. <LINK REL=STYLESHEET TYPE="text/css" HREF="http://style.com/cool"> * The <STYLE> tag inside the HTML documents `head' which would store style sheet information in the document itself. * An imported style sheet using the CSS style sheet notation, included between <STYLE> tags. * A STYLE attrubutes on each of the tags itself. <P STYLE="color: blue"> Under normal circumstances, only one of the above methods of including style sheets into an HTML documents would be used, with the exception of <STYLE> where this can be used to modify the appearance of a style introduced by another style sheet via a different method. Why style sheets for HTML? Netscapism HTML is a content oriented markup language, i.e. the author writes the document based upon sectioning tags like paragraphs, headings and so forth and it is upto the WWW browser to render the document appropriately. The document should be rendended in a presentable manner whatever browser it is displayed upon. There are two browsers, namely Netscape Communitcation's Netscape and and Microsoft's Internet Explorer, that a growing number of members on of the Internet community believe to be abusing the spirt of HTML. Netscape supports HTML 2.0 and a limited subset of the proposed HTML 3.0 but have also included 'extensions' to HTML 2.0 and HTML3.0. A lot of extenstions are based around presentation. For example, the ``BGCOLOR'' attribute to the <BODY> tag to change the background colour of the surface that the text is renedered on (The paper colour) and the <BLINK> take to make text flash. In essence, Netscape are removing the ``Browser Independencey'' of HTML, making Netscape the only brower that will ``Correctly'' view most HTML documents. There are a growing number of pages on the web that have the text ``These pages are Netscape Enhanced and are best viewed with Netscape..." followed by a button for the users to press to download Netscape. It seems that Netscape and other browser implementors are prepared to add new tags when ever they feel it is nessesary to further enhance the appearence of their pages. There is a term that is being widely used to describe the above; ``Netscapeism''. Solution Through the use of style sheets, the author is capable of changing the appearence of the document while still allowing the content of the document to be structured. The style sheet is seperate from the body of text. The use of style sheets for presentation instead of adding new HTML tags is much cleaner and more flexible. They can influence many things such as * Text-flow. * Font size. * Font weight. * Image positioning. * Context sensitivity for chages in presentation. * The ability for both author and reader to change the presentation. * Support of braille. Methology Basic Syntax A style for a particular tag is set by including the tag name (without the <>'s) followed by a pair of opening and closing braces, {}'s. Between the braces go the style information in a ``style:value'' pairing. If a user wishes to change the colour of the text of all level 1 headers to red, the style could be defined as follows:- H1 { color: red } Grouping There may be times where there are many similar tags that all need to have their style changed to the same value as each other. To eliminate the need to retype the same style information, the tags can be grouped together. Grouping is performed by separating the list of tags you wish to add style to with a comma. To specify that all headings, from level 1 to 6 all have their text in red, H1, H2, H3, H4, H5, H6 { color: red } Inheritence One of the key features of cascading style sheets is inheritence. If a HTML tag doesn't have a particular piece of style information assigned to it, it will inherit the style of that of the parent. For example, Suppose we have assigned the font size of the <BODY> tag to be 12pt and within our HTML document we have not specified any style information for the paragraph tag <P>. The paragraph will also have a font size of 12pt because <BODY> is its parent. Defining style sheets that incorporate inheritance save a considerable amount of keying by the person responsible for the documents presentation. Context sensitivity There may be times where the style sheet designer wishes to have a particular style for a section of his document, only if it is a child of another tag. An application of this could be in lists. Suppose we have the event of a nested list (a list within a list), and suppose we wished to have the second level of the list in a smaller font then the first. * level1.0 * level1.1 o level2.0 o level2.1 * level1.2 The style information that would produce the kind of style change present in above would be coded UL UL LI fontsize: 6pt where LI may be defined as having the fontsize set as ``12pt'' It is out of the scope of this document to go into detail about CCS. Further information can be found by reading though the CCS draft available at the time of writing this document at http://www.w3.org/pub/WWW/TR/WD-css1.html CCS support Support of CCS has been implemented into the following broswers: * Arena Experimental support for CCS has been built into Arena as of version 0.96. Arena is a test bed browser designed to reflect the current status of the HTML 3 draft. As such, its creaters do not intend to make it a complete full-featured browser. * Tamaya Tamaya is a WYSIWYG HTML editor/browser. It supports the whole of HTML 2 and the most invated features of the proposed HTML3 standard. Full implementation of HTML is in progress. More information can be obtained from http://www-bi.imag.fr/OPERA/Tamaya.en.html * W3 mode for Emacs A w3 mode has been developed for Emacs that has preliminary support for CCS and can be downloaded from ftp://ftp.cs.indiana.edu/pub/elisp/w3/w3.tar.Z DSSSL Lite DSSSL (Document Style and Semantics Specification Language) is an International Standard, ISO/IEC 10179:1995, for specifying document transformation and formatting in a platform- and vendor-neutral manner. DSSSL can be used with any document format for which a property set can be defined according to the Property Set Definition Requirements of ISO/IEC 10744. In particular, it can be used to specify the presentation of documents marked up according to ISO 8879:1986, Standard Generalized Markup Language (SGML). DSSSL consists of two main components: a transformation language and a style language. The transformation language is used to specify structural transformations on SGML source files. For example, a telephone directory structured as a series of entries ordered by last name could, by applying a transformation spec, be rendered as a series of entries sorted by first name instead. The transformation language can also be used to specify the merging of two or more documents, among other operations. While the transformation language is a powerful tool for gaining the maximum use from document bases, its commercial implementation is not expected to be fast in coming, and the focus in early versions of DSSSL will be on the style language component. Core DSSSL A. Common Core Features: table, table-auto-width Core query language, core expression language Basic flow object classes Sequence Paragraph Paragraph break Line field Character Rule External graphic Box Table flow object classes Table Table part Table column Table row Table cell Table border B. Dsssl-o (for online browsers and SGML editors) Common core plus the following: Features: online, simple-page Online display flow object classes Vertical scroll Multi-mode Link Marginalia Simple page flow object class Simple page sequence C. Dsssl-p (for SGML typesetting systems) Common core plus the following: Features: page, multi-column, nested-column-set, combine-char, general-indirect Printed page flow object classes Page sequence Column set sequence Printed typography flow object classes Display group Anchor Leader Score Side-by-side Side-by-side item A complete description of the DSSSL standard may be obtained from http://occam.sjf.novell.com:8080/dsssl/dsssl96 Others The number of commercial applications that claim to be SGML compliant is now extensive. The examples shown in Appendix B are the known SGML tools at the time of writing. This number is likely to increase rapidly as SGML gains a wider audience. Although most products do indeed enable users to create and manipulate SGML documents, when it comes to actually presenting them there is a problem. To date, there is no recognised standard for style sheets. As a consequence, most vendors use their own proprietary style sheet language. The majority of browsers/viewers for SGML documents will require the user to either adopt the style sheet format of the vendors product or provide a migration method for other formats. OmniMark Toolkit is an example of this. Many browsers will allow only a single DTD to be viewed. This means that conversion is necessary. Packages such as Explorer and Panorama from SoftQuad however allow any DTD to be loaded and an appropriate style sheet can be created and attached accordingly. As far as HTML 3.0 is concerned, a browser has been developed at WWW Org. This is available from http://www.w3.org/hypertext/WWW/Arena/source The browser is capable of providing support for HTML 3.0 and uses cascading style sheets (CSS). The method of independent style sheets and DTDs has been adopted for the JEDI project as it provides the most flexible approach and will most easily provide a migration path to DSSSL (ISO 10179.2) when this standard is universally adopted. Panorama the product Panorama is an SGML browser for the World Wide Web available from SoftQuad Inc of Toronto Canada. Panorama itself is NOT a WWW browser. Rather, it is a front end to any HTML 2.0 compliant WWW browser such as Netscape 1.1 and Mosaic. At the time of writing, only MicroSoft Windows based versions of Panorama are available. Panorama comes in two flavours :- Panorama PRO Panorama PRO has been designed as a publishing tool for the Internet that allows users and publishers to browse SGML documents on the WWW. The following features are supported :- * Multiple style sheets for a single DTD * Dynamically defined interactive table of contents * Arbitrary styles by elements * Maths and Table support * In-line graphics * External launch to support add multi-media to documents * Context-sensitive searching * Searching within specific SGML elements * Personal web annotations, bookmarks and links * Graphic - Text links The Free Viewer The Panorama free version allows users to experience the power of a SGML browsing facility but does not provide the ability to edit the associated style sheets. The free viewer is available from : http://www.ebt.com Arena the product Arena is a WWW browser that has been designed to be used with HTML 3.0 and style sheets. Arena is freely available in binary and source versions and may be obtained from http://www.w3.org/hypertext/WWW/Arena/ Apart from the cascading style sheet concept, arena supports HTML 3.0 tables and mathematics. Conclusions SGML is ideally suited for EDI as it is text based and is platform and operating system independent. For SGML to be "presented" it must have a style sheet mechanism that is also text based. The style sheet approaches we have studied all conform to this criterion. The Panorama style sheet can be generated from any text based editor or from within Panorama. They are flexible and readable whilst being comprehensive. It is possible for Panorama style sheets to be created for any DTD. The JEDI project will concentrate on the TEI Lite and Rainbow DTDs. The Arena style sheet mechanism is similar to Panorama's approach but concentrates on the HTML 3.0 DTD only. The DSSSL style sheet mechanism is the prefered one for future development as it is an ISO standard. Unfortunately its acceptance by software manufacturers has been slow to materialise. Transformations of DTDs and Styles sheets via specialised converter programs is possible as all of the mechanisms are open and are platform/operating system independent. These converters will be created and implemented and will be discussed in subsequent DMU-JEDI deliverables. References and further information %Up to referrence 20 should be the same as in your deliverable 1 as this 1. International Organisation for Standardisation (ISO). (ISO 8613) Office Document Architecture (ODA) and Interchange Format. (1988) 2. International Organisation for Standardisation (ISO). (ISO 8879) Information Processing Text and Office system Standard Generalised Mark-up language (SGML) (1986). 3. Handley, M and J. Crowcroft, The World Wide Web, UCL Press, 1995. 4. MicroSoft WORD User's Guide MicroSoft Corporation 5. Novell WordPerfect Work Book, ISBN 1-55692-476-3 6. An Introduction to latex , http://www.tex.ac.uk/CTAN/latex/intro.html 7. Rich Text Format (RTF) Specification, http://www.w3.org/hypertext/DataSources/RichTextFormat/RTF.txt 8. Borenstein, N.: Multipurpose Internet Mail Extension (MIME); Part one: Mechanisms for Specifying and describing the Format of Internet Message Bodies, RFC 1521, 1993. 9. Information Retrieval Service Definition and Protocol Specification for Library Applications. National Information Standards Organisation (1988) (Z39.50), P.O. Box1056, Bethesda, MD 20817. Available from Document Center, Belmont, CA, USA. 10. WAIS Server and WAIS Workstation for Unix Administrator Manual, Release 2.0 WAIS Inc., Menlo Park, CA, USA. http://www.wais.com 11. Document Style Semantics Specification Language (DSSSL) Lite standard, ISO/IEC DIS 1017.92, ISO, Paris, 1995. 12. Panaroma from SoftQuad, http://www.sq.com 13. Peek, J.: MH & xmh: E-mail for Users & Programmers. Second edition, ISBN 1- 56592-027-9. O'Reilly & Associates, Inc. 14. Goli Montasser-Kohsari, Peter Kirstein: The Current Status of ODA and SGML Converters in the context of the UCL - JEDI Project , UCL-JEDI D1 http://www.cs.ucl.ac.uk/jedi/d1/d1.ps 1995. 15. PDF Portable Document Format from Adobe system Inc, http://www.adobe.com 16. Gartland, A. and Houghton, D.: Document Format Analysis, DMU-JEDI D1 (1996), http://jedi.dmu.ac.uk/JEDI/d1/, (1996). 17. Kirstein, PT. and Montasser-Khosari, G. The current status of ODA and SGML convertors in the context of the JEDI Project, UCL-JEDI D1, http://www- mice.cs.ucl.ac.uk/jedi/d1/d1.html (1995). 18. Kirstein, PT and Montasser-Khosari, G.: Electronic Transfer and storage of multi- mode documents, UCL-JEDI2, http://www-mice.cs.ucl.ac.uk/jedi/d2-w/d2-w.html (1996). 19. Document interchange and sharing, JEDI project status, (1996), http://www.ukerna.ac.uk/technology/doci.html. 20. The ACH/ACL/ALLC Text Encoding Initiative (TEI), Susan Hockey TEI , J16 version 4 October 1994, http://www.uic.edu/org/tei/info/tij16.doc, http://www.uic.edu/org/tei/#Description 21. HyperText Mark-up Language Specification Version 3.0, <draft-ietf-html-spec2- 00.txt>, http://www.w3.org/hypertext/WWW/MarkUp/html3/CoverPage.html 22. Sklar, D.: The Annotated Rainbow DTD Rainbow version 2.5, Electronic Book Technologies, Inc. 8 Feb 1995, http://ftp.ebt.com/pub/nv/dtd/rainbow/ 23. Burnard C.M.: TEI Lite: An Introduction to Text Encoding for Interchange Lou Burnard, Sperberg-McQueen June 1995 TEI U 5, http://info.ox.ac.uk/ archive/teilite. 24. Van Herwijnen (1994) Practical SGML ; KAP 25. Liora Alschuler: A User's Guide to Structured Information, ITP 1995. 26. Ziv J., Lempel A: A Universal Algorithm for Sequential Data, IEEE Transactions on Information Theory, Vol. 23, No. 3, pp. 337-343. 27. Gartland, A. and Houghton, D.: Document Format Analysis, DMU-JEDI D2 (1996), http://jedi.dmu.ac.uk/JEDI/d2/, (1996). 28. Sperberg-McQueen, C.M., Goldstein, R.F. : HTML to the Max, A Manifesto for Adding SGML Intelligence to the WWW. The following is a list of WWW sites that concern themselves with the work on the DTDs and style sheet mechanisms discussed in this report. * SGML archive in Norway is ftp://ftp.ifi.uio.no/pub/SGML/ * Robin Cover's page is http://www.sil.org/sgml/sgml.html * SGML Open http://www.sgmlopen.org * SGML at Exeter http://www.ex.ac.uk/SGML/ * The Text Encoding Initiative is http://www.uic.edu/orgs/tei/#Description * Electronic Book Technologies is http://www.ebt.com * Arena is at http://www.w3.org/hypertext/WWW/Arena/Status.html % Glossary and expansions Glossary and expansions API Application Programming Interface. CALS Continuous Acquisition Life-cycle. Formerly Computer-aided Acquisition and Logistic Support. A set of military specifications originating from the US military of defence and is being taken up by several other allied nations. CCS Cascading Style Sheets The favoured Style Sheet mechanism to be supported by furture web browsers. CGI Common Gateway Interface. The standard interface between HTTP servers and external programs. DAP Document Application Profile. A DAP defines a consistent subset of the ODA standard targeted to a specific level of services. DTD Document Type Definition. A DTD defines the structure of an SGML document. DSSSL Document Style Semantics and Specification Language. ISO/IEC DIS 10179:1990 The objectives of the DSSSL Standard is to provide a formal and rigorous means of expressing the range of document production specifications, including high-quality typography, required by the graphics arts industry. It is net yet a full International Standard. http Hyper-Text Transfer Protocol. httpd Hyper-Text Transfer Protocol Daemon. HTML Hyper Text Markup Language. HTML is mainly used to represents documents in the World Wide Web. Hytime Hypermedia/Time-base. (Extract from Robin Cover's Bibliography:) "HyTime is a standard neutral markup language for representing hypertext, multimedia, hypermedia and time - and space-based documents in terms of their logical structure. Its purpose is to make hyper-documents inter-operable and maintainable over the long term. HyTime can be used to represent documents containing any combination of digital notations. HyTime is parsable as Standard Generalised Markup Language..." HyTime was accepted as a full International Standard in spring 1992. IETF Internet Engineering Task Force. NNTP Network News Transport Protocol. ODA Open (or Office) Document architecture (ISO 8613). ODIF Document Application Profile. ODIF defines rules for encoding documents for interchange that are structured in accordance with ODA. OSI Open Systems Interconnection. A set of standards defined to provide a method of communication between different computer systems supplied by different vendors. PDF Portable Document Format. RFC Request For Comment. RTF Rich Text Format. Used in Microsoft word and can also be imported into may mainstream word processors. SGML Standard Generalised Markup Language. SGML is defined by ISO 8879:1986. SGML's purpose is for document representation. SGML-B A standard for describing a compiled form of SGML (?). James David Mason (Convenor, ISO/IEC JTC1/SC18/WG8), posted the following message to comp.text.sgml (15 Aug 1992) "The official status of SGML-B is that it is an approved work item in ISO/IEC JTC1/SC18/ WG8, the group responsible for SGML itself. The editors are Dr. Charles Goldfarb, the SGML project leader, and Dr. David Abrahamson, of Trinity College, Dublin. The project is being maintained as officially active, with the provision that it will not be progressed until the current review and potential revision of SGML itself is further along. Our intention is to make SGML-B reflect whatever revisions we decide to incorporate into the base standard and then to make it a part of the revised standard rather than something independent. SPDL Standard Page Description Language. (ISO/IEC DIS 10190:1991) Standard Page Description Language (ISO/IEC DIS 10190:1991) A Standard for mapping to (and possibly from) a description language for output devices. Thus an SGML document might go through DSSSL- and SPDL- conforming processes before being output on a printer. SPDL might be seen to be competing with de facto standards such as Postscript. TEI Text Encoding Initiative. URL Uniform Resource Locator. WAIS Wide Area Information Server An information retrieval system using the z39.50 query protocol. WAIS clients are able to connect to the WAIS server and request documents by supplying a list of `key words' by which to match. WWW World Wide Web. Appendix A : THE SOLUTION: RAINBOW Electronic Book Technologies (EBT), in conjunction with several other key SGML vendors and promoters, has designed a format that is suitable for acting as the starting point for up-conversion efforts. It is called "Rainbow", because it represents a unification of the wide spectrum of proprietary formats. The Rainbow format is actually an SGML DTD; this design decision (although not strictly necessary) offers several benefits. It ensures that the format is readily understood by all members of the SGML community, and that existing tools can be used for validation, viewing, analysis, and editing of Rainbow files. It also means that a larger variety of tools can be used for up conversion; in particular, SGML transformation tools can play a role that was previously unavailable to them. The Rainbow DTD is publicly available, and can be used and modified by organizations and individuals freely. An FTP server has been created to provide a forum for the distribution of Rainbow-related data, and a mailing list has been created to keep interested parties informed of Rainbow-related developments. To subscribe to the mailing list, send email to rainbow@ebt.com; you will receive a reply with specific information on how to access the FTP server. To "jump start" the Rainbow-Maker effort, EBT decided to develop public-domain Rainbow Makers for four key WP formats. Three of them are available now in beta versions: RTF (Microsoft Word), MIF, and Interleaf. The fourth one (WordPerfect) is in the planning stages. Initially, EBT will distribute only executable versions (PC and several UNIX platforms) of these Makers, but when the versions become more stable, EBT will make the source code available. Independently of EBT, another member of the SGML community is contributing a Rainbow Maker for the Ventura format; that Maker will be released in the form of an OmniMark script via the mailing-list mechanism described above. THE SCOPE OF THE RAINBOW FORMAT Quite early in the Rainbow design effort, it was decided to restrict the scope of Rainbow, in order to ensure that proprietary complexity is not replaced with standardized complexity ("out of the frying pan, into the fire"). Rainbow's primary goal is to store information useful for the performance of the second phase of up conversion; thus, Rainbow does not attempt to represent all of the formatting and page-layout information inherent in WP formats. Rainbow does retain all the textual data found in the original WP document, but it retains formatting information only if it is useful for recognition of content and structure. For example, information on explicit page breaks and column breaks is maintained, because such information could be useful in recognizing the boundaries of high-level strutures (e.g. chapters). However, information on the number of columns per page is not retained, because column count is rarely an indication of structure and content. Thus, Rainbow is not intended for use in driving typesetting and display engines. Moreover, it is not possible to convert a Rainbow document back into the original WP document from which it came. By keeping the Rainbow design simple, it will keep the format stable, well-documented, easy to learn and use, and well insulated from developments in the state of word-processor technology. RAINBOW AS A MEANS, NOT AN END Although Rainbow is an SGML format, it is not appropriate for the permanent representation of data. It contains no more structure or content identification than that found in the original WP document; it can be considered to be "content free". And so it should be, for its purpose is to be the *starting* point for up conversion, not the ending point! Some members of the SGML community have expressed concern that Rainbow may be abused - that some organizations will attempt to satisfy "SGML mandates" by converting documents to Rainbow and going no further. But it is important to note that Rainbow is actually a rather late entry in the field of "content-minimal" DTDs. HTML and the OracleBook viewer's native DTD are two examples of content-minimal DTDs that existed long before Rainbow; HTML is the only one of the three that is being used as an "end" instead of a "means". As always, education is the primary weapon against abuse; that is as true in the promotion of SGML as it is in the fight against drugs. FOR MORE INFORMATION Join the Rainbow mailing list by sending email to rainbow@ebt.com. You will receive a reply that includes information on how to access the Rainbow FTP server that contains the Annotated Rainbow DTD (in PostScript format); that document is essential reading if you wish to successfully use or experiment with Rainbow. Appendix B The Whirlwind Guide: SGML Tools and Vendors The purpose of this listing is to give a brief overview of SGML Tools currently available on the market. While we would like the list to be as comprehensive as possible, we are not interested in every piece of software that claims 'SGML compatibility'. The main criterion for inclusion is that the software incorporates some kind of SGML parsing capability, or that it is in some way specifically geared to handling SGML documents. (However, certain non-SGML products that have SGML conversion toolkits bundled with them are included in the Electronic delivery and Page layout categories.) Neither does this list necessarily cover every product from a particular vendor. Ancilliary products, such as application toolkits, DTD compilers and the like, are not included. The products in the list are arranged in a set of very broad categories that should not be taken too literally since no two tools have exactly the same functionality. (We could have carried on subdividing categories forever in order to express the finer distinctions, but we had to stop somewhere...) Bear in mind also that some products could have been listed under more than one category. There are bound to be some inaccuracies, for which we apologise in advance. Please send corrections and additions to the address below. Updated versions of this list will be posted periodically at ftp://ftp.falch.no/pub/SGML-Tools. Steve Pepper Falch Infotek A/S Postboks 130 Kalbakken N-0902 Oslo Norway Phone: +47-22 16 30 40 Fax: +47-22 16 23 50 <pepper@falch.no> By product category Supported platforms (where known) are shown in parentheses as D = MS-DOS I = IBM CMS/MVS M = Macintosh O = OS/2 U = UNIX V = DEC/VMS W = MS-Windows Document analysis/design tools - CADE Groupware (W) Microstar - Document Analyzer (U D) Avalanche - DTD Viewer (W) ZifTech - DTD2HTML (U) PD - DTDocumenter (U) SoftQuad - EasyDTD (D U) PD - NEAR & FAR (U W) Microstar - RulesBuilder (U W M) SoftQuad - SGML Companion (W) PublDev Conversion software - AAP2ISO (U W) NICE - Alchemy (W) Zandar - Balise (U D V) AIS - CoST: Copenhagen SGML Tool (U) PD - DynaTag (U W) EBT - EasyTag (W M O U) TetraSys - FastTAG (U W D) Avalanche - i2c (ISO/CALS table conversion) (U D) MID - Integrated Chameleon Architecture (U) PD - OmniMark (D I M O U V W) Exoterica - PowerPaste (U) Arbortext - qwertz/FORMAT (U) PD - Rainbow-makers (U D) PD - SGML Exportfilter for FrameBuilder (U) MID - SGML Hammer (U W) Avalanche - SGML2TeX (D) PD - SureSTYLE (W) Avalanche - TableTAG (U D) Unifilt - TagWrite (W) Zandar Databases - ActiveSearch (W) ActiveSystems - ActiveServer (U) ActiveSystems - Basis SGMLserver (U W V) IDI - Impact Search and Retrieval (U) Auto-Graphics - PAT (U) OpenText - SARA (SGML Aware Retrieval Application) (U W) BNC - SGML/Search (U) AIS - SGML/Store (U) AIS - SINDA (U) STEP Electronic delivery - DynaText (U W M) EBT - Folio VIEWS (W D M) Folio - Grif SGML ActiveViews (U W) Grif - Guide Professional Publisher (W) InfoAccess - HyperTag (W M O U) TetraSys - HyperWriter for SGML (D W) Ntergaid - Lector (U W) OpenText - OLIAS Browser (U) HaL - SGML Darc (U W) Synex - SoftQuad Explorer (W) SoftQuad - SoftQuad Panorama (W) SoftQuad - SuperBook System (U W M O) Bellcore - WorldView (U W) Interleaf HyTime engines - HyMinder (U D) TechnoTeacher Page layout - ADEPT Publisher (U W) ArborText - CAPS (U) XSoft - Corel Ventura (W) Corel - DL Composer (U) Datalogics - FrameBuilder (U W) Frame - Interleaf 5 SGML (U D) Interleaf - Parlance Publisher (U) Xyvision - SGML Enabler QuarkXTension (W M) SoftQuad Document management - DocMan (U) STEP - DynaBase Publishing Environment (U) EBT - Information Manager (U) Texcel - Life*CDM (U) Corena - Parlance Document Manager (U W) XyVision - PassagePRO (U) Passage - S4 (SGML Standard Support System) (M U W) Infrastructures - SGML Editorial System (U W) MID - SIM (Structured Information Manager) (U W) Ferntree - WorkSMART (U W M) InfoDesign Parsers - Amsterdam Parser (U) PD - ARC-SGML (D U M) PD - IBM SGML Translator (I) IBM - Mark-It (U D) SEMA - MarkMinder (U D) TechnoTeacher - SGML Kernel (D I M O U V W) Exoterica - sgmls (U D O I V) PD - SP (U D) PD - YASP (Yorktown SGML Parser) (U D O V I) PD Text editors - ADEPT Editor (U W) ArborText - Author/Editor (U W M) SoftQuad - EASE (E2S Advanced SGML Editor) (D) E2S - EditTime (W) Timelux - Extended SGML Structured Editor (W) Lexicon - Grif SGML Editor (U) Grif - Grif SGML Notes (W) Grif - HotMetal (U W) SoftQuad - InContext (W) InContext - Intellitag (U D) WordPerfect - PSGML (emacs mode) (U D) PD - SGML Smart Editor (U D W) Auto-Graphics - SGML Tag Wizard (W) NICE - SGML Tagger (D) OUP - WordPerfect SGML Edition for Windows (W) WordPerfect - Write-It (D) SEMA - WriterStation (D W O) Datalogics Various - CTI/Sema harmonised test suite (-) PD - SGML Conformance Test Suite (U D M) Exoterica - SGML World Tour (U W M) SoftQuad By vendor Application category is shown in brackets as A = Document analysis/design C = Conversion software D = Database E = Electronic delivery H = HyTime engine L = Page layout software M = Document management P = Parser T = Text editor V = Various ActiveSystems 11 Holland Avenue, Suite 700 Ottawa, Ontario K1Y 4S1 Canada Tel: +1 (613) 729-2043 Fax: +1 (613) 729-2874 - ActiveSearch <D> - ActiveServer <D> AIS Berger-Levrault 35, rue du Pont F-92200 Neuilly-sur-Seine France Tel: +33 (1) 46-40-84-00 Fax: +33 (1) 46-40-84-10 - Balise <C> - SGML/Search <D> - SGML/Store <D> Arbortext Inc. 1000 Victors Way, Suite 400 Ann Arbor, MI 48108 USA Tel: +1 (313) 996-3566 Fax: +1 (313) 996-3573 - ADEPT Editor <T> - ADEPT Publisher <L> - PowerPaste <C> Auto-Graphics, Inc. 3201 Temple Avenue Pomona, CA 91768 USA Tel: +1 (909) 595-7204 Fax: +1 (909) 595-3506 Email: info@auto-graphics.com - Impact Search and Retrieval <D> - SGML Smart Editor <T> Avalanche Development Co. 947 Walnut Street Boulder, CO 80302 USA Tel: +1 (303) 449-5032 Fax: +1 (303) 449-3246 Email: sales@avalanche.com - Document Analyzer <A> - FastTAG <C> - SGML Hammer <C> - SureSTYLE <C> Bellcore 8 Corporate Place - Room 3A184 Piscataway, NJ 08854 USA Tel: +1 (908) 699-5800 Fax: +1 (908) 336-2559 Email: ccl@bellcore.com - SuperBook System <E> British National Corpus Oxford University Computing Services 13 Banbury Road Oxford, OX2 6NN United Kingdom Tel: +44 (865) 273280 Fax: +44 (865) 273275 Email: natcorp@vax.ox.ac.uk - SARA (SGML Aware Retrieval Application) <D> Corel Corporation 1600 Carling Avenue Ottawa, Ontario K1Z 8R7 Canada Tel: +1 (613) 728-8200 Fax: +1 (613) 728-9790 - Corel Ventura <L> Corena A/S Askerveien 61 P.O.Box 470 N-1371 Asker Norway Tel: +47-66 79 45 00 Fax: +47-66 79 45 90 Email: toralf@corena.no - Life*CDM <M> Datalogics, Inc. 441 West Huron Street Chicago, IL 60610 USA Tel: +1 (312) 266-3202 - DL Composer <L> - WriterStation <T> Expert Software Systems Building "de Schelde" Moutstraat 100 B-9000 Gent Belgium Tel: +32 91 21.03.83 Fax: +32 91 20.31.91 Email: e2s@e2s.be - EASE (E2S Advanced SGML Editor) <T> Electronic Book Technologies, Inc. One Richmond Square Providence, RI 02906 USA Tel: +1 (401) 421-9550 Fax: +1 (401) 421-9551 - DynaBase Publishing Environment <M> - DynaTag <C> - DynaText <E> Exoterica Corp. 1545 Carling Avenue, Suite 404 Ottawa, Ontario K1Z 8P9 Canada Tel: +1 (613) 722-1700 Fax: +1 (613) 722-5706 Email: info@exoterica.com - OmniMark <C> - SGML Conformance Test Suite <V> - SGML Kernel <P> Ferntree Computer Corp. GPO Box 3000 Canberra ACT 2601 Australia Tel: +61 6-248-8488 Fax: +61 6-247-6773 Email: johncook@acslink.net.au - SIM (Structured Information Manager) <M> Folio Corporation 2155 North Freedom Blvd. Suite 150 Provo, UT 84604 USA Tel: +1 (801) 344-3700 Fax: +1 (801) 229-6790 Email: sales@folio.com - Folio VIEWS <E> Frame Technology Corp. 1010 Rincon Circle San Jose, CA 95131 USA Tel: +1 (408) 433-3311 - FrameBuilder <L> Grif S.A. Immeuble "Le Florestan" 2, boulevard Vauban B.P. 266 F-78053 St. Quentin en Yvelines France Tel: +33 (1) 30-12-14-30 Fax: +33 (1) 30-64-06-46 - Grif SGML ActiveViews <E> - Grif SGML Editor <T> - Grif SGML Notes <T> HaL Software Systems, Inc. 3006A Longhorn Blvd., Suite 113 Austin, TX 78758 USA Tel: +1 (512) 834-9962 Fax: +1 (512) 834-9963 Email: jps@hal.com - OLIAS Browser <E> IBM Corp. 400 Columbus Avenue Valhalla, NY 10595 USA Tel: +1 (914) 749-3409 - IBM SGML Translator <P> Information Dimensions Inc. 5080 Tuttle Crossing Blvd Dublin, OH 43017-3569 USA Tel: +1 (614) 761-8083 Fax: +1 (614) 761-7290 - Basis SGMLserver <D> InContext Corp. 2 St. Clair Ave. West, Suite 1701 Toronto M4V IL5 Canada Tel: +1 (416) 922-0087 Fax: +1 (416) 922-4282 - InContext <T> InfoAccess Inc. 2800 156th Avenue SE Bellevue WA 98007 USA Tel: +1 (206) 747-3203 Fax: +1 (206) 641-9367 Email: guide@halcyon.com - Guide Professional Publisher <E> InfoDesign Corporation Waterpark Place 10 Bay Street, Suite 610 Toronto, Ontario M5J 2R8 Canada Tel: +1 (416) 369-9125 Fax: +1 (416) 369-0042 Email: info@idc.com - WorkSMART <M> Infrastructures for Information Inc. 330 Dupont, Suite 302 Toronto, Ontario M5R 1V9 Canada Tel: +1 (416) 920-6489 Fax: +1 (416) 920-6493 Email: i4i@i4i.org - S4 (SGML Standard Support System) <M> Interleaf, Inc. Prospect Place 9 Hillside Avenue Waltham, MA 02154 USA Tel: +1 (617) 290-0710 Fax: +1 (617) 290-4943 - Interleaf 5 SGML <L> - WorldView <E> Lexicon Systems, Inc. 6165 Lehman Drive, Suite 204 Colorado Springs CO 80918 USA Tel: +1 (719) 593-8971 Fax: +1 (719) 593-9268 - Extended SGML Structured Editor <T> Microstar Software Ltd. 34 Colonnade Rd N Nepean, Ontario K2E 7J6 Canada Tel: +1 (613) 727-5696 Fax: +1 (613) 727-9491 Email: cade@microstar.com - CADE Groupware <A> - NEAR & FAR <A> MID Information Logistics Group Ringstrasse 19 D-69115 Heidelberg Germany Tel: +49 6221-166091 Fax: +49 6221-23921 Email: post@mid-heidelberg.de - i2c (ISO/CALS table conversion) <C> - SGML Editorial System <M> - SGML Exportfilter for FrameBuilder <C> NICE Technologies Chemin des Hutins Veraz F-01170 Gex France Tel: +33 50-42-49-40 Fax: +33 50-42-49-40 Email: evh@altern.com - AAP2ISO <C> - SGML Tag Wizard <T> Ntergaid, Inc. 60 Commerce Park Milford, CT 06460 USA Tel: +1 (203) 783-1280 Fax: +1 (203) 882-0850 Email: p00869@psilink.com - HyperWriter for SGML <E> Open Text Corp. 180 King Street South, Suite 550 Waterloo, Ontario N2L 1P8 Canada Tel: +1 (519) 888-7111 Fax: +1 (519) 888-0677 - Lector <E> - PAT <D> Oxford University Press Walton Street Oxford OX2 6DP UK Tel: +44 (865) 267979 Fax: +44 (865) 267990 - SGML Tagger <T> Passage Systems, Inc. 465 Fairchild Dr., Suite 201 Mt. View, CA 94043 USA Tel: +1 (415) 390-0911 - PassagePRO <M> Public Domain ftp://ifi.uio.no/pub/SGML/ ftp://info.ex.ac.uk/pub/SGML/ ftp://th-darmstadt.de/pub/text/sgml/ - Amsterdam Parser <P> - ARC-SGML <P> - CoST: Copenhagen SGML Tool <C> - CTI/Sema harmonised test suite <V> - DTD2HTML <A> - EasyDTD <A> - Integrated Chameleon Architecture <C> - PSGML (emacs mode) <T> - qwertz/FORMAT <C> - Rainbow-makers <C> - SGML2TeX <C> - sgmls <P> - SP <P> - YASP (Yorktown SGML Parser) <P> Publishing Development AB Torpvagen 10 S-175 43 Jarfalla Sweden Tel: +46 (8) 580-37579 Fax: +46 (8) 580-37579 Email: christian@pubdev.se - SGML Companion <A> Sema Group AG Building Place du Champ de Mars 5 Bte 40 B-1050 Bruxelles Belgium Tel: +32 2 508 5323 Fax: +32 2 512 1499 - Mark-It <P> - Write-It <T> SoftQuad Inc. 56 Aberfoyle Crescent, Suite 810 Toronto, Ontario M8X 2W4 Canada Tel: +1 (416) 239-4801 Fax: +1 (416) 239-7105 - Author/Editor <T> - DTDocumenter <A> - HotMetal <T> - RulesBuilder <A> - SGML Enabler QuarkXTension <L> - SGML World Tour <V> - SoftQuad Explorer <E> - SoftQuad Panorama <E> STEP Technologiepark Wurzburg-Rimpar Kettelerstrasse D-97222 Rimpar Germany Tel: +49-9365/8062-0 Fax: +49-9365/8062-66 Email: step@step.de - DocMan <M> - SINDA <D> Synex Information AB Kallforsv. 24 S-124 32 Bandhagen Sweden Email: haitto@nada.kth.se - SGML Darc <E> TechnoTeacher, Inc. P.O.Box 23795 3800 Monroe Avenue, Pittsford, NY Rochester New York 14692-3795 USA Tel: +1 (716) 389-0961 Fax: +1 (716) 389-0960 Email: hyminder@techno.com - HyMinder <H> - MarkMinder <P> TetraSys 26 avenue de Tourville F-75 007 Paris France Tel: +33 (1) 45-56-99-22 Fax: +33 (1) 45-56-98-77 - EasyTag <C> - HyperTag <E> Texcel (UK) Ltd. Fountain Court 28-32 Frances Road Windsor Berkshire SL4 3AA United Kingdom Tel: +44-753-833111 Fax: +44-753-854090 Email: sales@texcel.no - Information Manager <M> TIME LUX sarl 61 avenue de la Gare L-1611 Luxembourg Luxembourg Tel: +352 40 53 221 Fax: +352 40 50 09 - EditTime <T> Unifilt Co. P.O.Box 2528 Edison, NJ 08817 USA Tel: +1 (908) 225-2243 Fax: +1 (908) 225-2248 - TableTAG <C> WordPerfect Corp. 1555 N. Technology Way Orem, UT 84057 USA Tel: +1 (801) 228 5006 - Intellitag <T> - WordPerfect SGML Edition for Windows <T> XSoft 10200 Willow Creek Road San Diego, CA 92131 USA Tel: +1 (619) 695 7700 Fax: +1 (619) 695 7710 - CAPS <L> XyVision Inc. 101 Edgewater Drive Wakefield, MA 01880 USA Tel: +1 (617) 245-4100 Fax: +1 (617) 246-6209 - Parlance Document Manager <M> - Parlance Publisher <L> Zandar Corporation R.R.2 Box 962 (Hanley Lane) PO Box 467 Jericho, VT 05465 USA Tel: +1 (802) 899-1058 - Alchemy <C> - TagWrite <C> ZIFTech Computer Systems, Inc. 120 Herchmer Crescent Kingston, Ontario K7M 2V9 Canada Tel: +1 (613) 531-9226 Fax: +1 (613) 531-8003 Email: 70444.126@compuserve.com - DTD Viewer <A> Appendix C : Panorama Style Sheet Example The DTD used in this example is the Elsevier DTD from Elsevier Reed publishing. The Style Sheet file is Elsevier.ssh :- <!DOCTYPE STYLESHEET PUBLIC "-//Synex Information AB//DTD Stylesheet Explorer//EN"> <STYLESHEET DTD="ELSEVIER.DTD" NAME="Fulltext"> <STYLE TAG="BIBL"> <FONT-SIZE V=12> <FONT-COLOR V=Navy> <FONT-WEIGHT V=Bold> <SPC-ABOVE V="50"> <A-TEXT V='Bibliography' <BEFORE> <FONT-SIZE V=24> \ifatt(COLOR="Red")<FONT-COLOR V=Green>\else<FONT-COLOR V=Red>\endif <FONT-WEIGHT V=Italic> <SPC-BELOW V="50"> <BREAK-BEFORE> <BREAK-AFTER> </BEFORE> </STYLE> <STYLE TAG="ART"> <FONT-COLOR V=Red> <BREAK-INLINE> </STYLE> <STYLE TAG="ATL"> <JUSTIFY V=CENTER> <FONT-SIZE V=14> <FONT-WEIGHT V=BOLD> <FONT-COLOR V=Navy> <BREAK-BEFORE> <BREAK-AFTER> <Z-RULER V=21> </STYLE> <STYLE TAG="AUG"> <FONT-WEIGHT V=BOLD> <FONT-SIZE V=10> <BREAK-BEFORE> <BREAK-AFTER> </STYLE> <STYLE TAG="COLLAB"> <FONT-WEIGHT V=BOLD>\ <FONT-SIZE V=10> <BREAK-BEFORE> <BREAK-AFTER> </STYLE> <STYLE TAG="ABS"> <SPC-ABOVE V="12"> <FONT-SIZE V=12> <FONT-SLANT V=ITALIC> <BREAK-BEFORE> <BREAK-AFTER> </STYLE> <STYLE TAG="P"> <SPC-ABOVE V="5"> <BREAK-BEFORE> <BREAK-AFTER> </STYLE> <STYLE TAG="EMPTY"> </STYLE> <STYLE TAG="KWDG"> <SPACE-ABOVE V=12> <FONT-SLANT V=EMPHASIS> <BREAK-BEFORE> <BREAK-AFTER> </STYLE> </STYLESHEET> The EntityRC file looks like :- --************* ENTITYRC DEFINITIONS AND MAPPING *************-- PUBLIC "-//SOFTQUAD INC//DTD ELSEVIER//EN" STYLESPEC "Testing" "elsevier.ssh" PUBLIC "-//SQ LIAM QUIN//DTD PANORAMA SAMPLE HARMSWORTH 1.0//EN" The resulting screen is :- [tex2html_wrap277] About this document ... This document was generated using the LaTeX2HTML translator Version .95.3 (Nov 17 1995) Copyright © 1993, 1994, Nikos Drakos, Computer Based Learning Unit, University of Leeds. The command line arguments were: latex2html -split 0 d3.tex. The translation was initiated by Adrian Gartland on Tue 6 Aug 14:46:30 1996 ---------------------------------------------------------------------------- Adrian Gartland Tue 6 Aug 14:46:30 1996