Re: [Standards] LAST CALL: XEP-0402 (Bookmarks 2 (This Time it's Serious))

2020-01-29 Thread Daniel Gultsch
Am Mi., 29. Jan. 2020 um 16:34 Uhr schrieb Jonas Schäfer : > > This message constitutes notice of a Last Call for comments on > XEP-0402. > > Title: Bookmarks 2 (This Time it's Serious) > Abstract: > This specification defines a syntax and storage profile for keeping a > list of chatroom bookmarks

Re: [Standards] LAST CALL: XEP-0402 (Bookmarks 2 (This Time it's Serious))

2020-01-29 Thread Philipp Hörist
> 1. Is this specification needed to fill gaps in the XMPP protocol > stack or to clarify an existing protocol? > Yes > 2. Does the specification solve the problem stated in the introduction > and requirements? > It solves the problem described and introduces a new problem. Migration to this

Re: [Standards] Proposed XMPP Extension: Inbox

2020-01-29 Thread Florian Schmaus
On 1/26/20 8:45 PM, Maxime Buquet wrote: > On 2020/01/21, Jonas Schäfer wrote: >> The XMPP Extensions Editor has received a proposal for a new XEP. >> >> Title: Inbox >> Abstract: >> This specification proposes a mechanism by which clients can find a >> list of ongoing conversations and their

[Standards] UPDATED: XEP-0431 (Full Text Search in MAM)

2020-01-29 Thread XSF Editor
Version 0.2.0 of XEP-0431 (Full Text Search in MAM) has been released. Abstract: This specification proposes a field in the MAM form for full text searching. Changelog: * No More Beer * Quasi-normative language around syntactic implementation (dwd) URL: https://xmpp.org/extensions/xep-0431.html

Re: [Standards] LAST CALL: XEP-0402 (Bookmarks 2 (This Time it's Serious))

2020-01-29 Thread Sam Whited
I would like to mention again that as funny as the title is, we should stop this trend of putting silly things after the XEP title. They do not add value, they make it harder to cite (do I really have to write the joke after every single use of the title when referencing it from another XEP, for

[Standards] LAST CALL: XEP-0402 (Bookmarks 2 (This Time it's Serious))

2020-01-29 Thread XSF Editor
This message constitutes notice of a Last Call for comments on XEP-0402. Title: Bookmarks 2 (This Time it's Serious) Abstract: This specification defines a syntax and storage profile for keeping a list of chatroom bookmarks on the server. URL: https://xmpp.org/extensions/xep-0402.html This Last

[Standards] NEW: XEP-0430 (Inbox)

2020-01-29 Thread XSF Editor
Version 0.1.0 of XEP-0430 (Inbox) has been released. Abstract: This specification proposes a mechanism by which clients can find a list of ongoing conversations and their state. Changelog: Accepted by vote of Council on 2020-01-22. (XEP Editor (jsc)) URL:

[Standards] NEW: XEP-0431 (Full Text Search in MAM)

2020-01-29 Thread XSF Editor
Version 0.1.0 of XEP-0431 (Full Text Search in MAM) has been released. Abstract: This specification proposes a field in the MAM form for full text searching. Changelog: Accepted by vote of Council on 2020-01-22. (XEP Editor (jsc)) URL: https://xmpp.org/extensions/xep-0431.html Note: The

Re: [Standards] Council Minutes 2020-01-22

2020-01-29 Thread Dave Cridland
On Wed, 29 Jan 2020 at 08:27, Georg Lukas wrote: > * Tedd Sterr [2020-01-28 19:04]: > > 3a) Proposed XMPP Extension: Full Text Search in MAM - > https://xmpp.org/extensions/inbox/fulltext.html > > +1 this is a good first step, and I'm sure we can figure out the > remaining parts (like an

Re: [Standards] Council Minutes 2020-01-22

2020-01-29 Thread Kevin Smith
On 29 Jan 2020, at 08:27, Georg Lukas wrote: > > * Tedd Sterr [2020-01-28 19:04]: >> 3a) Proposed XMPP Extension: Full Text Search in MAM - >> https://xmpp.org/extensions/inbox/fulltext.html > > +1 this is a good first step, and I'm sure we can figure out the > remaining parts (like an

Re: [Standards] Council Minutes 2020-01-22

2020-01-29 Thread Georg Lukas
* Tedd Sterr [2020-01-28 19:04]: > 3a) Proposed XMPP Extension: Full Text Search in MAM - > https://xmpp.org/extensions/inbox/fulltext.html +1 this is a good first step, and I'm sure we can figure out the remaining parts (like an additional form field for "exact string match") on the go. > 3b)