Fix XEP-0068 reference

This commit is contained in:
Dave Cridland 2020-01-21 13:16:14 +00:00
parent 2af1cade8c
commit 8405123978
1 changed files with 1 additions and 1 deletions

View File

@ -51,7 +51,7 @@
<section1 topic="Protocol Elements"> <section1 topic="Protocol Elements">
<section2 topic="Querying"> <section2 topic="Querying">
<p>A text input field of <tt>{&ns;}fulltext</tt> is hereby defined for the 'urn:xmpp:mam:2' FORM_TYPE, as conforming to the syntax defined in &xep-0068;</p> <p>A text input field of <tt>{&ns;}fulltext</tt> is hereby defined for the 'urn:xmpp:mam:2' FORM_TYPE, as conforming to the syntax defined in &xep0068;</p>
</section2> </section2>
<section2 topic="Results"> <section2 topic="Results">
<p>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.</p> <p>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.</p>