anchor.diff:  1) All operations in OpenAPI spec need to have a tag, in camel case, that is translated to a REST-SERVER api operation. For example: 'createUser', gets translated to CREATE-USER entry point in REST-SERVER api.
   2) Operations in OpenAPI spec need to be tagged with a name for the resource. This is because REST-SERVER is designed based on an old version of Swagger API that groups operations in resources. But OpenAPI v3 does not group in resources, it just has paths. So, the tagging is needed for the OpenAPI -> REST-SERVER api translation. For example, if you have two paths, /invoice/{id}, and /invoice/{id}/payments, you should tag them both with 'Invoice', so that both operations are created under an INVOICE resource.
   
  -Use this together with DEFINE-SCHEMAS-FROM-SPEC 
  +Use this together with DEFINE-SCHEMAS-FROM-SPEC
   "
     (let ((spec (read-spec-file filepath)))
       (define-api-from-v3-spec name superclasses options spec)))
  
positive.code: (defun api-paths (api)
    (let ((paths (make-hash-table :test 'equalp)))
      (loop for resource being the hash-values of (rs::resources api)
         do
           (loop for operation being the hash-values of (rs::resource-operations resource)
              do
                (push (list :tag (rs:resource-name resource)
                            :operation operation)
                      (gethash (rs::path operation)
                               paths))))
      paths))
  
  (defun render-api-spec (api stream)
  
negative.code: 
  (defun parse-schemas-from-v3-spec (spec)
    (loop for (schema-name . schema-def) in (alist (access:accesses spec "components" "schemas"))
          collect
          (cons (intern (json::simplified-camel-case-to-lisp schema-name))
                (schemata.json-schema:schema-from-json-schema schema-def))))
  
  (defmacro define-schemas-from-spec (filepath)
    "Define REST-SERVER schemas from an OpenAPI spec file.
  