Skip to content

Commit 36d793a

Browse files
author
Jinyu Li
committed
fix issues from acrolinx
1 parent 002b98d commit 36d793a

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

articles/ai-services/computer-vision/sdk/understand-the-liveness-sdk-versions.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -11,21 +11,21 @@ ms.date: 01/15/2025
1111

1212
# Understand the Liveness Client-side SDK versions
1313

14-
Microsoft will regularly upgrade the liveness detection client SDK and service to improve security, reliability, and user convenience. Staying current with these updates is crucial because the liveness detection field faces active and sophisticated attacks.
14+
Microsoft regularly upgrades the liveness detection client SDK and service to improve security, reliability, and user convenience. Staying current with these updates is crucial because the liveness detection field faces active and sophisticated attacks.
1515

1616
## Client-side SDK Versions
1717

1818
Liveness detection client-side SDK uses major.minor.patch format to indicate software version.
19-
- A patch version update is optional reliability fix on client SDK, it won’t impact the compatibility with service.
20-
- A minor version update is important security and reliability improvement. We will try to extend support for a minor update as long as possible, Azure service might announce retirement of minor update after 6 months
21-
- A major version update is critical security or breaking API updates. Customers should make client update as soon as possible. Azure service will block the previous major version after 6 months.
19+
- A patch version update is an optional reliability fix on the client SDK that doesn't impact compatibility with the service.
20+
- A minor version update is important security and reliability improvement. We'll try to extend support for a minor update as long as possible, Azure service might announce retirement of minor update after six months
21+
- A major version update is critical security or breaking API updates. Customers should make client update as soon as possible. Azure service will block the previous major version after six months.
2222

2323
## Azure Face API Service Version
2424

25-
Face liveness detection feature is generally available from version 1.2. Face API will follow the Azure developing cycle, newer API version will add new features in preview release, then general available. A newer service version may require a newer minimal client SDK version. The requirement will be announced when new service version is available.
25+
Face liveness detection feature is generally available from version 1.2. Face API follows the Azure developing cycle, newer API version adds new features in preview release, then general available. A newer service version may require a newer minimal client SDK version. The requirement is announced when new service version is available.
2626

2727
## Service Model Version
2828

2929
In the Create Liveness Session operation, customers can specify a liveness model version to classify the session. Azure service is also progressively updating new models. We strongly recommend customers always use the latest model version, which means simply leaving the model version parameter empty.
30-
- The latest model version (default version) will be compatible with all supported client versions.
31-
- When a service model is to be retired, Azure service will announce this 6 months ahead, providing customers with buffer time to update their backend service.
30+
- The latest model version (default version) is compatible with all supported client versions.
31+
- When a service model is to be retired, Azure service will announce the decision six months ahead, providing customers with buffer time to update their backend service.

0 commit comments

Comments
 (0)