[Avalon4] Context Consensus - after the vote

No, the vote isn't over - just a few notes:

There have been some last-minute suggestions for changes to the proposal. I 
am against changing a proposal while it is being voted on, and I think it 
would be a loss to stop the vote, get another version of the proposal out, 
and then re-start the vote. In short, there is so much in the current 
proposal that we have consensus on that I think it should go in and not be 
held up by very small changes. There's always some improvement that can be 
done, but at some point one has to say -OK, this is good enough for now, 
let's put it in.

On the other hand, just because something has gone from proposal to vote it 
is not automaticaly immune from opposition.

So, my suggestion is this: We have postponed some things, among them:

  + The metainfo model.
  + The metainfo DTD
  + The list of standard context keys
  + The naming of context keys.

These things were postponed with the intention that we would deal with them 
separately and shortly after this vote. Now, I suggest that anyone who has 
a minor change to the current proposal that is enough to stop you from 
voting an immediate +1, but not enough to make you -1 the proposal, that 
you reply to this message with your concern, and we can then have a second 
vote shortly after this vote. That way, these last-minute changes aren't 
lost, but neither do we have to restart the proposal->vote cycle, and no 
one has to worry that this is the last chance to provide input regarding 
the Context interface for the next two years.

I already have Paul Hammant suggestion of changing the WARNING-note 
attached to the castable context part of the proposal, Peter Donald's 
comments regarding the context entry samples, and I promise to take them up 
ASAP after this vote ends Tuesday 1200.

And of course, if you have a major problem with the proposal as it is now, 
feel free to -1 it.

Does this seem like a fair suggestion?

/LS