Marker type for built-in combinators.
A context that can be passed passed into the callback of the matched intent.
Main entry point for intent-based user input matcher.
Convenient adapter for conversational unordered intent.
An intent is a collection of terms defining a formal template for user input.
Convenient adapter for non-conversational unordered intent.
Declarative predicate over
Term is a building block of the intent.
XNOR (exclusive NOR)-combinator.
XOR (exclusive OR)-combinator.
Control flow exception to skip current intent.
Annotation to define an intent on the method serving as its callback.
Annotations referencing an intent defined externally.
Annotation to mark callback parameter to receive term's tokens.
Intent-based input matcher (or solver) is intended for simpler and more declarative implementation of model's
method. This is the main method in the data model and it is responsible for converting parsed user input into an action.
It cannot be defined in the external JSON or YAML model definition and, therefore, has to be defined in the code.
Although this method can be implemented manually by encoding the logic of parsing query context and its list of
parsing variants - it is often more complex and error-prone than necessary.
Intent solver is based on an idea of adding one or more user input templates, also
intents, and letting the solver select the best
matching intent for a given the user input. Each intent defines a pattern of the user input and associated action
to take when that pattern is selected. While selecting the best matching intent the solver uses sophisticated NLP
analysis and conversation context for anaphoras resolution. Among multiple detected intents the solver will always
select the most specific one.
Copyright © 2013-2019 NLPCraft Project. All rights reserved.