Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[IC3 ACS Chat ] API Review #31697

Open
azure-sdk opened this issue Nov 28, 2024 · 1 comment · May be fixed by #31243
Open

[IC3 ACS Chat ] API Review #31697

azure-sdk opened this issue Nov 28, 2024 · 1 comment · May be fixed by #31243
Labels
API Review Scoping This is an issue that will track work on a specific set of API changes.

Comments

@azure-sdk
Copy link
Collaborator

New API Review meeting has been requested.

Service Name: IC3 ACS Chat
Review Created By: Cheuk Chuen Siow
Review Date: 01/14/2025 01:00 PM PT
Release Plan:
PR: #31243
Hero Scenarios Link: Not Provided
Core Concepts Doc Link: Not Provided

Description: ACS Chat faces several concerns regarding the existing bot channel implementation:

  • Only partial support to a subset of bot activities
  • Certain properties of supported bot activities are being discarded during transit
  • Inability to enrich messages for bots to consume
  • Unable to propagate thread and participant metadata to bots

The way we currently implement bot channel integration is not ideal. We're reserving a space in chat message metadata that is meant to be reserved for Contoso's usage, and having json string payload in the message content.

We're introducing new message types (AzureBotActivity and AzureBotCommand) in ChatMessageType enum, enabling ACS Chat to act as transport layer so that the entire bot payload can be sent and received by Azure bots in the form of bot activity.

Detailed meeting information and documents provided can be accessed here
For more information that will help prepare you for this review, the requirements, and office hours, visit the documentation here

@azure-sdk azure-sdk added the API Review Scoping This is an issue that will track work on a specific set of API changes. label Nov 28, 2024
@mikekistler
Copy link
Member

Azure Versioning policy requires any change to service behavior / API surface be done in a new API version. Please make the proposed changes in a new API version or explain why this is not possible / practical.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API Review Scoping This is an issue that will track work on a specific set of API changes.
Projects
Status: Triage
2 participants