hi milton

>Karen:
>As Danny explained, the PDP _schedule_ is honored mainly in the breach.
>
>The "map" however does give you an idea of the process structure; e.g.,
>what does it mean when the secretariat issues a "call for public
>comment". what is the relationship between the GNSO Council, a Task
>Force, etc.

obviously policy development is a very fluid process, and difficult 
to descibe excepting as you say - by having the more structural 
elements described (which i understand then the map does provide) and 
with some (brief) annotation.. along the lines of what you go on to say

>If you want to know what is going on in any specific policy development
>process, the only way is to get people to attend the teleconferences and
>to report to the rest of us on what is really going on.

i'm interested in this now when thinking about the nomcom process.. 
how one would describe the nature of GSNO policy development to 
potential candidates who aren't necessarily ICANN insiders.. but who 
may bring useful skills, expertise and perspectives to the process..

karen