On Wed Aug 10 03:01:20 2011, Matthew Wild wrote:
That makes perfect sense, but I guess my mental block is... isn't
that
what PEP is for?
+1
You're not engaged in a meeting on one client, but not on another, so
I don't see the benefit of a presence/ stanza indicator here.
Whereas #4 is
On Tue, 2011-08-09 at 20:41 -0600, Peter Saint-Andre wrote:
On 8/9/11 8:01 PM, Matthew Wild wrote:
On 9 August 2011 20:19, Peter Saint-Andre stpe...@stpeter.im wrote:
On 8/9/11 4:59 PM, Matthew Wild wrote:
On 9 August 2011 18:53, Peter Saint-Andre stpe...@stpeter.im wrote:
I've had
On Wed Aug 10 03:41:40 2011, Peter Saint-Andre wrote:
I can't think of anything more appropriate for presence than
communication context. As RFC 6121 says:
Any extended content included in a presence stanza SHOULD
represent
aspects of an entity's availability for communication or
Am 10.08.2011 00:53, schrieb Peter Saint-Andre:
I've had several conversations recently with folks who indicate that
they'd like a presence extension for what we could call communication
context -- basically a machine-readable version of some of the strings
that go into thestatus/ element.
On 8/10/11 2:31 AM, Dave Cridland wrote:
On Wed Aug 10 03:41:40 2011, Peter Saint-Andre wrote:
I can't think of anything more appropriate for presence than
communication context. As RFC 6121 says:
Any extended content included in a presence stanza SHOULD represent
aspects of an
On Wed, 2011-08-10 at 09:34 -0600, Peter Saint-Andre wrote:
To my mind, PEP is for everything else -- tunes, activities,
location,
and other things that change more or less frequently than presence
itself.
(As I'm about to hit send, I've seen Ralph's note arrive - +1 to
everything in
On Wed Aug 10 16:34:28 2011, Peter Saint-Andre wrote:
(As I'm about to hit send, I've seen Ralph's note arrive - +1 to
everything in that,
Perhaps in rfc6121bis we should remove show/ and status/ then?
;-)
Many of the usages we encounter with those are indeed unfortunate, in
particular
I've had several conversations recently with folks who indicate that
they'd like a presence extension for what we could call communication
context -- basically a machine-readable version of some of the strings
that go into the status/ element. Examples might include:
1. in-a-meeting (could be IRL
On 9 August 2011 18:53, Peter Saint-Andre stpe...@stpeter.im wrote:
I've had several conversations recently with folks who indicate that
they'd like a presence extension for what we could call communication
context -- basically a machine-readable version of some of the strings
that go into the
On 8/9/11 4:59 PM, Matthew Wild wrote:
On 9 August 2011 18:53, Peter Saint-Andre stpe...@stpeter.im wrote:
I've had several conversations recently with folks who indicate that
they'd like a presence extension for what we could call communication
context -- basically a machine-readable version
On 9 August 2011 20:19, Peter Saint-Andre stpe...@stpeter.im wrote:
On 8/9/11 4:59 PM, Matthew Wild wrote:
On 9 August 2011 18:53, Peter Saint-Andre stpe...@stpeter.im wrote:
I've had several conversations recently with folks who indicate that
they'd like a presence extension for what we could
On 8/9/11 8:01 PM, Matthew Wild wrote:
On 9 August 2011 20:19, Peter Saint-Andre stpe...@stpeter.im wrote:
On 8/9/11 4:59 PM, Matthew Wild wrote:
On 9 August 2011 18:53, Peter Saint-Andre stpe...@stpeter.im wrote:
I've had several conversations recently with folks who indicate that
they'd
12 matches
Mail list logo
