Section 6 of XEP-0001 states in part:
**
If an Experimental XEP is inactive (i.e., no updated versions are
published) for a period of six (6) months, the XMPP Extensions Editor
shall automatically change the status of the XEP to Deferred unless it
is in the queue of XEPs under active consider
Robert Quattlebaum wrote:
> On Jan 30, 2008, at 11:22 AM, Greg Hudson wrote:
>
>> On Wed, 2008-01-30 at 19:16 +, Alexander Jones wrote:
I have a few implementation observations with respect to Jingle. The
current implementation really requires all Jingle stuff to be managed
cent
Version 0.2 of XEP-0221 (Data Forms Media Element) has been released.
Abstract: This specification defines an XMPP protocol extension for including
media data in XEP-0004 data forms.
Changelog: [See revision history] (psa)
Diff:
http://svn.xmpp.org:18080/browse/XMPP/trunk/extensions/xep-0221.x
On Jan 30, 2008, at 6:08 PM, Greg Hudson wrote:
On Wed, 2008-01-30 at 17:53 -0800, Robert Quattlebaum wrote:
What if these plug-ins are actually separate processes? Imagine if
you
were using some sort of XMPP client daemon, for example. In such a
setup, you would have separate processes for
On Wed, 2008-01-30 at 17:53 -0800, Robert Quattlebaum wrote:
> What if these plug-ins are actually separate processes? Imagine if you
> were using some sort of XMPP client daemon, for example. In such a
> setup, you would have separate processes for file transfer,
> audio/video chat, roster, etc.
On Jan 30, 2008, at 11:22 AM, Greg Hudson wrote:
On Wed, 2008-01-30 at 19:16 +, Alexander Jones wrote:
I have a few implementation observations with respect to Jingle. The
current implementation really requires all Jingle stuff to be
managed
centrally in an app. For example, you need a "J
Daniel Henninger wrote:
> Hi folk!
>
> We have a need to connect multiple iterations of a component to the
> same JID.
Currently, XEP-0225 talks about the same component binding multiple
hostnames, but it does not talk about multiple components binding the
same hostname. Whether that is allowed
Ralph Meijer wrote:
> Hi,
>
> I am working on getting publish-subscribe collection nodes implemented
> in Idavoll. There are two ways to subscribe to a collection nodes using
> the 'pubsub#subscription_type' subscription configuration option: nodes
> and items.
>
> In the 'nodes' case, you get no
Nick Vidal wrote:
> Hi Peter and Kevin,
>
> In the spirit of illustrating a generic solution that would suit this
> specific question-and-answer pattern, I offer a simple example:
>
> - Peter creates a node called "philosophy" where he publishes all
> philosophical questions he has.
> - Some frie
Peter Saint-Andre wrote:
Lauri Kaila wrote:
A small note. When there already is a session, instead of normal IBB,
the payload could be carried inside info-messages. Maybe not a good
idea, but possible.
I hadn't considered that. Yes, it's possible. I was trying to keep
Jingle File Transfer as c
Version 0.1 of XEP-0233 (Use of Domain-Based Service Names in XMPP SASL
Negotiation) has been released.
Abstract: This specification defines a method by which a connection manager
associated with an XMPP server can inform a connecting client about its
domain-based service name.
Changelog: Init
Version 0.1 of XEP-0232 (Software Information) has been released.
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 including detailed data about
Version 0.1 of XEP-0231 (Data Element) has been released.
Abstract: This specification defines an XMPP protocol extension for including
small bits of binary data in an XML stanza.
Changelog: Initial published version. (psa)
Diff: N/A
URL: http://www.xmpp.org/extensions/xep-0231.html
Version 0.1 of XEP-0230 (Service Discovery Notifications) has been released.
Abstract: This specification defines a method for requesting and receiving
notifications regarding XMPP service discovery items.
Changelog: Initial published version. (psa)
Diff: N/A
URL: http://www.xmpp.org/extension
Version 1.2 of XEP-0118 (User Tune) has been released.
Abstract: This specification defines a payload format for communicating
information about music to which a user is listening, including the title,
track number, collection, performer, composer, length, and user rating. The
payload format is
Version 2.4 of XEP-0078 (Non-SASL Authentication) has been released.
Abstract: This document specifies a protocol for authentication with Jabber
servers and services using the jabber:iq:auth namespace. Note Well: The
protocol specified herein has been deprecated in favor of SASL authentication
Version 1.5 of XEP-0080 (User Location) has been released.
Abstract: This specification defines an XMPP protocol extension for
communicating information about the current geographical or physical location
of an entity.
Changelog: Added speed element. (jjh/psa)
Diff:
http://svn.xmpp.org:18080/
FYI.
Original Message
Date: Wed, 30 Jan 2008 13:21:58 -0700
From: Peter Saint-Andre <[EMAIL PROTECTED]>
To: XMPP Council <[EMAIL PROTECTED]>
Subject: [Council] meeting minutes, 2008-01-30
Results of the XMPP Council meeting held 2008-01-30...
Agenda:
http://www.jabber.org/coun
On Wed, 30 Jan 2008, Greg Hudson wrote:
On Wed, 2008-01-30 at 19:16 +, Alexander Jones wrote:
I have a few implementation observations with respect to Jingle. The
current implementation really requires all Jingle stuff to be managed
centrally in an app. For example, you need a "Jingle engin
On Wed, 2008-01-30 at 19:16 +, Alexander Jones wrote:
> > I have a few implementation observations with respect to Jingle. The
> > current implementation really requires all Jingle stuff to be managed
> > centrally in an app. For example, you need a "Jingle engine" that things
> > like file tra
On Wed, 2008-01-30 at 12:08 -0700, Peter Saint-Andre wrote:
> Here is some anonymous feedback I received in an IM conversation today:
>
> **
>
> I have a few implementation observations with respect to Jingle. The
> current implementation really requires all Jingle stuff to be managed
> cen
Here is some anonymous feedback I received in an IM conversation today:
**
I have a few implementation observations with respect to Jingle. The
current implementation really requires all Jingle stuff to be managed
centrally in an app. For example, you need a "Jingle engine" that things
like f
Hi Peter and Kevin,
In the spirit of illustrating a generic solution that would suit this
specific question-and-answer pattern, I offer a simple example:
- Peter creates a node called "philosophy" where he publishes all
philosophical questions he has.
- Some friends subscribe to it.
- Kevin publi
On Wed Jan 30 17:16:44 2008, Peter Saint-Andre wrote:
Kevin Smith wrote:
>> Perhaps I confused things by calling it "bleg". Qian called it
"Q-and-A"
>> before I changed the name to be more edgy.
> > Well, my inclination is that if you're interested enough to
answer,
> you're probably intere
Kevin Smith wrote:
>> Perhaps I confused things by calling it "bleg". Qian called it "Q-and-A"
>> before I changed the name to be more edgy.
>
> Well, my inclination is that if you're interested enough to answer,
> you're probably interested enough to see how it 'turns out', and so
> would want t
Ok, this one's definitely going to the list \o/
> >> No, but what I was meaning was that you don't gain anything from this
> >> xep, apart from that filtering - it's not clear to me really what the
> >> motivation is. To look at it another way, how do people want this to
> >> appear in a client? T
Kevin Smith wrote:
> -- Forwarded message --
> From: Peter Saint-Andre
>
>> Did you mean to send this to the list? :)
>
> Yes, yes I did.
Sorry, Kevin and I seem to have duelling mail settings so that when he
replies to my list posts, the mail goes to me and not to the list...
>
-- Forwarded message --
From: Peter Saint-Andre
>Did you mean to send this to the list? :)
Yes, yes I did.
Kevin Smith wrote:
>>> Perhaps someone could talk me through this one, please? The
>>> pep/message mix seems a bit peculiar to me, particularly as it seems
>>> to miss out o
Lauri Kaila wrote:
> A small note. When there already is a session, instead of normal IBB,
> the payload could be carried inside info-messages. Maybe not a good
> idea, but possible.
I hadn't considered that. Yes, it's possible. I was trying to keep
Jingle File Transfer as close as possible to XEP
29 matches
Mail list logo
