Discriminator syntax not aligned to the spec OpenApi 3.x Schema composition

[dilluz]

Actually the AsyncApi spec, under the schemaComposition paragaph, describe and implement the use of Dirscriminator attribute in an old way (imho inherited from swagger 2.0)

It would be great to evolve it as described by openApi 3.0.
This will enable to share and align the same schema definition between the two spec.

[github-actions]

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[jonaslagoni]

Technically there is no reason to align as you can define the message payload with OpenAPI schema directly using schemaFormat 🙂

[dilluz]

Thanks for Reply!
Just follow my reasoning, walking through the pre-release 3.0.0 doc of AsyncApi, the Message attribute

schemaFormat: application/vnd.oai.openapi+json;version=3.0.0

is supposed to be the default when not provided, and the AscynApi 2.6.0 format is not listed more.

Help me with my doubt so: Is it valid just for a $Ref Schema payload? Or it should be valid also for Object Schema payload? Bcs in my opinion if i try to setup an Object Schema compliant with the OAI3.0.0 Discriminator it should be valid following the default schemaFormat applied

thanks :)

[jonaslagoni]

Just follow my reasoning, walking through the pre-release 3.0.0 doc of AsyncApi, the Message attribute

schemaFormat: application/vnd.oai.openapi+json;version=3.0.0

is supposed to be the default when not provided, and the AscynApi 2.6.0 format is not listed more.

I don't follow. In v3 we grouped the schema format and schema information in the multi-format schema object. Which still uses the same schema formats as in v2: https://www.asyncapi.com/docs/reference/specification/v3.0.0-next-major-spec.16#multiFormatSchemaFormatTable

I doubt will default to OpenAPI Schema object, but feel free to suggest it.

Help me with my doubt so: Is it valid just for a $Ref Schema payload?

You can use $ref yea.

Or it should be valid also for Object Schema payload?

I don't follow :)

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

[derberg]

Closing as looks as answered with no further followup.

@dilluz if you have more questions, please create another issue and not here but in spec repo