Skip to content
This repository was archived by the owner on Jan 15, 2025. It is now read-only.

Commit 0f77ec9

Browse files
authored
Merge branch 'master' into vishwac/model-as-feature
2 parents d97ab3b + 7837b71 commit 0f77ec9

File tree

11 files changed

+1098
-227
lines changed

11 files changed

+1098
-227
lines changed
Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
# Creating LUIS JSON model file
2+
3+
Once you have created individual .lu files you can parse them all to a LUIS JSON model using this command:
4+
```bash
5+
> bf luis:convert --in <folder with .lu files> --out <outputfolder> --name <luisAppName> --culture <luisAppCulture>]
6+
```
7+
8+
This will parse all .lu files found and will create **ONE** LUIS JSON model.
9+
10+
If you would like to create multiple luis apps, then you can add a [root.lu file](../examples/en-us/root.lu) that holds reference to other relevant .lu files and parse it like this:
11+
12+
```bash
13+
> bf luis:convert --in <root_file.lu> [--out <outputFolder> --name <luisAppName> --culture <luisAppCulture>]
14+
```
15+
16+
This will parse all .lu files referenced in the root_file.lu and output **ONE** LUIS JSON model.
17+
18+
# Creating a New LUIS App
19+
## using command line
20+
You can use the new LUIS JSON file to create a new LUIS application using this command.
21+
```bash
22+
luis import application --in _LUISApp.json --authoringKey "" --endpoint ""
23+
```
24+
Note: You can install LUIS CLI from [here](../../LUIS). If you are using LUIS CLI, you might see the option to provide a versionId, application name directly in the LUIS CLI. You can also provide this information to the Ludown tool to generate your LUIS JSON model as well. Information explicitly specified in the LUIS CLI will override any information captured by Ludown tool.
25+
26+
## using [LUIS](http://luis.ai) portal
27+
- Navigate to [LUIS](http://luis.ai)
28+
- Sign in
29+
- Click on My apps
30+
- "Import new App"
31+
- Choose file -> select the _LUISApp.json generated by LUDown tool
Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
# Creating QnA Maker JSON model file
2+
3+
Once you have created individual .lu files you can parse them all to a QnA Maker JSON model using this command:
4+
```bash
5+
> bf qnamaker --in <folder with .lu files> [--out <outputfolder> --name <QnAKBName>]
6+
```
7+
8+
This will parse all .lu files found and will create **ONE** QnA Maker JSON model.
9+
10+
If you would like to create multiple QnA Maker KB's, then you can add a [root.lu file](../examples/en-us/root.lu) that holds reference to other relevant .lu files and parse it like this:
11+
12+
```bash
13+
> bf qnamaker --in <root_file.lu> [-o <outputFolder> -n <QnAKBName> --log]
14+
```
15+
16+
This will parse all .lu files referenced in the root_file.lu and output **ONE** QnA Maker JSON model.
17+
18+
# Creating word alterations/ synonyms list
19+
You can use ludown to parse and compile all word alterations/ synonyms list that can then be used to replace your existing [QnA Maker alterations](https://westus.dev.cognitive.microsoft.com/docs/services/5a93fcf85b4ccd136866eb37/operations/5ac266295b4ccd1554da75fd) list.
20+
21+
See [here](lu-file-format.md#QnA-Maker-alterations) for defining word alterations/ synonyms list in .lu files.
22+
23+
```bash
24+
> bf qnamaker --alterations --in <root_file.lu> [-o <outputFolder> -n <QnAKBName> --log]
25+
```
26+
27+
# Creating a new QnAMaker KB
28+
29+
```bash
30+
> bf qnamaker:create:kb --in _qnaKB.json --subscriptionKey <key> --hostname <url> --endpointKey <key>
31+
```
32+
33+
# Replacing QnA Maker word alterations/ synonyms list
34+
35+
```bash
36+
> qnamaker:replace:alterations --in _Alterations.json --subscriptionKey <key> --hostname <url> --endpointKey <key>
37+
```
38+

0 commit comments

Comments
 (0)