Skip to content
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

Add support for LUIS batch test format #35

Closed
rozele opened this issue Jul 1, 2019 · 0 comments · Fixed by #99
Closed

Add support for LUIS batch test format #35

rozele opened this issue Jul 1, 2019 · 0 comments · Fixed by #99

Comments

@rozele
Copy link
Contributor

rozele commented Jul 1, 2019

LUIS batch test format is slightly different than the generic utterance model. Namely:

{
    "intent": "<intent label>",
    "text": "<utterance text>",
    "entities": [
        {
            "entity": "<entity match text>",
            "startPos": <start pos>,
            "endPos": <end pos>
        }
    ]
}

So, "matchText" is replaced by "entity" and "matchIndex" is replaced by "startPos" and "endPos".

rozele added a commit to rozele/NLU.DevOps that referenced this issue Aug 8, 2019
Rather than specifying "text" for the generic utterance text, the generic utterance may now use "query", which aligns with the expected input for LUIS v3 requests.

Additionally, rather than requiring the "matchText" and "matchIndex" for each entity, the format now also supports the LUIS batch test format, which uses "startPos" and "endPos".

Fixes microsoft#35
rozele added a commit to rozele/NLU.DevOps that referenced this issue Aug 8, 2019
Rather than specifying "text" for the generic utterance text, the generic utterance may now use "query", which aligns with the expected input for LUIS v3 requests.

Additionally, rather than requiring the "matchText" and "matchIndex" for each entity, the format now also supports the LUIS batch test format, which uses "startPos" and "endPos".

Fixes microsoft#35
rozele added a commit to rozele/NLU.DevOps that referenced this issue Aug 8, 2019
Rather than specifying "text" for the generic utterance text, the generic utterance may now use "query", which aligns with the expected input for LUIS v3 requests.

Additionally, rather than requiring the "matchText" and "matchIndex" for each entity, the format now also supports the LUIS batch test format, which uses "startPos" and "endPos".

Fixes microsoft#35
rozele added a commit to rozele/NLU.DevOps that referenced this issue Aug 8, 2019
Rather than specifying "text" for the generic utterance text, the generic utterance may now use "query", which aligns with the expected input for LUIS v3 requests.

Additionally, rather than requiring the "matchText" and "matchIndex" for each entity, the format now also supports the LUIS batch test format, which uses "startPos" and "endPos".

Fixes microsoft#35
rozele added a commit to rozele/NLU.DevOps that referenced this issue Aug 8, 2019
Rather than specifying "text" for the generic utterance text, the generic utterance may now use "query", which aligns with the expected input for LUIS v3 requests.

Additionally, rather than requiring the "matchText" and "matchIndex" for each entity, the format now also supports the LUIS batch test format, which uses "startPos" and "endPos".

Fixes microsoft#35
rozele added a commit to rozele/NLU.DevOps that referenced this issue Aug 8, 2019
Rather than specifying "text" for the generic utterance text, the generic utterance may now use "query", which aligns with the expected input for LUIS v3 requests.

Additionally, rather than requiring the "matchText" and "matchIndex" for each entity, the format now also supports the LUIS batch test format, which uses "startPos" and "endPos".

Fixes microsoft#35
rozele added a commit to rozele/NLU.DevOps that referenced this issue Aug 8, 2019
Rather than specifying "text" for the generic utterance text, the generic utterance may now use "query", which aligns with the expected input for LUIS v3 requests.

Additionally, rather than requiring the "matchText" and "matchIndex" for each entity, the format now also supports the LUIS batch test format, which uses "startPos" and "endPos".

Fixes microsoft#35
rozele added a commit to rozele/NLU.DevOps that referenced this issue Aug 8, 2019
Rather than specifying "text" for the generic utterance text, the generic utterance may now use "query", which aligns with the expected input for LUIS v3 requests.

Additionally, rather than requiring the "matchText" and "matchIndex" for each entity, the format now also supports the LUIS batch test format, which uses "startPos" and "endPos".

Fixes microsoft#35
@rozele rozele closed this as completed in #99 Aug 8, 2019
rozele added a commit that referenced this issue Aug 8, 2019
Rather than specifying "text" for the generic utterance text, the generic utterance may now use "query", which aligns with the expected input for LUIS v3 requests.

Additionally, rather than requiring the "matchText" and "matchIndex" for each entity, the format now also supports the LUIS batch test format, which uses "startPos" and "endPos".

Fixes #35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant