[Prev] .................... Web Working Groups

Important Web-Related Draft Documents

This document lists the important working group drafts under current discussion. I will attempt to keep this list up-to-date, but you should be aware that this is not possible, given time limitations and the ever growing number of topics under simultaneous discussion.

On This Page: HTML | URN | HTTP | Stylesheets | Graphics

HTML Documents

Internationalization (I18N) of The Web

Draft Name: draft-ietf-html-i18n-03.txt
Author: Francois Yergeau, G. Nicol, G. Adams, M. Duerst
Date: 13-Feb-1996

This document is meant to address the issue of the internationalization of HTML by extending the specification of HTML and giving additional recommendations for proper internationalisation support. A foremost consideration is to make sure that HTML remains a valid application of SGML, while enabling its use in all languages of the world.

In particular, this document discusses issues such as language and character set specifications, language-dependend text layout direction, and so on.

Other Internationalization-Related Resources

Michael Gschwind's large collection of Internationalization/Localization resources.

Tables Revisions

Draft Name: draft-ietf-html-tables-03.txt
Author: Dave Raggett

This document proposes extensions to the TABLE elements, allowing for a richer description of table content and for compatibility with non-graphical presentation of tables.

HTML And Style Sheets

Draft Name: draft-ietf-html-style-00.txt
Authors: B. Bos, D. Raggett, H. Lie
Date: 22 November 1995

This specification extends HTML to provide support for rendering instructions expressed in separately specified notations. It is no longer necessary to extend HTML when new forms of rendering instructions are needed. Rendering instructions can be included with individual HTML elements to which they apply, or grouped together in the document head, or placed in associated style sheets. This specification does not specify particular style sheet notations, leaving that to other specifications.

Compound Documents in HTML

Draft Name: draft-ietf-html-cda-00.txt
Authors: P. Burchard, D. Raggett

This specification provides an HTML implementation of a simple compound document architecture for the World Wide Web, based on a new EMBED/INSERT element.

INSERT Element; For Inserting Active Multimedia Objects

Draft Name: draft-ietf-html-cda-00.txt
Authors:Charlie Kindel, Microsoft Corporation; Lou Montulli, Netscape Communications Corp.; Eric Sink, Spyglass Inc.; Wayne Gramlich, Sun Microsystems; Jonathan Hirschman, Pathfinder; Tim Berners-Lee, W3C; Dan Connolly, W3C
Editor:Dave Raggett
(this is a link to the most recent version). Currently archived versions are as follows:

This specification extends HTML to support the insertion of multimedia objects including Java applets, Microsoft Component Object Model (COM) objects (e.g. OLE Controls and OLE Document embeddings), and a wide range of other media plug-ins. The approach allows objects to be specified in a general manner and provides the ability to override the default implementation of objects.

Client Side Imagemaps

Draft Name: draft-seidman-clientsideimagemap-02.txt
Authors: J. Seidman
Date: 12 December 1995
Pages: 5
The markup language known as "HTML/2.0" provides for image maps. Image maps are document elements which allow clicking different areas of an image to reference different network resources, as specified by Uniform Identifier (URIs). The image map capability in HTML/2.0 is limited in several ways, such as the restriction that it only works with documents served via the "HTTP" protocol, and the lack of a viable fallback for users of text-only browsers. This document specifies an extension to the HTML language, referred to as "Client-Side Image Maps," which resolves these limitations. This draft is implemented in Netscape Navigator 2.0, Microsoft Internet Explorer 2.0, and the latest Spyglass browsers.

Security Extensions For HTML

Draft Name: draft-ietf-wts-shtml-00.txt
Authors: E. Rescorla, A. Schiffman
Date: 13-Feb-1996
Pages: 3
See Also: SHTTP Tranfer Protocol
This memo describes a syntax for embedding S-HTTP negotiation parameters in HTML documents. S-HTTP as described by draft-ietf-wts-shttp-01.txt contains the concept of negotation headers which reflect the potential receiver of a message's preferences as to which cryptographic enhancements should be applied to the message. This document describes a syntax for binding these negotiation parameters to HTML anchors.

URN Documents

Uniform Resource Names, ISO OIDs and DNS

Draft Name: draft-mealling-oid-dns-00.txt
Authors: M. Mealling, P. Faltstrom, L. Daigle
Date: 12 December 1995
Pages: 5
This paper describes a "resolution-mechanism"-independent architecture for Unifrom Resource Name (URN) usage and name space management. This non-monolothic architecture allows different components of the name space to be managed by the appropriate level of network authority. This not only integrates well with traditional Internet models, it allows flexibility in choice of implementation of support for each layer of the name space. An implementation for the architecture, using OIDs and DNS-based infrastructure, is outlined.

Uniform Resource Names, ISO OIDs and DNS

Draft Name: draft-ietf-mimesgml-exch-00.txt
Authors: D. Stinchfield, EBT, Inc.
Date: 31 August 1995

This draft proposes a standard for exchanging SGML documents over the World Wide Web using catalogs and MIME. This draft extends SGML Open's definition of catalogs [10] by adding to it new keywords and storage object identifier (SOI) types. The new keywords identify SGML document objects (such as document type declarations and document entities) and non-SGML document objects (such as stylesheets).

An SGML-based URC Service

Draft Name: draft-ietf-uri-urc-sgml-00.txt
Authors: Ron Daniel Jr., Terry Allen
Date: 16 June 1995

The URI Working Group has been developing an architecture where Internet resources are identified using a Uniform Resource Name (URN), and retrieved using a Uniform Resource Locator (URL). Mapping URNs to URLs is the job of the Uniform Resource Characteristics (URC) service, whose requirements are yet to be specified....

Other URN Resources

Uniform Resource Characteristics -- Overview and links

An Overview of Addressing Issues

Maintainer: Tim Berners-Lee

This is the W3C plage describing Web addressing issues, with links to related documentation.

HTTP Documents

The HyperText Transfer Protocol -- HTTP/1.0

Draft Name: draft-ietf-http-v10-spec-04.txt
Authors: T. Berners-Lee, R. Fielding, H. Frystyk
Date: 14 October 1995
Pages: 40+

The Hypertext Transfer Protocol (HTTP) is an application-level protocol with the lightness and speed necessary for distributed, collaborative, hypermedia information systems. It is a generic, stateless, object-oriented protocol which can be used for many tasks, such as name servers and distributed object management systems, through extension of its request methods (commands). A feature of HTTP is the typing of data representation, allowing systems to be built independently of the data being transferred.

HTTP has been in use by the World-Wide Web global information initiative since 1990. This specification reflects common usage of the protocol referred to as "HTTP/1.0".

The HyperText Transfer Protocol -- HTTP/1.1

Draft Name: draft-ietf-http-v11-spec-01.txt
Authors: R. Fielding, H, Frystyk, T. Berners-Lee
Date: 19 January 1996
Pages: 40+

This memo discusses proposed extensions to the HTTP 1.0 protocol, to include such features as: logic bags; support for caching; range retrieval; content negotiation; MIME compatibility; authentication; and timing of the PUT operation. This is very much a work in progress, and should not be considered as a definitive standard.

The Secure HyperText Transfer Protocol (SHTTP)

Draft Name: draft-ietf-wts-shttp-01.txt
Authors: E. Rescorla, A. Schiffman
Date: 13 February 1996
Pages: 47

This memo describes a syntax for securing messages sent using the Hypertext Transfer Protocol (HTTP), which forms the basis for the World Wide Web. Secure HTTP (S-HTTP) is an extension of HTTP, providing independently applicable security services for transaction confidentiality, authenticity/integrity and non-repudiability of origin. The protocol emphasizes maximum flexibility in choice of key management mechanisms, security policies and cryptographic algorithms by supporting option negotiation between parties for each transaction.

Stylesheet Documents

Cascading Style Sheets, level 1

Draft Name: ?? (W3C Specification)
Authors: Håkon W Lie, Bert Bosss
Date: 22 December 1995

This document specifies level 1 of the Cascading Style Sheet mechanism (CSS1). CSS1 is a simple style sheet mechanism that allows authors and readers to attach style (e.g. fonts, colors and spacing) to HTML documents. The CSS1 language is human readable and writable, and expresses style in common desktop publishing terminology.

One of the fundamental features of CSS is that style sheets cascade; authors can attach a preferred style sheet, while the reader may have a personal style sheet to adjust for human or technological handicaps. The rules for resolving conflicts between different style sheets are defined in this specification.

DSSSL Online Application Profile

Draft Name: ?? (Web Document)
Authos: Jon Bosak
Date: 12 December 1995

This draft describes an application profile of DSSSL designed for the formatting specification requirements of online SGML browsers and editors. This subset, DSSSL Online (informally "dsssl-o"), supports the basic features needed to provide publisher-oriented formatting control of online displays and a minimum set of page-oriented features needed to provide utility printouts from browsers and editors.

Note that this draft is based on committee drafts of the full DSSSL Standard and may not accurately represent the final DSSSL Standard as published. Also, this document is not intended as an introduction to DSSSL, but rather as a matrix for discussions about conformance levels among people who have already read the standard

Graphics Documents

Portable Network Graphics (PNG) Specification

Draft Name: ?? (W3C Specification)
Authors: (see draft)
Editor: Thomas Boutell (boutell@boutell.com)
Date: 26 November 1995

The PNG format is intended to provide a portable, legally unencumbered, well-compressed, well-specified standard for lossless bitmapped image files.

Although the initial motivation for developing PNG was to replace GIF, the design provides some useful new features not available in GIF, with minimal cost to developers.

JPEG Information Compression FAQ

Maintainer: Tom Lane

This FAQ provides a summary of the JPEG technology, and links to various programming utilities and libraries.

[Prev] .................... Web Working Groups
Ian S. Graham, 1994-1995