Language Understanding (LUIS)
Welcome to the LUIS API Forum
(Language Understanding Intelligent Service)
Categories
Documentation – Any ideas or suggestions for the API Reference or Documentation.
Language Support – Submit a request to have a particular language supported.
luis.ai WebApp – Ideas and suggestions for luis.ai and functionality used through the WebApp.
Programmatic API – Any ideas or feedback pertaining to features or enhancements to LUIS programmatic API.
Samples & SDK Request – Let us know if you would like to see a tutorial/sample or a SDK provided.
-
163 votes
Hello,
For LUIS, the current plan for language support is to extend the current language support to be at parity with our English language support.
For information about our current language support, please see: https://docs.microsoft.com/en-us/azure/cognitive-services/luis/luis-language-support.
Thanks,
Luke -
7 votes
Hello,
For LUIS, the current plan for language support is to extend the current language support to be at parity with our English language support.
For information about our current language support, please see: https://docs.microsoft.com/en-us/azure/cognitive-services/luis/luis-language-support.
Thanks,
Luke -
Description field in Custom Entities
When creating new custom Entities, it would be helpful if there was a description field for any additional notes. The description field would then show (i.e. title html attribute) when hovering over an Entity when labelling utterances in the Entity selection popup box.
2 votes -
Add security to LUIS applications so only trusted clients can make queries
It would be very useful to be able to create applications that are not publicly available. Our customers would not appreciate a public component as part of their solutions.
1 voteHello,
You can deploy LUIS with containers and have control over where the deployment occurs, and it will not be part of the shared runtime.
However, each application is not public, it will require a key to be accessed and is encrypted through Azure.
For more information, please see: https://docs.microsoft.com/en-us/azure/cognitive-services/luis/luis-container-howto.
Thanks,
Luke -
Bug: If you enter an utterance that has already been labeled
Just a minor bug: If you enter an utterance that has already been labeled, a message tells you "This utterance has already been labeled." But if you enter it again, the message goes away. Enter again, it comes back, and so on.
1 vote -
It would help if the entities were highlighted on the review labels page for "show all labeled utterances"
It would help if the entities were highlighted on the review labels page for "show all labeled utterances"
2 votesHello,
Entities are now highlighted on that page.
Thanks,
Luke -
Allow LUIS to detect multiple intents (complex intents) instead of just 1
For example:
I want to book a flight and reserve a seatI want to order a special meal and find out how many miles I will earn for this trip.
21 votesHello,
Multiple intent support will be released for Build. Please see: https://www.microsoft.com/en-us/build.
Thanks,
Luke -
Allow developers to programmatically retrieve the remaining quota for the API they are using
This should actually be applied across the board to all of the APIs
6 votesHello,
This is managed by Azure, and you can see it here: https://docs.microsoft.com/en-us/rest/api/compute/usage/list.
Thanks,
Luke -
Sharing LUIS Applications
It would be very useful to have the possibility to share a LUIS application with other users so they are also able to edit the settings, intents, entities, etc.
58 votesThis feature is now supported as collaborators, you can find the details about it here.
https://docs.microsoft.com/en-us/azure/cognitive-services/luis/luis-how-to-collaborate
-
Show the total number of utterances and most recent utterance received in the my applications view
In the My Applications view I'd like to see the last timestamp an utterance was received (helps to see which models are in active use) and the total number of utterances. Currently it shows the # of intents, entities, and some other info.
4 votesHello,
You can now sort by the number of endpoint hits.
Thanks,
Luke -
More than 10 entities
There should be more than 10 entities available for use, despite the availability of children for each entity.
This might actually be more constraining than the limitation of 10 intents
25 votesYou can now add up to 30 entities to a LUIS app.
-
Use of phrase lists eliminates child entities being reported
Phrase lists are very useful for cleaning up ambiguity in picking up entities, but also seem to cause any of their expressions to be picked up as a single entity type but without the child role.
5 votes -
Phrase list extension
The phrase lists are limited to only 10.
We need more
33 votesHello,
You can use a LUIS dispatch app or a LUIS container. For more information, please see: https://docs.microsoft.com/en-us/azure/cognitive-services/luis/luis-boundaries.
Thanks,
Luke -
API read and write needs to be unified
Token positions over character positions – one way or the other, not both when reading and writing.
And adding a space in our character is a pain.
6 votes -
Performance analysis should allow inspection of child entities
It would be very useful if the performance analysis allowed the inspection and potential intersection of child entities rather than just parent entities. At the moment, this prevents analysis and correction of child entity intersection.
9 votesHello,
Can you please clarify what it is you are asking for?
Thanks,
Luke -
Improve entity colour control
Entity colours should be selectable, or at the very least more differentiated so you can tell children apart.
The white colour for children entities makes them completely undetectable until you hover over them. Grey is difficult too.
9 votes -
Improved Search
It would be useful to have additional search operations (e.g. searching for specific usages of entity expressions across all utterances).
5 votesHello,
Clicking on an entity in the entities page shows you all the utterances for that entity.
Thanks,
Luke -
Interface timeouts
The interface should make fuller use of websockets so that the page doesn't lag and timeout during operations.
5 votesHello,
The portal has been completely revamped.
Thanks,
Luke -
Performance analysis section broken
The performance analysis section on the right of the web interface does not have a scroll bar, and this is a hindrance when there are more intents than can fit on one page.
9 votes -
Service Status Page for LUIS.
It would be very useful to include a Service Status Page for LUIS.
This would ideally include status and performance metrics for the consumer endpoint, the programmatic API, and the web application. This would really help us out in understanding expected performance.
22 votesHello,
We have an analytics page planned for Build: https://www.microsoft.com/en-us/build.
Thanks,
Luke
- Don't see your idea?