[Text Analytics] Updates/Renames for Custom Text and language
See original GitHub issueIn the context of Custom Text (models, method names, samples, docs, etc), the service team requested the following renames:
Category
(as in machine learning class/label and not to be confused with entity category) toLabel
Custom Entity
toCustom Named Entity
- Any prefixes/postfixes to
projectName
anddeploymentName
to be dropped. For instanceCUSTOM_ENTITIES_PROJECT_NAME
should be renamed toprojectName
subCategory
shouldn’t be part of the returned custom named entity structures/classes.
In the context of references to the service:
Text Analytics
should be renamed toLanguage
- References to the API key (e.g. AZURE_TEXT_ANALYTICS_KEY or apiKey) should be renamed to
Azure Language key
The original request is documented in https://microsoft.sharepoint.com/:x:/t/luis_core/EabmFH8uAk1Jry2cY6Ug1qEB4APAE1x-uXm73uJy7rmitA?e=QWcHYm
Issue Analytics
- State:
- Created a year ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Text Analytics | Microsoft Azure
Use Microsoft Azure's Cognitive Services, Text Analytics, to mine insights from unstructured text using natural language.
Read more >Text Analysis Tools: The Complete List for 2022 - MonkeyLearn
Discover the best text analysis tools to extract insights from your unstructured text data. Including MonkeyLearn, IBM Watson, Aylien, ...
Read more >What Is Text Analytics? We Analyze the Jargon
Text analytics is a complex technology. To get started, you'll need to learn some new vocabulary and concepts, which we'll explain in plain ......
Read more >What is Text Mining, Text Analytics and Natural Language ...
Text mining (also referred to as text analytics) is an artificial intelligence (AI) technology that uses natural language processing (NLP) to transform the ......
Read more >SAP HANA Text Analysis Developer Guide
The language modules included with the software contain system ... You can also customize the text analysis process and even define your own...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@jsquire Here is a list of things that are proposed to be changed:
Category => Label
TextAnalyticsActions.SingleCategoryClassifyActions
=>TextAnalyticsActions.SingleLabelClassifyActions
SingleCategoryClassifyAction
=>SingleLabelClassifyAction
SingleCategoryClassifyActionResult
=>SingleLabelClassifyActionResult
SingleCategoryClassifyResult
=>SingleLabelClassifyResult
SingleCategoryClassifyResultCollection
=>SingleLabelClassifyResultCollection
AnalyzeActionsResult.SingleCategoryClassifyResults
=>AnalyzeActionsResult.SingleLabelClassifyResults
Please apply the same renaming to the corresponding names for the MultiCategory variant.
Custom Entity => Custom Named Entity*
AnalyzeActionsResult.RecognizeCustomEntitiesResults
=>AnalyzeActionsResult.RecognizeCustomNamedEntitiesResults
RecognizeCustomEntitiesActionResult
=>RecognizeCustomNamedEntitiesActionResult
RecognizeCustomEntitiesResultCollection
=>RecognizeCustomNamedEntitiesResultCollection
TextAnalyticsActions.RecognizeCustomEntitiesActions
=>RecognizeCustomNamedEntitiesActions
RecognizeCustomEntitiesAction
=>RecognizeCustomNamedEntitiesAction
Dropping subCategory from Custom Named Entities results*
It currently inherits from the standard entity results type which has a
subCategory
field and the ask here is to use a model that does not havesubCategory
in it.Others
The rest of the proposal are mainly terminology and variable name changes.
Please talk to your architects about those changes, especially the ones with the * since one will make a long name even longer and the other will introduce new models that share most of its members with a current one.
I hope that helps!
These renames have been adopted by the swagger for v2022-04-01-preview and v6.0.0-beta.1 is following that swagger closely so I believe this issue has been addressed for JS.