Re: What to slash Re: Proc Doc: time to Slash and Burn, Divide and Conquer, or what?

Karl Dubost said (on May 23rd)
Things I would like to see (not complete):

* What are the goals of the Process Document?
* What is the fundamental set of values governing the process?
* Roles
* Required steps for working (input/output/flowcharts/validation/etc)

The following set of goals (which cover both those for recommendations and for the process by which the Recommendations are produced) are taken from a set first prepared by Ian Jacobs as part of a response to a proposal for simplifying the Process and then edited by me for a similar draft proposal (incomplete as of this date).
The Process should be and produce Recommendations that are:
Useful
A Recommendation should reflect industry-specified use cases and requirements to ensure its relevance and usefulness. It should help move the Web to its full potential.
Interoperable
Independent implementations are expected and are only effective it they are interoperable. The W3C specifications should be written to help accomplish interoperability and the process should facilitate demonstrations of such interoperability. Designs that bear this in mind, documents written to facilitate tests, and quality supporting test suites help achieve the goal of broad interoperability. W3C standards must also interoperate with standards developed by other organizations, so processes must allow and support external collaboration.
Prompt
The market for Web technology can move very quickly, and so it is important that W3C support a specification development process that allows rapid deployment of new technology.
Multistakeholder
The Web belongs to everyone. That means that all parties should be able to participate in the creation of Web standards and their substantive input given due consideration.
Public Review
There is a wide range of potential reviewers from implementers to end users and advocates for affected communities. The process must help make these reviews feasible and effective.
Royalty-Free
Royalty-Free standards lower barriers to adoption, one of the keys to the success of the Web. The process must allow sufficient time for owners of revelant Intellectual Property to make Royalty-Free commitments.
Stable
Just as developers release stable snapshots of software for those stakeholders that require stability, W3C publishes stable standards to promote interoperability and increase comfort around intellectual property commitments.
Support for a variety of development methodologies
The process should be usable with a variety of development methodologies ranging from a traditional "waterfall" methodology to an agile methodology based on incremental improvements.

I make no claim that this list is complete, but I believe all the things on it are necessary.

Steve Zilles