Are spaces in the q parameter supposed to represent OR or AND?

[hrodmn]

I am having some trouble keeping track of the different specs so please bear with me!

It looks like OGC API - Features - Part 9: Text Search specifies that spaces between terms in the q parameter indicate an AND clause and that commas between terms indicate an OR clause, while the examples in the README here suggest that spaces will be interpreted as OR clauses. Is this the difference between the basic and the advanced free-text search implementations?

Also, does anyone know of an implementation that parses a q parameter into a regex?

[vincentsarago]

From https://docs.ogc.org/DRAFTS/24-031.html#q-parameter

Search terms that may appear together (logical OR) in a resource SHALL be separated by literal commas.

so q=ocean,beaches == ocean OR beaches

Search terms that must appear together, and in the order specified, in a resource SHALL be separated by one or more white space characters.

so q=ocean beaches == ocean AND beaches

from their examples

q=ocean,climate%20%09change,desalination

gives

(anytext CONTAINS 'ocean') OR
(anytext CONTAINS 'climate\s+change') OR
(anytext CONTAINS 'desalination')`

so from my understanding white spaces do not mean Logical AND but more that terms are together and do not mean

(anytext CONTAINS 'ocean') OR
((anytext CONTAINS 'climate') AND(anytext CONTAINS 'change'))OR
(anytext CONTAINS 'desalination')`