data-models | Data models is the beautiful way

I'm using Swashbuckle (6.1.1) in a .Net 5.0 Web API. I'm still learning, but I'd like to implement a class where certain properties only are valid when 'reading' with a GET, and other properties when 'writing' with a POST. According to the OpenAPI spec:

You can use the readOnly and writeOnly keywords to mark specific properties as read-only or write-only. This is useful, for example, when GET returns more properties than used in POST – you can use the same schema in both GET and POST and mark the extra properties as readOnly. readOnly properties are included in responses but not in requests, and writeOnly properties may be sent in requests but not in responses.

This is exactly what I want to achieve. However, I'm struggling to get Swashbuckle to generate the OpenAPI spec with the readOnly and writeOnly keyworks.

For example:

I'm trying to document a micros service using OpenAPI 3.0 The service returns Json that has any field name and can contain any of array, string, number, true, false, null, but not object. Strings could contain an ISO date. There are only very few known field names (e.g. "@id")

Sample:

I already found this script by the FIWARE-Community, which converts an NGSI-v2 normalized representation into an NGSI-LD representation.

Is there something similar for the opposite direction? I am aware that most of the steps can be done backwards. However, I am not sure about the usual procedure for converting back the "type": "Property" nodes.

E.g given an NGSI-v2 entity representation:

I am trying to set Additional Properties element into the Open API Schema 3.X but unfortunatel I was not able to find anything in the documentation that help me on it. I have a Application in Spring boot and it is using Spring doc OAS that relies on Swagger OAS as transitive dependency. Let me pick some code snippet here:

In my custom API that I am creating using Swagger, I need to input a timestamp.

In my YAML file I have defined the format of my input parameter as date-time as mentioned on the Swagger webpage date-time – the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

I want to convert the resulting zoned timestamp to com.google.protobuf.Timestamp but I don´t know how to do that and need help. I am using Kotlin.

So far I´ve tried implementing some of the Java examples from StackOverflow (after converting to Kotlin), for instance:

I am a little confused by Swagger's enum support for OpenAPI3.0. My point here being that there have been new improvements in swagger doc where there is support for re-usable enums as documented here:

https://swagger.io/docs/specification/data-models/enums/

where support for reusable enums is stated using $ref. However, when I post my swagger.json to swagger editor/validator which looks like following

From my Java backend I'm consuming another backend which I don't manage and it's API definition is not available. I'm creating the OpenAPI definition of it's services and using Swagger Codegen to generate the client.

There is an endpoint which returns a complex object:

When running my swagger definition test I get the following error below:

I'm using openapi 3.0.2, and the codegen plugin: