| [Prev] | .................... Web Working Groups |
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.
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
- http://www.w3.org/pub/WWW/International/
- http://www.vlsivie.tuwien.ac.at/mike/i18n.html
- Michael Gschwind's large collection of Internationalization/Localization resources.
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.
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.
This specification provides an HTML implementation of a simple compound document architecture for the World Wide Web, based on a new EMBED/INSERT element.
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.
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).
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....
This is the W3C plage describing Web addressing issues, with links to related documentation.
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".
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.
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.
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.
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
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.
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 |