anchor.diff:  already covered by the JAX-RS framework (e.g. the HTTP method of an operation).
   
   2. Take the initial output from `/openapi` as a starting point to document
  -your APIs is via <<Static OpenAPI files>>.  It's worth mentioning that these static
  +your APIs via <<Static OpenAPI files>>.  It's worth mentioning that these static
   files can also be written before any code, which is an approach often adopted by
   enterprises that want to lock-in the contract of the API.  In this case, we refer
   to the OpenAPI document as the "source of truth", by which the client and provider
  
positive.code: @POST
          @Path("/user")
          @Operation(summary = "Create user",
                  description = "This can only be done by the logged in user.")
          public Response methodWithRequestBodyAndTwoParameters(
                  @RequestBody(description = "Created user object", required = true,
                          content = @Content(
                                  schema = @Schema(implementation = User.class))) User user,
                  @QueryParam("name") String name, @QueryParam("code") String code)
                  { ... }
  ----
  
negative.code: @GET
  @Path("/{username}")
  @Operation(summary = "Get user by user name",
             responses = {
                  @APIResponse(description = "The user",
                               content = @Content(mediaType = "application/json",
                               schema = @Schema(implementation = User.class))),
                  @APIResponse(responseCode = "400", description = "User not found")})
  public Response getUserByName(
          @Parameter(description = "The name that needs to be fetched. Use user1 for testing. ", required = true) @PathParam("username") String username)
   {...}
  