[JDEV] Jabber Client Compliance
Sebastian Vollnhals
sebastian at vollnhals.info
Wed Aug 6 13:48:09 CDT 2003
i think, the best way to handle this, is, to interprete everything as
online, that is not specified.
Am Mit, 2003-08-06 um 20.15 schrieb Julian Missig:
> Actually, looking at the XMPP spec, <show>online</show> isn't even
> valid. Ok. <show>normal</show> wasn't even used in Jabber prior to
> XMPP, so clients shouldn't start using that now.
>
> Julian
>
> On Wednesday, Aug 6, 2003, at 14:10 US/Eastern, Julian Missig wrote:
>
> > I'm getting really sick of looking at my roster and seeing things like
> > <presence from="some at jid"
> > to="julian at jabber.org"><show>normal</show></presence>
> >
> > <show>normal</show> is not compliant with Jabber or XMPP--"normal" is
> > not a valid type. It's "online"--it always has been "online".
> >
> > I know that Jabber Compliance Testing is one of those things that
> > people keep talking about doing and saying we will do someday, etc,
> > etc., but I'd like to propose that we start doing this stuff *now*.
> >
> > I propose that I set up a "Jabber Client Compliance" project on
> > jabberstudio.org. I'll set up a Component for each client people
> > report protocol compliance issues with. "Bugs" would be a list of
> > *errors* in protocol compliance. "Feature requests" would be a list of
> > areas in which clients are completely lacking protocol support that
> > they should have. This requires very little work on my part, and
> > little work on the part of people who find protocol compliance errors.
> > We then have an easy system to add comments, etc, etc. All you have to
> > do is point the client author at the bug. If you find a protocol error
> > in the client, you can report it. When it's fixed, it can be marked
> > completed. The Jabber community will then have a running list of
> > clients which are not compliant.
> >
> > What do people think? Good idea? Or should I wait for people to build
> > up a real system?
> >
> > Julian
> >
> > _______________________________________________
> > jdev mailing list
> > jdev at jabber.org
> > http://mailman.jabber.org/listinfo/jdev
>
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
URL: <https://www.jabber.org/jdev/attachments/20030806/003aa05f/attachment-0002.pgp>
More information about the JDev
mailing list