You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As you use this API in your application, see the [reference documentation](/rest/api/language/conversational-analysis-authoring) for additional information.
113
+
As you use this API in your application, see the [reference documentation](/rest/api/language/2022-05-01/conversational-analysis-authoring) for additional information.
114
114
115
115
### Conversation analysis runtime API
116
116
@@ -122,7 +122,7 @@ It additionally enables you to use the following features, without creating any
*[Personally Identifiable Information (PII) detection for conversations](../personally-identifiable-information/how-to-call-for-conversations.md?tabs=rest-api#examples)
124
124
125
-
As you use this API in your application, see the [reference documentation](/rest/api/language/conversation-analysis-runtime) for additional information.
125
+
As you use this API in your application, see the [reference documentation](/rest/api/language/2022-05-01/conversation-analysis-runtime) for additional information.
126
126
127
127
128
128
### Text analysis authoring API
@@ -131,7 +131,7 @@ The text analysis authoring API enables you to author custom models and create/m
131
131
*[Custom named entity recognition](../custom-named-entity-recognition/quickstart.md?pivots=rest-api)
132
132
*[Custom text classification](../custom-text-classification/quickstart.md?pivots=rest-api)
133
133
134
-
As you use this API in your application, see the [reference documentation](/rest/api/language/text-analysis-authoring) for additional information.
134
+
As you use this API in your application, see the [reference documentation](/rest/api/language/2022-05-01/text-analysis-authoring) for additional information.
135
135
136
136
### Text analysis runtime API
137
137
@@ -150,7 +150,7 @@ It additionally enables you to use the following features, without creating any
150
150
*[Sentiment analysis and opinion mining](../sentiment-opinion-mining/quickstart.md?pivots=rest-api)
151
151
*[Text analytics for health](../text-analytics-for-health/quickstart.md?pivots=rest-api)
152
152
153
-
As you use this API in your application, see the [reference documentation](/rest/api/language/text-analysis-runtime) for additional information.
153
+
As you use this API in your application, see the [reference documentation](/rest/api/language/2022-05-01/text-analysis-runtime/analyze-text) for additional information.
Copy file name to clipboardExpand all lines: articles/cognitive-services/language-service/concepts/use-asynchronously.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,7 @@ To submit an asynchronous job, review the [reference documentation](/rest/api/la
37
37
1. In the `tasks` object, include the operations you want performed on your data. For example, if you wanted to perform sentiment analysis, you would include the `SentimentAnalysisLROTask` object.
38
38
1. You can optionally:
39
39
1. Choose a specific [version of the model](model-lifecycle.md) used on your data.
40
-
1. Include additional Language ervice features in the `tasks` object, to be performed on your data at the same time.
40
+
1. Include additional Language service features in the `tasks` object, to be performed on your data at the same time.
41
41
42
42
Once you've created the JSON body for your request, add your key to the `Ocp-Apim-Subscription-Key` header. Then send your API request to job creation endpoint. For example:
43
43
@@ -51,7 +51,7 @@ A successful call will return a 202 response code. The `operation-location` in t
51
51
GET {Endpoint}/language/analyze-text/jobs/12345678-1234-1234-1234-12345678?api-version=2022-05-01
52
52
```
53
53
54
-
To [get the status and retrieve the results](/rest/api/language/text-analysis-runtime/job-status) of the request, send a GET request to the URL you received in the `operation-location` header from the previous API response. Remember to include your key in the `Ocp-Apim-Subscription-Key`. The response will include the results of your API call.
54
+
To [get the status and retrieve the results](/rest/api/language/2022-05-01/text-analysis-runtime/job-status) of the request, send a GET request to the URL you received in the `operation-location` header from the previous API response. Remember to include your key in the `Ocp-Apim-Subscription-Key`. The response will include the results of your API call.
55
55
56
56
## Send asynchronous API requests using the client library
Copy file name to clipboardExpand all lines: articles/cognitive-services/language-service/conversational-language-understanding/how-to/migrate-from-luis.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,8 +47,8 @@ The following table presents a side-by-side comparison between the features of L
47
47
|Role-Based Access Control (RBAC) for LUIS resources |Role-Based Access Control (RBAC) available for Language resources |Language resource RBAC must be [manually added after migration](../../concepts/role-based-access-control.md). |
48
48
|Single training mode| Standard and advanced [training modes](#how-are-the-training-times-different-in-clu-how-is-standard-training-different-from-advanced-training)| Training will be required after application migration. |
49
49
|Two publishing slots and version publishing |Ten deployment slots with custom naming | Deployment will be required after the application’s migration and training. |
50
-
|LUIS authoring APIs and SDK support in .NET, Python, Java, and Node.js |[CLU Authoring REST APIs](/rest/api/language/conversational-analysis-authoring). | For more information, see the [quickstart article](../quickstart.md?pivots=rest-api) for information on the CLU authoring APIs. [Refactoring](#do-i-have-to-refactor-my-code-if-i-migrate-my-applications-from-luis-to-clu) will be necessary to use the CLU authoring APIs. |
51
-
|LUIS Runtime APIs and SDK support in .NET, Python, Java, and Node.js |[CLU Runtime APIs](/rest/api/language/conversation-analysis-runtime). CLU Runtime SDK support for [.NET](/dotnet/api/overview/azure/ai.language.conversations-readme) and [Python](/python/api/overview/azure/ai-language-conversations-readme?view=azure-python-preview&preserve-view=true). | See [how to call the API](../how-to/call-api.md#use-the-client-libraries-azure-sdk) for more information. [Refactoring](#do-i-have-to-refactor-my-code-if-i-migrate-my-applications-from-luis-to-clu) will be necessary to use the CLU runtime API response. |
50
+
|LUIS authoring APIs and SDK support in .NET, Python, Java, and Node.js |[CLU Authoring REST APIs](/rest/api/language/2022-05-01/conversational-analysis-authoring). | For more information, see the [quickstart article](../quickstart.md?pivots=rest-api) for information on the CLU authoring APIs. [Refactoring](#do-i-have-to-refactor-my-code-if-i-migrate-my-applications-from-luis-to-clu) will be necessary to use the CLU authoring APIs. |
51
+
|LUIS Runtime APIs and SDK support in .NET, Python, Java, and Node.js |[CLU Runtime APIs](/rest/api/language/2022-05-01/conversation-analysis-runtime). CLU Runtime SDK support for [.NET](/dotnet/api/overview/azure/ai.language.conversations-readme) and [Python](/python/api/overview/azure/ai-language-conversations-readme?view=azure-python-preview&preserve-view=true). | See [how to call the API](../how-to/call-api.md#use-the-client-libraries-azure-sdk) for more information. [Refactoring](#do-i-have-to-refactor-my-code-if-i-migrate-my-applications-from-luis-to-clu) will be necessary to use the CLU runtime API response. |
52
52
53
53
## Migrate your LUIS applications
54
54
@@ -269,9 +269,9 @@ The API objects of CLU applications are different from LUIS and therefore code r
269
269
270
270
If you are using the LUIS [programmatic](https://westus.dev.cognitive.microsoft.com/docs/services/luis-programmatic-apis-v3-0-preview/operations/5890b47c39e2bb052c5b9c40) and [runtime](https://westus.dev.cognitive.microsoft.com/docs/services/luis-endpoint-api-v3-0/operations/5cb0a9459a1fe8fa44c28dd8) APIs, you can replace them with their equivalent APIs.
271
271
272
-
[CLU authoring APIs](/rest/api/language/conversational-analysis-authoring): Instead of LUIS's specific CRUD APIs for individual actions such as _add utterance_, _delete entity_, and _rename intent_, CLU offers an [import API](/rest/api/language/conversational-analysis-authoring/import) that replaces the full content of a project using the same name. If your service used LUIS programmatic APIs to provide a platform for other customers, you must consider this new design paradigm. All other APIs such as: _listing projects_, _training_, _deploying_, and _deleting_ are available. APIs for actions such as _importing_ and _deploying_ are asynchronous operations instead of synchronous as they were in LUIS.
272
+
[CLU authoring APIs](/rest/api/language/2022-05-01/conversational-analysis-authoring): Instead of LUIS's specific CRUD APIs for individual actions such as _add utterance_, _delete entity_, and _rename intent_, CLU offers an [import API](/rest/api/language/2022-05-01/conversational-analysis-authoring/import) that replaces the full content of a project using the same name. If your service used LUIS programmatic APIs to provide a platform for other customers, you must consider this new design paradigm. All other APIs such as: _listing projects_, _training_, _deploying_, and _deleting_ are available. APIs for actions such as _importing_ and _deploying_ are asynchronous operations instead of synchronous as they were in LUIS.
273
273
274
-
[CLU runtime APIs](/rest/api/language/conversation-analysis-runtime/analyze-conversation): The new API request and response includes many of the same parameters such as: _query_, _prediction_, _top intent_, _intents_, _entities_, and their values. The CLU response object offers a more straightforward approach. Entity predictions are provided as they are within the utterance text, and any additional information such as resolution or list keys are provided in extra parameters called `extraInformation` and `resolution`. See the [reference documentation](/rest/api/language/conversation-analysis-runtime/analyze-conversation) for more information on the API response structure.
274
+
[CLU runtime APIs](/rest/api/language/2022-05-01/conversation-analysis-runtime): The new API request and response includes many of the same parameters such as: _query_, _prediction_, _top intent_, _intents_, _entities_, and their values. The CLU response object offers a more straightforward approach. Entity predictions are provided as they are within the utterance text, and any additional information such as resolution or list keys are provided in extra parameters called `extraInformation` and `resolution`. See the [reference documentation](/rest/api/language/2022-05-01/conversation-analysis-runtime) for more information on the API response structure.
275
275
276
276
You can use the [.NET](https://github.com/Azure/azure-sdk-for-net/tree/Azure.AI.Language.Conversations_1.0.0-beta.3/sdk/cognitivelanguage/Azure.AI.Language.Conversations/samples/) or [Python](https://github.com/Azure/azure-sdk-for-python/blob/azure-ai-language-conversations_1.1.0b1/sdk/cognitivelanguage/azure-ai-language-conversations/samples/README.md) CLU runtime SDK to replace the LUIS runtime SDK. There is currently no authoring SDK available for CLU.
Use this quickstart to send entity linking requests using the REST API. In the following example, you will use cURL to identify and disambiguate entities found in text.
19
19
@@ -156,4 +156,4 @@ curl -i -X POST https://<your-language-resource-endpoint>/language/:analyze-text
156
156
157
157
*[Entity linking language support](../../language-support.md)
158
158
*[How to call the entity linking API](../../how-to/call-api.md)
Use this quickstart to send key phrase extraction requests using the REST API. In the following example, you will use cURL to identify key words and phrases found in text.
Use this quickstart to send language detection requests using the REST API. In the following example, you will use cURL to identify the language that a text sample was written in.
Use this quickstart to send Named Entity Recognition (NER) requests using the REST API. In the following example, you will use cURL to identify [recognized entities](../../concepts/named-entity-categories.md) in text.
Copy file name to clipboardExpand all lines: articles/cognitive-services/language-service/personally-identifiable-information/includes/quickstarts/rest-api.md
Use this quickstart to send Personally Identifiable Information (PII) detection requests using the REST API. In the following example, you will use cURL to identify [recognized sensitive information](../../concepts/entity-categories.md) in text.
0 commit comments