FYI, all are welcome as always. This is at 20:00 UTC (which may be
morning, afternoon, or evening depending on where you are ;-).
Original Message
Subject: [Council] meeting this evening
Date: Wed, 21 Jan 2009 09:08:32 +
From: Kevin Smith ke...@kismith.co.uk
Reply-To:
FYI:
-- Forwarded message --
From: Kevin Smith
Date: Wed, Jan 21, 2009 at 8:51 PM
Subject: Minutes 2009-01-21
To: XMPP Council
Date: 2009-01-21
Time: 20:00 UTC
Place: xmpp:coun...@conference.jabber.org
Log:
Version 1.0 of XEP-0245 (The /me Command) has been released.
Abstract: This specification defines recommended handling of the /me command in
XMPP instant messaging clients.
Changelog: Per a vote of the XMPP Council, advanced specification to Active and
changed type from Historical to
This message constitutes notice of a Last Call for comments on XEP-0232
(Software Information).
Abstract: This document specifies an extended data format whereby XMPP service
discovery responses can include detailed information about the software
application that powers a given XMPP entity for
Version 0.1 of XEP-0259 (Message Mine-ing) has been released.
Abstract: In servers that deliver messages intended for the bare JID to
all resources, the resource that claims a conversation notifies all
of the other resources of that claim.
Changelog: Initial published version. (psa)
Diff:
This message constitutes notice of a Last Call for comments on XEP-0232
(Software Information).
Can someone remind me why we use data forms for this, and not real
elements? I never really understood why we have data forms in
protocols that have nothing to do with displaying of data. Why not
Can someone remind me why we use data forms for this, and not real
elements?
I guess it has something to do with how disco information is to be
extended (looking at XEP-115). Anyway, I guess we don't have a choice
here, but that doesn't mean I like it :-)
cheers,
Remko
Remko Tronçon wrote:
Can someone remind me why we use data forms for this, and not real
elements?
I guess it has something to do with how disco information is to be
extended (looking at XEP-115). Anyway, I guess we don't have a choice
here, but that doesn't mean I like it :-)
Right, it's
Le mercredi 21 janvier 2009, XMPP Extensions Editor a écrit :
This message constitutes notice of a Last Call for comments on XEP-0232
(Software Information).
Abstract: This document specifies an extended data format whereby XMPP
service discovery responses can include detailed information
On Wed Jan 21 20:51:55 2009, Kevin Smith wrote:
4) Message Mine-ing
What do we do?
Several objections, but agreement that a spec to address these
problems
is needed, and rough agreement to publish both this and an upcoming
alternative to experimental and to compare them both once they're
Attached is part of a solution to the (largely unstated) problem.
Apart from the spelling mistakes, I like it so far.
1) A refinement on the remote control ad-hoc commands to send only some
pending messages. (Not really essential, but might be nice).
Actually, a real protocol (based on
11 matches
Mail list logo
