Skip to content

Main content

Query Stopword Policy Flag

Apply an explicit exact-token stopword policy without language detection, case folding, or tokenization.

Loading tool…

Description

Apply a supplied stopword-list membership policy to one token.

Information records distinguish identifiers, controlled vocabularies, language fallbacks, assertion times and valid times. A supplied inverse predicate differs from an inferred semantic relation. Text offsets require an explicit code-point or code-unit basis, and a metadata count check does not validate field content or an entire schema.

Apply a supplied stopword-list membership policy to one token.

When to use this tool

Use Query Stopword Policy Flag when you already have token, suppliedStopwords, removeListed and need to apply a supplied stopword-list membership policy to one token.

How to use the tool and how it works

  1. Enter token, suppliedStopwords, removeListed. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read listed, retained. Inspect listed, retained before interpreting the associated values.

Return listed for literal membership; retained means !removeListed || !listed.1

Input fieldMeaning and unitsAccepted input
tokenTokenRequired. Text; maximum UTF-16 length 8192.
suppliedStopwordsLiteral tokens, allowing empty text; no normalization, language model or case folding.Required. Array of text; maximum UTF-16 length 8192; maximum items 256.
removeListedRemove ListedRequired. Boolean.
Output fieldInterpretationReturned shape
listedListedRequired. Boolean.
retainedRetainedRequired. Boolean.
json
{
  "input": {
    "token": "the",
    "suppliedStopwords": [
      "the",
      "a"
    ],
    "removeListed": true
  },
  "output": {
    "listed": true,
    "retained": false
  }
}

Limitations and assumptions

  • Empty text and repeated list entries are allowed; no tokenization, case folding, language rule or full query normalization is performed.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.

Alternative or Complementary methods

Use the actual record, vocabulary authority and complete metadata schema for semantic or conformance questions. Apply the identifier scheme's real comparison rules and the intended language/offset policy rather than inferring them from a local string operation.

References

  1. Calculation and input contract: information-science/query-stopword-policy-flag — tool.io

Similar or alternative tools