Update Face spec (#29120)

* Rename url as uri for cs

* Add PassiveActive for liveness

* Update OAS

specification/ai/Face/models.session.tsp

@@ -8,12 +8,15 @@ using TypeSpec.Rest;
 
 namespace Face;
 
-@doc("The operation mode for the liveness modal.")
+@doc("The liveness operation mode to drive the client’s end-user experience.")
 union LivenessOperationMode {
   string,
 
-  @doc("The operation mode for the liveness modal.")
+  @doc("Utilizes a passive liveness technique that requires no additional actions from the user. Requires normal indoor lighting and high screen brightness for optimal performance. And thus, this mode has a narrow operational envelope and will not be suitable for scenarios that requires the end-user’s to be in bright lighting conditions. Note: this is the only supported mode for the Mobile (iOS and Android) solution.")
   "Passive",
+
+  @doc("This mode utilizes a hybrid passive or active liveness technique that necessitates user cooperation. It is optimized to require active motion only under suboptimal lighting conditions. Unlike the passive mode, this mode has no lighting restrictions, and thus offering a broader operational envelope. This mode is preferable on Web based solutions due to the lack of automatic screen brightness control available on browsers which hinders the Passive mode’s operational envelope on Web based solutions.")
+  "PassiveActive",
 }
 
 #suppress "@azure-tools/typespec-autorest/unsupported-multipart-type" "Provide convenient interface for multipart/form-data in SDK"

specification/ai/Face/routes.common.tsp

@@ -1,11 +1,13 @@
 import "@typespec/http";
 import "@typespec/rest";
 import "@azure-tools/typespec-azure-core";
+import "@azure-tools/typespec-client-generator-core";
 import "./models.common.tsp";
 import "./models.detect.tsp";
 
 using TypeSpec.Http;
 using TypeSpec.Rest;
+using Azure.ClientGenerator.Core;
 using Azure.Core;
 using Azure.Core.Traits;
 using Foundations;
@@ -66,6 +68,7 @@ op AddFace<TFace extends BaseFace> is Foundations.ResourceCollectionOperation<
 op AddFaceFromUrl<TFace extends BaseFace> is Foundations.ResourceCollectionOperation<
   TFace,
   AddFaceOptions & {
+    @clientName("uri", "csharp")
     @doc("URL of input image.")
     url: url;
   },

specification/ai/Face/routes.detection.tsp

@@ -6,6 +6,7 @@ import "./models.detect.tsp";
 
 using TypeSpec.Http;
 using TypeSpec.Rest;
+using Azure.ClientGenerator.Core;
 using Azure.Core;
 using Azure.Core.Traits;
 using Foundations;
@@ -46,6 +47,7 @@ interface FaceDetectionOperations {
     @header
     contentType: "application/json";
 
+    @clientName("uri", "csharp")
     @doc("URL of input image.")
     url: url;
   }>;

specification/ai/Face/routes.persondirectory.tsp

@@ -5,6 +5,7 @@ import "./models.persondirectory.tsp";
 
 using TypeSpec.Http;
 using TypeSpec.Rest;
+using Azure.ClientGenerator.Core;
 using Azure.Core;
 using Azure.Core.Traits;
 using Foundations;
@@ -182,6 +183,7 @@ interface PersonDirectoryOperations {
   #suppress "@azure-tools/typespec-azure-core/byos" "It's an RPC call to detect face from an image, it doesn't store anything. There's a BYOS version of this call, but it's not this one."
   #suppress "@azure-tools/typespec-azure-core/long-running-polling-operation-required" "Doesn't fit in generated long-running operation"
   addPersonFaceFromUrl is AddPersonFaceOperation<{
+    @clientName("uri", "csharp")
     @doc("URL of input image.")
     url: url;
   }>;

specification/ai/data-plane/Face/preview/v1.1-preview.1/Face.json

@@ -8627,9 +8627,10 @@
     },
     "LivenessOperationMode": {
       "type": "string",
-      "description": "The operation mode for the liveness modal.",
+      "description": "The liveness operation mode to drive the client’s end-user experience.",
       "enum": [
-        "Passive"
+        "Passive",
+        "PassiveActive"
       ],
       "x-ms-enum": {
         "name": "LivenessOperationMode",
@@ -8638,7 +8639,12 @@
           {
             "name": "Passive",
             "value": "Passive",
-            "description": "The operation mode for the liveness modal."
+            "description": "Utilizes a passive liveness technique that requires no additional actions from the user. Requires normal indoor lighting and high screen brightness for optimal performance. And thus, this mode has a narrow operational envelope and will not be suitable for scenarios that requires the end-user’s to be in bright lighting conditions. Note: this is the only supported mode for the Mobile (iOS and Android) solution."
+          },
+          {
+            "name": "PassiveActive",
+            "value": "PassiveActive",
+            "description": "This mode utilizes a hybrid passive or active liveness technique that necessitates user cooperation. It is optimized to require active motion only under suboptimal lighting conditions. Unlike the passive mode, this mode has no lighting restrictions, and thus offering a broader operational envelope. This mode is preferable on Web based solutions due to the lack of automatic screen brightness control available on browsers which hinders the Passive mode’s operational envelope on Web based solutions."
           }
         ]
       }