-
-
Notifications
You must be signed in to change notification settings - Fork 303
Add official XSD schema format #915
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@jessemenning @damaru-inc you are the only ones I know in the community that advocated for XSD in the past. So maybe you can help define those |
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 ❤️ |
I struggle again about this issue and i am not sure if there is any beautiful solution to map this xml example: <outer attributeA="foo" attributeB=12>
<inner>the first</inner>
<inner>the second</inner>
<inner>the third</inner>
<innerB>the first</innerB>
<outer> to json schema the parser.js internal model. properties:
attributeA:
type: string
attributeB
type: integer
innerA:
type: array
items:
type: string
innerB:
type: string Than it is not clear that To support this we need to enhance json schema some how. |
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 ❤️ |
Are there any plans to add XSD support to AsyncAPI? |
Description
We discussed this in the following meeting: https://www.youtube.com/watch?v=8Yjles2pEHo
It would be nice to have official schemaFormat types for XSD, so all tooling can understand when XSD is in use instead of each having using it's own.
I have no specific suggestion for the value it self, that needs to be researched.
The text was updated successfully, but these errors were encountered: