For the project we need a common understanding of some such ability-description framework. We need to know what user differences matter before we start writing an HTTP message data dictionary, or any of our other task outputs. Probably there are people on the team such as Gregg and Javier that already know more than enough about this. We need them to teach us, people like Paul to check it out, and get it into the project bookshelf where people that join the process later can read up without tying up meeting time. That is my idea of the need.
Some future visions allow for control widgets in the content that comes from the server.
I think that we really need to back off to defining requirements on the browse dialog between user and content that can later be allocated to tool and protocol by the developers. If this is not clear to people, we need to talk about it.