I'm very much in favor of not applying changes to the 2019 suite that can wait for the 2020 edition.
On Thu, 7 Mar 2019 at 08:39, Daniel Gultsch <[email protected]> wrote: > Am Mi., 6. März 2019 um 21:07 Uhr schrieb Georg Lukas <[email protected]>: > > Example 1: "Modern" Use of OOB for Inline Images > > <message from='[email protected]/secondwitch' type='groupchat'> > > <body>https://xmpp.org/theme/images/xmpp-logo.svg</body> > > <x xmlns='jabber:x:oob'> > > <url>https://xmpp.org/theme/images/xmpp-logo.svg</url> > > </x> > > </message> > > > > While XEP-0066 is less than ideal for the purpose of embedding images, > > and the body=url requirement isn't written down anywhere, it is > > something that client developers should know about, at least to > > implement it on the receiving side. > > Independently of whether or not you want the Compliance Suite to > become a document describing the quirks of a particular client (which > I don’t think is a good idea) I'd wait with those modifications for > the 2020 compliance suite. > Just get the 2019 out now and then start working on 2020. > > That’s the thing about the compliance suites. There will always be one > more new thing that should be documented. But at some point we will > have to decide that we are done for the year. That's why we are > planning on doing this every year. > > For the future I'd actually suggest that we do some kind of 'feature > freeze' in ~October and then spend the remainder of the year clearing > up the wording and getting it to Draft. > > cheers > Daniel > _______________________________________________ > Standards mailing list > Info: https://mail.jabber.org/mailman/listinfo/standards > Unsubscribe: [email protected] > _______________________________________________ >
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
