[Members] the "Proposed" state in XEP-0001

Kurt Zeilenga Kurt.Zeilenga at Isode.COM
Thu Mar 10 16:12:20 CST 2011


On Mar 10, 2011, at 1:29 PM, Peter Saint-Andre wrote:

> I've effectively stopped using the "Proposed" state defined in XEP-0001
> (too many specs went into Proposed during Last Call but had to be moved
> back to Experimental because the authors needed to revise the XEP before
> the Council would approve it, and sometimes they were in the Proposed
> state for a long time). I wonder if we want to get rid of it entirely...

+1

What about Reject?  The state digram shows the only way to Reject is via Proposed.


As I understand the standards process, that if the Council determines that a document is not ready to progress on the Standard as requested the document moves into a Rejected state.   I would rather the document remain in its current state.   Further, I rather documents only be moved to Rejected by affirmative vote of the Council in response to a request for such a move.  This would be appropriate for say a XEP for which had not be deprecated in favor of some other XEP but for which the Council has determined that the protocol defined therein should no longer be implemented or deployed.

That is, I propose:


     +--> Retracted
     |
     |
     +--> Deferred    
     |                
     |                
Experimental ----> Draft ----> Final
     |               |           |
     +--> Rejected   |           |
                     +-----------+---> Deprecated
                                 |
                                 +--> Obsolete

Moves between Experimental->Rejected, just like Draft/Final to Deprecated should require an affirmative vote of the Council.

-- Kurt



More information about the Members mailing list