Mike Ralphson

For this and other issues, we may be able to learn things from [fromsmithy](https://github.com/awslabs/smithy/blob/main/smithy-openapi/src/main/java/software/amazon/smithy/openapi/fromsmithy/OpenApiConverter.java)

Project Communication

1

Firstly, thanks for getting involved! Please make sure you are familiar with the project's [Code of Conduct](https://github.com/asyncapi/asyncapi/blob/master/CODE_OF_CONDUCT.md#contributor-covenant-code-of-conduct). There are several ways to communicate with the AsyncAPI project: * Subscribe to...

Outstanding items to include

3

From #1 - [ ] **Callbacks and Webhooks** [Advanced]: What’s the difference, with examples. #76 - [ ] **Schemas [Advanced]**: examples for schemas, responses and parameters. - [ ] **Security...

See https://github.com/OAI/OpenAPI-Specification/pull/3185#issuecomment-1456832981 and follow-on comments. - [ ] format best practices - [ ] alternative JSON schema approaches

* we just return `false` early if there is no `parentNode`.

Hi @tedepstein - some discussions have taken place within the OpenAPI and AsyncAPI communities where we'd very much like something like Semoasa to have a place in defining a machine-readable...

Consider aligning context objectType enums with OAS spec. fragment-ids

1

I.e. in the example, `OperationObject` -> `operationObject`. The rationale for this is that fragment identifiers are case-sensitive. This would aid linking to the relevant area of the specifications. It might...

Add example property / components object

3

Looking at various specification extension documentation pages, an example is a common theme. It may need to be an object with a description and value a la OAS.

Suggest adding a (cut-down) info object at the root

5

Which might look something like: ##### Fixed Fields Field Name | Type | Description ---|:---:|--- title | `string` | **REQUIRED**. The title of the SEMOASA documentation. description | `string` |...