wsc-xit next steps

Now that we all have a full round of review, comments, and issues on 
wsc-xit, it's a good time to take a step back and plan what we'll do gong 
forward. We'll discuss this in more detail at the f2f in Palo Alto, and I 
encourage pre-meeting email discussion as well. 

My impression (from Issues and review) is that a number of recommendations 
in wsc-xit are more mature and conservative than others. Their claims are 
modest, and they are by and large based on either currently deployed best 
practice or modest increments on that. Anil will have a draft of wsc-xit 
with a mapping of issues, so we can take a look at them and more 
objectively determine which portions have only a few, straightforward 
issues. 

Assuming that is the case, we should use the face to face to map out next 
steps on both the mature and the future looking recommendations. Here's my 
current take. 

We identify which issues are mature, and which future looking. There may 
be some border or edge conditions. As well as robust discussion of the 
categories themselves. 

--------------------------------------------------
For the Mature Recommendations: 

Resolve any outstanding issues. Prioritize issues (if any) that need a 
resolution before usability walkthrough. 

Determine what further usability related testing is needed on the mature 
recommendations. At a minimum, we would devote one meeting to a walk 
through of each logical unit, with usability goals, any usability 
evaluation, and a prototype as input. We would determine what further 
usability testing would be needed as well, and make concrete plans for it. 


Issue another working draft of the mature recommendations. 

Determine what, if any, dependancies there are between the mature 
recommendations and other groups, and make sure those dependancies are 
satisfied. 

Determine the relationship between existing standards and work outside of 
W3C and the mature recommendations, and make sure that's documented.

Go to Last Call. 

--------------------------------------------------
For the Future Looking Recommendations: 

We need to discuss what's needed for these. At a minimum we'll need some 
sort of more extensive prototype (lo fi or otherwise) for better 
understanding and usability evaluation. I have a less clear vision of 
large grained next steps for these. It will be useful to discuss this with 
the group. It might be that they're different on a section by section 
basis. 

          Mez