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
Copy file name to clipboardExpand all lines: articles/cognitive-services/language-service/concepts/model-lifecycle.md
+8-18Lines changed: 8 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,41 +15,31 @@ ms.author: aahi
15
15
16
16
# Model lifecycle
17
17
18
-
Language service features utilize AI models that are versioned. We update the language service with new model versions to improve accuracy, support, and quality. As models become older, they're retired. Use this article for information on that process, and what you can expect for your applications.
18
+
Language service features utilize AI models. We update the language service with new model versions to improve accuracy, support, and quality. As models become older, they are retired. Use this article for information on that process, and what you can expect for your applications.
19
19
20
20
## Prebuilt features
21
21
22
-
### Expiration timeline
23
-
24
-
Our standard (not customized) language service features are built upon AI models that we call pre-trained models. We update the language service with new model versions every few months to improve model accuracy, support, and quality.
25
22
26
-
As new models and functionalities become available, older less accurate models are deprecated. To ensure you're using the latest model version and avoid interruptions to your applications, we highly recommend using the default model-version parameter (`latest`) in your API calls. After their deprecation date, pre-built model versions will no longer be functional, and your implementation may be broken.
23
+
Our standard (not customized) language service features are built on AI models that we call pre-trained models.
27
24
28
-
Stable (not preview) model versions are deprecated six months after the release of another stable model version. Features in preview don't maintain a minimum retirement period and may be deprecated at any time.
25
+
We regularly update the language service with new model versions to improve model accuracy, support, and quality.
29
26
27
+
By default, all API requests will use the latest Generally Available (GA) model.
30
28
31
29
#### Choose the model-version used on your data
32
30
33
-
By default, API requests will use the latest Generally Available model. You can use an optional parameter to select the version of the model to be used (not recommended).
34
-
35
-
> [!TIP]
36
-
> If you’re using the SDK for C#, Java, JavaScript or Python, see the reference documentation for information on the appropriate model-version parameter.
31
+
We recommend using the `latest` model version to utilize the latest and highest quality models. As our models improve, it’s possible that some of your model results may change.
37
32
38
-
For synchronous endpoints, use the `model-version` query parameter. For example:
33
+
Preview models used for preview features do not maintain a minimum retirement period and may be deprecated at any time.
For asynchronous endpoints, use the `model-version` property in the request body under task properties.
43
-
44
-
The model-version used in your API request will be included in the response object.
35
+
By default, API and SDK requests will use the latest Generally Available model. You can use an optional parameter to select the version of the model to be used (not recommended).
45
36
46
37
> [!NOTE]
47
38
> If you are using an model version that is not listed in the table, then it was subjected to the expiration policy.
48
39
49
40
Use the table below to find which model versions are supported by each feature:
50
41
51
-
52
-
| Feature | Supported versions | Model versions to be deprecated |
42
+
| Feature | Supported versions | Model versions to be deprecated October 30, 2022|
0 commit comments