Eric Will wrote:
On Oct 8, 2008, at 4:22 PM, Peter Saint-Andre wrote:
5c. XEP-0091: Delayed Delivery
Consensus that we need to determine how widely XEP-0203 is
deployed before changing this to Obsolete.
Not that I'm important, but I implemented XEP-0203 in synapse.
Next Gajim
Consensus that we need to determine how widely XEP-0203 is
deployed before changing this to Obsolete.
This in favor of XEP-91, right? I know XEP-0146 depends on it since
recently, but that can be changed to XEP-91.
cheers,
Remko
On Thu, Oct 9, 2008 at 8:22 AM, Remko Tronçon [EMAIL PROTECTED] wrote:
Consensus that we need to determine how widely XEP-0203 is
deployed before changing this to Obsolete.
This in favor of XEP-91, right? I know XEP-0146 depends on it since
recently, but that can be changed to XEP-91.
On Thu Oct 9 07:34:02 2008, Yann Leboulanger wrote:
Eric Will wrote:
On Oct 8, 2008, at 4:22 PM, Peter Saint-Andre wrote:
5c. XEP-0091: Delayed Delivery
Consensus that we need to determine how widely XEP-0203 is
deployed before changing this to Obsolete.
Not that I'm important, but
On Thu Oct 9 00:07:03 2008, Brett Zamir wrote:
Greetings!
Was item #18 on the agenda, re: conflicting examples in the way the
IQ type attribute is used in Jabber Search (0055) and Result Set
Management (0059) tabled to another meeting?
Since we now have a British chair, it's no longer
Peter Saint-Andre wrote:
Brett Zamir wrote:
In Jabber Search, iq type=set is used to submit a search form whereas
in the examples in 0059, the type used--also using the jabber:iq:search
namespace--is 'get'.
The Core spec defines an iq type 'get' stanza as a request for
information or
Brett Zamir wrote:
But I'm still curious about how a Jabber Search search
provides required
data, sets new values, or replaces existing values if it is to match
the description of iq type=set in the Core spec.
It provides data that is required for a search operation to occur, e.g.
please
Am 08.10.2008 um 22:22 schrieb Peter Saint-Andre:
7. XEP-0085: Chat State Notifications
Consensus to issue Call for Experience in preparation for advancing
this
Standards Track XEP to Final.
Uhm, I think there should be one change before it gets final:
Currently, determining support is
On Oct 8, 2008, at 4:22 PM, Peter Saint-Andre wrote:
5c. XEP-0091: Delayed Delivery
Consensus that we need to determine how widely XEP-0203 is
deployed before changing this to Obsolete.
Not that I'm important, but I implemented XEP-0203 in synapse.
--
Peter Saint-Andre
Greetings!
Was item #18 on the agenda, re: conflicting examples in the way the IQ
type attribute is used in Jabber Search (0055) and Result Set Management
(0059) tabled to another meeting?
In Jabber Search, iq type=set is used to submit a search form whereas
in the examples in 0059, the
Brett Zamir wrote:
Greetings!
Was item #18 on the agenda, re: conflicting examples in the way the IQ
type attribute is used in Jabber Search (0055) and Result Set Management
(0059) tabled to another meeting?
Those seem to be typos in XEP-0059. Something else to fix. :)
In Jabber Search,
11 matches
Mail list logo
