From 2af1cade8c33530951cde41acfa4bd5bfc5b840d Mon Sep 17 00:00:00 2001 From: Dave Cridland Date: Tue, 21 Jan 2020 09:43:33 +0000 Subject: [PATCH] ProtoXEP: Full Text Search in MAM --- inbox/fulltext.xml | 81 ++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 81 insertions(+) create mode 100644 inbox/fulltext.xml diff --git a/inbox/fulltext.xml b/inbox/fulltext.xml new file mode 100644 index 00000000..bd984698 --- /dev/null +++ b/inbox/fulltext.xml @@ -0,0 +1,81 @@ + + +%ents; + + +]> + + +
+ Full Text Search in MAM + This specification proposes a field in the MAM form for full text searching. + &LEGALNOTICE; + XXXX + ProtoXEP + Standards Track + Standards + + XMPP Core + XEP-0313 + + + + fulltextmam + &dcridland; + + 0.0.1 + 2020-01-21 + dwd + +
    +
  • Initial Revision
  • +
+
+
+
+ + +

&xep0313; has an extensible form. This specification extends the extensible form with an extension which extends MAM to perform full text searching. A number of existing implementations of this extension exist - extending their existing extensions to confirm to the extension in this specification now it exists is intended to be trivial.

+
+ + + +

Support for this protocol is advertised by the Service Discovery protocol defined in &xep0030; using a feature + of &ns;.

+
+ +

Searching using full text is performed by the client supplying an additional text key, which if non-empty is used as input to a full text search of some form. The precise meaning of this field is left entirely implementation-defined at this time. Future revisions of this specification might impose additional constraints.

+
+
+ + + +

A text input field of {&ns;}fulltext is hereby defined for the 'urn:xmpp:mam:2' FORM_TYPE, as conforming to the syntax defined in &xep-0068;

+
+ +

The precise matching of the supplied text string is left implementation-defined. Servers MAY use any full-text search engine. While this might mean that certain characters are deemed "special", clients are RECOMMENDED not to attempt any support for these, as they are unlikely to be portable between implementations. A conformant implementation of this protocol could be made, therefore, by accepting any string in the text field and returning nothing (or everything). Any server developer implementing this protocol in such a way MUST buy beers for everyone.

+
+
+ + +

Not sure this is needed at all.

+
+ + +

None?

+
+ + +

This XEP requires no interaction with &IANA;.

+
+ + +

Registration of the field pointing to this document.

+
+ + +

Guus der Kinderen nudged me into doing this.

+
+ +