Parsing support for OAS 3.1

[krissirk]

Your issue may already be reported! Please search on Github issues before creating one.

• I'm submitting a ...

  • bug report
  • feature request
  • question
  • other

• What is the current behavior?
  Only OAS 2.0 and 3.0 are documented as supported at https://a.ml/docs/amf/using-amf/amf_parsing/

• If the current behavior is a bug, please provide the minimal steps to reproduce with AMF code. Please don't upload AMF code mixed with yours.

• What is the expected behavior?
  OAS 3.1 is parseable.

• What is the motivation/use case for changing the behavior? (for feature requests)
  3.1 is the current version of the OpenAPI specification documented at https://swagger.io/specification/.

• Please tell us about your environment:

  • AMF Version:
  • AMF Distribution: JVM or JS
  • Operating System:
  • Link to your project:

• Other information (e.g. detailed explanation, stack traces, related issues, suggestions how to fix, links for us to have context, eg. StackOverflow, Gitter, etc)