Xml is more suitable than Json for Api doc

[niltor]

Using JSON as the content for HTTP data transmission is quite convenient.

However, using JSON to represent OpenAPI documentation, who was the genius that thought of this?

There are too many issues like allof, oneof, $ref, circular references during JSON parsing, and so on.
Even Microsoft's official library has not been perfected in over two years.

JSON Schema? Expressing various types like generics and inheritance is very convoluted.
Microsoft should not follow the "popular but incorrect" trend but instead take a true leadership role.

Perhaps XML is a more suitable choice for API documentation, as it is also easier to parse.

What do you think?

[martincostello]

Perhaps XML is a more suitable choice for API documentation, as it is also easier to parse.

OpenAPI is an industry standard that supports JSON or YAML. If you want to try and convince them to add support for XML too, then it's best to propose over there. Then if it were accepted and added to Microsoft.OpenApi, then a future release of ASP.NET Core would inherit support for it.

I highly doubt there's any appetite for the ASP.NET Core team to create its own parallel API description standard that uses XML.