W3C publishes "Architecture of the World Wide Web".

The World Wide Web Consortium (W3C) has announced the publication of 'Architecture of the World Wide Web" The authors of this document, W3C's Technical Architecture Group (TAG), invite review by the community of this description of principles that guide the evolution of the World Wide Web. The TAG invites comments on the First Edition by 5 March 2004; see the TAG home page for more information about the review. In November 2001, W3C responded to a clear demand from the Web community and the W3C Membership to write down a description of the architecture of the Web. The architecture has been described and debated many times in the past, but has not been described in a single, coherent document by a group of acknowledged experts, and reviewed in such a focused manner by the community

"The nine people on the TAG today have had a hand in many parts of the design of the Web," explains Tim Berners-Lee, W3C Director, and Co-Chair of the TAG. "In the Architecture Document, they describe how it works.

They emphasize what characteristics of the Web must be preserved when inventing new technology. They notice where the current systems don't adhere well, and as a result show weakness. This document is a pithy summary of the wisdom of community."

The TAG conducts its work on an active, public mailing list, which helps ensure that its description of the Web reflects the real world concerns of developers. URIs, HTTP, and HTML Anchor the information Space

The Web architecture consists of three fundamental concepts: identification (URIs), interaction (protocols such as HTTP and SOAP), and representation (formats such as UTML, SVG, and PNG). These three branches are typified by the familiar user experience of using a browser to click on a link that identifies a Web site, leading to interaction with the Web site (referred to generically as a 'Web resource"), and then to the display of information in the browser.

Some of the important topics covered by the Architecture Document include important considerations when managing a Web server, such as persistence; how to take advantage of 'sale" Web interactions and allow bookmarking and caching; and pitfalls to avoid when using content negotiation. The document also explains how XML fits into the Web, and how to ensure that new formats "play well" on the Web.

Through stories, examples, and references to supplementary TAG findings, the Architecture Document explains the impact of the design on real world issues, ranging from designing and registering new document formats,, to managing a Web server.

wwwq.3c.org