anchor.diff:  ==== Location and formats
   
   Vendors are required to fetch a single document named `openapi` with an extension
  -of `yml`, `yaml` or `json`, inside the application's `META-INF` folder.  If there
  -is more than one document found that matches one of these extensions the behavior
  -of which file is chosen is undefined (i.e. each vendor may implement their own logic),
  -which means that application developers should only place a single `openapi` document
  -into that folder.
  +of `yml`, `yaml` or `json`, inside the application module's (i.e. WAR artifact)
  +`META-INF` folder.  If there is more than one document found that matches one of
  +these extensions the behavior of which file is chosen is undefined (i.e. each vendor
  +may implement their own logic), which means that application developers should
  +only place a single `openapi` document into that folder.
   
   === Programming model
   
  
positive.code: the `/openapi` endpoint may be partitioned in the event that the MicroProfile
  runtime supports deployment of multiple applications. If an implementation wishes
  to support multiple applications within a MicroProfile runtime, the semantics of
  the `/openapi` endpoint are expected to be the logical AND of all the applications
  in the runtime, which would imply merging multiple OpenAPI documents into a single
  valid document (handling conflicting IDs and unique names).
  
  
negative.code: post:
    operationId: createBooking
    requestBody:
      description: Create a new booking.
      content:
        application/json:
          schema:
  