Just from reading XEP-0001 (i did not read any other XEPs that regulate what council should or shouldnt do) its very hard to say.
I dont think the rules how to deprecate a XEP is really touched by XEP-0001. In many places it speaks about "any change in status must be approved" referring to the approval process. But then it mentions the status Final as being the "final approval" implying that the approval process has ended at that point. Certainly a thing that could be written more explicit, as deprecating a XEP can be a point of contention. To go the save route and not assume a normal majority vote is probably wise. just my 2 cents regards philipp 2017-10-25 19:57 GMT+02:00 Peter Saint-Andre <[email protected]>: > On 10/25/17 9:58 AM, Tobias M wrote: > > Hi all. > > > >> On 25. Oct 2017, at 17:55, JC Brand <[email protected] > >> <mailto:[email protected]>> wrote: > >> > >> With 3 (+1) votes and 2 (-1) votes the council has decided to change > >> the state > >> of XEP-0071: XHTML-IM to Deprecated > > > > Kev pointed out that XEP-0001 says: > > > >> A XEP shall not be advanced to the next stage in the approval process > >> so long as any Council Member continues to vote -1. > > > > So XEP-0071: XHTML-IM is currently NOT deprecated. The council will > > revisit the topic when another request for deprecation comes in. > > Although it's not clear whether deprecation counts as advancement, it > seems that the Council did the right thing here. > > Peter > > > > > _______________________________________________ > Standards mailing list > Info: https://mail.jabber.org/mailman/listinfo/standards > Unsubscribe: [email protected] > _______________________________________________ > >
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
