Operators include:

"sameTerm"

Match triple index values which are the same RDF term as $value. This compares aspects of values that are ignored in XML Schema comparison semantics, like timezone and derived type of $value.

"<"

Match range index values less than $value.

"<="

Match range index values less than or equal to $value.

">"

Match range index values greater than $value.

">="

Match range index values greater than or equal to $value.

"="

Match range index values equal to $value.

"!="

Match range index values not equal to $value.

Options include:

"order-pso"

Return results ordered by predicate, then subject, then object.

"order-sop"

Return results ordered by subject, then object, then predicate.

"order-ops"

Return results ordered by object, then predicate, then subject.

"quads"

Return quads that include values for the named graph that the triples are in. Requires the collection lexicon enabled.

"any"

Values from any fragment should be included.

"document"

Values from document fragments should be included.

"properties"

Values from properties fragments should be included.

"locks"

Values from locks fragments should be included.

"fragment-frequency"

Frequency should be the number of fragments with an included value. This option is used with cts:frequency.

"item-frequency"

Frequency should be the number of occurences of an included value. This option is used with cts:frequency. To get accurate results from item-frequency with cts:triples, enable the triple positions index.

"checked"

Word positions should be checked when resolving the query.

"unchecked"

Word positions should not be checked when resolving the query.

"too-many-positions-error"

If too much memory is needed to perform positions calculations to check whether a document matches a query, return an XDMP-TOOMANYPOSITIONS error, instead of accepting the document as a match.

"eager"

Perform work concurrently whilst returning triples from the index - buffering some results into memory. This usually takes the shortest time when returning a complete result.

"lazy"

Perform only some the work concurrently before returning the first triple from the index, and most of the work sequentially while iterating through the rest of the triples. This usually takes the shortest time when returning a partial result.

"concurrent"

Perform the work concurrently in another thread. This is a hint to the query optimizer to help parallelize the lexicon work, allowing the calling query to continue performing other work while the lexicon processing occurs. This is especially useful in cases where multiple lexicon calls occur in the same query (for example, resolving many facets in a single query).