declaration and ISO Latin1 ToDo list: ========= * Methods for mail, fax, queries, posting articles/responses ... Generalising actions beyond traversing simple hypertext links, and providing a means to exploit HTTP's range of methods. * Support for change bars? The guidelines in designing HTML+ were: * Similar to HTML, so that most existing documents conforming to the HTML DTD are also HTML+ compliant A simple program will be made available to convert HTML documents into HTML+. You will be able to use it with "find" to convert all your files in one command! * Fast and easy to render with modest programs, without the need for multiple parses, although that may be useful for more sophistocated styles of rendering. * Suitable for most forms of online and printed material, based upon a detailed analysis of a reference books, fiction, newspapers, magazines and technical documentation. Hierarchical groupings can be defined extending across multiple documents, and used to represent books, chapters, sections, etc. * Uses Internet URL's as a means of referencing external/remote documents, rather than SGML's formal public identifiers (which are based on ISO 9070 with ANSI as registration authority). The URL format is however, sensitive to changes in locations of documents, but this will be addressed by the proposed URN standard for universal resource numbering. * HYTIME compability - See CommsACM Nov91 vol 34 p67-83 for review of HyTime. HyTime is designed for interchanging documents between different hypermedia systems, and doesn't address the hard bit which would be coping with URLs. It is now clear that HTML+ does fit into the general model described by HyTime, but not the detailed SGML constructs that HyTime specifies. This isn't a real problem, and it will be easy to map HTML+ documents into a HyTime compliant format using a suitable DTD. I therefore see now need right now to add HyTime specific constructs to the HTML+ DTD. One most notable difference between HTML and HTML+ is the use of containers. For example

is a container in HTML+ rather than a separator. This change has been made to facilitate verification, and to provide greater flexibility in specifying link destinations. The major additions over HTML are: * nested lists * inline images and drawings * embedded data in foreign formats for mathematical equations etc. * tables with support for titles, and column headings and an ability to let entries/headings span columns * forms - for querying or updating information sources and filling in questionaires for mailing or faxing Links can now be anchored on a wide range of containers by using value of the container's id attribute as part of a hypertext link. Things dropped from HTML ------------------------ * MENU and DIR which are now handled as attributes to UL * all inline emphasis is now handled with the EMPH tag * PLAINTEXT, LIST and XMP have been obsoleted * IMG (X Mosaic) now handled with FIG element Common Attributes: ----------------- id the id attribute allows authors to name elements such as headers and paragraphs as potential destinations for links. Note that links don't specify points, but rather extended objects. index allows authors to specify how given headers etc should be indexed as primary or secondary keys. "/" separates primary from secondary keys ";" separates multiple entries href Universal resource locations (references to documents) --> ]>