Azure.AI.Language.QuestionAnswering.Authoring Namespace

Feedback for Active Learning.

Model factory for models.

Context class which will be filled in by the System.ClientModel.SourceGeneration. For more information see 'https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/core/System.ClientModel/src/docs/ModelReaderWriterContext.md'

Feedback Record for Active Learning.

Collection of files containing project assets that need to be imported.

Project assets that need to be imported.

Import QnA Record.

A file in an HTTP request, response, or multipart payload.

Files have a special meaning that the HTTP library understands. When the body of an HTTP request, response, or multipart payload is effectively an instance of TypeSpec.Http.File or any type that extends it, the operation is treated as a file upload or download.

When using file bodies, the fields of the file model are defined to come from particular locations by default:

• contentType: The Content-Type header of the request, response, or multipart payload (CANNOT be overridden or changed).
• contents: The body of the request, response, or multipart payload (CANNOT be overridden or changed).
• filename: The filename parameter value of the Content-Disposition header of the response or multipart payload (MAY be overridden or changed).

A File may be used as a normal structured JSON object in a request or response, if the request specifies an explicit Content-Type header. In this case, the entire File model is serialized as if it were any other model. In a JSON payload, it will have a structure like:

{
  "contentType": <string?>,
  "filename": <string?>,
  "contents": <string, base64>
}

The contentType within the file defines what media types the data inside the file can be, but if the specification defines a Content-Type for the payload as HTTP metadata, that Content-Type metadata defines how the file is serialized. See the examples below for more information.

NOTE: The filename and contentType fields are optional. Furthermore, the default location of filename (Content-Disposition: <disposition>; filename=<filename>) is only valid in HTTP responses and multipart payloads. If you wish to send the filename in a request, you must use HTTP metadata decorators to describe the location of the filename field. You can combine the metadata decorators with @visibility to control when the filename location is overridden, as shown in the examples below.

Project deployment details.

Job state represents the job metadata and any errors.

Configurable settings of the Project.

All assets for this project.

The QuestionAnsweringAuthoring service client.

Client options for QuestionAnsweringAuthoringClient.

Dialog associated with QnA Record.

The error object.

Export job status, project metadata, and assets.

Import job status, project metadata, and assets.

An object containing more specific information about the error. As per Microsoft One API guidelines - https://github.com/Microsoft/api-guidelines/blob/vNext/Guidelines.md#7102-error-condition-responses.

Represents the state of a project deletion job.

Prompt for an answer.

QnA record.

Custom source record with last updated date-time.

Job state represents the job metadata and any errors.

Job state represents the job metadata and any errors.

Represents the project.

QnA Record with last updated date-time.

Question suggested by the Active Learning feature.

Active Learning suggested questions cluster details.

Request payload for updating synonyms.

Collection of word alterations.

Kind of the asset of the project.

Knowledge base Import or Export format.

Supported source types.

Cloud audiences available for Question Answering Authoring.

Human-readable error code.

Human-readable error code.

Job Status.

Content structure type for sources.

The version of the service to use.