[Feat]: A2A v0.3.0 and v1.0.0 Coexistance

[sduskis]

Is your feature request related to a problem? Please describe.

My ecosystem has a bunch of agents talking A2A, primarily 0.3.0. I'd like to evolve the ecosystem to export services for 0.3.0 and 1.0.0. Is there a plan to support both in the same library?

Describe the solution you'd like

It would be useful to have APIs that convert between 0.3.0 and 1.0.0. I believe that most systems would start exposing 1.0.0 as a proxy for 0.3.0 and then migrate their implementation to be 1.0.0 compliant with a proxy that serves 0.3.0.

Describe alternatives you've considered

No response

Additional context

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[kabir]

Hi @sduskis thank you for flagging this. We made a conscious decision in the run-up to 1.0 to not support 0.3.0 of the spec.
However, we realise now that this might have been the wrong decision. Also, as the spec evolves beyond 1.0 we will need to support multiple protocols anyway. So we will look into this, and use this issue to discuss between ourselves.
It might not make it in time for our 1.0 release, but we think we can include it in a later 1.0.x release.