Introduce ProductInfo Node to entities to identify the internal channel / product of a channelID

Open

#77 opened on Mar 5, 2025 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 5/5
Estimated time: Over a week
Newbie friendliness: 30/100

Issue type: Feature
Clarity: Mostly clear
Activity status: Stale
Domain: api, backend-api-design

Research direction

Start by locating the Activity Protocol entity definitions and current channelId handling. Compare the proposed ProductInfo entity and subChannelInfo example with the existing protocol structure, then confirm the schema, serialization, and test or example coverage needed for the new product identifier.

Written by the indexing model from the issue text.

Description

Spec change accepted Specs

Within the concept of Clients/Channel providers there are some providers that group a set of channels behind a single "public" channel.
There are currently two examples of this inside the MSFT ecosystem.

Azure Communications Services
M365 msTeams Channel

In these cases, multiple clients are fronted by a single service,

Currently, the Activity Protocol described a single channel concept called "channel Id".
To handle the updated requirements, we would introduce a new component in entitles called "ProductInfo".
ProductInfo wil contain an ID used to identity if the 'subproduct' behind the channelid and any additional information about the channel client that is available.

This would take the shape of:

            "subChannelInfo": {
                "channelId": "COPILOT"
            }

as it would appear in the existing in the structure:

{
    "id": "1741193418370",
    "channelId": "msteams",
    "entities": [
        {
                "type" : "ProductInfo"
                "id": "COPILOT"
// Intent to expand at a later date with additional properties.
            }
        }
    ],
    "channelData": {
        "tenant": {
            "id": "000000-0000-0000-00000-00000000000"
        },
        "productContext": "COPILOT"
    }
}

Dominant language: TypeSpec
Stars: 1.1k
Forks: 340
Avg merge: 3d 13h
Merged PRs (30d): 12

Contributor guide

No contributing guide indexed for this repository

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

[Bug] [Connector-V2] [Http] A streaming Http source never completes a checkpoint: poll_interval_millis is waited out holding the checkpoint lock Open

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

apache/seatunnel#12411 · Opened Sep 20, 2026
wafv2: TagResource/UntagResource don't enforce the 50-tag limit or key/value length limits Open

Difficulty 2/5 1-3 hours Newbie friendliness 76/100

floci-io/floci#4035 · Opened Sep 20, 2026
[Duplicate Code] Repeated filtered model-alias assembly in proxy server Open

code-quality refactoring

Difficulty 2/5 1-3 hours Newbie friendliness 84/100

github/gh-aw-firewall#8816 · Opened Sep 20, 2026
popularity.exclude_admin does not work for admin2 Open

Difficulty 2/5 1-3 hours Newbie friendliness 68/100

getgrav/grav-plugin-api#45 · Opened Sep 20, 2026
quickjs: support `timeout=None` (no per-call deadline) in `CodeInterpreterMiddleware` Open

integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature

Difficulty 2/5 1-3 hours Newbie friendliness 74/100

langchain-ai/deepagents#6450 · Opened Sep 20, 2026

More Backend & API Design issues