Return-Path: Delivered-To: apmail-httpd-docs-archive@httpd.apache.org Received: (qmail 97462 invoked by uid 500); 28 Jun 2003 16:50:44 -0000 Mailing-List: contact docs-help@httpd.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: docs@httpd.apache.org Delivered-To: mailing list docs@httpd.apache.org Received: (qmail 97449 invoked from network); 28 Jun 2003 16:50:43 -0000 Date: Sat, 28 Jun 2003 18:44:37 +0200 From: Astrid =?ISO-8859-1?Q?Ke=DFler?= X-Mailer: Yes! Organization: Kess-Net X-Priority: 3 (Normal) Message-ID: <197792988727.20030628184437@kess-net.de> To: Joshua Slive Subject: Re: Beginnings of a standards document In-Reply-To: References: <20030628135156.L12922@lucid.net.au> <20030628135156.L12922@lucid.net.au> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N >> I've begun taking on the task of documenting all the drafts/standards th= at >> Apache adheres to, as per the STATUS file and PR 16938. >> >> Before I march on too much more, I'd like some feedback on roughly how i= t's >> looking and whatnot. Content isn't complete, nor is accuracy at this >> point. >> >> http://icarus.apache.org/~jsl/httpd-2.0/manual/relevant_standards.html.e= n [...] > For your doc, I'd tend to try to avoid tables. In general, we use tables > as little as possible in the docs, and we use them only for truly tabular > data. In this doc, I'd probably lean towards using a

or something o= f > the sort instead of a table. I'd also suggest a list rather then tables. Maybe something like: RFC2616 Hypertext Transfer Protocol (HTTP) The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. Status: Draft standard > The other question is does this belong in the manual, or should it be > maintained on the website alone, as it has been in the past: > http://httpd.apache.org/library/ > I don't have a strong opinion about that. In either case, an update is > much needed. I have been slighty thinking of an idea to collect all httpd corresponding documentation together to some books like - short introduction for beginners - users manual - technical documentation - introduction for developers - ... All books together present the httpd documentation. Banking on this idea, the standards list would fit into technical documentation. So I think, yes, it belongs to the docs like other stuff outside the manual. But since my idea is a long term prozess and may result into some restructuring of our pages, I'm not sure, where to put it now. Hm, just a thought ... Kess > Joshua. > --------------------------------------------------------------------- > To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org > For additional commands, e-mail: docs-help@httpd.apache.org Viele Gr=FC=DFe Kess E-Mail: kess@kess-net.de --------------------------------------------------------------------- To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org For additional commands, e-mail: docs-help@httpd.apache.org