Re: Organization of techniques document

Up to now the decision of the working group has been that we want everything
in one document. The benefit of having a Techniques note and a continuous
process is that we can change that decision if it no longer serves the
purpose.

I would propose that the primary way of spliting should be by the technology
addressed - most producers of image editing software are not going to care a
lot about HTML source editing software, and vice versa (although there are
some places in the guidelines where these two things have the same
requirements and interacting techniques, such as management of alternative
content).

Charles McCN

On Wed, 8 Mar 2000, Ian Jacobs wrote:

  Up to now, I was under the impression that people wanted everything
  in one document (e.g., sample information is available in the techniques
  document and in separate documents). You might split along the following
  lines:
  
   - General techniques, list of resources, links to other techniques
  documents
     (this would be the "main" techniques document).
   - Content techniques
   - User interface techniques
   - Sample implementations
  
   - Ian