-
Notifications
You must be signed in to change notification settings - Fork 2.5k
R11 #6104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This reverts commit 709fb56.
| ## References | ||
| **Intent Recognizer**: You can use Orchestrator as an intent recognizer with [Adaptive dialogs][6]. Using the same approach as in the dispatch scenario above in order to route to responses within your bot logic. | ||
|
|
||
| **Entity Extraction** is not supported yet. It is on the planning roadmap to add entity extraction in the future. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Entity Extraction is not supported yet but it is on the roadmap.
| * **Code First**: Orchestrator can be integrated into your code project by replacing LUIS for intent recognition such as for skill delegation or dispatching to subsequent language understanding services. See [Runtime Integration](#runtime-integration) section for more. | ||
| * [Bot Framework Composer][19]: Orchestrator can be selected as a recognizer within Bot Framework Composer. At this point there are limitations to using Orchestrator in Composer primarily around importing of existing models and tuning up recognition performance (* currently available only if the feature flag is enabled with Composer). | ||
|
|
||
| Thus, use of [BF command line tool][7] to prepare and optimize the model for your domain is required in most, if not all, use cases. To illustrate the workflow, here is a sample the end to end authoring experience: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
here is a sample of end to end authoring experience experience:
| 1. Author Intent-utterances example based .lu definition referred to as a *label file* using the Language Understanding practices as described in [Language Understanding][2] for dispatch (e.g. author .lu file or within the [Composer][3] GUI experience). | ||
| * Alternatively, [export][8] your LUIS application and [convert][9] to .lu format or [export][10] your QnA Maker KB to .qna format. | ||
| * See also the [.lu file format][21] to author a .lu file from scratch. | ||
| 2. Download Natural Language Representation ([NLR][20]) base Model (will be referred to as the *basemodel*) using the `bf orchestrator:basemodel:get` command. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Download Orchestrator base model using 'bf orchestrator:basemodel:get' ...
We no longer use NLR term..
| * Alternatively, [export][8] your LUIS application and [convert][9] to .lu format or [export][10] your QnA Maker KB to .qna format. | ||
| * See also the [.lu file format][21] to author a .lu file from scratch. | ||
| 2. Download Natural Language Representation ([NLR][20]) base Model (will be referred to as the *basemodel*) using the `bf orchestrator:basemodel:get` command. | ||
| * See `bf orchestrator:basemodel:list` for alternate models. You may need to experiment with the different models to find which performs best for your language domain. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might want to link to aka.ms/nlrmodels (the page Cez worked on with description to different models)
Fixes #
Proposed Changes
Testing