Re: [Standards] Comments on XEP-0301 (possible impact on -0308 in Section 4.2.3)

2012-08-03 Thread Paul E. Jones
Peter, > > Section 4.2.3 > > > > XEP-0308 specifies use of "id" in and . Could we > > not just use "" along with ""? It would require some > > text in > > XEP-0308 that says that if is received without , it > > shall be ignored. In -0301, it would not be ignored. "id" works, but > > I would

Re: [Standards] Comments on XEP-0301 (possible impact on -0308 in Section 4.2.3)

2012-08-03 Thread Peter Saint-Andre
On 8/3/12 2:54 PM, Paul E. Jones wrote: > Mark, et al, > > I re-read the draft and here are my comments. Thanks for the review. Paul, I agree with your comments, and I have a few further thoughts here and there... > Section 4.2.1: > > Why is "seq" only 31 bits? Since the same memory is consu

[Standards] Comments on XEP-0301 (possible impact on -0308 in Section 4.2.3)

2012-08-03 Thread Paul E. Jones
Mark, et al, I re-read the draft and here are my comments. After I wrote all of this, I thought it sounds like I'm pounding on everything. Overall, the text was great.. it has come a long way. That said, here are my comments and questions: Section 1: "and is favored by deaf and hard of hearing

Re: [Standards] LAST CALL: XEP-0308 (Last Message Correction)

2012-08-03 Thread Kurt Zeilenga
On Jul 31, 2012, at 1:52 PM, XMPP Extensions Editor wrote: > This message constitutes notice of a Last Call for comments on XEP-0308 (Last > Message Correction). > > Abstract: This specification defines a method for marking a message as a > correction of the last sent message. Edit suggestio

Re: [Standards] FW: pubsub question related to notification events

2012-08-03 Thread Peter Saint-Andre
On 8/3/12 9:47 AM, Todd Herman wrote: > I apologize that I didn't realize there was a separate pubsub list. I will > see if I can jump on to it. No worries. We have a big backlog of mostly small fixes to XEP-0060, and this bug is one of them. I suggest that we spend some focused time on the pu

Re: [Standards] FW: pubsub question related to notification events

2012-08-03 Thread Peter Saint-Andre
On 8/3/12 9:44 AM, Tuomas Koski wrote: > Hi Todd, > > On 3 August 2012 17:16, Todd Herman wrote: >>> I have been reviewing XEP-0060 (pubsub) and have come across something that >>> is bothering me. >> >>> Throughout the document, notification events are highlighted and discussed. >>> The events c

Re: [Standards] FW: pubsub question related to notification events

2012-08-03 Thread Todd Herman
> -Original Message- > From: Peter Saint-Andre [mailto:stpe...@stpeter.im] > Sent: Friday, August 03, 2012 11:36 AM > To: XMPP Standards > Cc: Todd Herman > Subject: Re: [Standards] FW: pubsub question related to notification events > > On 8/3/12 9:16 AM, Todd Herman wrote: > >>I have been

Re: [Standards] FW: pubsub question related to notification events

2012-08-03 Thread Tuomas Koski
Hi Todd, On 3 August 2012 17:16, Todd Herman wrote: >>I have been reviewing XEP-0060 (pubsub) and have come across something that >> is bothering me. > >>Throughout the document, notification events are highlighted and discussed. >> The events come as a Message element with a child Event element

Re: [Standards] FW: pubsub question related to notification events

2012-08-03 Thread Peter Saint-Andre
On 8/3/12 9:16 AM, Todd Herman wrote: >>I have been reviewing XEP-0060 (pubsub) and have come across something > that is bothering me. > > > >>Throughout the document, notification events are highlighted and > discussed. The events come as a Message element with a child Event > element that is

[Standards] FW: pubsub question related to notification events

2012-08-03 Thread Todd Herman
>I have been reviewing XEP-0060 (pubsub) and have come across something that is >bothering me. >Throughout the document, notification events are highlighted and discussed. >The events come as a Message element with a child Event element that is in the >jabber.org/protocol/pubsub#event >namespa