Am Mi., 6. Nov. 2019 um 13:45 Uhr schrieb Georg Lukas :
>
> * Kevin Smith [2019-11-06 12:24]:
> > I think the addition of ’66 is well-intentioned, but jabber:x:oob
> > is underspecified (it defines a syntax, but semantics are
> > missing).
>
> I agree, but nobody has written down the semantics
* Kevin Smith [2019-11-06 12:24]:
> I think the addition of ’66 is well-intentioned, but jabber:x:oob
> is underspecified (it defines a syntax, but semantics are
> missing).
I agree, but nobody has written down the semantics yet, so there is no
place to link to. On the other hand, this
> On 23 Oct 2019, at 16:07, Jonas Schäfer (XSF Editor)
> wrote:
>
> This message constitutes notice of a Last Call for comments on
> XEP-0423.
>
> Title: XMPP Compliance Suites 2020
> Abstract:
> This document defines XMPP application categories for different use
> cases (Core, Web, IM, and
Hi goffi,
* goffi [2019-11-05 22:58]:
> I'm really busy these days and couldn't do an extensive review, but here is
> my feedback:
Thank you for your feedback!
> It's really chat focused, and I would like to see other categories, notably
> a "social" one. I would put there XEP-0277 as the bare
On 6 Nov 2019, at 13:57, Daniel Gultsch wrote:
>
> Am Mi., 6. Nov. 2019 um 13:45 Uhr schrieb Georg Lukas :
>>
>> * Kevin Smith [2019-11-06 12:24]:
>>> I think the addition of ’66 is well-intentioned, but jabber:x:oob
>>> is underspecified (it defines a syntax, but semantics are
>>>
(And this time I’ll remember to thank Georg for taking this on. Thanks Georg)
> On 6 Nov 2019, at 13:43, Georg Lukas wrote:
>
> * Kevin Smith [2019-11-06 12:24]:
>> I think the addition of ’66 is well-intentioned, but jabber:x:oob
>> is underspecified (it defines a syntax, but semantics are
Version 0.3.0 of XEP-0423 (XMPP Compliance Suites 2020) has been
released.
Abstract:
This document defines XMPP application categories for different use
cases (Core, Web, IM, and Mobile), and specifies the required XEPs
that client and server software needs to implement for compliance with
the
