John Fallows

Note: requires `sse` support in AsyncAPI specification. Add an `asyncapi.proxy.sse` scenario in `zilla-examples`.

Equivalent to `openapi-asyncapi` mapping of `http-kafka`.

**Describe the desired outcome from the user's perspective** As devops, I want to validate `http` `asyncapi` channel parameters with runtime expressions. **Acceptance criteria** - Validate `http` path parameter matches payload...

**Describe the desired outcome from the user's perspective** As devops, I want to validate `mqtt` `asyncapi` channel parameters with runtime expressions. **Acceptance criteria** - Validate `mqtt` topic parameter matches payload...

Note: also assess consumer group limits per broker implementation.

**Describe the desired outcome from the user's perspective** As devops, I want to validate `mqtt` messages received from an `mqtt` broker to ensure correctness before passing to clients. **Acceptance criteria**...

**Describe the desired outcome from the user's perspective** As a catalog schema author, I want to be able to use cross-document `protobuf schema` references when supported by the catalog. **Acceptance...

**Describe the desired outcome from the user's perspective** As a catalog schema author, I want to be able to use cross-document `avro schema` references when supported by the catalog. **Acceptance...

**Describe the desired outcome from the user's perspective** As a catalog schema author, I want to be able to use cross-document `json schema` references when supported by the catalog. **Acceptance...

Unlike converters which always see the entire message, validators are applied to messages that can be fragmented. Therefore, if protobuf validation that requires observing the entire message, then buffering is...