Re: [Standards] LAST CALL: XEP-0423 (XMPP Compliance Suites 2020)
Hi! I'm not quite happy with the fact that an advanced mobile client must support push. While I understand the rationale behind this (*cough* iOS *cough*), I dislike the fact that in order to be considered an advanced client, the client MUST depend on a centralized push service (for example Google GCM/Firebase/whatever it is called nowadays). I can only speak for my own experiences, but I never had issues with battery life without Google services. Paul Wed Oct 23 17:07:41 GMT+02:00 2019 Jonas Schäfer (XSF Editor) : > 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 Mobile), and specifies the required XEPs > that client and server software needs to implement for compliance with > the use cases. > > URL: https://xmpp.org/extensions/xep-0423.html > > This Last Call begins today and shall end at the close of business on > 2019-11-06. > > Please consider the following questions during this Last Call and send > your feedback to the standards@xmpp.org discussion list: > > 1. Is this specification needed to fill gaps in the XMPP protocol > stack or to clarify an existing protocol? > > 2. Does the specification solve the problem stated in the introduction > and requirements? > > 3. Do you plan to implement this specification in your code? If not, > why not? > > 4. Do you have any security concerns related to this specification? > > 5. Is the specification accurate and clearly written? > > Your feedback is appreciated! > ___ > Standards mailing list > Info: https://mail.jabber.org/mailman/listinfo/standards > Unsubscribe: standards-unsubscr...@xmpp.org > ___ > ___ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org ___
Re: [Standards] LAST CALL: XEP-0423 (XMPP Compliance Suites 2020)
Thanks for the effort to push this well before the end of the year. :) On my first reading, I noticed two things: XEP-0385 "Stateless Inline Media Sharing (SIMS)" is mentioned both in section 1.1 "Changes since 2019", but also in section 3 "Future Development". Is that an error, or intended? I'd argue that if you're including something in this edition of the CS, then there's no point of adding it also as a 'keep an eye on this one for the future' I am surprised to see XEP-0392 "Consistent Color Generation" in the CS. What's the rationale to include it? Without giving this to much thought, I've regarded this XEP more as a useful guide for those who'd explicitly choose to implement a, rather than something that is required to implement to be considered 'compliant'. I'm expecting that there are projects that explicitly not want this (in favor of marketing-driven decisions on look-and-feel, themes, colors, etc). Is the functionality described this XEP of such a nature that we'd be willing to mandate it? Regards, Guus On Wed, 23 Oct 2019 at 17:07, Jonas Schäfer 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 Mobile), and specifies the required XEPs > that client and server software needs to implement for compliance with > the use cases. > > URL: https://xmpp.org/extensions/xep-0423.html > > This Last Call begins today and shall end at the close of business on > 2019-11-06. > > Please consider the following questions during this Last Call and send > your feedback to the standards@xmpp.org discussion list: > > 1. Is this specification needed to fill gaps in the XMPP protocol > stack or to clarify an existing protocol? > > 2. Does the specification solve the problem stated in the introduction > and requirements? > > 3. Do you plan to implement this specification in your code? If not, > why not? > > 4. Do you have any security concerns related to this specification? > > 5. Is the specification accurate and clearly written? > > Your feedback is appreciated! > ___ > Standards mailing list > Info: https://mail.jabber.org/mailman/listinfo/standards > Unsubscribe: standards-unsubscr...@xmpp.org > ___ > ___ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org ___
[Standards] LAST CALL: XEP-0423 (XMPP Compliance Suites 2020)
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 Mobile), and specifies the required XEPs that client and server software needs to implement for compliance with the use cases. URL: https://xmpp.org/extensions/xep-0423.html This Last Call begins today and shall end at the close of business on 2019-11-06. Please consider the following questions during this Last Call and send your feedback to the standards@xmpp.org discussion list: 1. Is this specification needed to fill gaps in the XMPP protocol stack or to clarify an existing protocol? 2. Does the specification solve the problem stated in the introduction and requirements? 3. Do you plan to implement this specification in your code? If not, why not? 4. Do you have any security concerns related to this specification? 5. Is the specification accurate and clearly written? Your feedback is appreciated! ___ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org ___
[Standards] Council Voting Summary 2019-10-22
2019-09-25 (expired 2019-10-09)
FAILED (-1:4:+0) PR #824 - XEP-0060: Add pubsub#public in Publish-Subscribe
features - https://github.com/xsf/xeps/pull/824
PASSED (-0:0:+5) PR #834 - XEP-0410: treat remote-server-{not-found,timeout}
like timeout - https://github.com/xsf/xeps/pull/834
VETOED (-2:3:+0) Proposed XMPP Extension: Authorization Tokens -
https://xmpp.org/extensions/inbox/auth-tokens.html
2019-10-02 (expired 2019-10-16)
PASSED (-0:1:+4)
Proposed XMPP Extension: Message Moderation -
https://xmpp.org/extensions/inbox/message-moderation.html
Dave: [abstained]
Georg: +1 (useful addition, and we can figure out the right wire-format; assume
actually means and not from 0359)
Jonas: +1 (what Georg says)
Kev: +1 (the part about iq ordering is often a nuisance server-side when there
are unnecessary constraints on ordering, and this one doesn't seem needed)
Link: +1 (useful addition and properly specified)
2019-10-09 (expiring 2019-10-23)
PASSED (-0:0:+5)
Proposed XMPP Extension: Message Retraction -
https://xmpp.org/extensions/inbox/message-retraction.html
Dave: +1 (willing to be told I'm wrong later)
Georg: +1 (useful addition, and we can figure out the right wire-format; assume
actually means and not from 0359)
Jonas: +1 (what Georg says)
Kev: +1
Link: +1 (useful addition and properly specified)
VETOED (-5:0:+0)
PR #840 - XEP-0060: Clarify unlimited behaviour for node config -
https://github.com/xsf/xeps/pull/840
Dave: -1 (having "-1" or empty seems sane for unlimited, but not novel unicode
glyphs)
Georg: -1 (agree with Dave; also don't understand the implied semantics of that
value)
Jonas: -1 (text needs to be clearer on the actual value for "use the server
limit")
Kev: -1 (for untypable glyphs in particular)
Link: -1 (indicating an arbitrarily high value wouldn't be nice)
2019-10-16 (expiring 2019-10-30)
Last Call: XEP-0423 (XMPP Compliance Suites 2020) -
https://xmpp.org/extensions/xep-0423.html
Dave: [pending]
Georg: +1
Jonas: +1
Kev: +1
Link: +1
Advance to Draft: XEP-0292 (vCard4 Over XMPP) -
https://xmpp.org/extensions/xep-0292.html
Dave: [pending]
Georg: [on-list]
Jonas: [on-list]
Kev: [on-list] (feels like we've done this already)
Link: [on-list] (will have to gather data about has been done and what should
be done)
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___
[Standards] Council Minutes 2019-10-16
http://logs.xmpp.org/council/2019-10-16?p=h#2019-10-16-19ada475330fcce4 Georg appears to be here, as do Link, Jonas, and Kev. Kev thinks the only thing for today is the CS-2020 Last Call; Georg points out the vote on Message Moderation, which expires today. Kev attempts to get the voting in motion; Georg requests making the meeting structure more formal. There is an informal commotion. Jonas takes the opportunity to seize The Chair. 1) Roll Call Here: Kev, Link, Jonas, Georg Elsewhere: Dave 2) Agenda Bashing Jonas notes the LC for CS-2020; Georg adds the upcoming DST change as AOB. 3a) Last Call: XEP-0423 (XMPP Compliance Suites 2020) - https://xmpp.org/extensions/xep-0423.html Kev: +1 Link: +1 Jonas: +1 Georg: +1 Dave: [pending] 3b) Advance to Draft: XEP-0292 (vCard4 Over XMPP) - https://xmpp.org/extensions/xep-0292.html Pep notes this has been Proposed since February - Jonas thinks it only had a single bit of feedback, which was mostly "this looks good" - Zash notes that there was discussion prior to the LC, but is unsure whether it lead to changes. Georg: [on-list] Jonas: [on-list] Link: [on-list] (will have to gather data about what has been done and what should be done) Kev: [on-list] (feels like we've done this already) Dave: [pending] 4) Date of Next 2019-10-23 1500 UTC Kev won't be able to make it. 5a) AOB i DST change (EU: Oct 27th; US: Nov 3rd) Kev suggests SOP (Standard Operating Procedure) that Council is pinned to European DST. Jonas notes that Council members are in UK, France, and Germany, all of which are subject to EU DST - so the meeting time will be moved to 1600 UTC, starting October 30th. 5b) AOB ii Link asks Council not to formalise formalism for the sake of formally formalising formal formalism for formalism's sake - Georg apologises. Jonas doesn't have a strong opinion, but felt it was the easiest way to break out of the meta discussion earlier. Link just felt that things had already started. Kev was trying to the meeting done quickly to have time to review CS-2020. Jonas apologises for stealing the chair. 6) Eaty Meaty East Thanks all. Georg wanted to vote on Message Moderation - Link notes he can still do so on-list, and will do the same. Everyone debates what "close of business" actually means. WRT 3b, Zash notes https://mail.jabber.org/pipermail/standards/2019-January/035714.html ___ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org ___
