Status update (week 11, 2019)
Tags: asyncapi, solace, opensource, microservices
Published: 2019-03-14 19:34:37

---
title: Status update (week 11, 2019)
published: true
description: Olà amigos! This is an exciting week for us. Solace joined the AsyncAPI Initiative as a Platinum Sponsor 🎉.
tags: asyncapi,solace,opensource,microservices
cover_image: https://thepracticaldev.s3.amazonaws.com/i/qq7czv41pj1mkwb2a8gf.png
---

Olà amigos! This is an exciting week for us. [Solace](https://solace.com) joined the AsyncAPI Initiative as a [Platinum Sponsor](https://opencollective.com/asyncapi) 🎉. Thank you, [Jonathan Schabowsky](https://twitter.com/JSchabowsky), for leading the process. And if that’s not enough, we finished our “[Protocol mappings](https://github.com/asyncapi/asyncapi/milestone/2?closed=1)” milestone. Keep reading!

## Latest changes in the specification

1. [Protocol-specific information](https://github.com/asyncapi/asyncapi/issues/42). This is a long-awaited feature. It allows you to define protocol-specific information in channels, operations, and messages.

2. [Separate application headers from protocol headers](https://github.com/asyncapi/asyncapi/issues/112). From now on, all the protocol-related headers must be included in a `protocolInfo` object, and the existing message `headers` must be used only for application headers, if any.

3. [Annotate a channel parameter as multi-level](https://github.com/asyncapi/asyncapi/issues/171). Do you want to tell your code a specific parameter should span across multiple levels? Now you can annotate channel parameters to indicate that. Pretty much like the `#` (pound) symbol in AMQP and MQTT or the `>` (greater than) symbol in NATS.

4. [Unify examples fields](https://github.com/asyncapi/asyncapi/issues/172). In the past, we had the `example` field in schemas and the `examples` field in some other places of the specification. They are now unified using the plural form and allowing for more than an example per object. However, we didn’t remove the support for `example` field in schemas, since we want to remain compatible with OpenAPI schemas.

![Cumulative flow chart showing the progress of AsyncAPI 2.0.0.](https://thepracticaldev.s3.amazonaws.com/i/t6vuotpn6a5jup9yc0wp.png)
<figcaption>Cumulative flow chart showing the progress of AsyncAPI 2.0.0.</figcaption>

![Release report showing the planned and predicted end dates. We’re 38 days ahead of plan! 🔥](https://thepracticaldev.s3.amazonaws.com/i/n5y7rvy96ixwaix85g7h.png)
<figcaption>Release report showing the planned and predicted end dates. We’re 38 days ahead of plan! 🔥</figcaption>


## Donate
And last but not least, we’ve completed our first three weeks running the sponsorship campaign. We greatly appreciate the support from [Solace](https://solace.com) and look forward to working together. You’ll hear more exciting news in the upcoming weeks. Stay tuned!

Remember, we’ve got different tiers so that everybody can show their love! ❤️


[Donate here](https://opencollective.com/asyncapi). Help Open Source projects.

---

> “Give yourself permission to slow down. You can speed up by slowing down.”
>
> — Gabby Bernstein

See you next week, folks! 👋