On Tue Mar 6 22:01:50 2012, Peter Saint-Andre wrote:
On 3/6/12 2:53 PM, Dave Cridland wrote:
> I also think that technically, this XEP should be "deprecated"
rather
> than "obsoleted" - it is out of date, rather than wrong.
Changing the status of a XEP to Obsolete does mean the protocol is
wrong, it means that you shouldn't implement the spec. In the case
of
XEPs 237, 192, 193, and 190 (all changed to Obsolete recently),
we're
saying you shouldn't implement the spec because the proper
documentation
is now in the RFCs (these XEPs were used only for the purpose of
discussing changes we'd make to the RFCs; with publication of the
RFCs,
those XEPs are now Obsolete).
Hmmm...
"""
9.9 Deprecated
A XEP of any type is in the Deprecated state if the XMPP Council has
determined that the protocol defined therein is out of date and that
new implementations are no longer encouraged (e.g., because it has
been superseded by a more modern protocol).
9.10 Obsolete
A XEP of any type is changed from Deprecated to Obsolete if the XMPP
Council has determined that the protocol defined therein should no
longer be implemented or deployed.
"""
I think perhaps those descriptions need updating, then - they
specifically refer to "the protocol defined therein", rather than the
specification per-se.
They're Obsolete in the IETF sense, for sure; but I'm not quite sure
that's the same sense as we've defined in XEP-0001.
Dave.
--
Dave Cridland - mailto:[email protected] - xmpp:[email protected]
- acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
- http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade
