Profile

Contact Details

Ribbons

Badges

Clemens Vasters


Contributions

1 to 5 of 50+ total
Posted By Clemens Vasters 10-27-2026 06:52
Found In Egroup: OASIS Advanced Message Queuing Protocol (AMQP) TC
\ view thread
Neither Rob nor I are available today. We had instituted the once-per-week cadence before MQ Summit, so I propose we go back to the 2-week cadence and resume next week. I will adjust the calendar accordingly.
Posted By Clemens Vasters 10-15-2026 10:21
Found In Egroup: OASIS Advanced Message Queuing Protocol (AMQP) TC
\ view thread
At the Tuesday TC meeting, chairs agreed with Stefan Moser's proposal to merge the following cleanup PRs into the MCP and JSON-RPC drafts that are on the ballot, and which Stefan had announced at the prior TC meeting: https://github.com/oasis-tcs/amqp-specs/pull/23 for the MCP binding draft https: ...
Posted By Clemens Vasters 10-08-2026 15:41
Found In Egroup: OASIS Advanced Message Queuing Protocol (AMQP) TC
\ view thread
TC members, The ballots for the JSON-RPC 2.0 over AMQP 1.0 and MCP over AMQP 1.0 bindings are now open. Each asks the TC to approve Working Draft 01 as Committee Specification Draft 01 and authorize the initial 30-day public review. JSON-RPC ballot: https://groups.oasis-open.org/higherlogic/ws/gro ...
Posted By Clemens Vasters 10-08-2026 14:19
Found In Egroup: OASIS Advanced Message Queuing Protocol (AMQP) TC
\ view thread
Hi everyone, I've opened PR #20 to prepare the Model Context Protocol (MCP) over AMQP 1.0 binding as Working Draft 01 in the current OASIS Markdown specification format: https://github.com/oasis-tcs/amqp-specs/pull/20 Stefan Moser and Vignesh Selvam (AWS) are listed as editors. The PR adds the cover ...
Posted By Clemens Vasters 10-08-2026 14:17
Found In Egroup: OASIS Advanced Message Queuing Protocol (AMQP) TC
\ view thread
Hi everyone, I've opened PR #19 to prepare the JSON-RPC 2.0 over AMQP 1.0 binding as Working Draft 01 in the current OASIS Markdown specification format: https://github.com/oasis-tcs/amqp-specs/pull/19 The PR is rebased on #17 and retains its non-normative guidance for receiver-created temporary reply ...