openapi: 3.0.2
info:
  version: '1.0.0-impl:etsi.org:ETSI_NFV_OpenAPI:1'
  title: SOL009 - NFV-MANO Log Management interface
  description: >
    SOL009 - NFV-MANO Log Management interface

    IMPORTANT: Please note that this file might be not aligned to the current
    version of the ETSI Group Specification
     it refers to. In case of discrepancies the published ETSI Group Specification takes precedence.

    Please report bugs to
    https://forge.etsi.org/bugzilla/buglist.cgi?component=Nfv-Openapis&list_id=61&product=NFV&resolution=
  license:
    name: ETSI Forge copyright notice
    url: 'https://forge.etsi.org/etsi-forge-copyright-notice.txt'
externalDocs:
  description: ETSI GS NFV-SOL 009 V3.3.1
  url: >-
    https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/009/03.03.01_60/gs_NFV-SOL009v030301p.pdf
security:
  - OauthSecurity:
      - all
servers:
  - url: 'http://127.0.0.1/nfvmanologm/v1'
  - url: 'https://127.0.0.1/nfvmanologm/v1'
paths:
  /api_versions:
    parameters:
      - name: Version
        description: |
          Version of the API requested to use when responding to this request.
        in: header
        required: false
        schema:
          type: string
      - name: Authorization
        description: 'The authorization token for the request. Reference: IETF RFC 7235'
        in: header
        required: false
        schema:
          type: string
    get:
      summary: Retrieve API version information
      description: >
        The GET method reads API version information. This method shall follow
        the provisions specified in table 4.6.3.3.3.2-1 for request and response
        data structures, and response codes. URI query parameters are not
        supported.
      responses:
        '200':
          description: >
            200 OK

            API version information was read successfully. The response body
            shall contain 4.4 API version information, as defined in clause
            4.4.1.13.
          content:
            application/json:
              schema:
                description: |
                  This type represents API version information.
                type: object
                required:
                  - uriPrefix
                  - apiVersions
                properties:
                  uriPrefix:
                    description: >
                      Specifies the URI prefix for the API, in the following
                      form {apiRoot}/{apiName}/{apiMajorVersion}/.
                    type: string
                  apiVersions:
                    description: >
                      Version(s) supported for the API signaled by the uriPrefix
                      attribute.
                    type: array
                    items:
                      type: object
                      required:
                        - version
                      properties:
                        version:
                          description: >
                            Identifies a supported version. The value of the
                            version attribute shall be a version identifier as
                            specified in clause 9.1 (SOL013).
                          type: string
                        isDeprecated:
                          description: >
                            If such information is available, this attribute
                            indicates whether use of the version signaled by the
                            version attribute is deprecated (true) or not
                            (false).

                            A deprecated version is still supported by the API
                            producer but is recommended not to be used any
                            longer. When a version is no longer supported, it
                            does not appear in the response body.
                          type: boolean
                        retirementDate:
                          description: >
                            Date-time stamp. Representation: String formatted
                            according to IETF RFC 3339.
                          type: string
                          format: date-time
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: The used API version.
              schema:
                type: string
                maximum: 1
                minimum: 1
        '400':
          description: >
            400 BAD REQUEST

            400 code can be returned in the following specified cases, the
            specific cause has to be proper specified in the "ProblemDetails"
            structure to be returned.

            If the request is malformed or syntactically incorrect (e.g. if the
            request URI contains incorrect query parameters or the payload body
            contains a syntactically incorrect data structure), the API producer
            shall respond with this response code. The "ProblemDetails"
            structure shall be provided, and should include in the "detail"
            attribute more information about the source of the problem.

            If the response to a GET request which queries a container resource
            would be so big that the performance of the API producer is
            adversely affected, and the API producer does not support paging for
            the affected resource, it shall respond with this response code. The
            "ProblemDetails" structure shall be provided, and should include in
            the "detail" attribute more information about the source of the
            problem.

            If there is an application error related to the client's input that
            cannot be easily mapped to any other HTTP response code ("catch all
            error"), the API producer shall respond with this response code. The
            "ProblemDetails" structure shall be provided, and shall include in
            the "detail" attribute more information about the source of the
            problem.

            If the request contains a malformed access token, the API producer
            should respond with this response. The details of the error shall be
            returned in the WWW Authenticate HTTP header, as defined in IETF RFC
            6750 and IETF RFC 7235. The ProblemDetails structure may be
            provided.

            The use of this HTTP error response code described above is
            applicable to the use of the OAuth 2.0 for the authorization of API
            requests and notifications, as defined in clauses 4.5.3.3 and
            4.5.3.4.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '401':
          description: >
            401 UNAUTHORIZED

            If the request contains no access token even though one is required,
            or if the request contains an authorization token that is invalid
            (e.g. expired or revoked), the API producer should respond with this
            response. The details of the error shall be returned in the
            WWW-Authenticate HTTP header, as defined in IETF RFC 6750 and IETF
            RFC 7235. The ProblemDetails structure may be provided.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '403':
          description: >
            403 FORBIDDEN

            If the API consumer is not allowed to perform a particular request
            to a particular resource, the API producer shall respond with this
            response code. The "ProblemDetails" structure shall be provided. It
            should include in the "detail" attribute information about the
            source of the problem, and may indicate how to solve it.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '404':
          description: >
            404 NOT FOUND

            If the API producer did not find a current representation for the
            resource addressed by the URI passed in the request or is not
            willing to disclose that one exists, it shall respond with this
            response code. The "ProblemDetails" structure may be provided,
            including in the "detail" attribute information about the source of
            the problem, e.g. a wrong resource URI variable.

            This response code is not appropriate in case the resource addressed
            by the URI is a container resource which is designed to contain
            child resources, but does not contain any child resource at the time
            the request is received. For a GET request to an existing empty
            container resource, a typical response contains a 200 OK response
            code and a payload body with an empty array.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '405':
          description: >
            405 METHOD NOT ALLOWED

            If a particular HTTP method is not supported for a particular
            resource, the API producer shall respond with this response code.
            The "ProblemDetails" structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '406':
          description: >
            406 NOT ACCEPTABLE

            If the "Accept" HTTP header does not contain at least one name of a
            content type that is acceptable to the API producer, the API
            producer shall respond with this response code. The "ProblemDetails"
            structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '413':
          description: >
            413 PAYLOAD TOO LARGE

            If the payload body of a request is larger than the amount of data
            the API producer is willing or able to process, it shall respond
            with this response code, following the provisions in IETF RFC 7231
            for the use of the "Retry-After" HTTP header and for closing the
            connection. The "ProblemDetails" structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '414':
          description: >
            414 URI TOO LONG

            If the request URI of a request is longer than the API producer is
            willing or able to process, it shall respond with this response
            code. This condition can e.g. be caused by passing long queries in
            the request URI of a GET request. The "ProblemDetails" structure may
            be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '416':
          description: |
            416 Range Not Satisfiable
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '422':
          description: >
            422 UNPROCESSABLE ENTITY

            If the payload body of a request contains syntactically correct data
            (e.g. well-formed JSON) but the data cannot be processed (e.g.
            because it fails validation against a schema), the API producer
            shall respond with this response code. The "ProblemDetails"
            structure shall be provided, and should include in the "detail"
            attribute more information about the source of the problem.

            This error response code is only applicable for methods that have a
            request body.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '429':
          description: >
            429 TOO MANY REQUESTS

            If the API consumer has sent too many requests in a defined period
            of time and the API producer is able to detect that condition ("rate
            limiting"), the API producer shall respond with this response code,
            following the provisions in IETF RFC 6585 [17] for the use of the
            "Retry-After" HTTP header. The "ProblemDetails" structure shall be
            provided and shall include in the "detail" attribute more
            information about the source of the problem.

            The period of time and allowed number of requests are configured
            within the API producer by means outside the scope of the present
            document.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '500':
          description: >
            500 INTERNAL SERVER ERROR

            If there is an application error not related to the client's input
            that cannot be easily mapped to any other HTTP response code ("catch
            all error"), the API producer shall respond with this response code.
            The "ProblemDetails" structure shall be provided, and shall include
            in the "detail" attribute more information about the source of the
            problem.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '503':
          description: >
            503 SERVICE UNAVAILABLE

            If the API producer encounters an internal overload situation of
            itself or of a system it relies on, it should respond with this
            response code, following the provisions in IETF RFC 7231 for the use
            of the "Retry-After" HTTP header and for the alternative to refuse
            the connection. The "ProblemDetails" structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '504':
          description: >
            504 GATEWAY TIMEOUT

            If the API producer encounters a timeout while waiting for a
            response from an upstream server (i.e. a server that the API
            producer communicates with when fulfilling a request), it should
            respond with this response code.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
  /log_jobs:
    description: >-
      This resource represents logging jobs. The API consumer can use this
      resource to create and query logging jobs.
    post:
      description: >-
        The POST method creates a logging job. This method shall follow the
        provisions specified in the tables 8.5.3.3.1-1 and 8.5.3.3.1-2 for URI
        query parameters, request and response data structures, and response
        codes. As the result of successfully executing this method, a new
        "Individual logging job" resource as defined in clause 9.5.4 shall have
        been created.
      parameters:
        - name: Version
          description: |
            Version of the API requested to use when responding to this request.
          in: header
          required: true
          schema:
            type: string
        - name: Accept
          description: >
            Content-Types that are acceptable for the response. Reference: IETF
            RFC 7231.
          in: header
          required: true
          schema:
            type: string
        - name: Content-Type
          description: |
            The MIME type of the body of the request. Reference: IETF RFC 7231
          in: header
          required: true
          schema:
            type: string
        - name: Authorization
          description: |
            The authorization token for the request. Reference: IETF RFC 7235.
          in: header
          required: false
          schema:
            type: string
      requestBody:
        description: >-
          This type represents a request to create a logging job. It shall
          comply with the provisions defined in table 8.6.2.5-1.
        content:
          application/json:
            schema:
              description: Information on application context created by the MEC system
              type: object
              required:
                - objectInstanceIds
                - jobCriteria
                - jobConfig
              properties:
                objectInstanceIds:
                  description: >-
                    Identifiers of the object instance for which logging
                    information is requested to be collected. This attribute
                    shall contain the identifier of the instance of the object
                    to be logged according to their type. If more than one
                    identifier is provided, values shall all refer to object
                    instances of the same type, for which the same criteria is
                    then applicable.
                  type: array
                  minItems: 1
                  items:
                    description: >
                      This type represents the identifier to reference a managed
                      object of a  particular type. 
                    type: object
                    properties:
                      type:
                        description: >
                          Indicates the type of managed object. Permitted
                          values:
                            - MANO_ENTITY
                            - MANO_SERVICE
                            - MANO_SERVICE_IF
                            - CONSUMED_MANO_IF
                            - MANO_ENTITY_COMPONENT

                          The "MANO_ENTITY COMPONENT" is only applicable if
                          attribute "manoEntityComponents" in "ManoEntity" is
                          supported by the API producer.
                        type: string
                        enum:
                          - MANO_ENTITY
                          - MANO_SERVICE
                          - MANO_SERVICE_IF
                          - CONSUMED_MANO_IF
                          - MANO_ENTITY_COMPONENT
                      objectId:
                        description: >
                          An identifier with the intention of being globally
                          unique.
                        type: string
                      subObjectId:
                        description: >
                          An identifier that is unique for the respective type
                          within a NFV-MANO functional entity, but that need not
                          be globally unique. Representation: string of variable
                          length..
                        type: string
                    required:
                      - type
                      - objectId
                jobCriteria:
                  description: >-
                    This type represents collection criteria for logging jobs.
                    It shall comply with the provisions defined in table
                    8.6.3.2-1.
                  type: object
                  required:
                    - loggingType
                  properties:
                    loggingType:
                      description: >-
                        Type of logging. This defines the types of logged
                        information to collect.

                        Permitted values: - MESSAGES: logged NFV-MANO service
                        interface messages. - SERVICES: logged messages about
                        processes pertaining to NFV-MANO services. - SYSTEM:
                        logged messages about the NFV-MANO functional entity’s
                        system enabled by the provider.
                      type: string
                      enum:
                        - MESSAGES
                        - SERVICES
                        - SYSTEM
                    messagesLogDetail:
                      description: >-
                        This type represents criteria for logging jobs to
                        collect logged messages on NFV-MANO service interfaces.
                        It shall comply with the provisions defined in table
                        8.6.3.3-1.
                      type: object
                      required:
                        - direction
                      properties:
                        direction:
                          description: >-
                            The direction of the interface messages to match.

                            Permitted values: - IN: input messages into the
                            interface. - OUT: output messages from the
                            interface. - ALL: both input and output messages
                            into/from the interface.
                          type: string
                          enum:
                            - IN
                            - OUT
                            - ALL
                        matchingPatterns:
                          description: >-
                            Patterns to be matched in the interface message. If
                            provided, only messages that match all the values
                            provided in the sub-attributes shall be logged. An
                            API consumer can provide more than one
                            "matchingPattern" if combinations of patterns are to
                            be considered to match diverse sets of interface
                            messages.
                          type: array
                          items:
                            type: object
                            anyOf:
                              - required:
                                  - srcIpAddress
                              - required:
                                  - dstIpAddress
                              - required:
                                  - requestMethod
                              - required:
                                  - requestUriPattern
                              - required:
                                  - responseCodes
                            properties:
                              srcIpAddress:
                                description: >
                                  An IPV4 or IPV6 address. Representation: In
                                  case of an IPV4 address, string that consists
                                  of four decimal integers separated by dots,
                                  each integer ranging from 0 to 255. In case of
                                  an IPV6 address, string that consists of
                                  groups of zero to four hexadecimal digits,
                                  separated by colons.
                                type: string
                                format: IP
                              requestMethod:
                                description: >-
                                  HTTP request method to be matched. To match,
                                  the HTTP request method of the message shall
                                  be the same as the value of this attribute.
                                  Valid values are specified in IETF RFC 7231.
                                  The API producer shall support this attribute.
                                type: string
                              requestUriPattern:
                                description: >-
                                  Substring to be matched in the request URI. To
                                  match, the request URI shall include the value
                                  of
                                   this attribute as a substring. This is typically used to match messages which associate to RESTful
                                   resources, or to a specific API (e.g., by using the "apiName" of the API). The API producer shall
                                   support this attribute.
                                type: string
                              dstIpAddress:
                                description: >
                                  An IPV4 or IPV6 address. Representation: In
                                  case of an IPV4 address, string that consists
                                  of four decimal integers separated by dots,
                                  each integer ranging from 0 to 255. In case of
                                  an IPV6 address, string that consists of
                                  groups of zero to four hexadecimal digits,
                                  separated by colons.
                                type: string
                                format: IP
                              responseCodes:
                                description: >-
                                  HTTP response codes or patterns to match. A
                                  list of all valid HTTP response codes and
                                  their specification documents can be obtained
                                  from the HTTP status code registry. In
                                  addition, if supported, the following patterns
                                  may be used (case-insensitive): - "1XX": for
                                  matching any kind of informational response. -
                                  "2XX": for matching any kind of success
                                  response. - "3XX": for matching any kind
                                  redirection response. - "4XX": for matching
                                  any kind of client error response. - "5XX":
                                  for matching any kind of server error
                                  response.

                                  The API producer shall support this attribute
                                type: array
                                items:
                                  type: string
                              headerField:
                                description: >-
                                  Name of the header field to be matched. The
                                  header field name shall be one of the
                                  supported fields in a request message as
                                  defined in clause 4.2.2 of ETSI GS NFV-SOL 013
                                  or in a response message as defined in clause
                                  4.2.3 of ETSI GS NFV-SOL 013, in accordance
                                  with the "direction" criteria input. The API
                                  producer may support this attribute.
                                type: string
                              headerValue:
                                description: >-
                                  Value in the header to be matched. To match,
                                  the value in the header field indicated by
                                  "headerField" shall be the same as in this
                                  attribute. Shall be provided if a
                                  "headerField" is provided. The API producer
                                  may support this attribute.
                                type: string
                              bodyValues:
                                description: >-
                                  A list of strings to be matched in the body
                                  part of the interface message (e.g., the body
                                  of an HTTP message). If provided, only
                                  messages with text in the body part containing
                                  all the values from the list shall match the
                                  filter. In addition to a matching filter for
                                  the body of the message, a corresponding
                                  "headerField" filter shall also be provided,
                                  with "headerField" set to "Content-Type", to
                                  restrict matching to appropriate textual
                                  payloads such as "application/json" or
                                  "text/plain". The API producer may support
                                  this attribute
                                type: string
                    servicesLogDetail:
                      description: >-
                        This type represents criteria for logging jobs to
                        collect logged messages about processes pertaining to
                        NFV-MANO services. It shall comply with the provisions
                        defined in table 8.6.3.4-1.
                      type: object
                      properties:
                        logGarbageCollection:
                          description: >-
                            Indicates to collect logged information about
                            garbage collection processes associated to NFV-MANO
                            services.
                          type: boolean
                    systemLogDetail:
                      description: >-
                        This type represents criteria for logging jobs to
                        collect logged system events of the NFV-MANO functional
                        entity. It shall comply with the provisions defined in
                        table 8.6.3.5-1.
                      type: object
                      required:
                        - systemLogs
                        - severityLevel
                      properties:
                        systemLogs:
                          description: >
                            This type represents a list of key-value pairs. The
                            order of the pairs in the list is not significant.
                            In JSON, a set of keyvalue pairs is represented as
                            an object. It shall comply with the provisions
                            defined in clause 4 of IETF RFC 8259. In the
                            following example, a list of key-value pairs with
                            four keys ("aString", "aNumber", "anArray" and
                            "anObject") is provided to illustrate that the
                            values associated with different keys can be of
                            different type.
                          type: object
                        severityLevelScheme:
                          description: >-
                            Identifies a severity level scheme. The default
                            value is "rfc5424", which represents the set of
                            values specified in the clause 6.2.1, table 2 of
                            IETF RFC 5424. Other values may be used to signal
                            different schemes.
                          type: string
                        severityLevel:
                          description: >-
                            The severity level, which determines the severity of
                            the system messages to collect. The NFV-MANO
                            functional entity shall collect system log messages,
                            as indicated by the "systemLogs" attribute, with
                            severity levels lower (i.e., more severe) or equal
                            to the value provided by this present attribute.
                          type: number
                jobConfig:
                  description: >-
                    This type represents configuration data for a logging job.
                    It shall comply with the provisions defined in table
                    8.6.3.6-1. NOTE: The present document version does not
                    specify the support for "log compilation and reporting based
                    on events" as specified in clause 6.6.2.2 of ETSI GS NFV-IFA
                    031.
                  type: object
                  required:
                    - reportingCondition
                    - securityConf
                  properties:
                    startTime:
                      description: >
                        Date-time stamp. Representation: String formatted
                        according to IETF RFC 3339.
                      type: string
                      format: date-time
                    endTime:
                      description: >
                        Date-time stamp. Representation: String formatted
                        according to IETF RFC 3339.
                      type: string
                      format: date-time
                    reportingCondition:
                      description: >-
                        Specifies the condition under which the producer will
                        report to the consumer about the compiled log data.
                      required:
                        - reportingType
                      properties:
                        reportingType:
                          description: >-
                            Specifies the type of reporting condition. Permitted
                            values: - REPORTING_ON_COMPILATION: the producer
                            shall notify the consumer once the compilation of
                            the
                                            collected logging data into a file is completed and a new log report is available.
                            - NO_REPORTING: no reporting is requested (the
                            consumer can query the logging jobs to know about
                            the
                                            availability of new log reports).
                          type: string
                          enum:
                            - REPORTING_ON_COMPILATION
                            - NO_REPORTING
                        minimumReportingPeriod:
                          description: >-
                            Specifies the minimum periodicity at which the
                            producer will report to the consumer about the
                            collected log information, in seconds.
                          type: integer
                          format: int32
                    compileBySizeValue:
                      description: >-
                        An indicative size threshold for compiling the collected
                        log data, in bytes. It is used when the compilation is
                        based on the size of the collected log data. If not
                        present, a default value as specified with the
                        "defaultLogCompileBySizeValue" configuration in the
                        "ManoEntityConfigurableParams" shall be used
                      type: integer
                      format: int32
                    compileByTimerValue:
                      description: >-
                        The periodicity threshold for compiling the filtered
                        log, in seconds. It is used when the compilation is
                        based on a timer (e.g., every 24 hours). If not present,
                        a default value as specified with the
                        "defaultLogCompileByTimerValue" configuration in the
                        "ManoEntityConfigurableParams" shall be used
                      type: integer
                      format: int32
                    securityConf:
                      description: >-
                        Configuration about the security aspects of the logging
                        job.
                      type: object
                      properties:
                        logFileEncryption:
                          description: >-
                            Information about the encryption of the compiled log
                            files. Shall be present if the log file is requested
                            to be encrypted.
                          required:
                            - encryptionCertificate
                            - cipherAlgorithm
                          type: object
                          properties:
                            encryptionCertificate:
                              description: >-
                                X.509 certificate with the public key to use for
                                the encryption of the compiled log file.
                              type: string
                            cipherAlgorithm:
                              description: >-
                                Cryptographic algorithm to be used for the
                                encryption of the compiled log file. More than
                                one algorithm can be provided from higher (lower
                                array index) to lower (higher array index)
                                precedence. Valid values are: "AES-CBC-128",
                                "AES-GCM-128", "AES-CBC-256", and "AES-GCM-256",
                                as specified in clause 6.5 of ETSI GS NFV-SEC
                                012
                              type: array
                              items:
                                type: string
                                minItems: 1
                            encryptAndSignOrder:
                              description: >-
                                Indication about the order in signing and
                                encrypting the compiled log file. Valid values
                                are: "encryptFirst", to apply the order "first
                                encrypt, then sign", and "signFirst" for the
                                order "first sign, then encrypt". Default value
                                is "encryptFirst".
                              type: string
                        logTransferSecurity:
                          description: >-
                            Information about the security measures for
                            retrieving/accessing the compiled log files.
                          type: object
                          properties:
                            publicKey:
                              description: >-
                                The public key of the API consumer used for the
                                client authentication with the file server.
                                Shall be provided if required by the type of
                                transfer protocol. May be omitted if the key has
                                been provided to the API producer by other
                                means, or if it has already been provided in
                                some previous CreateLoggingJobRequest issued by
                                the same API consumer, whose public key has not
                                changed.
                              type: string
        required: true
      responses:
        '201':
          description: >-
            The response body contains the Application Context as it was created
            by the MEC system
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
          content:
            application/json:
              schema:
                description: >-
                  This type represents a logging job. It shall comply with the
                  provisions defined in table 8.6.2.6-1.
                type: object
                required:
                  - id
                  - objectInstanceIds
                  - jobCriteria
                  - jobConfig
                  - _links
                properties:
                  id:
                    description: |
                      An identifier with the intention of being globally unique.
                    type: string
                  objectInstanceIds:
                    description: >-
                      Identifiers of the object instance for which logging
                      information is collected. This attribute shall contain the
                      identifier of the instance of the object that is logged
                      according to their type.
                    type: array
                    items:
                      description: >
                        This type represents the identifier to reference a
                        managed object of a  particular type. 
                      type: object
                      properties:
                        type:
                          description: >
                            Indicates the type of managed object. Permitted
                            values:
                              - MANO_ENTITY
                              - MANO_SERVICE
                              - MANO_SERVICE_IF
                              - CONSUMED_MANO_IF
                              - MANO_ENTITY_COMPONENT

                            The "MANO_ENTITY COMPONENT" is only applicable if
                            attribute "manoEntityComponents" in "ManoEntity" is
                            supported by the API producer.
                          type: string
                          enum:
                            - MANO_ENTITY
                            - MANO_SERVICE
                            - MANO_SERVICE_IF
                            - CONSUMED_MANO_IF
                            - MANO_ENTITY_COMPONENT
                        objectId:
                          description: >
                            An identifier with the intention of being globally
                            unique.
                          type: string
                        subObjectId:
                          description: >
                            An identifier that is unique for the respective type
                            within a NFV-MANO functional entity, but that need
                            not be globally unique. Representation: string of
                            variable length..
                          type: string
                      required:
                        - type
                        - objectId
                  jobCriteria:
                    description: >-
                      This type represents collection criteria for logging jobs.
                      It shall comply with the provisions defined in table
                      8.6.3.2-1.
                    type: object
                    required:
                      - loggingType
                    properties:
                      loggingType:
                        description: >-
                          Type of logging. This defines the types of logged
                          information to collect.

                          Permitted values: - MESSAGES: logged NFV-MANO service
                          interface messages. - SERVICES: logged messages about
                          processes pertaining to NFV-MANO services. - SYSTEM:
                          logged messages about the NFV-MANO functional entity’s
                          system enabled by the provider.
                        type: string
                        enum:
                          - MESSAGES
                          - SERVICES
                          - SYSTEM
                      messagesLogDetail:
                        description: >-
                          This type represents criteria for logging jobs to
                          collect logged messages on NFV-MANO service
                          interfaces. It shall comply with the provisions
                          defined in table 8.6.3.3-1.
                        type: object
                        required:
                          - direction
                        properties:
                          direction:
                            description: >-
                              The direction of the interface messages to match.

                              Permitted values: - IN: input messages into the
                              interface. - OUT: output messages from the
                              interface. - ALL: both input and output messages
                              into/from the interface.
                            type: string
                            enum:
                              - IN
                              - OUT
                              - ALL
                          matchingPatterns:
                            description: >-
                              Patterns to be matched in the interface message.
                              If provided, only messages that match all the
                              values provided in the sub-attributes shall be
                              logged. An API consumer can provide more than one
                              "matchingPattern" if combinations of patterns are
                              to be considered to match diverse sets of
                              interface messages.
                            type: array
                            items:
                              type: object
                              anyOf:
                                - required:
                                    - srcIpAddress
                                - required:
                                    - dstIpAddress
                                - required:
                                    - requestMethod
                                - required:
                                    - requestUriPattern
                                - required:
                                    - responseCodes
                              properties:
                                srcIpAddress:
                                  description: >
                                    An IPV4 or IPV6 address. Representation: In
                                    case of an IPV4 address, string that
                                    consists of four decimal integers separated
                                    by dots, each integer ranging from 0 to 255.
                                    In case of an IPV6 address, string that
                                    consists of groups of zero to four
                                    hexadecimal digits, separated by colons.
                                  type: string
                                  format: IP
                                requestMethod:
                                  description: >-
                                    HTTP request method to be matched. To match,
                                    the HTTP request method of the message shall
                                    be the same as the value of this attribute.
                                    Valid values are specified in IETF RFC 7231.
                                    The API producer shall support this
                                    attribute.
                                  type: string
                                requestUriPattern:
                                  description: >-
                                    Substring to be matched in the request URI.
                                    To match, the request URI shall include the
                                    value of
                                     this attribute as a substring. This is typically used to match messages which associate to RESTful
                                     resources, or to a specific API (e.g., by using the "apiName" of the API). The API producer shall
                                     support this attribute.
                                  type: string
                                dstIpAddress:
                                  description: >
                                    An IPV4 or IPV6 address. Representation: In
                                    case of an IPV4 address, string that
                                    consists of four decimal integers separated
                                    by dots, each integer ranging from 0 to 255.
                                    In case of an IPV6 address, string that
                                    consists of groups of zero to four
                                    hexadecimal digits, separated by colons.
                                  type: string
                                  format: IP
                                responseCodes:
                                  description: >-
                                    HTTP response codes or patterns to match. A
                                    list of all valid HTTP response codes and
                                    their specification documents can be
                                    obtained from the HTTP status code registry.
                                    In addition, if supported, the following
                                    patterns may be used (case-insensitive): -
                                    "1XX": for matching any kind of
                                    informational response. - "2XX": for
                                    matching any kind of success response. -
                                    "3XX": for matching any kind redirection
                                    response. - "4XX": for matching any kind of
                                    client error response. - "5XX": for matching
                                    any kind of server error response.

                                    The API producer shall support this
                                    attribute
                                  type: array
                                  items:
                                    type: string
                                headerField:
                                  description: >-
                                    Name of the header field to be matched. The
                                    header field name shall be one of the
                                    supported fields in a request message as
                                    defined in clause 4.2.2 of ETSI GS NFV-SOL
                                    013 or in a response message as defined in
                                    clause 4.2.3 of ETSI GS NFV-SOL 013, in
                                    accordance with the "direction" criteria
                                    input. The API producer may support this
                                    attribute.
                                  type: string
                                headerValue:
                                  description: >-
                                    Value in the header to be matched. To match,
                                    the value in the header field indicated by
                                    "headerField" shall be the same as in this
                                    attribute. Shall be provided if a
                                    "headerField" is provided. The API producer
                                    may support this attribute.
                                  type: string
                                bodyValues:
                                  description: >-
                                    A list of strings to be matched in the body
                                    part of the interface message (e.g., the
                                    body of an HTTP message). If provided, only
                                    messages with text in the body part
                                    containing all the values from the list
                                    shall match the filter. In addition to a
                                    matching filter for the body of the message,
                                    a corresponding "headerField" filter shall
                                    also be provided, with "headerField" set to
                                    "Content-Type", to restrict matching to
                                    appropriate textual payloads such as
                                    "application/json" or "text/plain". The API
                                    producer may support this attribute
                                  type: string
                      servicesLogDetail:
                        description: >-
                          This type represents criteria for logging jobs to
                          collect logged messages about processes pertaining to
                          NFV-MANO services. It shall comply with the provisions
                          defined in table 8.6.3.4-1.
                        type: object
                        properties:
                          logGarbageCollection:
                            description: >-
                              Indicates to collect logged information about
                              garbage collection processes associated to
                              NFV-MANO services.
                            type: boolean
                      systemLogDetail:
                        description: >-
                          This type represents criteria for logging jobs to
                          collect logged system events of the NFV-MANO
                          functional entity. It shall comply with the provisions
                          defined in table 8.6.3.5-1.
                        type: object
                        required:
                          - systemLogs
                          - severityLevel
                        properties:
                          systemLogs:
                            description: >
                              This type represents a list of key-value pairs.
                              The order of the pairs in the list is not
                              significant. In JSON, a set of keyvalue pairs is
                              represented as an object. It shall comply with the
                              provisions defined in clause 4 of IETF RFC 8259.
                              In the following example, a list of key-value
                              pairs with four keys ("aString", "aNumber",
                              "anArray" and "anObject") is provided to
                              illustrate that the values associated with
                              different keys can be of different type.
                            type: object
                          severityLevelScheme:
                            description: >-
                              Identifies a severity level scheme. The default
                              value is "rfc5424", which represents the set of
                              values specified in the clause 6.2.1, table 2 of
                              IETF RFC 5424. Other values may be used to signal
                              different schemes.
                            type: string
                          severityLevel:
                            description: >-
                              The severity level, which determines the severity
                              of the system messages to collect. The NFV-MANO
                              functional entity shall collect system log
                              messages, as indicated by the "systemLogs"
                              attribute, with severity levels lower (i.e., more
                              severe) or equal to the value provided by this
                              present attribute.
                            type: number
                  jobConfig:
                    description: >-
                      This type represents configuration data for a logging job.
                      It shall comply with the provisions defined in table
                      8.6.3.6-1. NOTE: The present document version does not
                      specify the support for "log compilation and reporting
                      based on events" as specified in clause 6.6.2.2 of ETSI GS
                      NFV-IFA 031.
                    type: object
                    required:
                      - reportingCondition
                      - securityConf
                    properties:
                      startTime:
                        description: >
                          Date-time stamp. Representation: String formatted
                          according to IETF RFC 3339.
                        type: string
                        format: date-time
                      endTime:
                        description: >
                          Date-time stamp. Representation: String formatted
                          according to IETF RFC 3339.
                        type: string
                        format: date-time
                      reportingCondition:
                        description: >-
                          Specifies the condition under which the producer will
                          report to the consumer about the compiled log data.
                        required:
                          - reportingType
                        properties:
                          reportingType:
                            description: >-
                              Specifies the type of reporting condition.
                              Permitted values: - REPORTING_ON_COMPILATION: the
                              producer shall notify the consumer once the
                              compilation of the
                                              collected logging data into a file is completed and a new log report is available.
                              - NO_REPORTING: no reporting is requested (the
                              consumer can query the logging jobs to know about
                              the
                                              availability of new log reports).
                            type: string
                            enum:
                              - REPORTING_ON_COMPILATION
                              - NO_REPORTING
                          minimumReportingPeriod:
                            description: >-
                              Specifies the minimum periodicity at which the
                              producer will report to the consumer about the
                              collected log information, in seconds.
                            type: integer
                            format: int32
                      compileBySizeValue:
                        description: >-
                          An indicative size threshold for compiling the
                          collected log data, in bytes. It is used when the
                          compilation is based on the size of the collected log
                          data. If not present, a default value as specified
                          with the "defaultLogCompileBySizeValue" configuration
                          in the "ManoEntityConfigurableParams" shall be used
                        type: integer
                        format: int32
                      compileByTimerValue:
                        description: >-
                          The periodicity threshold for compiling the filtered
                          log, in seconds. It is used when the compilation is
                          based on a timer (e.g., every 24 hours). If not
                          present, a default value as specified with the
                          "defaultLogCompileByTimerValue" configuration in the
                          "ManoEntityConfigurableParams" shall be used
                        type: integer
                        format: int32
                      securityConf:
                        description: >-
                          Configuration about the security aspects of the
                          logging job.
                        type: object
                        properties:
                          logFileEncryption:
                            description: >-
                              Information about the encryption of the compiled
                              log files. Shall be present if the log file is
                              requested to be encrypted.
                            required:
                              - encryptionCertificate
                              - cipherAlgorithm
                            type: object
                            properties:
                              encryptionCertificate:
                                description: >-
                                  X.509 certificate with the public key to use
                                  for the encryption of the compiled log file.
                                type: string
                              cipherAlgorithm:
                                description: >-
                                  Cryptographic algorithm to be used for the
                                  encryption of the compiled log file. More than
                                  one algorithm can be provided from higher
                                  (lower array index) to lower (higher array
                                  index) precedence. Valid values are:
                                  "AES-CBC-128", "AES-GCM-128", "AES-CBC-256",
                                  and "AES-GCM-256", as specified in clause 6.5
                                  of ETSI GS NFV-SEC 012
                                type: array
                                items:
                                  type: string
                                  minItems: 1
                              encryptAndSignOrder:
                                description: >-
                                  Indication about the order in signing and
                                  encrypting the compiled log file. Valid values
                                  are: "encryptFirst", to apply the order "first
                                  encrypt, then sign", and "signFirst" for the
                                  order "first sign, then encrypt". Default
                                  value is "encryptFirst".
                                type: string
                          logTransferSecurity:
                            description: >-
                              Information about the security measures for
                              retrieving/accessing the compiled log files.
                            type: object
                            properties:
                              publicKey:
                                description: >-
                                  The public key of the API consumer used for
                                  the client authentication with the file
                                  server. Shall be provided if required by the
                                  type of transfer protocol. May be omitted if
                                  the key has been provided to the API producer
                                  by other means, or if it has already been
                                  provided in some previous
                                  CreateLoggingJobRequest issued by the same API
                                  consumer, whose public key has not changed.
                                type: string
                  logReports:
                    description: >-
                      Information about available log reports created by the
                      logging job.
                    type: array
                    items:
                      type: object
                      required:
                        - logReportId
                        - logReportLoc
                      properties:
                        logReportId:
                          description: >
                            An identifier with the intention of being globally
                            unique.
                          type: string
                        logReportLoc:
                          description: >
                            This type represents a link to a resource using an
                            absolute URI.
                          type: object
                          required:
                            - href
                          properties:
                            href:
                              description: |
                                String formatted according to IETF RFC 3986.
                              type: string
                  _links:
                    description: Links for this resource.
                    type: object
                    required:
                      - self
                    properties:
                      self:
                        description: >
                          This type represents a link to a resource using an
                          absolute URI.
                        type: object
                        required:
                          - href
                        properties:
                          href:
                            description: |
                              String formatted according to IETF RFC 3986.
                            type: string
                      objects:
                        description: >-
                          Links to resources representing the object instances
                          that are logged. Shall be present if the logged object
                          instance information is accessible as a resource.
                        type: array
                        items:
                          description: >
                            This type represents a link to a resource using an
                            absolute URI.
                          type: object
                          required:
                            - href
                          properties:
                            href:
                              description: |
                                String formatted according to IETF RFC 3986.
                              type: string
        '400':
          description: >
            400 BAD REQUEST

            400 code can be returned in the following specified cases, the
            specific cause has to be proper specified in the "ProblemDetails"
            structure to be returned.

            If the request is malformed or syntactically incorrect (e.g. if the
            request URI contains incorrect query parameters or the payload body
            contains a syntactically incorrect data structure), the API producer
            shall respond with this response code. The "ProblemDetails"
            structure shall be provided, and should include in the "detail"
            attribute more information about the source of the problem.

            If the response to a GET request which queries a container resource
            would be so big that the performance of the API producer is
            adversely affected, and the API producer does not support paging for
            the affected resource, it shall respond with this response code. The
            "ProblemDetails" structure shall be provided, and should include in
            the "detail" attribute more information about the source of the
            problem.

            If there is an application error related to the client's input that
            cannot be easily mapped to any other HTTP response code ("catch all
            error"), the API producer shall respond with this response code. The
            "ProblemDetails" structure shall be provided, and shall include in
            the "detail" attribute more information about the source of the
            problem.

            If the request contains a malformed access token, the API producer
            should respond with this response. The details of the error shall be
            returned in the WWW Authenticate HTTP header, as defined in IETF RFC
            6750 and IETF RFC 7235. The ProblemDetails structure may be
            provided.

            The use of this HTTP error response code described above is
            applicable to the use of the OAuth 2.0 for the authorization of API
            requests and notifications, as defined in clauses 4.5.3.3 and
            4.5.3.4.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '401':
          description: >
            401 UNAUTHORIZED

            If the request contains no access token even though one is required,
            or if the request contains an authorization token that is invalid
            (e.g. expired or revoked), the API producer should respond with this
            response. The details of the error shall be returned in the
            WWW-Authenticate HTTP header, as defined in IETF RFC 6750 and IETF
            RFC 7235. The ProblemDetails structure may be provided.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '403':
          description: >
            403 FORBIDDEN

            If the API consumer is not allowed to perform a particular request
            to a particular resource, the API producer shall respond with this
            response code. The "ProblemDetails" structure shall be provided. It
            should include in the "detail" attribute information about the
            source of the problem, and may indicate how to solve it.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '404':
          description: >
            404 NOT FOUND

            If the API producer did not find a current representation for the
            resource addressed by the URI passed in the request or is not
            willing to disclose that one exists, it shall respond with this
            response code. The "ProblemDetails" structure may be provided,
            including in the "detail" attribute information about the source of
            the problem, e.g. a wrong resource URI variable.

            This response code is not appropriate in case the resource addressed
            by the URI is a container resource which is designed to contain
            child resources, but does not contain any child resource at the time
            the request is received. For a GET request to an existing empty
            container resource, a typical response contains a 200 OK response
            code and a payload body with an empty array.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '405':
          description: >
            405 METHOD NOT ALLOWED

            If a particular HTTP method is not supported for a particular
            resource, the API producer shall respond with this response code.
            The "ProblemDetails" structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '406':
          description: >
            406 NOT ACCEPTABLE

            If the "Accept" HTTP header does not contain at least one name of a
            content type that is acceptable to the API producer, the API
            producer shall respond with this response code. The "ProblemDetails"
            structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '422':
          description: >
            422 UNPROCESSABLE ENTITY

            If the payload body of a request contains syntactically correct data
            (e.g. well-formed JSON) but the data cannot be processed (e.g.
            because it fails validation against a schema), the API producer
            shall respond with this response code. The "ProblemDetails"
            structure shall be provided, and should include in the "detail"
            attribute more information about the source of the problem.

            This error response code is only applicable for methods that have a
            request body.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '500':
          description: >
            500 INTERNAL SERVER ERROR

            If there is an application error not related to the client's input
            that cannot be easily mapped to any other HTTP response code ("catch
            all error"), the API producer shall respond with this response code.
            The "ProblemDetails" structure shall be provided, and shall include
            in the "detail" attribute more information about the source of the
            problem.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '503':
          description: >
            503 SERVICE UNAVAILABLE

            If the API producer encounters an internal overload situation of
            itself or of a system it relies on, it should respond with this
            response code, following the provisions in IETF RFC 7231 for the use
            of the "Retry-After" HTTP header and for the alternative to refuse
            the connection. The "ProblemDetails" structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '504':
          description: >
            504 GATEWAY TIMEOUT

            If the API producer encounters a timeout while waiting for a
            response from an upstream server (i.e. a server that the API
            producer communicates with when fulfilling a request), it should
            respond with this response code.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
    get:
      description: >-
        The API consumer can use this method to retrieve information about
        logging jobs. This method shall follow the provisions specified in the
        tables 8.5.3.3.2-1 and 8.5.3.3.2-2 for URI query parameters, request and
        response data structures, and response codes.
      parameters:
        - name: filter
          description: >
            Attribute-based filtering expression according to clause 5.2 of ETSI
            GS NFV-SOL 013. The NFV-MANO functional entity shall support
            receiving this parameter as part of the URI query string. The API
            consumer may supply this parameter. All attribute names that appear
            in the FmSubscription and in data types referenced from it shall be
            supported by the NFV-MANO functional entity in the filter
            expression.
          in: query
          required: false
          schema:
            type: string
        - name: all_fields
          description: >
            Include all complex attributes in the response. See clause  5.3 of
            ETSI GS NFV-SOL 013. The NFV-MANO functional entity  shall support
            this parameter.
          in: query
          required: false
          schema:
            type: string
        - name: fields
          description: >
            Complex attributes to be included into the response. See clause  5.3
            of ETSI GS NFV-SOL 013 for details. The NFV-MANO functional  entity
            should support this parameter.
          in: query
          required: false
          schema:
            type: string
        - name: exclude_fields
          description: >
            Complex attributes to be excluded from the response. See clause  5.3
            of ETSI GS NFV-SOL 013 for details. The NFV-MANO functional  entity
            should support this parameter.
          in: query
          required: false
          schema:
            type: string
        - name: exclude_default
          in: query
          description: >-
            Indicates to exclude the following complex attributes from the
            response. See clause 5.3 of ETSI GS NFV-SOL 013 for details. The
            NFV-MANO functional entity shall support this parameter.
          required: false
          schema:
            type: string
        - name: nextpage_opaque_marker
          description: >
            Marker to obtain the next page of a paged response. Shall be
            supported by  the NFV-MANO functional entity if the entity supports
            alternative 2 (paging)  according to clause 5.4.2.1 of ETSI GS
            NFV-SOL 013 for this resource.
          in: query
          required: false
          schema:
            type: string
        - name: Version
          description: |
            Version of the API requested to use when responding to this request.
          in: header
          required: true
          schema:
            type: string
        - name: Accept
          description: >
            Content-Types that are acceptable for the response. Reference: IETF
            RFC 7231.
          in: header
          required: true
          schema:
            type: string
        - name: Authorization
          description: |
            The authorization token for the request. Reference: IETF RFC 7235.
          in: header
          required: false
          schema:
            type: string
      responses:
        '200':
          description: >-
            Shall be returned when information about zero or more logging jobs
            has been queried successfully.

            The response body shall contain in an array the representations of
            zero or more logging jobs, as defined in clause 8.6.2.6.

            If the "filter" URI parameter or one of the "all_fields", "fields"
            (if supported), "exclude_fields" (if supported) or "exclude_default"
            URI parameters was supplied in the request, the data in the response
            body shall have been transformed according to the rules specified in
            clauses 5.2.2 and 5.3.2 of ETSI GS NFV-SOL 013, respectively.

            If the NFV-MANO functional entity supports alternative 2 (paging)
            according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 for this
            resource, inclusion of the Link HTTP header in this response shall
            follow the provisions in clause 5.4.2.3 of ETSI GS NFV-SOL 013.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
          content:
            application/json:
              schema:
                type: array
                items:
                  description: >-
                    This type represents a logging job. It shall comply with the
                    provisions defined in table 8.6.2.6-1.
                  type: object
                  required:
                    - id
                    - objectInstanceIds
                    - jobCriteria
                    - jobConfig
                    - _links
                  properties:
                    id:
                      description: >
                        An identifier with the intention of being globally
                        unique.
                      type: string
                    objectInstanceIds:
                      description: >-
                        Identifiers of the object instance for which logging
                        information is collected. This attribute shall contain
                        the identifier of the instance of the object that is
                        logged according to their type.
                      type: array
                      items:
                        description: >
                          This type represents the identifier to reference a
                          managed object of a  particular type. 
                        type: object
                        properties:
                          type:
                            description: >
                              Indicates the type of managed object. Permitted
                              values:
                                - MANO_ENTITY
                                - MANO_SERVICE
                                - MANO_SERVICE_IF
                                - CONSUMED_MANO_IF
                                - MANO_ENTITY_COMPONENT

                              The "MANO_ENTITY COMPONENT" is only applicable if
                              attribute "manoEntityComponents" in "ManoEntity"
                              is supported by the API producer.
                            type: string
                            enum:
                              - MANO_ENTITY
                              - MANO_SERVICE
                              - MANO_SERVICE_IF
                              - CONSUMED_MANO_IF
                              - MANO_ENTITY_COMPONENT
                          objectId:
                            description: >
                              An identifier with the intention of being globally
                              unique.
                            type: string
                          subObjectId:
                            description: >
                              An identifier that is unique for the respective
                              type within a NFV-MANO functional entity, but that
                              need not be globally unique. Representation:
                              string of variable length..
                            type: string
                        required:
                          - type
                          - objectId
                    jobCriteria:
                      description: >-
                        This type represents collection criteria for logging
                        jobs. It shall comply with the provisions defined in
                        table 8.6.3.2-1.
                      type: object
                      required:
                        - loggingType
                      properties:
                        loggingType:
                          description: >-
                            Type of logging. This defines the types of logged
                            information to collect.

                            Permitted values: - MESSAGES: logged NFV-MANO
                            service interface messages. - SERVICES: logged
                            messages about processes pertaining to NFV-MANO
                            services. - SYSTEM: logged messages about the
                            NFV-MANO functional entity’s system enabled by the
                            provider.
                          type: string
                          enum:
                            - MESSAGES
                            - SERVICES
                            - SYSTEM
                        messagesLogDetail:
                          description: >-
                            This type represents criteria for logging jobs to
                            collect logged messages on NFV-MANO service
                            interfaces. It shall comply with the provisions
                            defined in table 8.6.3.3-1.
                          type: object
                          required:
                            - direction
                          properties:
                            direction:
                              description: >-
                                The direction of the interface messages to
                                match.

                                Permitted values: - IN: input messages into the
                                interface. - OUT: output messages from the
                                interface. - ALL: both input and output messages
                                into/from the interface.
                              type: string
                              enum:
                                - IN
                                - OUT
                                - ALL
                            matchingPatterns:
                              description: >-
                                Patterns to be matched in the interface message.
                                If provided, only messages that match all the
                                values provided in the sub-attributes shall be
                                logged. An API consumer can provide more than
                                one "matchingPattern" if combinations of
                                patterns are to be considered to match diverse
                                sets of interface messages.
                              type: array
                              items:
                                type: object
                                anyOf:
                                  - required:
                                      - srcIpAddress
                                  - required:
                                      - dstIpAddress
                                  - required:
                                      - requestMethod
                                  - required:
                                      - requestUriPattern
                                  - required:
                                      - responseCodes
                                properties:
                                  srcIpAddress:
                                    description: >
                                      An IPV4 or IPV6 address. Representation:
                                      In case of an IPV4 address, string that
                                      consists of four decimal integers
                                      separated by dots, each integer ranging
                                      from 0 to 255. In case of an IPV6 address,
                                      string that consists of groups of zero to
                                      four hexadecimal digits, separated by
                                      colons.
                                    type: string
                                    format: IP
                                  requestMethod:
                                    description: >-
                                      HTTP request method to be matched. To
                                      match, the HTTP request method of the
                                      message shall be the same as the value of
                                      this attribute. Valid values are specified
                                      in IETF RFC 7231. The API producer shall
                                      support this attribute.
                                    type: string
                                  requestUriPattern:
                                    description: >-
                                      Substring to be matched in the request
                                      URI. To match, the request URI shall
                                      include the value of
                                       this attribute as a substring. This is typically used to match messages which associate to RESTful
                                       resources, or to a specific API (e.g., by using the "apiName" of the API). The API producer shall
                                       support this attribute.
                                    type: string
                                  dstIpAddress:
                                    description: >
                                      An IPV4 or IPV6 address. Representation:
                                      In case of an IPV4 address, string that
                                      consists of four decimal integers
                                      separated by dots, each integer ranging
                                      from 0 to 255. In case of an IPV6 address,
                                      string that consists of groups of zero to
                                      four hexadecimal digits, separated by
                                      colons.
                                    type: string
                                    format: IP
                                  responseCodes:
                                    description: >-
                                      HTTP response codes or patterns to match.
                                      A list of all valid HTTP response codes
                                      and their specification documents can be
                                      obtained from the HTTP status code
                                      registry. In addition, if supported, the
                                      following patterns may be used
                                      (case-insensitive): - "1XX": for matching
                                      any kind of informational response. -
                                      "2XX": for matching any kind of success
                                      response. - "3XX": for matching any kind
                                      redirection response. - "4XX": for
                                      matching any kind of client error
                                      response. - "5XX": for matching any kind
                                      of server error response.

                                      The API producer shall support this
                                      attribute
                                    type: array
                                    items:
                                      type: string
                                  headerField:
                                    description: >-
                                      Name of the header field to be matched.
                                      The header field name shall be one of the
                                      supported fields in a request message as
                                      defined in clause 4.2.2 of ETSI GS NFV-SOL
                                      013 or in a response message as defined in
                                      clause 4.2.3 of ETSI GS NFV-SOL 013, in
                                      accordance with the "direction" criteria
                                      input. The API producer may support this
                                      attribute.
                                    type: string
                                  headerValue:
                                    description: >-
                                      Value in the header to be matched. To
                                      match, the value in the header field
                                      indicated by "headerField" shall be the
                                      same as in this attribute. Shall be
                                      provided if a "headerField" is provided.
                                      The API producer may support this
                                      attribute.
                                    type: string
                                  bodyValues:
                                    description: >-
                                      A list of strings to be matched in the
                                      body part of the interface message (e.g.,
                                      the body of an HTTP message). If provided,
                                      only messages with text in the body part
                                      containing all the values from the list
                                      shall match the filter. In addition to a
                                      matching filter for the body of the
                                      message, a corresponding "headerField"
                                      filter shall also be provided, with
                                      "headerField" set to "Content-Type", to
                                      restrict matching to appropriate textual
                                      payloads such as "application/json" or
                                      "text/plain". The API producer may support
                                      this attribute
                                    type: string
                        servicesLogDetail:
                          description: >-
                            This type represents criteria for logging jobs to
                            collect logged messages about processes pertaining
                            to NFV-MANO services. It shall comply with the
                            provisions defined in table 8.6.3.4-1.
                          type: object
                          properties:
                            logGarbageCollection:
                              description: >-
                                Indicates to collect logged information about
                                garbage collection processes associated to
                                NFV-MANO services.
                              type: boolean
                        systemLogDetail:
                          description: >-
                            This type represents criteria for logging jobs to
                            collect logged system events of the NFV-MANO
                            functional entity. It shall comply with the
                            provisions defined in table 8.6.3.5-1.
                          type: object
                          required:
                            - systemLogs
                            - severityLevel
                          properties:
                            systemLogs:
                              description: >
                                This type represents a list of key-value pairs.
                                The order of the pairs in the list is not
                                significant. In JSON, a set of keyvalue pairs is
                                represented as an object. It shall comply with
                                the provisions defined in clause 4 of IETF RFC
                                8259. In the following example, a list of
                                key-value pairs with four keys ("aString",
                                "aNumber", "anArray" and "anObject") is provided
                                to illustrate that the values associated with
                                different keys can be of different type.
                              type: object
                            severityLevelScheme:
                              description: >-
                                Identifies a severity level scheme. The default
                                value is "rfc5424", which represents the set of
                                values specified in the clause 6.2.1, table 2 of
                                IETF RFC 5424. Other values may be used to
                                signal different schemes.
                              type: string
                            severityLevel:
                              description: >-
                                The severity level, which determines the
                                severity of the system messages to collect. The
                                NFV-MANO functional entity shall collect system
                                log messages, as indicated by the "systemLogs"
                                attribute, with severity levels lower (i.e.,
                                more severe) or equal to the value provided by
                                this present attribute.
                              type: number
                    jobConfig:
                      description: >-
                        This type represents configuration data for a logging
                        job. It shall comply with the provisions defined in
                        table 8.6.3.6-1. NOTE: The present document version does
                        not specify the support for "log compilation and
                        reporting based on events" as specified in clause
                        6.6.2.2 of ETSI GS NFV-IFA 031.
                      type: object
                      required:
                        - reportingCondition
                        - securityConf
                      properties:
                        startTime:
                          description: >
                            Date-time stamp. Representation: String formatted
                            according to IETF RFC 3339.
                          type: string
                          format: date-time
                        endTime:
                          description: >
                            Date-time stamp. Representation: String formatted
                            according to IETF RFC 3339.
                          type: string
                          format: date-time
                        reportingCondition:
                          description: >-
                            Specifies the condition under which the producer
                            will report to the consumer about the compiled log
                            data.
                          required:
                            - reportingType
                          properties:
                            reportingType:
                              description: >-
                                Specifies the type of reporting condition.
                                Permitted values: - REPORTING_ON_COMPILATION:
                                the producer shall notify the consumer once the
                                compilation of the
                                                collected logging data into a file is completed and a new log report is available.
                                - NO_REPORTING: no reporting is requested (the
                                consumer can query the logging jobs to know
                                about the
                                                availability of new log reports).
                              type: string
                              enum:
                                - REPORTING_ON_COMPILATION
                                - NO_REPORTING
                            minimumReportingPeriod:
                              description: >-
                                Specifies the minimum periodicity at which the
                                producer will report to the consumer about the
                                collected log information, in seconds.
                              type: integer
                              format: int32
                        compileBySizeValue:
                          description: >-
                            An indicative size threshold for compiling the
                            collected log data, in bytes. It is used when the
                            compilation is based on the size of the collected
                            log data. If not present, a default value as
                            specified with the "defaultLogCompileBySizeValue"
                            configuration in the "ManoEntityConfigurableParams"
                            shall be used
                          type: integer
                          format: int32
                        compileByTimerValue:
                          description: >-
                            The periodicity threshold for compiling the filtered
                            log, in seconds. It is used when the compilation is
                            based on a timer (e.g., every 24 hours). If not
                            present, a default value as specified with the
                            "defaultLogCompileByTimerValue" configuration in the
                            "ManoEntityConfigurableParams" shall be used
                          type: integer
                          format: int32
                        securityConf:
                          description: >-
                            Configuration about the security aspects of the
                            logging job.
                          type: object
                          properties:
                            logFileEncryption:
                              description: >-
                                Information about the encryption of the compiled
                                log files. Shall be present if the log file is
                                requested to be encrypted.
                              required:
                                - encryptionCertificate
                                - cipherAlgorithm
                              type: object
                              properties:
                                encryptionCertificate:
                                  description: >-
                                    X.509 certificate with the public key to use
                                    for the encryption of the compiled log file.
                                  type: string
                                cipherAlgorithm:
                                  description: >-
                                    Cryptographic algorithm to be used for the
                                    encryption of the compiled log file. More
                                    than one algorithm can be provided from
                                    higher (lower array index) to lower (higher
                                    array index) precedence. Valid values are:
                                    "AES-CBC-128", "AES-GCM-128", "AES-CBC-256",
                                    and "AES-GCM-256", as specified in clause
                                    6.5 of ETSI GS NFV-SEC 012
                                  type: array
                                  items:
                                    type: string
                                    minItems: 1
                                encryptAndSignOrder:
                                  description: >-
                                    Indication about the order in signing and
                                    encrypting the compiled log file. Valid
                                    values are: "encryptFirst", to apply the
                                    order "first encrypt, then sign", and
                                    "signFirst" for the order "first sign, then
                                    encrypt". Default value is "encryptFirst".
                                  type: string
                            logTransferSecurity:
                              description: >-
                                Information about the security measures for
                                retrieving/accessing the compiled log files.
                              type: object
                              properties:
                                publicKey:
                                  description: >-
                                    The public key of the API consumer used for
                                    the client authentication with the file
                                    server. Shall be provided if required by the
                                    type of transfer protocol. May be omitted if
                                    the key has been provided to the API
                                    producer by other means, or if it has
                                    already been provided in some previous
                                    CreateLoggingJobRequest issued by the same
                                    API consumer, whose public key has not
                                    changed.
                                  type: string
                    logReports:
                      description: >-
                        Information about available log reports created by the
                        logging job.
                      type: array
                      items:
                        type: object
                        required:
                          - logReportId
                          - logReportLoc
                        properties:
                          logReportId:
                            description: >
                              An identifier with the intention of being globally
                              unique.
                            type: string
                          logReportLoc:
                            description: >
                              This type represents a link to a resource using an
                              absolute URI.
                            type: object
                            required:
                              - href
                            properties:
                              href:
                                description: |
                                  String formatted according to IETF RFC 3986.
                                type: string
                    _links:
                      description: Links for this resource.
                      type: object
                      required:
                        - self
                      properties:
                        self:
                          description: >
                            This type represents a link to a resource using an
                            absolute URI.
                          type: object
                          required:
                            - href
                          properties:
                            href:
                              description: |
                                String formatted according to IETF RFC 3986.
                              type: string
                        objects:
                          description: >-
                            Links to resources representing the object instances
                            that are logged. Shall be present if the logged
                            object instance information is accessible as a
                            resource.
                          type: array
                          items:
                            description: >
                              This type represents a link to a resource using an
                              absolute URI.
                            type: object
                            required:
                              - href
                            properties:
                              href:
                                description: |
                                  String formatted according to IETF RFC 3986.
                                type: string
        '400':
          description: >
            400 BAD REQUEST

            400 code can be returned in the following specified cases, the
            specific cause has to be proper specified in the "ProblemDetails"
            structure to be returned.

            If the request is malformed or syntactically incorrect (e.g. if the
            request URI contains incorrect query parameters or the payload body
            contains a syntactically incorrect data structure), the API producer
            shall respond with this response code. The "ProblemDetails"
            structure shall be provided, and should include in the "detail"
            attribute more information about the source of the problem.

            If the response to a GET request which queries a container resource
            would be so big that the performance of the API producer is
            adversely affected, and the API producer does not support paging for
            the affected resource, it shall respond with this response code. The
            "ProblemDetails" structure shall be provided, and should include in
            the "detail" attribute more information about the source of the
            problem.

            If there is an application error related to the client's input that
            cannot be easily mapped to any other HTTP response code ("catch all
            error"), the API producer shall respond with this response code. The
            "ProblemDetails" structure shall be provided, and shall include in
            the "detail" attribute more information about the source of the
            problem.

            If the request contains a malformed access token, the API producer
            should respond with this response. The details of the error shall be
            returned in the WWW Authenticate HTTP header, as defined in IETF RFC
            6750 and IETF RFC 7235. The ProblemDetails structure may be
            provided.

            The use of this HTTP error response code described above is
            applicable to the use of the OAuth 2.0 for the authorization of API
            requests and notifications, as defined in clauses 4.5.3.3 and
            4.5.3.4.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '401':
          description: >
            401 UNAUTHORIZED

            If the request contains no access token even though one is required,
            or if the request contains an authorization token that is invalid
            (e.g. expired or revoked), the API producer should respond with this
            response. The details of the error shall be returned in the
            WWW-Authenticate HTTP header, as defined in IETF RFC 6750 and IETF
            RFC 7235. The ProblemDetails structure may be provided.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '403':
          description: >
            403 FORBIDDEN

            If the API consumer is not allowed to perform a particular request
            to a particular resource, the API producer shall respond with this
            response code. The "ProblemDetails" structure shall be provided. It
            should include in the "detail" attribute information about the
            source of the problem, and may indicate how to solve it.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '404':
          description: >
            404 NOT FOUND

            If the API producer did not find a current representation for the
            resource addressed by the URI passed in the request or is not
            willing to disclose that one exists, it shall respond with this
            response code. The "ProblemDetails" structure may be provided,
            including in the "detail" attribute information about the source of
            the problem, e.g. a wrong resource URI variable.

            This response code is not appropriate in case the resource addressed
            by the URI is a container resource which is designed to contain
            child resources, but does not contain any child resource at the time
            the request is received. For a GET request to an existing empty
            container resource, a typical response contains a 200 OK response
            code and a payload body with an empty array.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '405':
          description: >
            405 METHOD NOT ALLOWED

            If a particular HTTP method is not supported for a particular
            resource, the API producer shall respond with this response code.
            The "ProblemDetails" structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '406':
          description: >
            406 NOT ACCEPTABLE

            If the "Accept" HTTP header does not contain at least one name of a
            content type that is acceptable to the API producer, the API
            producer shall respond with this response code. The "ProblemDetails"
            structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '422':
          description: >
            422 UNPROCESSABLE ENTITY

            If the payload body of a request contains syntactically correct data
            (e.g. well-formed JSON) but the data cannot be processed (e.g.
            because it fails validation against a schema), the API producer
            shall respond with this response code. The "ProblemDetails"
            structure shall be provided, and should include in the "detail"
            attribute more information about the source of the problem.

            This error response code is only applicable for methods that have a
            request body.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '500':
          description: >
            500 INTERNAL SERVER ERROR

            If there is an application error not related to the client's input
            that cannot be easily mapped to any other HTTP response code ("catch
            all error"), the API producer shall respond with this response code.
            The "ProblemDetails" structure shall be provided, and shall include
            in the "detail" attribute more information about the source of the
            problem.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '503':
          description: >
            503 SERVICE UNAVAILABLE

            If the API producer encounters an internal overload situation of
            itself or of a system it relies on, it should respond with this
            response code, following the provisions in IETF RFC 7231 for the use
            of the "Retry-After" HTTP header and for the alternative to refuse
            the connection. The "ProblemDetails" structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '504':
          description: >
            504 GATEWAY TIMEOUT

            If the API producer encounters a timeout while waiting for a
            response from an upstream server (i.e. a server that the API
            producer communicates with when fulfilling a request), it should
            respond with this response code.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
  '/log_jobs/{logJobId}':
    description: >-
      This resource represents an individual logging job. The API consumer can
      use this resource to delete and read the underlying logging job.
    parameters:
      - name: logJobId
        in: path
        description: Identifier of the logging job.
        required: true
        schema:
          description: |
            An identifier with the intention of being globally unique.
          type: string
    get:
      description: >-
        The API consumer can use this method for reading an individual logging
        job. This method shall follow the provisions specified in the tables
        8.5.4.3.2-1 and 8.5.4.3.2-2 for URI query parameters, request and
        response data structures, and response codes.
      parameters:
        - name: Version
          description: |
            Version of the API requested to use when responding to this request.
          in: header
          required: true
          schema:
            type: string
        - name: Accept
          description: >
            Content-Types that are acceptable for the response. Reference: IETF
            RFC 7231.
          in: header
          required: true
          schema:
            type: string
        - name: Authorization
          description: |
            The authorization token for the request. Reference: IETF RFC 7235.
          in: header
          required: false
          schema:
            type: string
      responses:
        '200':
          description: >-
            Shall be returned when information about an individual logging job
            has been read successfully. The response body shall contain a
            representation of the "Individual logging job" resource, as defined
            in clause 8.6.2.6.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
          content:
            application/json:
              schema:
                description: >-
                  This type represents a logging job. It shall comply with the
                  provisions defined in table 8.6.2.6-1.
                type: object
                required:
                  - id
                  - objectInstanceIds
                  - jobCriteria
                  - jobConfig
                  - _links
                properties:
                  id:
                    description: |
                      An identifier with the intention of being globally unique.
                    type: string
                  objectInstanceIds:
                    description: >-
                      Identifiers of the object instance for which logging
                      information is collected. This attribute shall contain the
                      identifier of the instance of the object that is logged
                      according to their type.
                    type: array
                    items:
                      description: >
                        This type represents the identifier to reference a
                        managed object of a  particular type. 
                      type: object
                      properties:
                        type:
                          description: >
                            Indicates the type of managed object. Permitted
                            values:
                              - MANO_ENTITY
                              - MANO_SERVICE
                              - MANO_SERVICE_IF
                              - CONSUMED_MANO_IF
                              - MANO_ENTITY_COMPONENT

                            The "MANO_ENTITY COMPONENT" is only applicable if
                            attribute "manoEntityComponents" in "ManoEntity" is
                            supported by the API producer.
                          type: string
                          enum:
                            - MANO_ENTITY
                            - MANO_SERVICE
                            - MANO_SERVICE_IF
                            - CONSUMED_MANO_IF
                            - MANO_ENTITY_COMPONENT
                        objectId:
                          description: >
                            An identifier with the intention of being globally
                            unique.
                          type: string
                        subObjectId:
                          description: >
                            An identifier that is unique for the respective type
                            within a NFV-MANO functional entity, but that need
                            not be globally unique. Representation: string of
                            variable length..
                          type: string
                      required:
                        - type
                        - objectId
                  jobCriteria:
                    description: >-
                      This type represents collection criteria for logging jobs.
                      It shall comply with the provisions defined in table
                      8.6.3.2-1.
                    type: object
                    required:
                      - loggingType
                    properties:
                      loggingType:
                        description: >-
                          Type of logging. This defines the types of logged
                          information to collect.

                          Permitted values: - MESSAGES: logged NFV-MANO service
                          interface messages. - SERVICES: logged messages about
                          processes pertaining to NFV-MANO services. - SYSTEM:
                          logged messages about the NFV-MANO functional entity’s
                          system enabled by the provider.
                        type: string
                        enum:
                          - MESSAGES
                          - SERVICES
                          - SYSTEM
                      messagesLogDetail:
                        description: >-
                          This type represents criteria for logging jobs to
                          collect logged messages on NFV-MANO service
                          interfaces. It shall comply with the provisions
                          defined in table 8.6.3.3-1.
                        type: object
                        required:
                          - direction
                        properties:
                          direction:
                            description: >-
                              The direction of the interface messages to match.

                              Permitted values: - IN: input messages into the
                              interface. - OUT: output messages from the
                              interface. - ALL: both input and output messages
                              into/from the interface.
                            type: string
                            enum:
                              - IN
                              - OUT
                              - ALL
                          matchingPatterns:
                            description: >-
                              Patterns to be matched in the interface message.
                              If provided, only messages that match all the
                              values provided in the sub-attributes shall be
                              logged. An API consumer can provide more than one
                              "matchingPattern" if combinations of patterns are
                              to be considered to match diverse sets of
                              interface messages.
                            type: array
                            items:
                              type: object
                              anyOf:
                                - required:
                                    - srcIpAddress
                                - required:
                                    - dstIpAddress
                                - required:
                                    - requestMethod
                                - required:
                                    - requestUriPattern
                                - required:
                                    - responseCodes
                              properties:
                                srcIpAddress:
                                  description: >
                                    An IPV4 or IPV6 address. Representation: In
                                    case of an IPV4 address, string that
                                    consists of four decimal integers separated
                                    by dots, each integer ranging from 0 to 255.
                                    In case of an IPV6 address, string that
                                    consists of groups of zero to four
                                    hexadecimal digits, separated by colons.
                                  type: string
                                  format: IP
                                requestMethod:
                                  description: >-
                                    HTTP request method to be matched. To match,
                                    the HTTP request method of the message shall
                                    be the same as the value of this attribute.
                                    Valid values are specified in IETF RFC 7231.
                                    The API producer shall support this
                                    attribute.
                                  type: string
                                requestUriPattern:
                                  description: >-
                                    Substring to be matched in the request URI.
                                    To match, the request URI shall include the
                                    value of
                                     this attribute as a substring. This is typically used to match messages which associate to RESTful
                                     resources, or to a specific API (e.g., by using the "apiName" of the API). The API producer shall
                                     support this attribute.
                                  type: string
                                dstIpAddress:
                                  description: >
                                    An IPV4 or IPV6 address. Representation: In
                                    case of an IPV4 address, string that
                                    consists of four decimal integers separated
                                    by dots, each integer ranging from 0 to 255.
                                    In case of an IPV6 address, string that
                                    consists of groups of zero to four
                                    hexadecimal digits, separated by colons.
                                  type: string
                                  format: IP
                                responseCodes:
                                  description: >-
                                    HTTP response codes or patterns to match. A
                                    list of all valid HTTP response codes and
                                    their specification documents can be
                                    obtained from the HTTP status code registry.
                                    In addition, if supported, the following
                                    patterns may be used (case-insensitive): -
                                    "1XX": for matching any kind of
                                    informational response. - "2XX": for
                                    matching any kind of success response. -
                                    "3XX": for matching any kind redirection
                                    response. - "4XX": for matching any kind of
                                    client error response. - "5XX": for matching
                                    any kind of server error response.

                                    The API producer shall support this
                                    attribute
                                  type: array
                                  items:
                                    type: string
                                headerField:
                                  description: >-
                                    Name of the header field to be matched. The
                                    header field name shall be one of the
                                    supported fields in a request message as
                                    defined in clause 4.2.2 of ETSI GS NFV-SOL
                                    013 or in a response message as defined in
                                    clause 4.2.3 of ETSI GS NFV-SOL 013, in
                                    accordance with the "direction" criteria
                                    input. The API producer may support this
                                    attribute.
                                  type: string
                                headerValue:
                                  description: >-
                                    Value in the header to be matched. To match,
                                    the value in the header field indicated by
                                    "headerField" shall be the same as in this
                                    attribute. Shall be provided if a
                                    "headerField" is provided. The API producer
                                    may support this attribute.
                                  type: string
                                bodyValues:
                                  description: >-
                                    A list of strings to be matched in the body
                                    part of the interface message (e.g., the
                                    body of an HTTP message). If provided, only
                                    messages with text in the body part
                                    containing all the values from the list
                                    shall match the filter. In addition to a
                                    matching filter for the body of the message,
                                    a corresponding "headerField" filter shall
                                    also be provided, with "headerField" set to
                                    "Content-Type", to restrict matching to
                                    appropriate textual payloads such as
                                    "application/json" or "text/plain". The API
                                    producer may support this attribute
                                  type: string
                      servicesLogDetail:
                        description: >-
                          This type represents criteria for logging jobs to
                          collect logged messages about processes pertaining to
                          NFV-MANO services. It shall comply with the provisions
                          defined in table 8.6.3.4-1.
                        type: object
                        properties:
                          logGarbageCollection:
                            description: >-
                              Indicates to collect logged information about
                              garbage collection processes associated to
                              NFV-MANO services.
                            type: boolean
                      systemLogDetail:
                        description: >-
                          This type represents criteria for logging jobs to
                          collect logged system events of the NFV-MANO
                          functional entity. It shall comply with the provisions
                          defined in table 8.6.3.5-1.
                        type: object
                        required:
                          - systemLogs
                          - severityLevel
                        properties:
                          systemLogs:
                            description: >
                              This type represents a list of key-value pairs.
                              The order of the pairs in the list is not
                              significant. In JSON, a set of keyvalue pairs is
                              represented as an object. It shall comply with the
                              provisions defined in clause 4 of IETF RFC 8259.
                              In the following example, a list of key-value
                              pairs with four keys ("aString", "aNumber",
                              "anArray" and "anObject") is provided to
                              illustrate that the values associated with
                              different keys can be of different type.
                            type: object
                          severityLevelScheme:
                            description: >-
                              Identifies a severity level scheme. The default
                              value is "rfc5424", which represents the set of
                              values specified in the clause 6.2.1, table 2 of
                              IETF RFC 5424. Other values may be used to signal
                              different schemes.
                            type: string
                          severityLevel:
                            description: >-
                              The severity level, which determines the severity
                              of the system messages to collect. The NFV-MANO
                              functional entity shall collect system log
                              messages, as indicated by the "systemLogs"
                              attribute, with severity levels lower (i.e., more
                              severe) or equal to the value provided by this
                              present attribute.
                            type: number
                  jobConfig:
                    description: >-
                      This type represents configuration data for a logging job.
                      It shall comply with the provisions defined in table
                      8.6.3.6-1. NOTE: The present document version does not
                      specify the support for "log compilation and reporting
                      based on events" as specified in clause 6.6.2.2 of ETSI GS
                      NFV-IFA 031.
                    type: object
                    required:
                      - reportingCondition
                      - securityConf
                    properties:
                      startTime:
                        description: >
                          Date-time stamp. Representation: String formatted
                          according to IETF RFC 3339.
                        type: string
                        format: date-time
                      endTime:
                        description: >
                          Date-time stamp. Representation: String formatted
                          according to IETF RFC 3339.
                        type: string
                        format: date-time
                      reportingCondition:
                        description: >-
                          Specifies the condition under which the producer will
                          report to the consumer about the compiled log data.
                        required:
                          - reportingType
                        properties:
                          reportingType:
                            description: >-
                              Specifies the type of reporting condition.
                              Permitted values: - REPORTING_ON_COMPILATION: the
                              producer shall notify the consumer once the
                              compilation of the
                                              collected logging data into a file is completed and a new log report is available.
                              - NO_REPORTING: no reporting is requested (the
                              consumer can query the logging jobs to know about
                              the
                                              availability of new log reports).
                            type: string
                            enum:
                              - REPORTING_ON_COMPILATION
                              - NO_REPORTING
                          minimumReportingPeriod:
                            description: >-
                              Specifies the minimum periodicity at which the
                              producer will report to the consumer about the
                              collected log information, in seconds.
                            type: integer
                            format: int32
                      compileBySizeValue:
                        description: >-
                          An indicative size threshold for compiling the
                          collected log data, in bytes. It is used when the
                          compilation is based on the size of the collected log
                          data. If not present, a default value as specified
                          with the "defaultLogCompileBySizeValue" configuration
                          in the "ManoEntityConfigurableParams" shall be used
                        type: integer
                        format: int32
                      compileByTimerValue:
                        description: >-
                          The periodicity threshold for compiling the filtered
                          log, in seconds. It is used when the compilation is
                          based on a timer (e.g., every 24 hours). If not
                          present, a default value as specified with the
                          "defaultLogCompileByTimerValue" configuration in the
                          "ManoEntityConfigurableParams" shall be used
                        type: integer
                        format: int32
                      securityConf:
                        description: >-
                          Configuration about the security aspects of the
                          logging job.
                        type: object
                        properties:
                          logFileEncryption:
                            description: >-
                              Information about the encryption of the compiled
                              log files. Shall be present if the log file is
                              requested to be encrypted.
                            required:
                              - encryptionCertificate
                              - cipherAlgorithm
                            type: object
                            properties:
                              encryptionCertificate:
                                description: >-
                                  X.509 certificate with the public key to use
                                  for the encryption of the compiled log file.
                                type: string
                              cipherAlgorithm:
                                description: >-
                                  Cryptographic algorithm to be used for the
                                  encryption of the compiled log file. More than
                                  one algorithm can be provided from higher
                                  (lower array index) to lower (higher array
                                  index) precedence. Valid values are:
                                  "AES-CBC-128", "AES-GCM-128", "AES-CBC-256",
                                  and "AES-GCM-256", as specified in clause 6.5
                                  of ETSI GS NFV-SEC 012
                                type: array
                                items:
                                  type: string
                                  minItems: 1
                              encryptAndSignOrder:
                                description: >-
                                  Indication about the order in signing and
                                  encrypting the compiled log file. Valid values
                                  are: "encryptFirst", to apply the order "first
                                  encrypt, then sign", and "signFirst" for the
                                  order "first sign, then encrypt". Default
                                  value is "encryptFirst".
                                type: string
                          logTransferSecurity:
                            description: >-
                              Information about the security measures for
                              retrieving/accessing the compiled log files.
                            type: object
                            properties:
                              publicKey:
                                description: >-
                                  The public key of the API consumer used for
                                  the client authentication with the file
                                  server. Shall be provided if required by the
                                  type of transfer protocol. May be omitted if
                                  the key has been provided to the API producer
                                  by other means, or if it has already been
                                  provided in some previous
                                  CreateLoggingJobRequest issued by the same API
                                  consumer, whose public key has not changed.
                                type: string
                  logReports:
                    description: >-
                      Information about available log reports created by the
                      logging job.
                    type: array
                    items:
                      type: object
                      required:
                        - logReportId
                        - logReportLoc
                      properties:
                        logReportId:
                          description: >
                            An identifier with the intention of being globally
                            unique.
                          type: string
                        logReportLoc:
                          description: >
                            This type represents a link to a resource using an
                            absolute URI.
                          type: object
                          required:
                            - href
                          properties:
                            href:
                              description: |
                                String formatted according to IETF RFC 3986.
                              type: string
                  _links:
                    description: Links for this resource.
                    type: object
                    required:
                      - self
                    properties:
                      self:
                        description: >
                          This type represents a link to a resource using an
                          absolute URI.
                        type: object
                        required:
                          - href
                        properties:
                          href:
                            description: |
                              String formatted according to IETF RFC 3986.
                            type: string
                      objects:
                        description: >-
                          Links to resources representing the object instances
                          that are logged. Shall be present if the logged object
                          instance information is accessible as a resource.
                        type: array
                        items:
                          description: >
                            This type represents a link to a resource using an
                            absolute URI.
                          type: object
                          required:
                            - href
                          properties:
                            href:
                              description: |
                                String formatted according to IETF RFC 3986.
                              type: string
        '400':
          description: >
            400 BAD REQUEST

            400 code can be returned in the following specified cases, the
            specific cause has to be proper specified in the "ProblemDetails"
            structure to be returned.

            If the request is malformed or syntactically incorrect (e.g. if the
            request URI contains incorrect query parameters or the payload body
            contains a syntactically incorrect data structure), the API producer
            shall respond with this response code. The "ProblemDetails"
            structure shall be provided, and should include in the "detail"
            attribute more information about the source of the problem.

            If the response to a GET request which queries a container resource
            would be so big that the performance of the API producer is
            adversely affected, and the API producer does not support paging for
            the affected resource, it shall respond with this response code. The
            "ProblemDetails" structure shall be provided, and should include in
            the "detail" attribute more information about the source of the
            problem.

            If there is an application error related to the client's input that
            cannot be easily mapped to any other HTTP response code ("catch all
            error"), the API producer shall respond with this response code. The
            "ProblemDetails" structure shall be provided, and shall include in
            the "detail" attribute more information about the source of the
            problem.

            If the request contains a malformed access token, the API producer
            should respond with this response. The details of the error shall be
            returned in the WWW Authenticate HTTP header, as defined in IETF RFC
            6750 and IETF RFC 7235. The ProblemDetails structure may be
            provided.

            The use of this HTTP error response code described above is
            applicable to the use of the OAuth 2.0 for the authorization of API
            requests and notifications, as defined in clauses 4.5.3.3 and
            4.5.3.4.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '401':
          description: >
            401 UNAUTHORIZED

            If the request contains no access token even though one is required,
            or if the request contains an authorization token that is invalid
            (e.g. expired or revoked), the API producer should respond with this
            response. The details of the error shall be returned in the
            WWW-Authenticate HTTP header, as defined in IETF RFC 6750 and IETF
            RFC 7235. The ProblemDetails structure may be provided.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '403':
          description: >
            403 FORBIDDEN

            If the API consumer is not allowed to perform a particular request
            to a particular resource, the API producer shall respond with this
            response code. The "ProblemDetails" structure shall be provided. It
            should include in the "detail" attribute information about the
            source of the problem, and may indicate how to solve it.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '404':
          description: >
            404 NOT FOUND

            If the API producer did not find a current representation for the
            resource addressed by the URI passed in the request or is not
            willing to disclose that one exists, it shall respond with this
            response code. The "ProblemDetails" structure may be provided,
            including in the "detail" attribute information about the source of
            the problem, e.g. a wrong resource URI variable.

            This response code is not appropriate in case the resource addressed
            by the URI is a container resource which is designed to contain
            child resources, but does not contain any child resource at the time
            the request is received. For a GET request to an existing empty
            container resource, a typical response contains a 200 OK response
            code and a payload body with an empty array.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '405':
          description: >
            405 METHOD NOT ALLOWED

            If a particular HTTP method is not supported for a particular
            resource, the API producer shall respond with this response code.
            The "ProblemDetails" structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '406':
          description: >
            406 NOT ACCEPTABLE

            If the "Accept" HTTP header does not contain at least one name of a
            content type that is acceptable to the API producer, the API
            producer shall respond with this response code. The "ProblemDetails"
            structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '422':
          description: >
            422 UNPROCESSABLE ENTITY

            If the payload body of a request contains syntactically correct data
            (e.g. well-formed JSON) but the data cannot be processed (e.g.
            because it fails validation against a schema), the API producer
            shall respond with this response code. The "ProblemDetails"
            structure shall be provided, and should include in the "detail"
            attribute more information about the source of the problem.

            This error response code is only applicable for methods that have a
            request body.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '500':
          description: >
            500 INTERNAL SERVER ERROR

            If there is an application error not related to the client's input
            that cannot be easily mapped to any other HTTP response code ("catch
            all error"), the API producer shall respond with this response code.
            The "ProblemDetails" structure shall be provided, and shall include
            in the "detail" attribute more information about the source of the
            problem.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '503':
          description: >
            503 SERVICE UNAVAILABLE

            If the API producer encounters an internal overload situation of
            itself or of a system it relies on, it should respond with this
            response code, following the provisions in IETF RFC 7231 for the use
            of the "Retry-After" HTTP header and for the alternative to refuse
            the connection. The "ProblemDetails" structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '504':
          description: >
            504 GATEWAY TIMEOUT

            If the API producer encounters a timeout while waiting for a
            response from an upstream server (i.e. a server that the API
            producer communicates with when fulfilling a request), it should
            respond with this response code.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
    delete:
      description: >-
        This method terminates an individual logging job. This method shall
        follow the provisions specified in the tables 8.5.4.3.5-1 and
        8.5.4.3.5-2 for URI query parameters, request and response data
        structures, and response codes. As the result of successfully executing
        this method, the "Individual logging job" resource shall not exist any
        longer
      parameters:
        - name: Version
          description: |
            Version of the API requested to use when responding to this request.
          in: header
          required: true
          schema:
            type: string
        - name: Authorization
          description: |
            The authorization token for the request. Reference: IETF RFC 7235.
          in: header
          required: false
          schema:
            type: string
      responses:
        '204':
          description: >-
            Shall be returned when the logging job has been deleted
            successfully. The response body shall be empty.
          headers:
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
            Version:
              description: Version of the API used in the response.
              schema:
                type: string
        '400':
          description: >
            400 BAD REQUEST

            400 code can be returned in the following specified cases, the
            specific cause has to be proper specified in the "ProblemDetails"
            structure to be returned.

            If the request is malformed or syntactically incorrect (e.g. if the
            request URI contains incorrect query parameters or the payload body
            contains a syntactically incorrect data structure), the API producer
            shall respond with this response code. The "ProblemDetails"
            structure shall be provided, and should include in the "detail"
            attribute more information about the source of the problem.

            If the response to a GET request which queries a container resource
            would be so big that the performance of the API producer is
            adversely affected, and the API producer does not support paging for
            the affected resource, it shall respond with this response code. The
            "ProblemDetails" structure shall be provided, and should include in
            the "detail" attribute more information about the source of the
            problem.

            If there is an application error related to the client's input that
            cannot be easily mapped to any other HTTP response code ("catch all
            error"), the API producer shall respond with this response code. The
            "ProblemDetails" structure shall be provided, and shall include in
            the "detail" attribute more information about the source of the
            problem.

            If the request contains a malformed access token, the API producer
            should respond with this response. The details of the error shall be
            returned in the WWW Authenticate HTTP header, as defined in IETF RFC
            6750 and IETF RFC 7235. The ProblemDetails structure may be
            provided.

            The use of this HTTP error response code described above is
            applicable to the use of the OAuth 2.0 for the authorization of API
            requests and notifications, as defined in clauses 4.5.3.3 and
            4.5.3.4.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '401':
          description: >
            401 UNAUTHORIZED

            If the request contains no access token even though one is required,
            or if the request contains an authorization token that is invalid
            (e.g. expired or revoked), the API producer should respond with this
            response. The details of the error shall be returned in the
            WWW-Authenticate HTTP header, as defined in IETF RFC 6750 and IETF
            RFC 7235. The ProblemDetails structure may be provided.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '403':
          description: >
            403 FORBIDDEN

            If the API consumer is not allowed to perform a particular request
            to a particular resource, the API producer shall respond with this
            response code. The "ProblemDetails" structure shall be provided. It
            should include in the "detail" attribute information about the
            source of the problem, and may indicate how to solve it.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '404':
          description: >
            404 NOT FOUND

            If the API producer did not find a current representation for the
            resource addressed by the URI passed in the request or is not
            willing to disclose that one exists, it shall respond with this
            response code. The "ProblemDetails" structure may be provided,
            including in the "detail" attribute information about the source of
            the problem, e.g. a wrong resource URI variable.

            This response code is not appropriate in case the resource addressed
            by the URI is a container resource which is designed to contain
            child resources, but does not contain any child resource at the time
            the request is received. For a GET request to an existing empty
            container resource, a typical response contains a 200 OK response
            code and a payload body with an empty array.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '405':
          description: >
            405 METHOD NOT ALLOWED

            If a particular HTTP method is not supported for a particular
            resource, the API producer shall respond with this response code.
            The "ProblemDetails" structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '406':
          description: >
            406 NOT ACCEPTABLE

            If the "Accept" HTTP header does not contain at least one name of a
            content type that is acceptable to the API producer, the API
            producer shall respond with this response code. The "ProblemDetails"
            structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '422':
          description: >
            422 UNPROCESSABLE ENTITY

            If the payload body of a request contains syntactically correct data
            (e.g. well-formed JSON) but the data cannot be processed (e.g.
            because it fails validation against a schema), the API producer
            shall respond with this response code. The "ProblemDetails"
            structure shall be provided, and should include in the "detail"
            attribute more information about the source of the problem.

            This error response code is only applicable for methods that have a
            request body.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '500':
          description: >
            500 INTERNAL SERVER ERROR

            If there is an application error not related to the client's input
            that cannot be easily mapped to any other HTTP response code ("catch
            all error"), the API producer shall respond with this response code.
            The "ProblemDetails" structure shall be provided, and shall include
            in the "detail" attribute more information about the source of the
            problem.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '503':
          description: >
            503 SERVICE UNAVAILABLE

            If the API producer encounters an internal overload situation of
            itself or of a system it relies on, it should respond with this
            response code, following the provisions in IETF RFC 7231 for the use
            of the "Retry-After" HTTP header and for the alternative to refuse
            the connection. The "ProblemDetails" structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '504':
          description: >
            504 GATEWAY TIMEOUT

            If the API producer encounters a timeout while waiting for a
            response from an upstream server (i.e. a server that the API
            producer communicates with when fulfilling a request), it should
            respond with this response code.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
  '/log_jobs/{logJobId}/log_reports/{logReportId}':
    description: "This resource represents an individual log report. The API consumer can use this resource to read information about a log report. The log report provides metadata information about a log and location information of the log file from where it can be obtained. NOTE:\tThe present document does not specify the mechanism how to retrieve the log files."
    parameters:
      - name: logJobId
        in: path
        description: Identifier of the logging job.
        required: true
        schema:
          description: |
            An identifier with the intention of being globally unique.
          type: string
      - name: logReportId
        in: path
        description: Identifier of the report.
        required: true
        schema:
          description: |
            An identifier with the intention of being globally unique.
          type: string
    get:
      description: >-
        The API consumer can use this method for reading an individual log
        report. This method shall follow the provisions specified in the tables
        8.5.5.3.2-1 and 8.5.5.3.2-2 for URI query parameters, request and
        response data structures, and response codes.
      parameters:
        - name: Version
          description: |
            Version of the API requested to use when responding to this request.
          in: header
          required: true
          schema:
            type: string
        - name: Accept
          description: >
            Content-Types that are acceptable for the response. Reference: IETF
            RFC 7231.
          in: header
          required: true
          schema:
            type: string
        - name: Authorization
          description: |
            The authorization token for the request. Reference: IETF RFC 7235.
          in: header
          required: false
          schema:
            type: string
      responses:
        '200':
          description: >-
            Shall be returned when information of an individual log report has
            been read successfully. The response body shall contain a
            representation of the "Individual log report" resource, as defined
            in clause 8.6.2.7.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
          content:
            application/json:
              schema:
                description: >
                  This type represents a log report, which provides information
                  about a compiled log and how to obtain it. It shall comply
                  with the provisions defined in table 8.6.2.7-1.
                type: object
                required:
                  - id
                  - objectInstanceId
                  - compilationTrigger
                  - readyTime
                  - fileFormat
                  - fileLocationInfo
                  - securityAndIntegrityInfo
                  - _links
                properties:
                  id:
                    description: |
                      An identifier with the intention of being globally unique.
                    type: string
                  objectInstanceId:
                    description: >
                      This type represents the identifier to reference a managed
                      object of a  particular type. 
                    type: object
                    properties:
                      type:
                        description: >
                          Indicates the type of managed object. Permitted
                          values:
                            - MANO_ENTITY
                            - MANO_SERVICE
                            - MANO_SERVICE_IF
                            - CONSUMED_MANO_IF
                            - MANO_ENTITY_COMPONENT

                          The "MANO_ENTITY COMPONENT" is only applicable if
                          attribute "manoEntityComponents" in "ManoEntity" is
                          supported by the API producer.
                        type: string
                        enum:
                          - MANO_ENTITY
                          - MANO_SERVICE
                          - MANO_SERVICE_IF
                          - CONSUMED_MANO_IF
                          - MANO_ENTITY_COMPONENT
                      objectId:
                        description: >
                          An identifier with the intention of being globally
                          unique.
                        type: string
                      subObjectId:
                        description: >
                          An identifier that is unique for the respective type
                          within a NFV-MANO functional entity, but that need not
                          be globally unique. Representation: string of variable
                          length..
                        type: string
                    required:
                      - type
                      - objectId
                  compilationTrigger:
                    description: >-
                      The trigger for the compilation of the log file.

                      Permitted values: - ON_DEMAND: created based on explicit
                      request by a client. - AUTOMATIC: created according to the
                      logging job compilation configuration.
                    type: string
                    enum:
                      - ON_DEMAND
                      - AUTOMATIC
                  readyTime:
                    description: >
                      Date-time stamp. Representation: String formatted
                      according to IETF RFC 3339.
                    type: string
                    format: date-time
                  expiryTime:
                    description: >
                      Date-time stamp. Representation: String formatted
                      according to IETF RFC 3339.
                    type: string
                    format: date-time
                  fileSize:
                    description: 'The size of the compiled log file in bytes, if known.'
                    type: integer
                    format: int32
                  fileFormat:
                    description: The encoding used by the file.
                    type: string
                  fileLocationInfo:
                    description: >-
                      Location and address information of the compiled log file.
                      The consumer can use this information to obtain the
                      compiled log file.
                    type: object
                    required:
                      - protocol
                      - fileEndpoint
                    properties:
                      protocol:
                        description: >-
                          Protocol over which the compiled log file can be
                          retrieved.

                          Permitted values: - HTTPS: transmission over HTTP
                          Secure (HTTPS). - SFTP: transmission over SSH file
                          transfer protocol (SFTP). - SCP: transmission over
                          secure copy protocol (SCP). - FTPS: transmission over
                          file transfer protocol secure (FTPS), as specified in
                          IETF RFC 2228 [i.11],
                               using explicit mode as specified in IETF RFC 4217 [i.12]. If FTPS is supported, "private" protection level shall be used.

                          HTTPS shall be supported, and other protocols may be
                          supported.
                        type: string
                        enum:
                          - HTTPS
                          - SFTP
                          - SCP
                          - FTPS
                      fileEndpoint:
                        description: >-
                          The host name (or IP address), optionally a port
                          number (if the host with the compile log file uses a
                          non-standard port number as per the supported
                          transmission protocol), a valid file directory path,
                          and the file name of the compiled log file, or a valid
                          URL.
                        type: string
                        format: URI
                  securityAndIntegrityInfo:
                    description: >-
                      Security and integrity information for the compilation of
                      the log files.
                    type: object
                    required:
                      - algorithm
                      - hash
                      - logFileSignature
                      - signingCertificate
                    properties:
                      algorithm:
                        description: >-
                          Algorithm used to generate the hash of the compiled
                          log file. Only SHA-256 and SHA-512 shall be used
                        type: string
                      hash:
                        description: >-
                          The hexadecimal value of the hash of the compiled log
                          file. The hash shall be computed from the encrypted
                          compiled log file, in case the encryption applies.
                        type: string
                      encryptionPublicKey:
                        description: >-
                          Public key used for the encryption of the compiled log
                          file. Shall be present if the compiled log file is
                          encrypted.
                        type: string
                      cipherAlgorithm:
                        description: >-
                          The cryptographic algorithm used for the encryption.
                          Shall be present if the compiled log file is
                          encrypted. Valid values are: "AES-CBC-128",
                          "AES-GCM-128", "AES-CBC-256", and "AES-GCM-256", as
                          specified in clause 6.5 of ETSI GS NFV-SEC 012 [14].
                        type: string
                      logFileSignature:
                        description: >-
                          Signature to the compiled log file generated with the
                          NFV-MANO functional entity’s private key, which is
                          used to ensure the authenticity of the compiled log
                          file. The signature shall be applied according to the
                          "encryptAndSignOrder" of the "LoggingJobConfig".
                        type: string
                      signingCertificate:
                        description: >-
                          X.509 certificate with the NFV-MANO functional
                          entity’s public key used for verifying the log report
                          and compiled log file signatures.
                        type: string
                  _links:
                    description: Links for this resource.
                    type: object
                    required:
                      - self
                    properties:
                      self:
                        description: >
                          This type represents a link to a resource using an
                          absolute URI.
                        type: object
                        required:
                          - href
                        properties:
                          href:
                            description: |
                              String formatted according to IETF RFC 3986.
                            type: string
                      objects:
                        description: >-
                          Links to resources representing the object instances
                          that are logged. Shall be present if the logged object
                          instance information is accessible as a resource.
                        type: array
                        items:
                          description: >
                            This type represents a link to a resource using an
                            absolute URI.
                          type: object
                          required:
                            - href
                          properties:
                            href:
                              description: |
                                String formatted according to IETF RFC 3986.
                              type: string
        '202':
          description: >-
            Shall be returned if the creation of the log report is ongoing and
            no log report is available yet (applicable in asynchronous mode of
            the "Compile log task" resource). The response body shall be empty.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
        '400':
          description: >
            400 BAD REQUEST

            400 code can be returned in the following specified cases, the
            specific cause has to be proper specified in the "ProblemDetails"
            structure to be returned.

            If the request is malformed or syntactically incorrect (e.g. if the
            request URI contains incorrect query parameters or the payload body
            contains a syntactically incorrect data structure), the API producer
            shall respond with this response code. The "ProblemDetails"
            structure shall be provided, and should include in the "detail"
            attribute more information about the source of the problem.

            If the response to a GET request which queries a container resource
            would be so big that the performance of the API producer is
            adversely affected, and the API producer does not support paging for
            the affected resource, it shall respond with this response code. The
            "ProblemDetails" structure shall be provided, and should include in
            the "detail" attribute more information about the source of the
            problem.

            If there is an application error related to the client's input that
            cannot be easily mapped to any other HTTP response code ("catch all
            error"), the API producer shall respond with this response code. The
            "ProblemDetails" structure shall be provided, and shall include in
            the "detail" attribute more information about the source of the
            problem.

            If the request contains a malformed access token, the API producer
            should respond with this response. The details of the error shall be
            returned in the WWW Authenticate HTTP header, as defined in IETF RFC
            6750 and IETF RFC 7235. The ProblemDetails structure may be
            provided.

            The use of this HTTP error response code described above is
            applicable to the use of the OAuth 2.0 for the authorization of API
            requests and notifications, as defined in clauses 4.5.3.3 and
            4.5.3.4.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '401':
          description: >
            401 UNAUTHORIZED

            If the request contains no access token even though one is required,
            or if the request contains an authorization token that is invalid
            (e.g. expired or revoked), the API producer should respond with this
            response. The details of the error shall be returned in the
            WWW-Authenticate HTTP header, as defined in IETF RFC 6750 and IETF
            RFC 7235. The ProblemDetails structure may be provided.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '403':
          description: >
            403 FORBIDDEN

            If the API consumer is not allowed to perform a particular request
            to a particular resource, the API producer shall respond with this
            response code. The "ProblemDetails" structure shall be provided. It
            should include in the "detail" attribute information about the
            source of the problem, and may indicate how to solve it.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '404':
          description: >
            404 NOT FOUND

            If the API producer did not find a current representation for the
            resource addressed by the URI passed in the request or is not
            willing to disclose that one exists, it shall respond with this
            response code. The "ProblemDetails" structure may be provided,
            including in the "detail" attribute information about the source of
            the problem, e.g. a wrong resource URI variable.

            This response code is not appropriate in case the resource addressed
            by the URI is a container resource which is designed to contain
            child resources, but does not contain any child resource at the time
            the request is received. For a GET request to an existing empty
            container resource, a typical response contains a 200 OK response
            code and a payload body with an empty array.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '405':
          description: >
            405 METHOD NOT ALLOWED

            If a particular HTTP method is not supported for a particular
            resource, the API producer shall respond with this response code.
            The "ProblemDetails" structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '406':
          description: >
            406 NOT ACCEPTABLE

            If the "Accept" HTTP header does not contain at least one name of a
            content type that is acceptable to the API producer, the API
            producer shall respond with this response code. The "ProblemDetails"
            structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '422':
          description: >
            422 UNPROCESSABLE ENTITY

            If the payload body of a request contains syntactically correct data
            (e.g. well-formed JSON) but the data cannot be processed (e.g.
            because it fails validation against a schema), the API producer
            shall respond with this response code. The "ProblemDetails"
            structure shall be provided, and should include in the "detail"
            attribute more information about the source of the problem.

            This error response code is only applicable for methods that have a
            request body.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '500':
          description: >
            500 INTERNAL SERVER ERROR

            If there is an application error not related to the client's input
            that cannot be easily mapped to any other HTTP response code ("catch
            all error"), the API producer shall respond with this response code.
            The "ProblemDetails" structure shall be provided, and shall include
            in the "detail" attribute more information about the source of the
            problem.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '503':
          description: >
            503 SERVICE UNAVAILABLE

            If the API producer encounters an internal overload situation of
            itself or of a system it relies on, it should respond with this
            response code, following the provisions in IETF RFC 7231 for the use
            of the "Retry-After" HTTP header and for the alternative to refuse
            the connection. The "ProblemDetails" structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '504':
          description: >
            504 GATEWAY TIMEOUT

            If the API producer encounters a timeout while waiting for a
            response from an upstream server (i.e. a server that the API
            producer communicates with when fulfilling a request), it should
            respond with this response code.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
  '/log_jobs/{logJobId}/compile_log':
    description: >-
      This resource represents the "Compile log" operation. The API consumer can
      use this resource to request compiling the logged data, collected via a
      logging job, into a file and creating the associated log report. As the
      result of successfully processing this request, a new "Individual log
      report" resource shall be created. Two modes of operation, synchronous or
      asynchronous, can take place depending on whether the NFV-MANO functional
      entity can compile the log data and create the log report immediately. In
      the synchronous case, which is indicated by responding with "201 Created",
      the resource shall be created before the "201 Created" response is
      returned. In the asynchronous case, which is indicated by responding with
      "202 Accepted", the resource may be created after the response is
      returned.
    parameters:
      - name: logJobId
        in: path
        description: Identifier of the logging job.
        required: true
        schema:
          description: |
            An identifier with the intention of being globally unique.
          type: string
    post:
      description: >-
        The POST method requests to compile the logged data into a file and
        create an associated log report. This method shall follow the provisions
        specified in the tables 8.5.6.3.1-1 and 8.5.6.3.1-2 for URI query
        parameters, request and response data structures, and response codes.
      parameters:
        - name: Version
          description: |
            Version of the API requested to use when responding to this request.
          in: header
          required: true
          schema:
            type: string
        - name: Accept
          description: >
            Content-Types that are acceptable for the response. Reference: IETF
            RFC 7231.
          in: header
          required: true
          schema:
            type: string
        - name: Content-Type
          description: |
            The MIME type of the body of the request. Reference: IETF RFC 7231
          in: header
          required: true
          schema:
            type: string
        - name: Authorization
          description: |
            The authorization token for the request. Reference: IETF RFC 7235.
          in: header
          required: false
          schema:
            type: string
      requestBody:
        description: Log compilation request.
        content:
          application/json:
            schema:
              description: >
                This type represents a request to compile the logged data
                associated to an object instance. It shall comply with the
                provisions defined in table 8.6.2.8-1.
              type: object
              properties:
                objectInstanceId:
                  description: >
                    This type represents the identifier to reference a managed
                    object of a  particular type. 
                  type: object
                  properties:
                    type:
                      description: >
                        Indicates the type of managed object. Permitted values:
                          - MANO_ENTITY
                          - MANO_SERVICE
                          - MANO_SERVICE_IF
                          - CONSUMED_MANO_IF
                          - MANO_ENTITY_COMPONENT

                        The "MANO_ENTITY COMPONENT" is only applicable if
                        attribute "manoEntityComponents" in "ManoEntity" is
                        supported by the API producer.
                      type: string
                      enum:
                        - MANO_ENTITY
                        - MANO_SERVICE
                        - MANO_SERVICE_IF
                        - CONSUMED_MANO_IF
                        - MANO_ENTITY_COMPONENT
                    objectId:
                      description: >
                        An identifier with the intention of being globally
                        unique.
                      type: string
                    subObjectId:
                      description: >
                        An identifier that is unique for the respective type
                        within a NFV-MANO functional entity, but that need not
                        be globally unique. Representation: string of variable
                        length..
                      type: string
                  required:
                    - type
                    - objectId
        required: true
      responses:
        '200':
          description: >-
            Shall be returned for a successful compilation of the log data and
            creation of the associated log report (synchronous mode). The
            response body shall contain a representation of the log report
            resource, as defined in clause 8.6.2.7. The HTTP response shall
            include a "Location" HTTP header that indicate the URI of the
            "Individual log report" resource just created
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
            Location:
              description: |
                URI of the "Individual log report" resource just created
              schema:
                type: string
          content:
            application/json:
              schema:
                description: >
                  This type represents a log report, which provides information
                  about a compiled log and how to obtain it. It shall comply
                  with the provisions defined in table 8.6.2.7-1.
                type: object
                required:
                  - id
                  - objectInstanceId
                  - compilationTrigger
                  - readyTime
                  - fileFormat
                  - fileLocationInfo
                  - securityAndIntegrityInfo
                  - _links
                properties:
                  id:
                    description: |
                      An identifier with the intention of being globally unique.
                    type: string
                  objectInstanceId:
                    description: >
                      This type represents the identifier to reference a managed
                      object of a  particular type. 
                    type: object
                    properties:
                      type:
                        description: >
                          Indicates the type of managed object. Permitted
                          values:
                            - MANO_ENTITY
                            - MANO_SERVICE
                            - MANO_SERVICE_IF
                            - CONSUMED_MANO_IF
                            - MANO_ENTITY_COMPONENT

                          The "MANO_ENTITY COMPONENT" is only applicable if
                          attribute "manoEntityComponents" in "ManoEntity" is
                          supported by the API producer.
                        type: string
                        enum:
                          - MANO_ENTITY
                          - MANO_SERVICE
                          - MANO_SERVICE_IF
                          - CONSUMED_MANO_IF
                          - MANO_ENTITY_COMPONENT
                      objectId:
                        description: >
                          An identifier with the intention of being globally
                          unique.
                        type: string
                      subObjectId:
                        description: >
                          An identifier that is unique for the respective type
                          within a NFV-MANO functional entity, but that need not
                          be globally unique. Representation: string of variable
                          length..
                        type: string
                    required:
                      - type
                      - objectId
                  compilationTrigger:
                    description: >-
                      The trigger for the compilation of the log file.

                      Permitted values: - ON_DEMAND: created based on explicit
                      request by a client. - AUTOMATIC: created according to the
                      logging job compilation configuration.
                    type: string
                    enum:
                      - ON_DEMAND
                      - AUTOMATIC
                  readyTime:
                    description: >
                      Date-time stamp. Representation: String formatted
                      according to IETF RFC 3339.
                    type: string
                    format: date-time
                  expiryTime:
                    description: >
                      Date-time stamp. Representation: String formatted
                      according to IETF RFC 3339.
                    type: string
                    format: date-time
                  fileSize:
                    description: 'The size of the compiled log file in bytes, if known.'
                    type: integer
                    format: int32
                  fileFormat:
                    description: The encoding used by the file.
                    type: string
                  fileLocationInfo:
                    description: >-
                      Location and address information of the compiled log file.
                      The consumer can use this information to obtain the
                      compiled log file.
                    type: object
                    required:
                      - protocol
                      - fileEndpoint
                    properties:
                      protocol:
                        description: >-
                          Protocol over which the compiled log file can be
                          retrieved.

                          Permitted values: - HTTPS: transmission over HTTP
                          Secure (HTTPS). - SFTP: transmission over SSH file
                          transfer protocol (SFTP). - SCP: transmission over
                          secure copy protocol (SCP). - FTPS: transmission over
                          file transfer protocol secure (FTPS), as specified in
                          IETF RFC 2228 [i.11],
                               using explicit mode as specified in IETF RFC 4217 [i.12]. If FTPS is supported, "private" protection level shall be used.

                          HTTPS shall be supported, and other protocols may be
                          supported.
                        type: string
                        enum:
                          - HTTPS
                          - SFTP
                          - SCP
                          - FTPS
                      fileEndpoint:
                        description: >-
                          The host name (or IP address), optionally a port
                          number (if the host with the compile log file uses a
                          non-standard port number as per the supported
                          transmission protocol), a valid file directory path,
                          and the file name of the compiled log file, or a valid
                          URL.
                        type: string
                        format: URI
                  securityAndIntegrityInfo:
                    description: >-
                      Security and integrity information for the compilation of
                      the log files.
                    type: object
                    required:
                      - algorithm
                      - hash
                      - logFileSignature
                      - signingCertificate
                    properties:
                      algorithm:
                        description: >-
                          Algorithm used to generate the hash of the compiled
                          log file. Only SHA-256 and SHA-512 shall be used
                        type: string
                      hash:
                        description: >-
                          The hexadecimal value of the hash of the compiled log
                          file. The hash shall be computed from the encrypted
                          compiled log file, in case the encryption applies.
                        type: string
                      encryptionPublicKey:
                        description: >-
                          Public key used for the encryption of the compiled log
                          file. Shall be present if the compiled log file is
                          encrypted.
                        type: string
                      cipherAlgorithm:
                        description: >-
                          The cryptographic algorithm used for the encryption.
                          Shall be present if the compiled log file is
                          encrypted. Valid values are: "AES-CBC-128",
                          "AES-GCM-128", "AES-CBC-256", and "AES-GCM-256", as
                          specified in clause 6.5 of ETSI GS NFV-SEC 012 [14].
                        type: string
                      logFileSignature:
                        description: >-
                          Signature to the compiled log file generated with the
                          NFV-MANO functional entity’s private key, which is
                          used to ensure the authenticity of the compiled log
                          file. The signature shall be applied according to the
                          "encryptAndSignOrder" of the "LoggingJobConfig".
                        type: string
                      signingCertificate:
                        description: >-
                          X.509 certificate with the NFV-MANO functional
                          entity’s public key used for verifying the log report
                          and compiled log file signatures.
                        type: string
                  _links:
                    description: Links for this resource.
                    type: object
                    required:
                      - self
                    properties:
                      self:
                        description: >
                          This type represents a link to a resource using an
                          absolute URI.
                        type: object
                        required:
                          - href
                        properties:
                          href:
                            description: |
                              String formatted according to IETF RFC 3986.
                            type: string
                      objects:
                        description: >-
                          Links to resources representing the object instances
                          that are logged. Shall be present if the logged object
                          instance information is accessible as a resource.
                        type: array
                        items:
                          description: >
                            This type represents a link to a resource using an
                            absolute URI.
                          type: object
                          required:
                            - href
                          properties:
                            href:
                              description: |
                                String formatted according to IETF RFC 3986.
                              type: string
        '202':
          description: >-
            Shall be returned when the request has been accepted for processing,
            and it is expected to take some time to compile the log file and
            create the associated log report (asynchronous mode). The response
            body shall be empty. The HTTP response shall include a "Location"
            HTTP header that indicates the URI of the "Individual log report"
            resource that will be created once the log file compilation is
            completed.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
            Location:
              description: >
                The URI of the "Individual log report" resource that will be
                created once the log file compilation is completed.
              schema:
                type: string
        '303':
          description: >-
            Shall be returned when a log data compilation and report creation is
            already ongoing, or a log report has just been created, for the
            specified logging job at the time of processing the request. The
            response body shall be empty. The HTTP response shall include a
            "Location" HTTP header that contains the resource URI of the log
            report resource just created, or to be created by the ongoing
            compilation and report creation.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
            Location:
              description: >
                The URI of the log report resource just created, or to be
                created by the ongoing compilation and report creation
              schema:
                type: string
        '400':
          description: >
            400 BAD REQUEST

            400 code can be returned in the following specified cases, the
            specific cause has to be proper specified in the "ProblemDetails"
            structure to be returned.

            If the request is malformed or syntactically incorrect (e.g. if the
            request URI contains incorrect query parameters or the payload body
            contains a syntactically incorrect data structure), the API producer
            shall respond with this response code. The "ProblemDetails"
            structure shall be provided, and should include in the "detail"
            attribute more information about the source of the problem.

            If the response to a GET request which queries a container resource
            would be so big that the performance of the API producer is
            adversely affected, and the API producer does not support paging for
            the affected resource, it shall respond with this response code. The
            "ProblemDetails" structure shall be provided, and should include in
            the "detail" attribute more information about the source of the
            problem.

            If there is an application error related to the client's input that
            cannot be easily mapped to any other HTTP response code ("catch all
            error"), the API producer shall respond with this response code. The
            "ProblemDetails" structure shall be provided, and shall include in
            the "detail" attribute more information about the source of the
            problem.

            If the request contains a malformed access token, the API producer
            should respond with this response. The details of the error shall be
            returned in the WWW Authenticate HTTP header, as defined in IETF RFC
            6750 and IETF RFC 7235. The ProblemDetails structure may be
            provided.

            The use of this HTTP error response code described above is
            applicable to the use of the OAuth 2.0 for the authorization of API
            requests and notifications, as defined in clauses 4.5.3.3 and
            4.5.3.4.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '401':
          description: >
            401 UNAUTHORIZED

            If the request contains no access token even though one is required,
            or if the request contains an authorization token that is invalid
            (e.g. expired or revoked), the API producer should respond with this
            response. The details of the error shall be returned in the
            WWW-Authenticate HTTP header, as defined in IETF RFC 6750 and IETF
            RFC 7235. The ProblemDetails structure may be provided.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '403':
          description: >
            403 FORBIDDEN

            If the API consumer is not allowed to perform a particular request
            to a particular resource, the API producer shall respond with this
            response code. The "ProblemDetails" structure shall be provided. It
            should include in the "detail" attribute information about the
            source of the problem, and may indicate how to solve it.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '404':
          description: >
            404 NOT FOUND

            If the API producer did not find a current representation for the
            resource addressed by the URI passed in the request or is not
            willing to disclose that one exists, it shall respond with this
            response code. The "ProblemDetails" structure may be provided,
            including in the "detail" attribute information about the source of
            the problem, e.g. a wrong resource URI variable.

            This response code is not appropriate in case the resource addressed
            by the URI is a container resource which is designed to contain
            child resources, but does not contain any child resource at the time
            the request is received. For a GET request to an existing empty
            container resource, a typical response contains a 200 OK response
            code and a payload body with an empty array.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '405':
          description: >
            405 METHOD NOT ALLOWED

            If a particular HTTP method is not supported for a particular
            resource, the API producer shall respond with this response code.
            The "ProblemDetails" structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '406':
          description: >
            406 NOT ACCEPTABLE

            If the "Accept" HTTP header does not contain at least one name of a
            content type that is acceptable to the API producer, the API
            producer shall respond with this response code. The "ProblemDetails"
            structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '422':
          description: >-
            The general cause for this error and its handling is specified in
            clause 6.4 of ETSI GS NFV-SOL 013, including rules for the presence
            of the response body. Specifically, in case of this task resource,
            the response code 422 shall also be returned if the
            "objectInstanceId" value provided in the payload body of the request
            does not correspond to an object instance for which log data is
            being collected by the logging job represented by this resource. The
            response body shall contain a ProblemDetails structure, in which the
            "detail" attribute should convey more information about the error.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '500':
          description: >
            500 INTERNAL SERVER ERROR

            If there is an application error not related to the client's input
            that cannot be easily mapped to any other HTTP response code ("catch
            all error"), the API producer shall respond with this response code.
            The "ProblemDetails" structure shall be provided, and shall include
            in the "detail" attribute more information about the source of the
            problem.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '503':
          description: >
            503 SERVICE UNAVAILABLE

            If the API producer encounters an internal overload situation of
            itself or of a system it relies on, it should respond with this
            response code, following the provisions in IETF RFC 7231 for the use
            of the "Retry-After" HTTP header and for the alternative to refuse
            the connection. The "ProblemDetails" structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '504':
          description: >
            504 GATEWAY TIMEOUT

            If the API producer encounters a timeout while waiting for a
            response from an upstream server (i.e. a server that the API
            producer communicates with when fulfilling a request), it should
            respond with this response code.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
  /subscriptions:
    description: >-
      This resource represents subscriptions. The client can use this resource
      to subscribe to notifications related to NFV-MANO performance management
      and to query its subscriptions.
    post:
      description: >-
        The POST method creates a new subscription. This method shall follow the
        provisions specified in the tables 8.5.7.3.1-1 and 8.5.7.3.1-2 for URI
        query
         parameters, request and response data structures, and response codes.
        As the result of successfully executing this method, a new "Individual
        subscription" resource as defined in clause 8.5.8 shall have been
        created. This method shall not trigger any notification. Creation of two
        "Individual subscription" resources with the same callbackURI and the
        same filter can result in performance degradation and will provide
        duplicates of notifications to the API consumer, and might make sense
        only in very rare use cases. Consequently, the NFV-MANO functional
        entity may either allow creating a new "Individual subscription"
        resource if another "Individual subscription" resource with the same
        filter and callbackUri already exists (in which case it shall return the
        "201 Created" response code), or may decide to not create a duplicate
        "Individual subscription" resource (in which case it shall return a "303
        See Other" response code referencing the existing "Individual
        subscription" resource with the same filter and callbackUri).
      parameters:
        - name: Version
          description: |
            Version of the API requested to use when responding to this request.
          in: header
          required: true
          schema:
            type: string
        - name: Accept
          description: >
            Content-Types that are acceptable for the response. Reference: IETF
            RFC 7231.
          in: header
          required: true
          schema:
            type: string
        - name: Content-Type
          description: |
            The MIME type of the body of the request. Reference: IETF RFC 7231
          in: header
          required: true
          schema:
            type: string
        - name: Authorization
          description: |
            The authorization token for the request. Reference: IETF RFC 7235.
          in: header
          required: false
          schema:
            type: string
      requestBody:
        description: Details of the subscription to be created
        content:
          application/json:
            schema:
              description: >-
                Information on application context created by the MEC system
                type: object
              required:
                - callbackUri
              type: object
              properties:
                filter:
                  description: >-
                    This type represents a filter that can be used to subscribe
                    for notifications related to log management events. It shall
                    comply with the provisions defined in table 8.6.3.7-1. At a
                    particular nesting level in the filter structure, the
                    following applies: All attributes shall match in order for
                    the filter to match (logical "and" between different filter
                    attributes). If an attribute is an array, the attribute
                    shall match if at least one of the values in the array
                    matches (logical "or" between the values of one filter
                    attribute).
                  type: object
                  properties:
                    objectInstanceFilter:
                      description: >-
                        This type represents subscription filter criteria to
                        match NFV-MANO functional entities and their associated
                        managed objects. It shall comply with the provisions
                        defined in Table 4.3.2.2-1.
                      type: object
                      anyOf:
                        - oneOf:
                            - required:
                                - manoServiceIds
                            - required:
                                - manoServiceNames
                        - oneOf:
                            - required:
                                - manoServiceInterfaceIds
                            - required:
                                - manoServiceInterfaceNames
                        - oneOf:
                            - required:
                                - consumedManoInterfaceIds
                            - required:
                                - consumedManoInterfaceNames
                      properties:
                        manoEntityId:
                          description: >
                            An identifier with the intention of being globally
                            unique.
                          type: string
                        manoServiceIds:
                          description: >-
                            If present, match NFV-MANO services with an instance
                            identifier listed in this attribute.
                          type: array
                          items:
                            description: >
                              An identifier that is unique for the respective
                              type within a NFV-MANO functional entity, but that
                              need not be globally unique. Representation:
                              string of variable length..
                            type: string
                        manoServiceNames:
                          description: >-
                            If present, match NFV-MANO services with an NFV-MANO
                            service name listed in this attribute.
                          type: array
                          items:
                            type: string
                        manoServiceInterfaceIds:
                          description: >-
                            If present, match NFV-MANO functional entity
                            produced interfaces with an instance identifier
                            listed in this attribute.
                          type: array
                          items:
                            description: >
                              An identifier that is unique for the respective
                              type within a NFV-MANO functional entity, but that
                              need not be globally unique. Representation:
                              string of variable length..
                            type: string
                        manoServiceInterfaceNames:
                          description: >-
                            If present, match NFV-MANO functional entity
                            produced interfaces with an instance Name listed in
                            this attribute.
                          type: array
                          items:
                            type: string
                        consumedManoInterfaceIds:
                          description: >-
                            If present, match NFV-MANO functional entity
                            consumed interfaces with an instance identifier
                            listed in this attribute.
                          type: array
                          items:
                            description: >
                              An identifier with the intention of being globally
                              unique.
                            type: string
                        consumedManoInterfaceNames:
                          description: >-
                            If present, match NFV-MANO functional entity
                            consumed interfaces with an instance Name listed in
                            this attribute.
                          type: array
                          items:
                            type: string
                    notificationTypes:
                      description: >-
                        Match particular notification types. Permitted values: -
                        LogReportAvailableNotification
                      type: string
                      enum:
                        - LogReportAvailableNotification
                callbackUri:
                  description: |
                    String formatted according to IETF RFC 3986.
                  type: string
                authentication:
                  type: object
                  required:
                    - authType
                  properties:
                    authType:
                      description: >
                        Defines the types of Authentication / Authorization
                        which the API consumer is willing to accept when
                        receiving a notification. Permitted values: * BASIC: In
                        every HTTP request to the notification endpoint, use
                          HTTP Basic authentication with the client credentials.
                        * OAUTH2_CLIENT_CREDENTIALS: In every HTTP request to
                        the
                          notification endpoint, use an OAuth 2.0 Bearer token, obtained
                          using the client credentials grant type.
                        * TLS_CERT: Every HTTP request to the notification
                        endpoint is sent
                          over a mutually authenticated TLS session, i.e. not only the
                          server is authenticated, but also the client is authenticated
                          during the TLS tunnel setup.
                      type: array
                      items:
                        type: string
                        enum:
                          - BASIC
                          - OAUTH2_CLIENT_CREDENTIALS
                          - TLS_CERT
                    paramsBasic:
                      description: >
                        Parameters for authentication/authorization using BASIC.
                        Shall be present if authType is "BASIC" and the
                        contained information has not been provisioned out of
                        band. Shall be absent otherwise.
                      type: object
                      properties:
                        userName:
                          description: >
                            Username to be used in HTTP Basic authentication.
                            Shall be present if it has not been provisioned out
                            of band.
                          type: string
                        password:
                          description: >
                            Password to be used in HTTP Basic authentication.
                            Shall be present if it has not been provisioned out
                            of band.
                          type: string
                    paramsOauth2ClientCredentials:
                      description: >
                        Parameters for authentication/authorization using
                        OAUTH2_CLIENT_CREDENTIALS. Shall be present if authType
                        is "OAUTH2_CLIENT_CREDENTIALS" and the contained
                        information has not been provisioned out of band. Shall
                        be absent otherwise.
                      type: object
                      properties:
                        clientId:
                          description: >
                            Client identifier to be used in the access token
                            request of the OAuth 2.0 client credentials grant
                            type. Shall be present if it has not been
                            provisioned out of band. The clientId and
                            clientPassword passed in a subscription shall not be
                            the same as the clientId and clientPassword that are
                            used to obtain authorization for API requests.
                            Client credentials may differ between subscriptions.
                            The value of clientPassword should be generated by a
                            random process.
                          type: string
                        clientPassword:
                          description: >
                            Client password to be used in the access token
                            request of the OAuth 2.0 client credentials grant
                            type. Shall be present if it has not been
                            provisioned out of band. The clientId and
                            clientPassword passed in a subscription shall not be
                            the same as the clientId and clientPassword that are
                            used to obtain authorization for API requests.
                            Client credentials may differ between subscriptions.
                            The value of clientPassword should be generated by a
                            random process.
                          type: string
                        tokenEndpoint:
                          description: |
                            String formatted according to IETF RFC 3986.
                          type: string
      responses:
        '201':
          description: >-
            Shall be returned when the subscription has been created
            successfully. A representation of the created "Individual
            subscription" resource shall be returned in the response body, as
            defined in clause 8.6.2.3. The HTTP response shall include a
            "Location" HTTP header that contains the resource URI of the created
            "Individual subscription" resource.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
            Location:
              description: |
                URI of the "Individual log report" resource just created
              schema:
                type: string
          content:
            application/json:
              schema:
                description: >-
                  This type represents a subscription. It shall comply with the
                  provisions defined in table 8.6.2.3-1.
                type: object
                required:
                  - id
                  - callbackUri
                  - _links
                properties:
                  id:
                    description: |
                      An identifier with the intention of being globally unique.
                    type: string
                  filter:
                    description: >-
                      This type represents a filter that can be used to
                      subscribe for notifications related to log management
                      events. It shall comply with the provisions defined in
                      table 8.6.3.7-1. At a particular nesting level in the
                      filter structure, the following applies: All attributes
                      shall match in order for the filter to match (logical
                      "and" between different filter attributes). If an
                      attribute is an array, the attribute shall match if at
                      least one of the values in the array matches (logical "or"
                      between the values of one filter attribute).
                    type: object
                    properties:
                      objectInstanceFilter:
                        description: >-
                          This type represents subscription filter criteria to
                          match NFV-MANO functional entities and their
                          associated managed objects. It shall comply with the
                          provisions defined in Table 4.3.2.2-1.
                        type: object
                        anyOf:
                          - oneOf:
                              - required:
                                  - manoServiceIds
                              - required:
                                  - manoServiceNames
                          - oneOf:
                              - required:
                                  - manoServiceInterfaceIds
                              - required:
                                  - manoServiceInterfaceNames
                          - oneOf:
                              - required:
                                  - consumedManoInterfaceIds
                              - required:
                                  - consumedManoInterfaceNames
                        properties:
                          manoEntityId:
                            description: >
                              An identifier with the intention of being globally
                              unique.
                            type: string
                          manoServiceIds:
                            description: >-
                              If present, match NFV-MANO services with an
                              instance identifier listed in this attribute.
                            type: array
                            items:
                              description: >
                                An identifier that is unique for the respective
                                type within a NFV-MANO functional entity, but
                                that need not be globally unique.
                                Representation: string of variable length..
                              type: string
                          manoServiceNames:
                            description: >-
                              If present, match NFV-MANO services with an
                              NFV-MANO service name listed in this attribute.
                            type: array
                            items:
                              type: string
                          manoServiceInterfaceIds:
                            description: >-
                              If present, match NFV-MANO functional entity
                              produced interfaces with an instance identifier
                              listed in this attribute.
                            type: array
                            items:
                              description: >
                                An identifier that is unique for the respective
                                type within a NFV-MANO functional entity, but
                                that need not be globally unique.
                                Representation: string of variable length..
                              type: string
                          manoServiceInterfaceNames:
                            description: >-
                              If present, match NFV-MANO functional entity
                              produced interfaces with an instance Name listed
                              in this attribute.
                            type: array
                            items:
                              type: string
                          consumedManoInterfaceIds:
                            description: >-
                              If present, match NFV-MANO functional entity
                              consumed interfaces with an instance identifier
                              listed in this attribute.
                            type: array
                            items:
                              description: >
                                An identifier with the intention of being
                                globally unique.
                              type: string
                          consumedManoInterfaceNames:
                            description: >-
                              If present, match NFV-MANO functional entity
                              consumed interfaces with an instance Name listed
                              in this attribute.
                            type: array
                            items:
                              type: string
                      notificationTypes:
                        description: >-
                          Match particular notification types. Permitted values:
                          - LogReportAvailableNotification
                        type: string
                        enum:
                          - LogReportAvailableNotification
                  callbackUri:
                    description: |
                      String formatted according to IETF RFC 3986.
                    type: string
                  _links:
                    description: Links to resources related to this resource.
                    type: object
                    required:
                      - self
                    properties:
                      self:
                        description: >
                          This type represents a link to a resource using an
                          absolute URI.
                        type: object
                        required:
                          - href
                        properties:
                          href:
                            description: |
                              String formatted according to IETF RFC 3986.
                            type: string
        '303':
          description: >-
            Shall be returned when a subscription with the same callbackURI and
            the same filter already exists and the policy of the NFV-MANO
            functional entity is to not create redundant subscriptions. The HTTP
            response shall include a "Location" HTTP header that contains the
            resource URI of the existing "Individual subscription" resource. The
            response body shall be empty.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
            Location:
              description: |
                URI of the "Individual log report" resource just created
              schema:
                type: string
        '400':
          description: >
            400 BAD REQUEST

            400 code can be returned in the following specified cases, the
            specific cause has to be proper specified in the "ProblemDetails"
            structure to be returned.

            If the request is malformed or syntactically incorrect (e.g. if the
            request URI contains incorrect query parameters or the payload body
            contains a syntactically incorrect data structure), the API producer
            shall respond with this response code. The "ProblemDetails"
            structure shall be provided, and should include in the "detail"
            attribute more information about the source of the problem.

            If the response to a GET request which queries a container resource
            would be so big that the performance of the API producer is
            adversely affected, and the API producer does not support paging for
            the affected resource, it shall respond with this response code. The
            "ProblemDetails" structure shall be provided, and should include in
            the "detail" attribute more information about the source of the
            problem.

            If there is an application error related to the client's input that
            cannot be easily mapped to any other HTTP response code ("catch all
            error"), the API producer shall respond with this response code. The
            "ProblemDetails" structure shall be provided, and shall include in
            the "detail" attribute more information about the source of the
            problem.

            If the request contains a malformed access token, the API producer
            should respond with this response. The details of the error shall be
            returned in the WWW Authenticate HTTP header, as defined in IETF RFC
            6750 and IETF RFC 7235. The ProblemDetails structure may be
            provided.

            The use of this HTTP error response code described above is
            applicable to the use of the OAuth 2.0 for the authorization of API
            requests and notifications, as defined in clauses 4.5.3.3 and
            4.5.3.4.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '401':
          description: >
            401 UNAUTHORIZED

            If the request contains no access token even though one is required,
            or if the request contains an authorization token that is invalid
            (e.g. expired or revoked), the API producer should respond with this
            response. The details of the error shall be returned in the
            WWW-Authenticate HTTP header, as defined in IETF RFC 6750 and IETF
            RFC 7235. The ProblemDetails structure may be provided.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '403':
          description: >
            403 FORBIDDEN

            If the API consumer is not allowed to perform a particular request
            to a particular resource, the API producer shall respond with this
            response code. The "ProblemDetails" structure shall be provided. It
            should include in the "detail" attribute information about the
            source of the problem, and may indicate how to solve it.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '404':
          description: >
            404 NOT FOUND

            If the API producer did not find a current representation for the
            resource addressed by the URI passed in the request or is not
            willing to disclose that one exists, it shall respond with this
            response code. The "ProblemDetails" structure may be provided,
            including in the "detail" attribute information about the source of
            the problem, e.g. a wrong resource URI variable.

            This response code is not appropriate in case the resource addressed
            by the URI is a container resource which is designed to contain
            child resources, but does not contain any child resource at the time
            the request is received. For a GET request to an existing empty
            container resource, a typical response contains a 200 OK response
            code and a payload body with an empty array.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '405':
          description: >
            405 METHOD NOT ALLOWED

            If a particular HTTP method is not supported for a particular
            resource, the API producer shall respond with this response code.
            The "ProblemDetails" structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '406':
          description: >
            406 NOT ACCEPTABLE

            If the "Accept" HTTP header does not contain at least one name of a
            content type that is acceptable to the API producer, the API
            producer shall respond with this response code. The "ProblemDetails"
            structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '422':
          description: >
            422 UNPROCESSABLE ENTITY

            If the payload body of a request contains syntactically correct data
            (e.g. well-formed JSON) but the data cannot be processed (e.g.
            because it fails validation against a schema), the API producer
            shall respond with this response code. The "ProblemDetails"
            structure shall be provided, and should include in the "detail"
            attribute more information about the source of the problem.

            This error response code is only applicable for methods that have a
            request body.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '500':
          description: >
            500 INTERNAL SERVER ERROR

            If there is an application error not related to the client's input
            that cannot be easily mapped to any other HTTP response code ("catch
            all error"), the API producer shall respond with this response code.
            The "ProblemDetails" structure shall be provided, and shall include
            in the "detail" attribute more information about the source of the
            problem.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '503':
          description: >
            503 SERVICE UNAVAILABLE

            If the API producer encounters an internal overload situation of
            itself or of a system it relies on, it should respond with this
            response code, following the provisions in IETF RFC 7231 for the use
            of the "Retry-After" HTTP header and for the alternative to refuse
            the connection. The "ProblemDetails" structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '504':
          description: >
            504 GATEWAY TIMEOUT

            If the API producer encounters a timeout while waiting for a
            response from an upstream server (i.e. a server that the API
            producer communicates with when fulfilling a request), it should
            respond with this response code.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
      callbacks:
        LogReportAvailableNotification:
          '{$request.body#/callbackUri}':
            description: >-
              This resource represents a notification endpoint for NFV-MANO log
              management. The API producer can use this resource to send
              notifications related to log management events to a subscribed API
              consumer, which has provided the URI of this resource during the
              subscription process.
            post:
              description: >-
                The POST method delivers a notification regarding a log
                management event from the API producer to the API consumer. The
                API consumer shall have previously created an "Individual
                subscription" resource with a matching filter. This method shall
                follow the provisions specified in the tables 8.5.9.3.1-1 and
                8.5.9.3.1-2 for URI query parameters, request and response data
                structures, and response codes.
              parameters:
                - name: Version
                  description: >
                    Version of the API requested to use when responding to this
                    request.
                  in: header
                  required: true
                  schema:
                    type: string
                - name: Authorization
                  description: >
                    The authorization token for the request. Reference: IETF RFC
                    7235.
                  in: header
                  required: false
                  schema:
                    type: string
              requestBody:
                description: Notification about the availability of a log report.
                content:
                  application/json:
                    schema:
                      description: >-
                        This notification informs the receiver that the log
                        report of the NFV-MANO functional entity is available.
                        It shall comply with the provisions defined in table
                        8.6.2.4-1. The notification shall be triggered by the
                        NFV-MANO functional entity when log information has been
                        collected by the logging job and the log report is
                        available.
                      type: object
                      required:
                        - id
                        - notificationType
                        - subscriptionId
                        - timeStamp
                        - objectInstanceId
                        - _links
                      properties:
                        id:
                          description: >
                            An identifier with the intention of being globally
                            unique.
                          type: string
                        notificationType:
                          description: >-
                            Discriminator for the different notification types.
                            Shall be set to "LogReportAvailableNotification" for
                            this notification type.
                          type: string
                        subscriptionId:
                          description: >
                            An identifier with the intention of being globally
                            unique.
                          type: string
                        timeStamp:
                          description: >
                            Date-time stamp. Representation: String formatted
                            according to IETF RFC 3339.
                          type: string
                          format: date-time
                        objectInstanceId:
                          description: >
                            This type represents the identifier to reference a
                            managed object of a  particular type. 
                          type: object
                          properties:
                            type:
                              description: >
                                Indicates the type of managed object. Permitted
                                values:
                                  - MANO_ENTITY
                                  - MANO_SERVICE
                                  - MANO_SERVICE_IF
                                  - CONSUMED_MANO_IF
                                  - MANO_ENTITY_COMPONENT

                                The "MANO_ENTITY COMPONENT" is only applicable
                                if attribute "manoEntityComponents" in
                                "ManoEntity" is supported by the API producer.
                              type: string
                              enum:
                                - MANO_ENTITY
                                - MANO_SERVICE
                                - MANO_SERVICE_IF
                                - CONSUMED_MANO_IF
                                - MANO_ENTITY_COMPONENT
                            objectId:
                              description: >
                                An identifier with the intention of being
                                globally unique.
                              type: string
                            subObjectId:
                              description: >
                                An identifier that is unique for the respective
                                type within a NFV-MANO functional entity, but
                                that need not be globally unique.
                                Representation: string of variable length..
                              type: string
                          required:
                            - type
                            - objectId
                        _links:
                          description: Links to resources related to this notification.
                          type: object
                          required:
                            - subscription
                            - logReports
                          properties:
                            subscription:
                              description: >
                                This type represents a link to a resource in a
                                notification, using an absolute or relative URI.
                              type: object
                              required:
                                - href
                              properties:
                                href:
                                  description: |
                                    String formatted according to IETF RFC 3986.
                                  type: string
                            objectInstance:
                              description: >
                                This type represents a link to a resource in a
                                notification, using an absolute or relative URI.
                              type: object
                              required:
                                - href
                              properties:
                                href:
                                  description: |
                                    String formatted according to IETF RFC 3986.
                                  type: string
                            LoggingJob:
                              description: >
                                This type represents a link to a resource in a
                                notification, using an absolute or relative URI.
                              type: object
                              required:
                                - href
                              properties:
                                href:
                                  description: |
                                    String formatted according to IETF RFC 3986.
                                  type: string
                            logReports:
                              description: >-
                                Link from which the available log report can be
                                obtained. Due to the relationship of the logging
                                job compilation and the logging information
                                availability reporting, more than one logReport
                                notification link can be provided.
                              type: array
                              items:
                                description: >
                                  This type represents a link to a resource in a
                                  notification, using an absolute or relative
                                  URI.
                                type: object
                                required:
                                  - href
                                properties:
                                  href:
                                    description: >
                                      String formatted according to IETF RFC
                                      3986.
                                    type: string
              responses:
                '204':
                  description: >-
                    Shall be returned when the notification has been delivered
                    successfully.
                  headers:
                    Content-Type:
                      description: The MIME type of the body of the response.
                      schema:
                        type: string
                    WWW-Authenticate:
                      description: >
                        Challenge if the corresponding HTTP request has not
                        provided authorization, or error details if the
                        corresponding HTTP request has provided an invalid
                        authorization token.
                      schema:
                        type: string
                    Version:
                      description: |
                        Version of the API used in the response.
                      schema:
                        type: string
                '400':
                  description: >
                    400 BAD REQUEST

                    400 code can be returned in the following specified cases,
                    the specific cause has to be proper specified in the
                    "ProblemDetails" structure to be returned.

                    If the request is malformed or syntactically incorrect (e.g.
                    if the request URI contains incorrect query parameters or
                    the payload body contains a syntactically incorrect data
                    structure), the API producer shall respond with this
                    response code. The "ProblemDetails" structure shall be
                    provided, and should include in the "detail" attribute more
                    information about the source of the problem.

                    If the response to a GET request which queries a container
                    resource would be so big that the performance of the API
                    producer is adversely affected, and the API producer does
                    not support paging for the affected resource, it shall
                    respond with this response code. The "ProblemDetails"
                    structure shall be provided, and should include in the
                    "detail" attribute more information about the source of the
                    problem.

                    If there is an application error related to the client's
                    input that cannot be easily mapped to any other HTTP
                    response code ("catch all error"), the API producer shall
                    respond with this response code. The "ProblemDetails"
                    structure shall be provided, and shall include in the
                    "detail" attribute more information about the source of the
                    problem.

                    If the request contains a malformed access token, the API
                    producer should respond with this response. The details of
                    the error shall be returned in the WWW Authenticate HTTP
                    header, as defined in IETF RFC 6750 and IETF RFC 7235. The
                    ProblemDetails structure may be provided.

                    The use of this HTTP error response code described above is
                    applicable to the use of the OAuth 2.0 for the authorization
                    of API requests and notifications, as defined in clauses
                    4.5.3.3 and 4.5.3.4.
                  headers:
                    Content-Type:
                      description: The MIME type of the body of the response.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 1
                    WWW-Authenticate:
                      description: >
                        Challenge if the corresponding HTTP request has not
                        provided authorization, or error details if the
                        corresponding HTTP request has provided an invalid
                        authorization token.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 0
                    Version:
                      description: |
                        Version of the API used in the response.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 1
                  content:
                    application/json:
                      schema:
                        description: >
                          The definition of the general "ProblemDetails" data
                          structure from IETF RFC 7807 [19] is reproduced inthis
                          structure. Compared to the general framework defined
                          in IETF RFC 7807 [19], the "status" and "detail"
                          attributes are mandated to be included by the present
                          document, to ensure that the response contains
                          additional textual information about an error. IETF
                          RFC 7807 [19] foresees extensibility of the
                          "ProblemDetails" type. It is possible that particular
                          APIs in the present document, or particular
                          implementations, define extensions to define
                          additional attributes that provide more information
                          about the error. The description column only provides
                          some explanation of the meaning to Facilitate
                          understanding of the design. For a full description,
                          see IETF RFC 7807 [19].
                        type: object
                        required:
                          - status
                          - detail
                        properties:
                          type:
                            description: >
                              A URI reference according to IETF RFC 3986 [5]
                              that identifies the problem type. It is encouraged
                              that the URI provides human-readable documentation
                              for the problem (e.g. using HTML) when
                              dereferenced. When this member is not present, its
                              value is assumed to be "about:blank".
                            type: string
                            format: URI
                          title:
                            description: >
                              A short, human-readable summary of the problem
                              type. It should not change from occurrence to
                              occurrence of the problem, except for purposes of
                              localization. If type is given and other than
                              "about:blank", this attribute shall also be
                              provided. A short, human-readable summary of the
                              problem type.  It SHOULD NOT change from
                              occurrence to occurrence of the problem, except
                              for purposes of localization (e.g., using
                              proactive content negotiation; see [RFC7231],
                              Section 3.4).
                            type: string
                          status:
                            description: >
                              The HTTP status code for this occurrence of the
                              problem. The HTTP status code ([RFC7231], Section
                              6) generated by the origin server for this
                              occurrence of the problem.
                            type: integer
                          detail:
                            description: >
                              A human-readable explanation specific to this
                              occurrence of the problem.
                            type: string
                          instance:
                            description: >
                              A URI reference that identifies the specific
                              occurrence of the problem. It may yield further
                              information if dereferenced.
                            type: string
                            format: URI
                '401':
                  description: >
                    401 UNAUTHORIZED

                    If the request contains no access token even though one is
                    required, or if the request contains an authorization token
                    that is invalid (e.g. expired or revoked), the API producer
                    should respond with this response. The details of the error
                    shall be returned in the WWW-Authenticate HTTP header, as
                    defined in IETF RFC 6750 and IETF RFC 7235. The
                    ProblemDetails structure may be provided.
                  headers:
                    Content-Type:
                      description: The MIME type of the body of the response.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 1
                    WWW-Authenticate:
                      description: >
                        Challenge if the corresponding HTTP request has not
                        provided authorization, or error details if the
                        corresponding HTTP request has provided an invalid
                        authorization token.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 0
                    Version:
                      description: |
                        Version of the API used in the response.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 1
                  content:
                    application/json:
                      schema:
                        description: >
                          The definition of the general "ProblemDetails" data
                          structure from IETF RFC 7807 [19] is reproduced inthis
                          structure. Compared to the general framework defined
                          in IETF RFC 7807 [19], the "status" and "detail"
                          attributes are mandated to be included by the present
                          document, to ensure that the response contains
                          additional textual information about an error. IETF
                          RFC 7807 [19] foresees extensibility of the
                          "ProblemDetails" type. It is possible that particular
                          APIs in the present document, or particular
                          implementations, define extensions to define
                          additional attributes that provide more information
                          about the error. The description column only provides
                          some explanation of the meaning to Facilitate
                          understanding of the design. For a full description,
                          see IETF RFC 7807 [19].
                        type: object
                        required:
                          - status
                          - detail
                        properties:
                          type:
                            description: >
                              A URI reference according to IETF RFC 3986 [5]
                              that identifies the problem type. It is encouraged
                              that the URI provides human-readable documentation
                              for the problem (e.g. using HTML) when
                              dereferenced. When this member is not present, its
                              value is assumed to be "about:blank".
                            type: string
                            format: URI
                          title:
                            description: >
                              A short, human-readable summary of the problem
                              type. It should not change from occurrence to
                              occurrence of the problem, except for purposes of
                              localization. If type is given and other than
                              "about:blank", this attribute shall also be
                              provided. A short, human-readable summary of the
                              problem type.  It SHOULD NOT change from
                              occurrence to occurrence of the problem, except
                              for purposes of localization (e.g., using
                              proactive content negotiation; see [RFC7231],
                              Section 3.4).
                            type: string
                          status:
                            description: >
                              The HTTP status code for this occurrence of the
                              problem. The HTTP status code ([RFC7231], Section
                              6) generated by the origin server for this
                              occurrence of the problem.
                            type: integer
                          detail:
                            description: >
                              A human-readable explanation specific to this
                              occurrence of the problem.
                            type: string
                          instance:
                            description: >
                              A URI reference that identifies the specific
                              occurrence of the problem. It may yield further
                              information if dereferenced.
                            type: string
                            format: URI
                '403':
                  description: >
                    403 FORBIDDEN

                    If the API consumer is not allowed to perform a particular
                    request to a particular resource, the API producer shall
                    respond with this response code. The "ProblemDetails"
                    structure shall be provided. It should include in the
                    "detail" attribute information about the source of the
                    problem, and may indicate how to solve it.
                  headers:
                    Content-Type:
                      description: The MIME type of the body of the response.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 1
                    WWW-Authenticate:
                      description: >
                        Challenge if the corresponding HTTP request has not
                        provided authorization, or error details if the
                        corresponding HTTP request has provided an invalid
                        authorization token.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 0
                    Version:
                      description: |
                        Version of the API used in the response.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 1
                  content:
                    application/json:
                      schema:
                        description: >
                          The definition of the general "ProblemDetails" data
                          structure from IETF RFC 7807 [19] is reproduced inthis
                          structure. Compared to the general framework defined
                          in IETF RFC 7807 [19], the "status" and "detail"
                          attributes are mandated to be included by the present
                          document, to ensure that the response contains
                          additional textual information about an error. IETF
                          RFC 7807 [19] foresees extensibility of the
                          "ProblemDetails" type. It is possible that particular
                          APIs in the present document, or particular
                          implementations, define extensions to define
                          additional attributes that provide more information
                          about the error. The description column only provides
                          some explanation of the meaning to Facilitate
                          understanding of the design. For a full description,
                          see IETF RFC 7807 [19].
                        type: object
                        required:
                          - status
                          - detail
                        properties:
                          type:
                            description: >
                              A URI reference according to IETF RFC 3986 [5]
                              that identifies the problem type. It is encouraged
                              that the URI provides human-readable documentation
                              for the problem (e.g. using HTML) when
                              dereferenced. When this member is not present, its
                              value is assumed to be "about:blank".
                            type: string
                            format: URI
                          title:
                            description: >
                              A short, human-readable summary of the problem
                              type. It should not change from occurrence to
                              occurrence of the problem, except for purposes of
                              localization. If type is given and other than
                              "about:blank", this attribute shall also be
                              provided. A short, human-readable summary of the
                              problem type.  It SHOULD NOT change from
                              occurrence to occurrence of the problem, except
                              for purposes of localization (e.g., using
                              proactive content negotiation; see [RFC7231],
                              Section 3.4).
                            type: string
                          status:
                            description: >
                              The HTTP status code for this occurrence of the
                              problem. The HTTP status code ([RFC7231], Section
                              6) generated by the origin server for this
                              occurrence of the problem.
                            type: integer
                          detail:
                            description: >
                              A human-readable explanation specific to this
                              occurrence of the problem.
                            type: string
                          instance:
                            description: >
                              A URI reference that identifies the specific
                              occurrence of the problem. It may yield further
                              information if dereferenced.
                            type: string
                            format: URI
                '404':
                  description: >
                    404 NOT FOUND

                    If the API producer did not find a current representation
                    for the resource addressed by the URI passed in the request
                    or is not willing to disclose that one exists, it shall
                    respond with this response code. The "ProblemDetails"
                    structure may be provided, including in the "detail"
                    attribute information about the source of the problem, e.g.
                    a wrong resource URI variable.

                    This response code is not appropriate in case the resource
                    addressed by the URI is a container resource which is
                    designed to contain child resources, but does not contain
                    any child resource at the time the request is received. For
                    a GET request to an existing empty container resource, a
                    typical response contains a 200 OK response code and a
                    payload body with an empty array.
                  headers:
                    Content-Type:
                      description: The MIME type of the body of the response.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 1
                    WWW-Authenticate:
                      description: >
                        Challenge if the corresponding HTTP request has not
                        provided authorization, or error details if the
                        corresponding HTTP request has provided an invalid
                        authorization token.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 0
                    Version:
                      description: |
                        Version of the API used in the response.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 1
                  content:
                    application/json:
                      schema:
                        description: >
                          The definition of the general "ProblemDetails" data
                          structure from IETF RFC 7807 [19] is reproduced inthis
                          structure. Compared to the general framework defined
                          in IETF RFC 7807 [19], the "status" and "detail"
                          attributes are mandated to be included by the present
                          document, to ensure that the response contains
                          additional textual information about an error. IETF
                          RFC 7807 [19] foresees extensibility of the
                          "ProblemDetails" type. It is possible that particular
                          APIs in the present document, or particular
                          implementations, define extensions to define
                          additional attributes that provide more information
                          about the error. The description column only provides
                          some explanation of the meaning to Facilitate
                          understanding of the design. For a full description,
                          see IETF RFC 7807 [19].
                        type: object
                        required:
                          - status
                          - detail
                        properties:
                          type:
                            description: >
                              A URI reference according to IETF RFC 3986 [5]
                              that identifies the problem type. It is encouraged
                              that the URI provides human-readable documentation
                              for the problem (e.g. using HTML) when
                              dereferenced. When this member is not present, its
                              value is assumed to be "about:blank".
                            type: string
                            format: URI
                          title:
                            description: >
                              A short, human-readable summary of the problem
                              type. It should not change from occurrence to
                              occurrence of the problem, except for purposes of
                              localization. If type is given and other than
                              "about:blank", this attribute shall also be
                              provided. A short, human-readable summary of the
                              problem type.  It SHOULD NOT change from
                              occurrence to occurrence of the problem, except
                              for purposes of localization (e.g., using
                              proactive content negotiation; see [RFC7231],
                              Section 3.4).
                            type: string
                          status:
                            description: >
                              The HTTP status code for this occurrence of the
                              problem. The HTTP status code ([RFC7231], Section
                              6) generated by the origin server for this
                              occurrence of the problem.
                            type: integer
                          detail:
                            description: >
                              A human-readable explanation specific to this
                              occurrence of the problem.
                            type: string
                          instance:
                            description: >
                              A URI reference that identifies the specific
                              occurrence of the problem. It may yield further
                              information if dereferenced.
                            type: string
                            format: URI
                '405':
                  description: >
                    405 METHOD NOT ALLOWED

                    If a particular HTTP method is not supported for a
                    particular resource, the API producer shall respond with
                    this response code. The "ProblemDetails" structure may be
                    omitted.
                  headers:
                    Content-Type:
                      description: The MIME type of the body of the response.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 1
                    WWW-Authenticate:
                      description: >
                        Challenge if the corresponding HTTP request has not
                        provided authorization, or error details if the
                        corresponding HTTP request has provided an invalid
                        authorization token.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 0
                    Version:
                      description: |
                        Version of the API used in the response.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 1
                  content:
                    application/json:
                      schema:
                        description: >
                          The definition of the general "ProblemDetails" data
                          structure from IETF RFC 7807 [19] is reproduced inthis
                          structure. Compared to the general framework defined
                          in IETF RFC 7807 [19], the "status" and "detail"
                          attributes are mandated to be included by the present
                          document, to ensure that the response contains
                          additional textual information about an error. IETF
                          RFC 7807 [19] foresees extensibility of the
                          "ProblemDetails" type. It is possible that particular
                          APIs in the present document, or particular
                          implementations, define extensions to define
                          additional attributes that provide more information
                          about the error. The description column only provides
                          some explanation of the meaning to Facilitate
                          understanding of the design. For a full description,
                          see IETF RFC 7807 [19].
                        type: object
                        required:
                          - status
                          - detail
                        properties:
                          type:
                            description: >
                              A URI reference according to IETF RFC 3986 [5]
                              that identifies the problem type. It is encouraged
                              that the URI provides human-readable documentation
                              for the problem (e.g. using HTML) when
                              dereferenced. When this member is not present, its
                              value is assumed to be "about:blank".
                            type: string
                            format: URI
                          title:
                            description: >
                              A short, human-readable summary of the problem
                              type. It should not change from occurrence to
                              occurrence of the problem, except for purposes of
                              localization. If type is given and other than
                              "about:blank", this attribute shall also be
                              provided. A short, human-readable summary of the
                              problem type.  It SHOULD NOT change from
                              occurrence to occurrence of the problem, except
                              for purposes of localization (e.g., using
                              proactive content negotiation; see [RFC7231],
                              Section 3.4).
                            type: string
                          status:
                            description: >
                              The HTTP status code for this occurrence of the
                              problem. The HTTP status code ([RFC7231], Section
                              6) generated by the origin server for this
                              occurrence of the problem.
                            type: integer
                          detail:
                            description: >
                              A human-readable explanation specific to this
                              occurrence of the problem.
                            type: string
                          instance:
                            description: >
                              A URI reference that identifies the specific
                              occurrence of the problem. It may yield further
                              information if dereferenced.
                            type: string
                            format: URI
                '406':
                  description: >
                    406 NOT ACCEPTABLE

                    If the "Accept" HTTP header does not contain at least one
                    name of a content type that is acceptable to the API
                    producer, the API producer shall respond with this response
                    code. The "ProblemDetails" structure may be omitted.
                  headers:
                    Content-Type:
                      description: The MIME type of the body of the response.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 1
                    WWW-Authenticate:
                      description: >
                        Challenge if the corresponding HTTP request has not
                        provided authorization, or error details if the
                        corresponding HTTP request has provided an invalid
                        authorization token.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 0
                    Version:
                      description: |
                        Version of the API used in the response.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 1
                  content:
                    application/json:
                      schema:
                        description: >
                          The definition of the general "ProblemDetails" data
                          structure from IETF RFC 7807 [19] is reproduced inthis
                          structure. Compared to the general framework defined
                          in IETF RFC 7807 [19], the "status" and "detail"
                          attributes are mandated to be included by the present
                          document, to ensure that the response contains
                          additional textual information about an error. IETF
                          RFC 7807 [19] foresees extensibility of the
                          "ProblemDetails" type. It is possible that particular
                          APIs in the present document, or particular
                          implementations, define extensions to define
                          additional attributes that provide more information
                          about the error. The description column only provides
                          some explanation of the meaning to Facilitate
                          understanding of the design. For a full description,
                          see IETF RFC 7807 [19].
                        type: object
                        required:
                          - status
                          - detail
                        properties:
                          type:
                            description: >
                              A URI reference according to IETF RFC 3986 [5]
                              that identifies the problem type. It is encouraged
                              that the URI provides human-readable documentation
                              for the problem (e.g. using HTML) when
                              dereferenced. When this member is not present, its
                              value is assumed to be "about:blank".
                            type: string
                            format: URI
                          title:
                            description: >
                              A short, human-readable summary of the problem
                              type. It should not change from occurrence to
                              occurrence of the problem, except for purposes of
                              localization. If type is given and other than
                              "about:blank", this attribute shall also be
                              provided. A short, human-readable summary of the
                              problem type.  It SHOULD NOT change from
                              occurrence to occurrence of the problem, except
                              for purposes of localization (e.g., using
                              proactive content negotiation; see [RFC7231],
                              Section 3.4).
                            type: string
                          status:
                            description: >
                              The HTTP status code for this occurrence of the
                              problem. The HTTP status code ([RFC7231], Section
                              6) generated by the origin server for this
                              occurrence of the problem.
                            type: integer
                          detail:
                            description: >
                              A human-readable explanation specific to this
                              occurrence of the problem.
                            type: string
                          instance:
                            description: >
                              A URI reference that identifies the specific
                              occurrence of the problem. It may yield further
                              information if dereferenced.
                            type: string
                            format: URI
                '422':
                  description: >
                    422 UNPROCESSABLE ENTITY

                    If the payload body of a request contains syntactically
                    correct data (e.g. well-formed JSON) but the data cannot be
                    processed (e.g. because it fails validation against a
                    schema), the API producer shall respond with this response
                    code. The "ProblemDetails" structure shall be provided, and
                    should include in the "detail" attribute more information
                    about the source of the problem.

                    This error response code is only applicable for methods that
                    have a request body.
                  headers:
                    Content-Type:
                      description: The MIME type of the body of the response.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 1
                    WWW-Authenticate:
                      description: >
                        Challenge if the corresponding HTTP request has not
                        provided authorization, or error details if the
                        corresponding HTTP request has provided an invalid
                        authorization token.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 0
                    Version:
                      description: |
                        Version of the API used in the response.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 1
                  content:
                    application/json:
                      schema:
                        description: >
                          The definition of the general "ProblemDetails" data
                          structure from IETF RFC 7807 [19] is reproduced inthis
                          structure. Compared to the general framework defined
                          in IETF RFC 7807 [19], the "status" and "detail"
                          attributes are mandated to be included by the present
                          document, to ensure that the response contains
                          additional textual information about an error. IETF
                          RFC 7807 [19] foresees extensibility of the
                          "ProblemDetails" type. It is possible that particular
                          APIs in the present document, or particular
                          implementations, define extensions to define
                          additional attributes that provide more information
                          about the error. The description column only provides
                          some explanation of the meaning to Facilitate
                          understanding of the design. For a full description,
                          see IETF RFC 7807 [19].
                        type: object
                        required:
                          - status
                          - detail
                        properties:
                          type:
                            description: >
                              A URI reference according to IETF RFC 3986 [5]
                              that identifies the problem type. It is encouraged
                              that the URI provides human-readable documentation
                              for the problem (e.g. using HTML) when
                              dereferenced. When this member is not present, its
                              value is assumed to be "about:blank".
                            type: string
                            format: URI
                          title:
                            description: >
                              A short, human-readable summary of the problem
                              type. It should not change from occurrence to
                              occurrence of the problem, except for purposes of
                              localization. If type is given and other than
                              "about:blank", this attribute shall also be
                              provided. A short, human-readable summary of the
                              problem type.  It SHOULD NOT change from
                              occurrence to occurrence of the problem, except
                              for purposes of localization (e.g., using
                              proactive content negotiation; see [RFC7231],
                              Section 3.4).
                            type: string
                          status:
                            description: >
                              The HTTP status code for this occurrence of the
                              problem. The HTTP status code ([RFC7231], Section
                              6) generated by the origin server for this
                              occurrence of the problem.
                            type: integer
                          detail:
                            description: >
                              A human-readable explanation specific to this
                              occurrence of the problem.
                            type: string
                          instance:
                            description: >
                              A URI reference that identifies the specific
                              occurrence of the problem. It may yield further
                              information if dereferenced.
                            type: string
                            format: URI
                '500':
                  description: >
                    500 INTERNAL SERVER ERROR

                    If there is an application error not related to the client's
                    input that cannot be easily mapped to any other HTTP
                    response code ("catch all error"), the API producer shall
                    respond with this response code. The "ProblemDetails"
                    structure shall be provided, and shall include in the
                    "detail" attribute more information about the source of the
                    problem.
                  headers:
                    Content-Type:
                      description: The MIME type of the body of the response.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 1
                    WWW-Authenticate:
                      description: >
                        Challenge if the corresponding HTTP request has not
                        provided authorization, or error details if the
                        corresponding HTTP request has provided an invalid
                        authorization token.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 0
                    Version:
                      description: |
                        Version of the API used in the response.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 1
                  content:
                    application/json:
                      schema:
                        description: >
                          The definition of the general "ProblemDetails" data
                          structure from IETF RFC 7807 [19] is reproduced inthis
                          structure. Compared to the general framework defined
                          in IETF RFC 7807 [19], the "status" and "detail"
                          attributes are mandated to be included by the present
                          document, to ensure that the response contains
                          additional textual information about an error. IETF
                          RFC 7807 [19] foresees extensibility of the
                          "ProblemDetails" type. It is possible that particular
                          APIs in the present document, or particular
                          implementations, define extensions to define
                          additional attributes that provide more information
                          about the error. The description column only provides
                          some explanation of the meaning to Facilitate
                          understanding of the design. For a full description,
                          see IETF RFC 7807 [19].
                        type: object
                        required:
                          - status
                          - detail
                        properties:
                          type:
                            description: >
                              A URI reference according to IETF RFC 3986 [5]
                              that identifies the problem type. It is encouraged
                              that the URI provides human-readable documentation
                              for the problem (e.g. using HTML) when
                              dereferenced. When this member is not present, its
                              value is assumed to be "about:blank".
                            type: string
                            format: URI
                          title:
                            description: >
                              A short, human-readable summary of the problem
                              type. It should not change from occurrence to
                              occurrence of the problem, except for purposes of
                              localization. If type is given and other than
                              "about:blank", this attribute shall also be
                              provided. A short, human-readable summary of the
                              problem type.  It SHOULD NOT change from
                              occurrence to occurrence of the problem, except
                              for purposes of localization (e.g., using
                              proactive content negotiation; see [RFC7231],
                              Section 3.4).
                            type: string
                          status:
                            description: >
                              The HTTP status code for this occurrence of the
                              problem. The HTTP status code ([RFC7231], Section
                              6) generated by the origin server for this
                              occurrence of the problem.
                            type: integer
                          detail:
                            description: >
                              A human-readable explanation specific to this
                              occurrence of the problem.
                            type: string
                          instance:
                            description: >
                              A URI reference that identifies the specific
                              occurrence of the problem. It may yield further
                              information if dereferenced.
                            type: string
                            format: URI
                '503':
                  description: >
                    503 SERVICE UNAVAILABLE

                    If the API producer encounters an internal overload
                    situation of itself or of a system it relies on, it should
                    respond with this response code, following the provisions in
                    IETF RFC 7231 for the use of the "Retry-After" HTTP header
                    and for the alternative to refuse the connection. The
                    "ProblemDetails" structure may be omitted.
                  headers:
                    Content-Type:
                      description: The MIME type of the body of the response.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 1
                    WWW-Authenticate:
                      description: >
                        Challenge if the corresponding HTTP request has not
                        provided authorization, or error details if the
                        corresponding HTTP request has provided an invalid
                        authorization token.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 0
                    Version:
                      description: |
                        Version of the API used in the response.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 1
                  content:
                    application/json:
                      schema:
                        description: >
                          The definition of the general "ProblemDetails" data
                          structure from IETF RFC 7807 [19] is reproduced inthis
                          structure. Compared to the general framework defined
                          in IETF RFC 7807 [19], the "status" and "detail"
                          attributes are mandated to be included by the present
                          document, to ensure that the response contains
                          additional textual information about an error. IETF
                          RFC 7807 [19] foresees extensibility of the
                          "ProblemDetails" type. It is possible that particular
                          APIs in the present document, or particular
                          implementations, define extensions to define
                          additional attributes that provide more information
                          about the error. The description column only provides
                          some explanation of the meaning to Facilitate
                          understanding of the design. For a full description,
                          see IETF RFC 7807 [19].
                        type: object
                        required:
                          - status
                          - detail
                        properties:
                          type:
                            description: >
                              A URI reference according to IETF RFC 3986 [5]
                              that identifies the problem type. It is encouraged
                              that the URI provides human-readable documentation
                              for the problem (e.g. using HTML) when
                              dereferenced. When this member is not present, its
                              value is assumed to be "about:blank".
                            type: string
                            format: URI
                          title:
                            description: >
                              A short, human-readable summary of the problem
                              type. It should not change from occurrence to
                              occurrence of the problem, except for purposes of
                              localization. If type is given and other than
                              "about:blank", this attribute shall also be
                              provided. A short, human-readable summary of the
                              problem type.  It SHOULD NOT change from
                              occurrence to occurrence of the problem, except
                              for purposes of localization (e.g., using
                              proactive content negotiation; see [RFC7231],
                              Section 3.4).
                            type: string
                          status:
                            description: >
                              The HTTP status code for this occurrence of the
                              problem. The HTTP status code ([RFC7231], Section
                              6) generated by the origin server for this
                              occurrence of the problem.
                            type: integer
                          detail:
                            description: >
                              A human-readable explanation specific to this
                              occurrence of the problem.
                            type: string
                          instance:
                            description: >
                              A URI reference that identifies the specific
                              occurrence of the problem. It may yield further
                              information if dereferenced.
                            type: string
                            format: URI
                '504':
                  description: >
                    504 GATEWAY TIMEOUT

                    If the API producer encounters a timeout while waiting for a
                    response from an upstream server (i.e. a server that the API
                    producer communicates with when fulfilling a request), it
                    should respond with this response code.
                  headers:
                    Content-Type:
                      description: The MIME type of the body of the response.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 1
                    WWW-Authenticate:
                      description: >
                        Challenge if the corresponding HTTP request has not
                        provided authorization, or error details if the
                        corresponding HTTP request has provided an invalid
                        authorization token.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 0
                    Version:
                      description: |
                        Version of the API used in the response.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 1
                  content:
                    application/json:
                      schema:
                        description: >
                          The definition of the general "ProblemDetails" data
                          structure from IETF RFC 7807 [19] is reproduced inthis
                          structure. Compared to the general framework defined
                          in IETF RFC 7807 [19], the "status" and "detail"
                          attributes are mandated to be included by the present
                          document, to ensure that the response contains
                          additional textual information about an error. IETF
                          RFC 7807 [19] foresees extensibility of the
                          "ProblemDetails" type. It is possible that particular
                          APIs in the present document, or particular
                          implementations, define extensions to define
                          additional attributes that provide more information
                          about the error. The description column only provides
                          some explanation of the meaning to Facilitate
                          understanding of the design. For a full description,
                          see IETF RFC 7807 [19].
                        type: object
                        required:
                          - status
                          - detail
                        properties:
                          type:
                            description: >
                              A URI reference according to IETF RFC 3986 [5]
                              that identifies the problem type. It is encouraged
                              that the URI provides human-readable documentation
                              for the problem (e.g. using HTML) when
                              dereferenced. When this member is not present, its
                              value is assumed to be "about:blank".
                            type: string
                            format: URI
                          title:
                            description: >
                              A short, human-readable summary of the problem
                              type. It should not change from occurrence to
                              occurrence of the problem, except for purposes of
                              localization. If type is given and other than
                              "about:blank", this attribute shall also be
                              provided. A short, human-readable summary of the
                              problem type.  It SHOULD NOT change from
                              occurrence to occurrence of the problem, except
                              for purposes of localization (e.g., using
                              proactive content negotiation; see [RFC7231],
                              Section 3.4).
                            type: string
                          status:
                            description: >
                              The HTTP status code for this occurrence of the
                              problem. The HTTP status code ([RFC7231], Section
                              6) generated by the origin server for this
                              occurrence of the problem.
                            type: integer
                          detail:
                            description: >
                              A human-readable explanation specific to this
                              occurrence of the problem.
                            type: string
                          instance:
                            description: >
                              A URI reference that identifies the specific
                              occurrence of the problem. It may yield further
                              information if dereferenced.
                            type: string
                            format: URI
            get:
              description: >-
                The GET method allows the API producer to test the notification
                endpoint that is provided by the API consumer, e.g. during
                subscription. This method shall follow the provisions specified
                in the tables 8.5.9.3.2-1 and 8.5.9.3.2-2 for URI query
                parameters, request and response data structures, and response
                codes.
              parameters:
                - name: Version
                  description: >
                    Version of the API requested to use when responding to this
                    request.
                  in: header
                  required: true
                  schema:
                    type: string
                - name: Accept
                  description: >
                    Content-Types that are acceptable for the response.
                    Reference: IETF RFC 7231.
                  in: header
                  required: true
                  schema:
                    type: string
                - name: Authorization
                  description: >
                    The authorization token for the request. Reference: IETF RFC
                    7235.
                  in: header
                  required: false
                  schema:
                    type: string
              responses:
                '204':
                  description: >-
                    Shall be returned to indicate that the notification endpoint
                    has been tested successfully. The response body shall be
                    empty.
                  headers:
                    Content-Type:
                      description: The MIME type of the body of the response.
                      schema:
                        type: string
                    WWW-Authenticate:
                      description: >
                        Challenge if the corresponding HTTP request has not
                        provided authorization, or error details if the
                        corresponding HTTP request has provided an invalid
                        authorization token.
                      schema:
                        type: string
                    Version:
                      description: |
                        Version of the API used in the response.
                      schema:
                        type: string
                '400':
                  description: >
                    400 BAD REQUEST

                    400 code can be returned in the following specified cases,
                    the specific cause has to be proper specified in the
                    "ProblemDetails" structure to be returned.

                    If the request is malformed or syntactically incorrect (e.g.
                    if the request URI contains incorrect query parameters or
                    the payload body contains a syntactically incorrect data
                    structure), the API producer shall respond with this
                    response code. The "ProblemDetails" structure shall be
                    provided, and should include in the "detail" attribute more
                    information about the source of the problem.

                    If the response to a GET request which queries a container
                    resource would be so big that the performance of the API
                    producer is adversely affected, and the API producer does
                    not support paging for the affected resource, it shall
                    respond with this response code. The "ProblemDetails"
                    structure shall be provided, and should include in the
                    "detail" attribute more information about the source of the
                    problem.

                    If there is an application error related to the client's
                    input that cannot be easily mapped to any other HTTP
                    response code ("catch all error"), the API producer shall
                    respond with this response code. The "ProblemDetails"
                    structure shall be provided, and shall include in the
                    "detail" attribute more information about the source of the
                    problem.

                    If the request contains a malformed access token, the API
                    producer should respond with this response. The details of
                    the error shall be returned in the WWW Authenticate HTTP
                    header, as defined in IETF RFC 6750 and IETF RFC 7235. The
                    ProblemDetails structure may be provided.

                    The use of this HTTP error response code described above is
                    applicable to the use of the OAuth 2.0 for the authorization
                    of API requests and notifications, as defined in clauses
                    4.5.3.3 and 4.5.3.4.
                  headers:
                    Content-Type:
                      description: The MIME type of the body of the response.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 1
                    WWW-Authenticate:
                      description: >
                        Challenge if the corresponding HTTP request has not
                        provided authorization, or error details if the
                        corresponding HTTP request has provided an invalid
                        authorization token.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 0
                    Version:
                      description: |
                        Version of the API used in the response.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 1
                  content:
                    application/json:
                      schema:
                        description: >
                          The definition of the general "ProblemDetails" data
                          structure from IETF RFC 7807 [19] is reproduced inthis
                          structure. Compared to the general framework defined
                          in IETF RFC 7807 [19], the "status" and "detail"
                          attributes are mandated to be included by the present
                          document, to ensure that the response contains
                          additional textual information about an error. IETF
                          RFC 7807 [19] foresees extensibility of the
                          "ProblemDetails" type. It is possible that particular
                          APIs in the present document, or particular
                          implementations, define extensions to define
                          additional attributes that provide more information
                          about the error. The description column only provides
                          some explanation of the meaning to Facilitate
                          understanding of the design. For a full description,
                          see IETF RFC 7807 [19].
                        type: object
                        required:
                          - status
                          - detail
                        properties:
                          type:
                            description: >
                              A URI reference according to IETF RFC 3986 [5]
                              that identifies the problem type. It is encouraged
                              that the URI provides human-readable documentation
                              for the problem (e.g. using HTML) when
                              dereferenced. When this member is not present, its
                              value is assumed to be "about:blank".
                            type: string
                            format: URI
                          title:
                            description: >
                              A short, human-readable summary of the problem
                              type. It should not change from occurrence to
                              occurrence of the problem, except for purposes of
                              localization. If type is given and other than
                              "about:blank", this attribute shall also be
                              provided. A short, human-readable summary of the
                              problem type.  It SHOULD NOT change from
                              occurrence to occurrence of the problem, except
                              for purposes of localization (e.g., using
                              proactive content negotiation; see [RFC7231],
                              Section 3.4).
                            type: string
                          status:
                            description: >
                              The HTTP status code for this occurrence of the
                              problem. The HTTP status code ([RFC7231], Section
                              6) generated by the origin server for this
                              occurrence of the problem.
                            type: integer
                          detail:
                            description: >
                              A human-readable explanation specific to this
                              occurrence of the problem.
                            type: string
                          instance:
                            description: >
                              A URI reference that identifies the specific
                              occurrence of the problem. It may yield further
                              information if dereferenced.
                            type: string
                            format: URI
                '401':
                  description: >
                    401 UNAUTHORIZED

                    If the request contains no access token even though one is
                    required, or if the request contains an authorization token
                    that is invalid (e.g. expired or revoked), the API producer
                    should respond with this response. The details of the error
                    shall be returned in the WWW-Authenticate HTTP header, as
                    defined in IETF RFC 6750 and IETF RFC 7235. The
                    ProblemDetails structure may be provided.
                  headers:
                    Content-Type:
                      description: The MIME type of the body of the response.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 1
                    WWW-Authenticate:
                      description: >
                        Challenge if the corresponding HTTP request has not
                        provided authorization, or error details if the
                        corresponding HTTP request has provided an invalid
                        authorization token.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 0
                    Version:
                      description: |
                        Version of the API used in the response.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 1
                  content:
                    application/json:
                      schema:
                        description: >
                          The definition of the general "ProblemDetails" data
                          structure from IETF RFC 7807 [19] is reproduced inthis
                          structure. Compared to the general framework defined
                          in IETF RFC 7807 [19], the "status" and "detail"
                          attributes are mandated to be included by the present
                          document, to ensure that the response contains
                          additional textual information about an error. IETF
                          RFC 7807 [19] foresees extensibility of the
                          "ProblemDetails" type. It is possible that particular
                          APIs in the present document, or particular
                          implementations, define extensions to define
                          additional attributes that provide more information
                          about the error. The description column only provides
                          some explanation of the meaning to Facilitate
                          understanding of the design. For a full description,
                          see IETF RFC 7807 [19].
                        type: object
                        required:
                          - status
                          - detail
                        properties:
                          type:
                            description: >
                              A URI reference according to IETF RFC 3986 [5]
                              that identifies the problem type. It is encouraged
                              that the URI provides human-readable documentation
                              for the problem (e.g. using HTML) when
                              dereferenced. When this member is not present, its
                              value is assumed to be "about:blank".
                            type: string
                            format: URI
                          title:
                            description: >
                              A short, human-readable summary of the problem
                              type. It should not change from occurrence to
                              occurrence of the problem, except for purposes of
                              localization. If type is given and other than
                              "about:blank", this attribute shall also be
                              provided. A short, human-readable summary of the
                              problem type.  It SHOULD NOT change from
                              occurrence to occurrence of the problem, except
                              for purposes of localization (e.g., using
                              proactive content negotiation; see [RFC7231],
                              Section 3.4).
                            type: string
                          status:
                            description: >
                              The HTTP status code for this occurrence of the
                              problem. The HTTP status code ([RFC7231], Section
                              6) generated by the origin server for this
                              occurrence of the problem.
                            type: integer
                          detail:
                            description: >
                              A human-readable explanation specific to this
                              occurrence of the problem.
                            type: string
                          instance:
                            description: >
                              A URI reference that identifies the specific
                              occurrence of the problem. It may yield further
                              information if dereferenced.
                            type: string
                            format: URI
                '403':
                  description: >
                    403 FORBIDDEN

                    If the API consumer is not allowed to perform a particular
                    request to a particular resource, the API producer shall
                    respond with this response code. The "ProblemDetails"
                    structure shall be provided. It should include in the
                    "detail" attribute information about the source of the
                    problem, and may indicate how to solve it.
                  headers:
                    Content-Type:
                      description: The MIME type of the body of the response.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 1
                    WWW-Authenticate:
                      description: >
                        Challenge if the corresponding HTTP request has not
                        provided authorization, or error details if the
                        corresponding HTTP request has provided an invalid
                        authorization token.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 0
                    Version:
                      description: |
                        Version of the API used in the response.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 1
                  content:
                    application/json:
                      schema:
                        description: >
                          The definition of the general "ProblemDetails" data
                          structure from IETF RFC 7807 [19] is reproduced inthis
                          structure. Compared to the general framework defined
                          in IETF RFC 7807 [19], the "status" and "detail"
                          attributes are mandated to be included by the present
                          document, to ensure that the response contains
                          additional textual information about an error. IETF
                          RFC 7807 [19] foresees extensibility of the
                          "ProblemDetails" type. It is possible that particular
                          APIs in the present document, or particular
                          implementations, define extensions to define
                          additional attributes that provide more information
                          about the error. The description column only provides
                          some explanation of the meaning to Facilitate
                          understanding of the design. For a full description,
                          see IETF RFC 7807 [19].
                        type: object
                        required:
                          - status
                          - detail
                        properties:
                          type:
                            description: >
                              A URI reference according to IETF RFC 3986 [5]
                              that identifies the problem type. It is encouraged
                              that the URI provides human-readable documentation
                              for the problem (e.g. using HTML) when
                              dereferenced. When this member is not present, its
                              value is assumed to be "about:blank".
                            type: string
                            format: URI
                          title:
                            description: >
                              A short, human-readable summary of the problem
                              type. It should not change from occurrence to
                              occurrence of the problem, except for purposes of
                              localization. If type is given and other than
                              "about:blank", this attribute shall also be
                              provided. A short, human-readable summary of the
                              problem type.  It SHOULD NOT change from
                              occurrence to occurrence of the problem, except
                              for purposes of localization (e.g., using
                              proactive content negotiation; see [RFC7231],
                              Section 3.4).
                            type: string
                          status:
                            description: >
                              The HTTP status code for this occurrence of the
                              problem. The HTTP status code ([RFC7231], Section
                              6) generated by the origin server for this
                              occurrence of the problem.
                            type: integer
                          detail:
                            description: >
                              A human-readable explanation specific to this
                              occurrence of the problem.
                            type: string
                          instance:
                            description: >
                              A URI reference that identifies the specific
                              occurrence of the problem. It may yield further
                              information if dereferenced.
                            type: string
                            format: URI
                '404':
                  description: >
                    404 NOT FOUND

                    If the API producer did not find a current representation
                    for the resource addressed by the URI passed in the request
                    or is not willing to disclose that one exists, it shall
                    respond with this response code. The "ProblemDetails"
                    structure may be provided, including in the "detail"
                    attribute information about the source of the problem, e.g.
                    a wrong resource URI variable.

                    This response code is not appropriate in case the resource
                    addressed by the URI is a container resource which is
                    designed to contain child resources, but does not contain
                    any child resource at the time the request is received. For
                    a GET request to an existing empty container resource, a
                    typical response contains a 200 OK response code and a
                    payload body with an empty array.
                  headers:
                    Content-Type:
                      description: The MIME type of the body of the response.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 1
                    WWW-Authenticate:
                      description: >
                        Challenge if the corresponding HTTP request has not
                        provided authorization, or error details if the
                        corresponding HTTP request has provided an invalid
                        authorization token.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 0
                    Version:
                      description: |
                        Version of the API used in the response.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 1
                  content:
                    application/json:
                      schema:
                        description: >
                          The definition of the general "ProblemDetails" data
                          structure from IETF RFC 7807 [19] is reproduced inthis
                          structure. Compared to the general framework defined
                          in IETF RFC 7807 [19], the "status" and "detail"
                          attributes are mandated to be included by the present
                          document, to ensure that the response contains
                          additional textual information about an error. IETF
                          RFC 7807 [19] foresees extensibility of the
                          "ProblemDetails" type. It is possible that particular
                          APIs in the present document, or particular
                          implementations, define extensions to define
                          additional attributes that provide more information
                          about the error. The description column only provides
                          some explanation of the meaning to Facilitate
                          understanding of the design. For a full description,
                          see IETF RFC 7807 [19].
                        type: object
                        required:
                          - status
                          - detail
                        properties:
                          type:
                            description: >
                              A URI reference according to IETF RFC 3986 [5]
                              that identifies the problem type. It is encouraged
                              that the URI provides human-readable documentation
                              for the problem (e.g. using HTML) when
                              dereferenced. When this member is not present, its
                              value is assumed to be "about:blank".
                            type: string
                            format: URI
                          title:
                            description: >
                              A short, human-readable summary of the problem
                              type. It should not change from occurrence to
                              occurrence of the problem, except for purposes of
                              localization. If type is given and other than
                              "about:blank", this attribute shall also be
                              provided. A short, human-readable summary of the
                              problem type.  It SHOULD NOT change from
                              occurrence to occurrence of the problem, except
                              for purposes of localization (e.g., using
                              proactive content negotiation; see [RFC7231],
                              Section 3.4).
                            type: string
                          status:
                            description: >
                              The HTTP status code for this occurrence of the
                              problem. The HTTP status code ([RFC7231], Section
                              6) generated by the origin server for this
                              occurrence of the problem.
                            type: integer
                          detail:
                            description: >
                              A human-readable explanation specific to this
                              occurrence of the problem.
                            type: string
                          instance:
                            description: >
                              A URI reference that identifies the specific
                              occurrence of the problem. It may yield further
                              information if dereferenced.
                            type: string
                            format: URI
                '405':
                  description: >
                    405 METHOD NOT ALLOWED

                    If a particular HTTP method is not supported for a
                    particular resource, the API producer shall respond with
                    this response code. The "ProblemDetails" structure may be
                    omitted.
                  headers:
                    Content-Type:
                      description: The MIME type of the body of the response.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 1
                    WWW-Authenticate:
                      description: >
                        Challenge if the corresponding HTTP request has not
                        provided authorization, or error details if the
                        corresponding HTTP request has provided an invalid
                        authorization token.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 0
                    Version:
                      description: |
                        Version of the API used in the response.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 1
                  content:
                    application/json:
                      schema:
                        description: >
                          The definition of the general "ProblemDetails" data
                          structure from IETF RFC 7807 [19] is reproduced inthis
                          structure. Compared to the general framework defined
                          in IETF RFC 7807 [19], the "status" and "detail"
                          attributes are mandated to be included by the present
                          document, to ensure that the response contains
                          additional textual information about an error. IETF
                          RFC 7807 [19] foresees extensibility of the
                          "ProblemDetails" type. It is possible that particular
                          APIs in the present document, or particular
                          implementations, define extensions to define
                          additional attributes that provide more information
                          about the error. The description column only provides
                          some explanation of the meaning to Facilitate
                          understanding of the design. For a full description,
                          see IETF RFC 7807 [19].
                        type: object
                        required:
                          - status
                          - detail
                        properties:
                          type:
                            description: >
                              A URI reference according to IETF RFC 3986 [5]
                              that identifies the problem type. It is encouraged
                              that the URI provides human-readable documentation
                              for the problem (e.g. using HTML) when
                              dereferenced. When this member is not present, its
                              value is assumed to be "about:blank".
                            type: string
                            format: URI
                          title:
                            description: >
                              A short, human-readable summary of the problem
                              type. It should not change from occurrence to
                              occurrence of the problem, except for purposes of
                              localization. If type is given and other than
                              "about:blank", this attribute shall also be
                              provided. A short, human-readable summary of the
                              problem type.  It SHOULD NOT change from
                              occurrence to occurrence of the problem, except
                              for purposes of localization (e.g., using
                              proactive content negotiation; see [RFC7231],
                              Section 3.4).
                            type: string
                          status:
                            description: >
                              The HTTP status code for this occurrence of the
                              problem. The HTTP status code ([RFC7231], Section
                              6) generated by the origin server for this
                              occurrence of the problem.
                            type: integer
                          detail:
                            description: >
                              A human-readable explanation specific to this
                              occurrence of the problem.
                            type: string
                          instance:
                            description: >
                              A URI reference that identifies the specific
                              occurrence of the problem. It may yield further
                              information if dereferenced.
                            type: string
                            format: URI
                '406':
                  description: >
                    406 NOT ACCEPTABLE

                    If the "Accept" HTTP header does not contain at least one
                    name of a content type that is acceptable to the API
                    producer, the API producer shall respond with this response
                    code. The "ProblemDetails" structure may be omitted.
                  headers:
                    Content-Type:
                      description: The MIME type of the body of the response.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 1
                    WWW-Authenticate:
                      description: >
                        Challenge if the corresponding HTTP request has not
                        provided authorization, or error details if the
                        corresponding HTTP request has provided an invalid
                        authorization token.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 0
                    Version:
                      description: |
                        Version of the API used in the response.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 1
                  content:
                    application/json:
                      schema:
                        description: >
                          The definition of the general "ProblemDetails" data
                          structure from IETF RFC 7807 [19] is reproduced inthis
                          structure. Compared to the general framework defined
                          in IETF RFC 7807 [19], the "status" and "detail"
                          attributes are mandated to be included by the present
                          document, to ensure that the response contains
                          additional textual information about an error. IETF
                          RFC 7807 [19] foresees extensibility of the
                          "ProblemDetails" type. It is possible that particular
                          APIs in the present document, or particular
                          implementations, define extensions to define
                          additional attributes that provide more information
                          about the error. The description column only provides
                          some explanation of the meaning to Facilitate
                          understanding of the design. For a full description,
                          see IETF RFC 7807 [19].
                        type: object
                        required:
                          - status
                          - detail
                        properties:
                          type:
                            description: >
                              A URI reference according to IETF RFC 3986 [5]
                              that identifies the problem type. It is encouraged
                              that the URI provides human-readable documentation
                              for the problem (e.g. using HTML) when
                              dereferenced. When this member is not present, its
                              value is assumed to be "about:blank".
                            type: string
                            format: URI
                          title:
                            description: >
                              A short, human-readable summary of the problem
                              type. It should not change from occurrence to
                              occurrence of the problem, except for purposes of
                              localization. If type is given and other than
                              "about:blank", this attribute shall also be
                              provided. A short, human-readable summary of the
                              problem type.  It SHOULD NOT change from
                              occurrence to occurrence of the problem, except
                              for purposes of localization (e.g., using
                              proactive content negotiation; see [RFC7231],
                              Section 3.4).
                            type: string
                          status:
                            description: >
                              The HTTP status code for this occurrence of the
                              problem. The HTTP status code ([RFC7231], Section
                              6) generated by the origin server for this
                              occurrence of the problem.
                            type: integer
                          detail:
                            description: >
                              A human-readable explanation specific to this
                              occurrence of the problem.
                            type: string
                          instance:
                            description: >
                              A URI reference that identifies the specific
                              occurrence of the problem. It may yield further
                              information if dereferenced.
                            type: string
                            format: URI
                '422':
                  description: >
                    422 UNPROCESSABLE ENTITY

                    If the payload body of a request contains syntactically
                    correct data (e.g. well-formed JSON) but the data cannot be
                    processed (e.g. because it fails validation against a
                    schema), the API producer shall respond with this response
                    code. The "ProblemDetails" structure shall be provided, and
                    should include in the "detail" attribute more information
                    about the source of the problem.

                    This error response code is only applicable for methods that
                    have a request body.
                  headers:
                    Content-Type:
                      description: The MIME type of the body of the response.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 1
                    WWW-Authenticate:
                      description: >
                        Challenge if the corresponding HTTP request has not
                        provided authorization, or error details if the
                        corresponding HTTP request has provided an invalid
                        authorization token.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 0
                    Version:
                      description: |
                        Version of the API used in the response.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 1
                  content:
                    application/json:
                      schema:
                        description: >
                          The definition of the general "ProblemDetails" data
                          structure from IETF RFC 7807 [19] is reproduced inthis
                          structure. Compared to the general framework defined
                          in IETF RFC 7807 [19], the "status" and "detail"
                          attributes are mandated to be included by the present
                          document, to ensure that the response contains
                          additional textual information about an error. IETF
                          RFC 7807 [19] foresees extensibility of the
                          "ProblemDetails" type. It is possible that particular
                          APIs in the present document, or particular
                          implementations, define extensions to define
                          additional attributes that provide more information
                          about the error. The description column only provides
                          some explanation of the meaning to Facilitate
                          understanding of the design. For a full description,
                          see IETF RFC 7807 [19].
                        type: object
                        required:
                          - status
                          - detail
                        properties:
                          type:
                            description: >
                              A URI reference according to IETF RFC 3986 [5]
                              that identifies the problem type. It is encouraged
                              that the URI provides human-readable documentation
                              for the problem (e.g. using HTML) when
                              dereferenced. When this member is not present, its
                              value is assumed to be "about:blank".
                            type: string
                            format: URI
                          title:
                            description: >
                              A short, human-readable summary of the problem
                              type. It should not change from occurrence to
                              occurrence of the problem, except for purposes of
                              localization. If type is given and other than
                              "about:blank", this attribute shall also be
                              provided. A short, human-readable summary of the
                              problem type.  It SHOULD NOT change from
                              occurrence to occurrence of the problem, except
                              for purposes of localization (e.g., using
                              proactive content negotiation; see [RFC7231],
                              Section 3.4).
                            type: string
                          status:
                            description: >
                              The HTTP status code for this occurrence of the
                              problem. The HTTP status code ([RFC7231], Section
                              6) generated by the origin server for this
                              occurrence of the problem.
                            type: integer
                          detail:
                            description: >
                              A human-readable explanation specific to this
                              occurrence of the problem.
                            type: string
                          instance:
                            description: >
                              A URI reference that identifies the specific
                              occurrence of the problem. It may yield further
                              information if dereferenced.
                            type: string
                            format: URI
                '500':
                  description: >
                    500 INTERNAL SERVER ERROR

                    If there is an application error not related to the client's
                    input that cannot be easily mapped to any other HTTP
                    response code ("catch all error"), the API producer shall
                    respond with this response code. The "ProblemDetails"
                    structure shall be provided, and shall include in the
                    "detail" attribute more information about the source of the
                    problem.
                  headers:
                    Content-Type:
                      description: The MIME type of the body of the response.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 1
                    WWW-Authenticate:
                      description: >
                        Challenge if the corresponding HTTP request has not
                        provided authorization, or error details if the
                        corresponding HTTP request has provided an invalid
                        authorization token.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 0
                    Version:
                      description: |
                        Version of the API used in the response.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 1
                  content:
                    application/json:
                      schema:
                        description: >
                          The definition of the general "ProblemDetails" data
                          structure from IETF RFC 7807 [19] is reproduced inthis
                          structure. Compared to the general framework defined
                          in IETF RFC 7807 [19], the "status" and "detail"
                          attributes are mandated to be included by the present
                          document, to ensure that the response contains
                          additional textual information about an error. IETF
                          RFC 7807 [19] foresees extensibility of the
                          "ProblemDetails" type. It is possible that particular
                          APIs in the present document, or particular
                          implementations, define extensions to define
                          additional attributes that provide more information
                          about the error. The description column only provides
                          some explanation of the meaning to Facilitate
                          understanding of the design. For a full description,
                          see IETF RFC 7807 [19].
                        type: object
                        required:
                          - status
                          - detail
                        properties:
                          type:
                            description: >
                              A URI reference according to IETF RFC 3986 [5]
                              that identifies the problem type. It is encouraged
                              that the URI provides human-readable documentation
                              for the problem (e.g. using HTML) when
                              dereferenced. When this member is not present, its
                              value is assumed to be "about:blank".
                            type: string
                            format: URI
                          title:
                            description: >
                              A short, human-readable summary of the problem
                              type. It should not change from occurrence to
                              occurrence of the problem, except for purposes of
                              localization. If type is given and other than
                              "about:blank", this attribute shall also be
                              provided. A short, human-readable summary of the
                              problem type.  It SHOULD NOT change from
                              occurrence to occurrence of the problem, except
                              for purposes of localization (e.g., using
                              proactive content negotiation; see [RFC7231],
                              Section 3.4).
                            type: string
                          status:
                            description: >
                              The HTTP status code for this occurrence of the
                              problem. The HTTP status code ([RFC7231], Section
                              6) generated by the origin server for this
                              occurrence of the problem.
                            type: integer
                          detail:
                            description: >
                              A human-readable explanation specific to this
                              occurrence of the problem.
                            type: string
                          instance:
                            description: >
                              A URI reference that identifies the specific
                              occurrence of the problem. It may yield further
                              information if dereferenced.
                            type: string
                            format: URI
                '503':
                  description: >
                    503 SERVICE UNAVAILABLE

                    If the API producer encounters an internal overload
                    situation of itself or of a system it relies on, it should
                    respond with this response code, following the provisions in
                    IETF RFC 7231 for the use of the "Retry-After" HTTP header
                    and for the alternative to refuse the connection. The
                    "ProblemDetails" structure may be omitted.
                  headers:
                    Content-Type:
                      description: The MIME type of the body of the response.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 1
                    WWW-Authenticate:
                      description: >
                        Challenge if the corresponding HTTP request has not
                        provided authorization, or error details if the
                        corresponding HTTP request has provided an invalid
                        authorization token.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 0
                    Version:
                      description: |
                        Version of the API used in the response.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 1
                  content:
                    application/json:
                      schema:
                        description: >
                          The definition of the general "ProblemDetails" data
                          structure from IETF RFC 7807 [19] is reproduced inthis
                          structure. Compared to the general framework defined
                          in IETF RFC 7807 [19], the "status" and "detail"
                          attributes are mandated to be included by the present
                          document, to ensure that the response contains
                          additional textual information about an error. IETF
                          RFC 7807 [19] foresees extensibility of the
                          "ProblemDetails" type. It is possible that particular
                          APIs in the present document, or particular
                          implementations, define extensions to define
                          additional attributes that provide more information
                          about the error. The description column only provides
                          some explanation of the meaning to Facilitate
                          understanding of the design. For a full description,
                          see IETF RFC 7807 [19].
                        type: object
                        required:
                          - status
                          - detail
                        properties:
                          type:
                            description: >
                              A URI reference according to IETF RFC 3986 [5]
                              that identifies the problem type. It is encouraged
                              that the URI provides human-readable documentation
                              for the problem (e.g. using HTML) when
                              dereferenced. When this member is not present, its
                              value is assumed to be "about:blank".
                            type: string
                            format: URI
                          title:
                            description: >
                              A short, human-readable summary of the problem
                              type. It should not change from occurrence to
                              occurrence of the problem, except for purposes of
                              localization. If type is given and other than
                              "about:blank", this attribute shall also be
                              provided. A short, human-readable summary of the
                              problem type.  It SHOULD NOT change from
                              occurrence to occurrence of the problem, except
                              for purposes of localization (e.g., using
                              proactive content negotiation; see [RFC7231],
                              Section 3.4).
                            type: string
                          status:
                            description: >
                              The HTTP status code for this occurrence of the
                              problem. The HTTP status code ([RFC7231], Section
                              6) generated by the origin server for this
                              occurrence of the problem.
                            type: integer
                          detail:
                            description: >
                              A human-readable explanation specific to this
                              occurrence of the problem.
                            type: string
                          instance:
                            description: >
                              A URI reference that identifies the specific
                              occurrence of the problem. It may yield further
                              information if dereferenced.
                            type: string
                            format: URI
                '504':
                  description: >
                    504 GATEWAY TIMEOUT

                    If the API producer encounters a timeout while waiting for a
                    response from an upstream server (i.e. a server that the API
                    producer communicates with when fulfilling a request), it
                    should respond with this response code.
                  headers:
                    Content-Type:
                      description: The MIME type of the body of the response.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 1
                    WWW-Authenticate:
                      description: >
                        Challenge if the corresponding HTTP request has not
                        provided authorization, or error details if the
                        corresponding HTTP request has provided an invalid
                        authorization token.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 0
                    Version:
                      description: |
                        Version of the API used in the response.
                      schema:
                        type: string
                        maximum: 1
                        minimum: 1
                  content:
                    application/json:
                      schema:
                        description: >
                          The definition of the general "ProblemDetails" data
                          structure from IETF RFC 7807 [19] is reproduced inthis
                          structure. Compared to the general framework defined
                          in IETF RFC 7807 [19], the "status" and "detail"
                          attributes are mandated to be included by the present
                          document, to ensure that the response contains
                          additional textual information about an error. IETF
                          RFC 7807 [19] foresees extensibility of the
                          "ProblemDetails" type. It is possible that particular
                          APIs in the present document, or particular
                          implementations, define extensions to define
                          additional attributes that provide more information
                          about the error. The description column only provides
                          some explanation of the meaning to Facilitate
                          understanding of the design. For a full description,
                          see IETF RFC 7807 [19].
                        type: object
                        required:
                          - status
                          - detail
                        properties:
                          type:
                            description: >
                              A URI reference according to IETF RFC 3986 [5]
                              that identifies the problem type. It is encouraged
                              that the URI provides human-readable documentation
                              for the problem (e.g. using HTML) when
                              dereferenced. When this member is not present, its
                              value is assumed to be "about:blank".
                            type: string
                            format: URI
                          title:
                            description: >
                              A short, human-readable summary of the problem
                              type. It should not change from occurrence to
                              occurrence of the problem, except for purposes of
                              localization. If type is given and other than
                              "about:blank", this attribute shall also be
                              provided. A short, human-readable summary of the
                              problem type.  It SHOULD NOT change from
                              occurrence to occurrence of the problem, except
                              for purposes of localization (e.g., using
                              proactive content negotiation; see [RFC7231],
                              Section 3.4).
                            type: string
                          status:
                            description: >
                              The HTTP status code for this occurrence of the
                              problem. The HTTP status code ([RFC7231], Section
                              6) generated by the origin server for this
                              occurrence of the problem.
                            type: integer
                          detail:
                            description: >
                              A human-readable explanation specific to this
                              occurrence of the problem.
                            type: string
                          instance:
                            description: >
                              A URI reference that identifies the specific
                              occurrence of the problem. It may yield further
                              information if dereferenced.
                            type: string
                            format: URI
    get:
      description: >-
        The API consumer can use this method to query the list of active
        subscriptions to log management notifications subscribed by the API
        consumer. This method shall follow the provisions specified in the
        tables 8.5.7.3.2-1 and 8.5.7.3.2-2 for URI query parameters, request and
        response data structures, and response codes.
      parameters:
        - name: filter
          description: >
            Attribute-based filtering expression according to clause 5.2 of ETSI
            GS NFV-SOL 013. The NFV-MANO functional entity shall support
            receiving this parameter as part of the URI query string. The API
            consumer may supply this parameter. All attribute names that appear
            in the FmSubscription and in data types referenced from it shall be
            supported by the NFV-MANO functional entity in the filter
            expression.
          in: query
          required: false
          schema:
            type: string
        - name: nextpage_opaque_marker
          description: >
            Marker to obtain the next page of a paged response. Shall be
            supported by  the NFV-MANO functional entity if the entity supports
            alternative 2 (paging)  according to clause 5.4.2.1 of ETSI GS
            NFV-SOL 013 for this resource.
          in: query
          required: false
          schema:
            type: string
        - name: Version
          description: |
            Version of the API requested to use when responding to this request.
          in: header
          required: true
          schema:
            type: string
        - name: Accept
          description: >
            Content-Types that are acceptable for the response. Reference: IETF
            RFC 7231.
          in: header
          required: true
          schema:
            type: string
        - name: Authorization
          description: |
            The authorization token for the request. Reference: IETF RFC 7235.
          in: header
          required: false
          schema:
            type: string
      responses:
        '200':
          description: >-
            Shall be returned when the list of subscriptions has been queried
            successfully. The response body shall contain in an array the
            representations of all active subscriptions of the functional block
            that invokes the method, i.e. zero or more representations of log
            management subscriptions as defined in clause 8.6.2.3. If the
            "filter" URI parameter was supplied in the request, the data in the
            response body shall have been transformed according to the rules
            specified in clause 5.2.2 of ETSI GS NFV-SOL 013. If the NFV-MANO
            functional entity supports alternative 2 (paging) according to
            clause 5.4.2.1 of ETSI GS NFV-SOL 013 for this resource, inclusion
            of the Link HTTP header in this response shall follow the provisions
            in clause 5.4.2.3 of ETSI GS NFV-SOL 013 .
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
          content:
            application/json:
              schema:
                type: array
                items:
                  description: >-
                    This type represents a subscription. It shall comply with
                    the provisions defined in table 8.6.2.3-1.
                  type: object
                  required:
                    - id
                    - callbackUri
                    - _links
                  properties:
                    id:
                      description: >
                        An identifier with the intention of being globally
                        unique.
                      type: string
                    filter:
                      description: >-
                        This type represents a filter that can be used to
                        subscribe for notifications related to log management
                        events. It shall comply with the provisions defined in
                        table 8.6.3.7-1. At a particular nesting level in the
                        filter structure, the following applies: All attributes
                        shall match in order for the filter to match (logical
                        "and" between different filter attributes). If an
                        attribute is an array, the attribute shall match if at
                        least one of the values in the array matches (logical
                        "or" between the values of one filter attribute).
                      type: object
                      properties:
                        objectInstanceFilter:
                          description: >-
                            This type represents subscription filter criteria to
                            match NFV-MANO functional entities and their
                            associated managed objects. It shall comply with the
                            provisions defined in Table 4.3.2.2-1.
                          type: object
                          anyOf:
                            - oneOf:
                                - required:
                                    - manoServiceIds
                                - required:
                                    - manoServiceNames
                            - oneOf:
                                - required:
                                    - manoServiceInterfaceIds
                                - required:
                                    - manoServiceInterfaceNames
                            - oneOf:
                                - required:
                                    - consumedManoInterfaceIds
                                - required:
                                    - consumedManoInterfaceNames
                          properties:
                            manoEntityId:
                              description: >
                                An identifier with the intention of being
                                globally unique.
                              type: string
                            manoServiceIds:
                              description: >-
                                If present, match NFV-MANO services with an
                                instance identifier listed in this attribute.
                              type: array
                              items:
                                description: >
                                  An identifier that is unique for the
                                  respective type within a NFV-MANO functional
                                  entity, but that need not be globally unique.
                                  Representation: string of variable length..
                                type: string
                            manoServiceNames:
                              description: >-
                                If present, match NFV-MANO services with an
                                NFV-MANO service name listed in this attribute.
                              type: array
                              items:
                                type: string
                            manoServiceInterfaceIds:
                              description: >-
                                If present, match NFV-MANO functional entity
                                produced interfaces with an instance identifier
                                listed in this attribute.
                              type: array
                              items:
                                description: >
                                  An identifier that is unique for the
                                  respective type within a NFV-MANO functional
                                  entity, but that need not be globally unique.
                                  Representation: string of variable length..
                                type: string
                            manoServiceInterfaceNames:
                              description: >-
                                If present, match NFV-MANO functional entity
                                produced interfaces with an instance Name listed
                                in this attribute.
                              type: array
                              items:
                                type: string
                            consumedManoInterfaceIds:
                              description: >-
                                If present, match NFV-MANO functional entity
                                consumed interfaces with an instance identifier
                                listed in this attribute.
                              type: array
                              items:
                                description: >
                                  An identifier with the intention of being
                                  globally unique.
                                type: string
                            consumedManoInterfaceNames:
                              description: >-
                                If present, match NFV-MANO functional entity
                                consumed interfaces with an instance Name listed
                                in this attribute.
                              type: array
                              items:
                                type: string
                        notificationTypes:
                          description: >-
                            Match particular notification types. Permitted
                            values: - LogReportAvailableNotification
                          type: string
                          enum:
                            - LogReportAvailableNotification
                    callbackUri:
                      description: |
                        String formatted according to IETF RFC 3986.
                      type: string
                    _links:
                      description: Links to resources related to this resource.
                      type: object
                      required:
                        - self
                      properties:
                        self:
                          description: >
                            This type represents a link to a resource using an
                            absolute URI.
                          type: object
                          required:
                            - href
                          properties:
                            href:
                              description: |
                                String formatted according to IETF RFC 3986.
                              type: string
        '400':
          description: >
            400 BAD REQUEST

            400 code can be returned in the following specified cases, the
            specific cause has to be proper specified in the "ProblemDetails"
            structure to be returned.

            If the request is malformed or syntactically incorrect (e.g. if the
            request URI contains incorrect query parameters or the payload body
            contains a syntactically incorrect data structure), the API producer
            shall respond with this response code. The "ProblemDetails"
            structure shall be provided, and should include in the "detail"
            attribute more information about the source of the problem.

            If the response to a GET request which queries a container resource
            would be so big that the performance of the API producer is
            adversely affected, and the API producer does not support paging for
            the affected resource, it shall respond with this response code. The
            "ProblemDetails" structure shall be provided, and should include in
            the "detail" attribute more information about the source of the
            problem.

            If there is an application error related to the client's input that
            cannot be easily mapped to any other HTTP response code ("catch all
            error"), the API producer shall respond with this response code. The
            "ProblemDetails" structure shall be provided, and shall include in
            the "detail" attribute more information about the source of the
            problem.

            If the request contains a malformed access token, the API producer
            should respond with this response. The details of the error shall be
            returned in the WWW Authenticate HTTP header, as defined in IETF RFC
            6750 and IETF RFC 7235. The ProblemDetails structure may be
            provided.

            The use of this HTTP error response code described above is
            applicable to the use of the OAuth 2.0 for the authorization of API
            requests and notifications, as defined in clauses 4.5.3.3 and
            4.5.3.4.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '401':
          description: >
            401 UNAUTHORIZED

            If the request contains no access token even though one is required,
            or if the request contains an authorization token that is invalid
            (e.g. expired or revoked), the API producer should respond with this
            response. The details of the error shall be returned in the
            WWW-Authenticate HTTP header, as defined in IETF RFC 6750 and IETF
            RFC 7235. The ProblemDetails structure may be provided.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '403':
          description: >
            403 FORBIDDEN

            If the API consumer is not allowed to perform a particular request
            to a particular resource, the API producer shall respond with this
            response code. The "ProblemDetails" structure shall be provided. It
            should include in the "detail" attribute information about the
            source of the problem, and may indicate how to solve it.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '404':
          description: >
            404 NOT FOUND

            If the API producer did not find a current representation for the
            resource addressed by the URI passed in the request or is not
            willing to disclose that one exists, it shall respond with this
            response code. The "ProblemDetails" structure may be provided,
            including in the "detail" attribute information about the source of
            the problem, e.g. a wrong resource URI variable.

            This response code is not appropriate in case the resource addressed
            by the URI is a container resource which is designed to contain
            child resources, but does not contain any child resource at the time
            the request is received. For a GET request to an existing empty
            container resource, a typical response contains a 200 OK response
            code and a payload body with an empty array.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '405':
          description: >
            405 METHOD NOT ALLOWED

            If a particular HTTP method is not supported for a particular
            resource, the API producer shall respond with this response code.
            The "ProblemDetails" structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '406':
          description: >
            406 NOT ACCEPTABLE

            If the "Accept" HTTP header does not contain at least one name of a
            content type that is acceptable to the API producer, the API
            producer shall respond with this response code. The "ProblemDetails"
            structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '500':
          description: >
            500 INTERNAL SERVER ERROR

            If there is an application error not related to the client's input
            that cannot be easily mapped to any other HTTP response code ("catch
            all error"), the API producer shall respond with this response code.
            The "ProblemDetails" structure shall be provided, and shall include
            in the "detail" attribute more information about the source of the
            problem.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '503':
          description: >
            503 SERVICE UNAVAILABLE

            If the API producer encounters an internal overload situation of
            itself or of a system it relies on, it should respond with this
            response code, following the provisions in IETF RFC 7231 for the use
            of the "Retry-After" HTTP header and for the alternative to refuse
            the connection. The "ProblemDetails" structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '504':
          description: >
            504 GATEWAY TIMEOUT

            If the API producer encounters a timeout while waiting for a
            response from an upstream server (i.e. a server that the API
            producer communicates with when fulfilling a request), it should
            respond with this response code.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
  '/subscriptions/{subscriptionId}':
    description: >-
      This resource represents an individual subscription for notifications
      about log management related events. The API consumer can use this
      resource to read and to terminate a subscription to notifications related
      o NFV-MANO log management.
    parameters:
      - name: subscriptionId
        in: path
        description: Identifier of the subscription
        required: true
        schema:
          description: |
            An identifier with the intention of being globally unique.
          type: string
    get:
      description: >-
        The API consumer can use this method for reading an individual
        subscription about log management notifications subscribed by the API
        consumer. This method shall follow the provisions specified in the
        tables 8.5.8.3.2-1 and 8.5.8.3.2-2 for URI query parameters, request and
        response data structures, and response codes.
      parameters:
        - name: Version
          description: |
            Version of the API requested to use when responding to this request.
          in: header
          required: true
          schema:
            type: string
        - name: Accept
          description: >
            Content-Types that are acceptable for the response. Reference: IETF
            RFC 7231.
          in: header
          required: true
          schema:
            type: string
        - name: Authorization
          description: |
            The authorization token for the request. Reference: IETF RFC 7235.
          in: header
          required: false
          schema:
            type: string
      responses:
        '200':
          description: >-
            Shall be returned when the subscription has been read successfully.
            The response body shall contain a representation of the "Individual
            subscription" resource, as defined in clause 8.6.2.3.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
          content:
            application/json:
              schema:
                description: >-
                  This type represents a subscription. It shall comply with the
                  provisions defined in table 8.6.2.3-1.
                type: object
                required:
                  - id
                  - callbackUri
                  - _links
                properties:
                  id:
                    description: |
                      An identifier with the intention of being globally unique.
                    type: string
                  filter:
                    description: >-
                      This type represents a filter that can be used to
                      subscribe for notifications related to log management
                      events. It shall comply with the provisions defined in
                      table 8.6.3.7-1. At a particular nesting level in the
                      filter structure, the following applies: All attributes
                      shall match in order for the filter to match (logical
                      "and" between different filter attributes). If an
                      attribute is an array, the attribute shall match if at
                      least one of the values in the array matches (logical "or"
                      between the values of one filter attribute).
                    type: object
                    properties:
                      objectInstanceFilter:
                        description: >-
                          This type represents subscription filter criteria to
                          match NFV-MANO functional entities and their
                          associated managed objects. It shall comply with the
                          provisions defined in Table 4.3.2.2-1.
                        type: object
                        anyOf:
                          - oneOf:
                              - required:
                                  - manoServiceIds
                              - required:
                                  - manoServiceNames
                          - oneOf:
                              - required:
                                  - manoServiceInterfaceIds
                              - required:
                                  - manoServiceInterfaceNames
                          - oneOf:
                              - required:
                                  - consumedManoInterfaceIds
                              - required:
                                  - consumedManoInterfaceNames
                        properties:
                          manoEntityId:
                            description: >
                              An identifier with the intention of being globally
                              unique.
                            type: string
                          manoServiceIds:
                            description: >-
                              If present, match NFV-MANO services with an
                              instance identifier listed in this attribute.
                            type: array
                            items:
                              description: >
                                An identifier that is unique for the respective
                                type within a NFV-MANO functional entity, but
                                that need not be globally unique.
                                Representation: string of variable length..
                              type: string
                          manoServiceNames:
                            description: >-
                              If present, match NFV-MANO services with an
                              NFV-MANO service name listed in this attribute.
                            type: array
                            items:
                              type: string
                          manoServiceInterfaceIds:
                            description: >-
                              If present, match NFV-MANO functional entity
                              produced interfaces with an instance identifier
                              listed in this attribute.
                            type: array
                            items:
                              description: >
                                An identifier that is unique for the respective
                                type within a NFV-MANO functional entity, but
                                that need not be globally unique.
                                Representation: string of variable length..
                              type: string
                          manoServiceInterfaceNames:
                            description: >-
                              If present, match NFV-MANO functional entity
                              produced interfaces with an instance Name listed
                              in this attribute.
                            type: array
                            items:
                              type: string
                          consumedManoInterfaceIds:
                            description: >-
                              If present, match NFV-MANO functional entity
                              consumed interfaces with an instance identifier
                              listed in this attribute.
                            type: array
                            items:
                              description: >
                                An identifier with the intention of being
                                globally unique.
                              type: string
                          consumedManoInterfaceNames:
                            description: >-
                              If present, match NFV-MANO functional entity
                              consumed interfaces with an instance Name listed
                              in this attribute.
                            type: array
                            items:
                              type: string
                      notificationTypes:
                        description: >-
                          Match particular notification types. Permitted values:
                          - LogReportAvailableNotification
                        type: string
                        enum:
                          - LogReportAvailableNotification
                  callbackUri:
                    description: |
                      String formatted according to IETF RFC 3986.
                    type: string
                  _links:
                    description: Links to resources related to this resource.
                    type: object
                    required:
                      - self
                    properties:
                      self:
                        description: >
                          This type represents a link to a resource using an
                          absolute URI.
                        type: object
                        required:
                          - href
                        properties:
                          href:
                            description: |
                              String formatted according to IETF RFC 3986.
                            type: string
        '400':
          description: >
            400 BAD REQUEST

            400 code can be returned in the following specified cases, the
            specific cause has to be proper specified in the "ProblemDetails"
            structure to be returned.

            If the request is malformed or syntactically incorrect (e.g. if the
            request URI contains incorrect query parameters or the payload body
            contains a syntactically incorrect data structure), the API producer
            shall respond with this response code. The "ProblemDetails"
            structure shall be provided, and should include in the "detail"
            attribute more information about the source of the problem.

            If the response to a GET request which queries a container resource
            would be so big that the performance of the API producer is
            adversely affected, and the API producer does not support paging for
            the affected resource, it shall respond with this response code. The
            "ProblemDetails" structure shall be provided, and should include in
            the "detail" attribute more information about the source of the
            problem.

            If there is an application error related to the client's input that
            cannot be easily mapped to any other HTTP response code ("catch all
            error"), the API producer shall respond with this response code. The
            "ProblemDetails" structure shall be provided, and shall include in
            the "detail" attribute more information about the source of the
            problem.

            If the request contains a malformed access token, the API producer
            should respond with this response. The details of the error shall be
            returned in the WWW Authenticate HTTP header, as defined in IETF RFC
            6750 and IETF RFC 7235. The ProblemDetails structure may be
            provided.

            The use of this HTTP error response code described above is
            applicable to the use of the OAuth 2.0 for the authorization of API
            requests and notifications, as defined in clauses 4.5.3.3 and
            4.5.3.4.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '401':
          description: >
            401 UNAUTHORIZED

            If the request contains no access token even though one is required,
            or if the request contains an authorization token that is invalid
            (e.g. expired or revoked), the API producer should respond with this
            response. The details of the error shall be returned in the
            WWW-Authenticate HTTP header, as defined in IETF RFC 6750 and IETF
            RFC 7235. The ProblemDetails structure may be provided.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '403':
          description: >
            403 FORBIDDEN

            If the API consumer is not allowed to perform a particular request
            to a particular resource, the API producer shall respond with this
            response code. The "ProblemDetails" structure shall be provided. It
            should include in the "detail" attribute information about the
            source of the problem, and may indicate how to solve it.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '404':
          description: >
            404 NOT FOUND

            If the API producer did not find a current representation for the
            resource addressed by the URI passed in the request or is not
            willing to disclose that one exists, it shall respond with this
            response code. The "ProblemDetails" structure may be provided,
            including in the "detail" attribute information about the source of
            the problem, e.g. a wrong resource URI variable.

            This response code is not appropriate in case the resource addressed
            by the URI is a container resource which is designed to contain
            child resources, but does not contain any child resource at the time
            the request is received. For a GET request to an existing empty
            container resource, a typical response contains a 200 OK response
            code and a payload body with an empty array.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '405':
          description: >
            405 METHOD NOT ALLOWED

            If a particular HTTP method is not supported for a particular
            resource, the API producer shall respond with this response code.
            The "ProblemDetails" structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '406':
          description: >
            406 NOT ACCEPTABLE

            If the "Accept" HTTP header does not contain at least one name of a
            content type that is acceptable to the API producer, the API
            producer shall respond with this response code. The "ProblemDetails"
            structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '500':
          description: >
            500 INTERNAL SERVER ERROR

            If there is an application error not related to the client's input
            that cannot be easily mapped to any other HTTP response code ("catch
            all error"), the API producer shall respond with this response code.
            The "ProblemDetails" structure shall be provided, and shall include
            in the "detail" attribute more information about the source of the
            problem.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '503':
          description: >
            503 SERVICE UNAVAILABLE

            If the API producer encounters an internal overload situation of
            itself or of a system it relies on, it should respond with this
            response code, following the provisions in IETF RFC 7231 for the use
            of the "Retry-After" HTTP header and for the alternative to refuse
            the connection. The "ProblemDetails" structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '504':
          description: >
            504 GATEWAY TIMEOUT

            If the API producer encounters a timeout while waiting for a
            response from an upstream server (i.e. a server that the API
            producer communicates with when fulfilling a request), it should
            respond with this response code.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
    delete:
      description: "This method terminates an individual subscription. This method shall follow the provisions specified in the tables 8.5.8.3.5-1 and 8.5.8.3.5-2 for URI query parameters, request and response data structures, and response codes. As the result of successfully executing this method, the \"Individual subscription\" resource shall not exist any longer. This means that no notifications for that subscription shall be sent to the formerly-subscribed API consumer. NOTE:\tDue to race conditions, some notifications might still be received by the formerly-subscribed API consumer for a certain time period after the deletion."
      parameters:
        - name: Version
          description: |
            Version of the API requested to use when responding to this request.
          in: header
          required: true
          schema:
            type: string
        - name: Authorization
          description: |
            The authorization token for the request. Reference: IETF RFC 7235.
          in: header
          required: false
          schema:
            type: string
      responses:
        '204':
          description: >-
            Shall be returned when the "Individual subscription" resource has
            been deleted successfully. The response body shall be empty.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
        '400':
          description: >
            400 BAD REQUEST

            400 code can be returned in the following specified cases, the
            specific cause has to be proper specified in the "ProblemDetails"
            structure to be returned.

            If the request is malformed or syntactically incorrect (e.g. if the
            request URI contains incorrect query parameters or the payload body
            contains a syntactically incorrect data structure), the API producer
            shall respond with this response code. The "ProblemDetails"
            structure shall be provided, and should include in the "detail"
            attribute more information about the source of the problem.

            If the response to a GET request which queries a container resource
            would be so big that the performance of the API producer is
            adversely affected, and the API producer does not support paging for
            the affected resource, it shall respond with this response code. The
            "ProblemDetails" structure shall be provided, and should include in
            the "detail" attribute more information about the source of the
            problem.

            If there is an application error related to the client's input that
            cannot be easily mapped to any other HTTP response code ("catch all
            error"), the API producer shall respond with this response code. The
            "ProblemDetails" structure shall be provided, and shall include in
            the "detail" attribute more information about the source of the
            problem.

            If the request contains a malformed access token, the API producer
            should respond with this response. The details of the error shall be
            returned in the WWW Authenticate HTTP header, as defined in IETF RFC
            6750 and IETF RFC 7235. The ProblemDetails structure may be
            provided.

            The use of this HTTP error response code described above is
            applicable to the use of the OAuth 2.0 for the authorization of API
            requests and notifications, as defined in clauses 4.5.3.3 and
            4.5.3.4.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '401':
          description: >
            401 UNAUTHORIZED

            If the request contains no access token even though one is required,
            or if the request contains an authorization token that is invalid
            (e.g. expired or revoked), the API producer should respond with this
            response. The details of the error shall be returned in the
            WWW-Authenticate HTTP header, as defined in IETF RFC 6750 and IETF
            RFC 7235. The ProblemDetails structure may be provided.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '403':
          description: >
            403 FORBIDDEN

            If the API consumer is not allowed to perform a particular request
            to a particular resource, the API producer shall respond with this
            response code. The "ProblemDetails" structure shall be provided. It
            should include in the "detail" attribute information about the
            source of the problem, and may indicate how to solve it.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '404':
          description: >
            404 NOT FOUND

            If the API producer did not find a current representation for the
            resource addressed by the URI passed in the request or is not
            willing to disclose that one exists, it shall respond with this
            response code. The "ProblemDetails" structure may be provided,
            including in the "detail" attribute information about the source of
            the problem, e.g. a wrong resource URI variable.

            This response code is not appropriate in case the resource addressed
            by the URI is a container resource which is designed to contain
            child resources, but does not contain any child resource at the time
            the request is received. For a GET request to an existing empty
            container resource, a typical response contains a 200 OK response
            code and a payload body with an empty array.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '405':
          description: >
            405 METHOD NOT ALLOWED

            If a particular HTTP method is not supported for a particular
            resource, the API producer shall respond with this response code.
            The "ProblemDetails" structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '406':
          description: >
            406 NOT ACCEPTABLE

            If the "Accept" HTTP header does not contain at least one name of a
            content type that is acceptable to the API producer, the API
            producer shall respond with this response code. The "ProblemDetails"
            structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '422':
          description: >
            422 UNPROCESSABLE ENTITY

            If the payload body of a request contains syntactically correct data
            (e.g. well-formed JSON) but the data cannot be processed (e.g.
            because it fails validation against a schema), the API producer
            shall respond with this response code. The "ProblemDetails"
            structure shall be provided, and should include in the "detail"
            attribute more information about the source of the problem.

            This error response code is only applicable for methods that have a
            request body.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '500':
          description: >
            500 INTERNAL SERVER ERROR

            If there is an application error not related to the client's input
            that cannot be easily mapped to any other HTTP response code ("catch
            all error"), the API producer shall respond with this response code.
            The "ProblemDetails" structure shall be provided, and shall include
            in the "detail" attribute more information about the source of the
            problem.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '503':
          description: >
            503 SERVICE UNAVAILABLE

            If the API producer encounters an internal overload situation of
            itself or of a system it relies on, it should respond with this
            response code, following the provisions in IETF RFC 7231 for the use
            of the "Retry-After" HTTP header and for the alternative to refuse
            the connection. The "ProblemDetails" structure may be omitted.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
        '504':
          description: >
            504 GATEWAY TIMEOUT

            If the API producer encounters a timeout while waiting for a
            response from an upstream server (i.e. a server that the API
            producer communicates with when fulfilling a request), it should
            respond with this response code.
          headers:
            Content-Type:
              description: The MIME type of the body of the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
            WWW-Authenticate:
              description: >
                Challenge if the corresponding HTTP request has not provided
                authorization, or error details if the corresponding HTTP
                request has provided an invalid authorization token.
              schema:
                type: string
                maximum: 1
                minimum: 0
            Version:
              description: |
                Version of the API used in the response.
              schema:
                type: string
                maximum: 1
                minimum: 1
          content:
            application/json:
              schema:
                description: >
                  The definition of the general "ProblemDetails" data structure
                  from IETF RFC 7807 [19] is reproduced inthis structure.
                  Compared to the general framework defined in IETF RFC 7807
                  [19], the "status" and "detail" attributes are mandated to be
                  included by the present document, to ensure that the response
                  contains additional textual information about an error. IETF
                  RFC 7807 [19] foresees extensibility of the "ProblemDetails"
                  type. It is possible that particular APIs in the present
                  document, or particular implementations, define extensions to
                  define additional attributes that provide more information
                  about the error. The description column only provides some
                  explanation of the meaning to Facilitate understanding of the
                  design. For a full description, see IETF RFC 7807 [19].
                type: object
                required:
                  - status
                  - detail
                properties:
                  type:
                    description: >
                      A URI reference according to IETF RFC 3986 [5] that
                      identifies the problem type. It is encouraged that the URI
                      provides human-readable documentation for the problem
                      (e.g. using HTML) when dereferenced. When this member is
                      not present, its value is assumed to be "about:blank".
                    type: string
                    format: URI
                  title:
                    description: >
                      A short, human-readable summary of the problem type. It
                      should not change from occurrence to occurrence of the
                      problem, except for purposes of localization. If type is
                      given and other than "about:blank", this attribute shall
                      also be provided. A short, human-readable summary of the
                      problem type.  It SHOULD NOT change from occurrence to
                      occurrence of the problem, except for purposes of
                      localization (e.g., using proactive content negotiation;
                      see [RFC7231], Section 3.4).
                    type: string
                  status:
                    description: >
                      The HTTP status code for this occurrence of the problem.
                      The HTTP status code ([RFC7231], Section 6) generated by
                      the origin server for this occurrence of the problem.
                    type: integer
                  detail:
                    description: >
                      A human-readable explanation specific to this occurrence
                      of the problem.
                    type: string
                  instance:
                    description: >
                      A URI reference that identifies the specific occurrence of
                      the problem. It may yield further information if
                      dereferenced.
                    type: string
                    format: URI
components:
  parameters:
    logJobId:
      name: logJobId
      in: path
      description: Identifier of the logging job.
      required: true
      schema:
        description: |
          An identifier with the intention of being globally unique.
        type: string
    logReportId:
      name: logReportId
      in: path
      description: Identifier of the report.
      required: true
      schema:
        description: |
          An identifier with the intention of being globally unique.
        type: string
    subscriptionId:
      name: subscriptionId
      in: path
      description: Identifier of the subscription
      required: true
      schema:
        description: |
          An identifier with the intention of being globally unique.
        type: string
  requestBodies:
    LogmSubscriptionRequest:
      description: Details of the subscription to be created
      content:
        application/json:
          schema:
            description: >-
              Information on application context created by the MEC system type:
              object
            required:
              - callbackUri
            type: object
            properties:
              filter:
                description: >-
                  This type represents a filter that can be used to subscribe
                  for notifications related to log management events. It shall
                  comply with the provisions defined in table 8.6.3.7-1. At a
                  particular nesting level in the filter structure, the
                  following applies: All attributes shall match in order for the
                  filter to match (logical "and" between different filter
                  attributes). If an attribute is an array, the attribute shall
                  match if at least one of the values in the array matches
                  (logical "or" between the values of one filter attribute).
                type: object
                properties:
                  objectInstanceFilter:
                    description: >-
                      This type represents subscription filter criteria to match
                      NFV-MANO functional entities and their associated managed
                      objects. It shall comply with the provisions defined in
                      Table 4.3.2.2-1.
                    type: object
                    anyOf:
                      - oneOf:
                          - required:
                              - manoServiceIds
                          - required:
                              - manoServiceNames
                      - oneOf:
                          - required:
                              - manoServiceInterfaceIds
                          - required:
                              - manoServiceInterfaceNames
                      - oneOf:
                          - required:
                              - consumedManoInterfaceIds
                          - required:
                              - consumedManoInterfaceNames
                    properties:
                      manoEntityId:
                        description: >
                          An identifier with the intention of being globally
                          unique.
                        type: string
                      manoServiceIds:
                        description: >-
                          If present, match NFV-MANO services with an instance
                          identifier listed in this attribute.
                        type: array
                        items:
                          description: >
                            An identifier that is unique for the respective type
                            within a NFV-MANO functional entity, but that need
                            not be globally unique. Representation: string of
                            variable length..
                          type: string
                      manoServiceNames:
                        description: >-
                          If present, match NFV-MANO services with an NFV-MANO
                          service name listed in this attribute.
                        type: array
                        items:
                          type: string
                      manoServiceInterfaceIds:
                        description: >-
                          If present, match NFV-MANO functional entity produced
                          interfaces with an instance identifier listed in this
                          attribute.
                        type: array
                        items:
                          description: >
                            An identifier that is unique for the respective type
                            within a NFV-MANO functional entity, but that need
                            not be globally unique. Representation: string of
                            variable length..
                          type: string
                      manoServiceInterfaceNames:
                        description: >-
                          If present, match NFV-MANO functional entity produced
                          interfaces with an instance Name listed in this
                          attribute.
                        type: array
                        items:
                          type: string
                      consumedManoInterfaceIds:
                        description: >-
                          If present, match NFV-MANO functional entity consumed
                          interfaces with an instance identifier listed in this
                          attribute.
                        type: array
                        items:
                          description: >
                            An identifier with the intention of being globally
                            unique.
                          type: string
                      consumedManoInterfaceNames:
                        description: >-
                          If present, match NFV-MANO functional entity consumed
                          interfaces with an instance Name listed in this
                          attribute.
                        type: array
                        items:
                          type: string
                  notificationTypes:
                    description: >-
                      Match particular notification types. Permitted values: -
                      LogReportAvailableNotification
                    type: string
                    enum:
                      - LogReportAvailableNotification
              callbackUri:
                description: |
                  String formatted according to IETF RFC 3986.
                type: string
              authentication:
                type: object
                required:
                  - authType
                properties:
                  authType:
                    description: >
                      Defines the types of Authentication / Authorization which
                      the API consumer is willing to accept when receiving a
                      notification. Permitted values: * BASIC: In every HTTP
                      request to the notification endpoint, use
                        HTTP Basic authentication with the client credentials.
                      * OAUTH2_CLIENT_CREDENTIALS: In every HTTP request to the
                        notification endpoint, use an OAuth 2.0 Bearer token, obtained
                        using the client credentials grant type.
                      * TLS_CERT: Every HTTP request to the notification
                      endpoint is sent
                        over a mutually authenticated TLS session, i.e. not only the
                        server is authenticated, but also the client is authenticated
                        during the TLS tunnel setup.
                    type: array
                    items:
                      type: string
                      enum:
                        - BASIC
                        - OAUTH2_CLIENT_CREDENTIALS
                        - TLS_CERT
                  paramsBasic:
                    description: >
                      Parameters for authentication/authorization using BASIC.
                      Shall be present if authType is "BASIC" and the contained
                      information has not been provisioned out of band. Shall be
                      absent otherwise.
                    type: object
                    properties:
                      userName:
                        description: >
                          Username to be used in HTTP Basic authentication.
                          Shall be present if it has not been provisioned out of
                          band.
                        type: string
                      password:
                        description: >
                          Password to be used in HTTP Basic authentication.
                          Shall be present if it has not been provisioned out of
                          band.
                        type: string
                  paramsOauth2ClientCredentials:
                    description: >
                      Parameters for authentication/authorization using
                      OAUTH2_CLIENT_CREDENTIALS. Shall be present if authType is
                      "OAUTH2_CLIENT_CREDENTIALS" and the contained information
                      has not been provisioned out of band. Shall be absent
                      otherwise.
                    type: object
                    properties:
                      clientId:
                        description: >
                          Client identifier to be used in the access token
                          request of the OAuth 2.0 client credentials grant
                          type. Shall be present if it has not been provisioned
                          out of band. The clientId and clientPassword passed in
                          a subscription shall not be the same as the clientId
                          and clientPassword that are used to obtain
                          authorization for API requests. Client credentials may
                          differ between subscriptions. The value of
                          clientPassword should be generated by a random
                          process.
                        type: string
                      clientPassword:
                        description: >
                          Client password to be used in the access token request
                          of the OAuth 2.0 client credentials grant type. Shall
                          be present if it has not been provisioned out of band.
                          The clientId and clientPassword passed in a
                          subscription shall not be the same as the clientId and
                          clientPassword that are used to obtain authorization
                          for API requests. Client credentials may differ
                          between subscriptions. The value of clientPassword
                          should be generated by a random process.
                        type: string
                      tokenEndpoint:
                        description: |
                          String formatted according to IETF RFC 3986.
                        type: string
    CreateLoggingJobRequest:
      description: >-
        This type represents a request to create a logging job. It shall comply
        with the provisions defined in table 8.6.2.5-1.
      content:
        application/json:
          schema:
            description: Information on application context created by the MEC system
            type: object
            required:
              - objectInstanceIds
              - jobCriteria
              - jobConfig
            properties:
              objectInstanceIds:
                description: >-
                  Identifiers of the object instance for which logging
                  information is requested to be collected. This attribute shall
                  contain the identifier of the instance of the object to be
                  logged according to their type. If more than one identifier is
                  provided, values shall all refer to object instances of the
                  same type, for which the same criteria is then applicable.
                type: array
                minItems: 1
                items:
                  description: >
                    This type represents the identifier to reference a managed
                    object of a  particular type. 
                  type: object
                  properties:
                    type:
                      description: >
                        Indicates the type of managed object. Permitted values:
                          - MANO_ENTITY
                          - MANO_SERVICE
                          - MANO_SERVICE_IF
                          - CONSUMED_MANO_IF
                          - MANO_ENTITY_COMPONENT

                        The "MANO_ENTITY COMPONENT" is only applicable if
                        attribute "manoEntityComponents" in "ManoEntity" is
                        supported by the API producer.
                      type: string
                      enum:
                        - MANO_ENTITY
                        - MANO_SERVICE
                        - MANO_SERVICE_IF
                        - CONSUMED_MANO_IF
                        - MANO_ENTITY_COMPONENT
                    objectId:
                      description: >
                        An identifier with the intention of being globally
                        unique.
                      type: string
                    subObjectId:
                      description: >
                        An identifier that is unique for the respective type
                        within a NFV-MANO functional entity, but that need not
                        be globally unique. Representation: string of variable
                        length..
                      type: string
                  required:
                    - type
                    - objectId
              jobCriteria:
                description: >-
                  This type represents collection criteria for logging jobs. It
                  shall comply with the provisions defined in table 8.6.3.2-1.
                type: object
                required:
                  - loggingType
                properties:
                  loggingType:
                    description: >-
                      Type of logging. This defines the types of logged
                      information to collect.

                      Permitted values: - MESSAGES: logged NFV-MANO service
                      interface messages. - SERVICES: logged messages about
                      processes pertaining to NFV-MANO services. - SYSTEM:
                      logged messages about the NFV-MANO functional entity’s
                      system enabled by the provider.
                    type: string
                    enum:
                      - MESSAGES
                      - SERVICES
                      - SYSTEM
                  messagesLogDetail:
                    description: >-
                      This type represents criteria for logging jobs to collect
                      logged messages on NFV-MANO service interfaces. It shall
                      comply with the provisions defined in table 8.6.3.3-1.
                    type: object
                    required:
                      - direction
                    properties:
                      direction:
                        description: >-
                          The direction of the interface messages to match.

                          Permitted values: - IN: input messages into the
                          interface. - OUT: output messages from the interface.
                          - ALL: both input and output messages into/from the
                          interface.
                        type: string
                        enum:
                          - IN
                          - OUT
                          - ALL
                      matchingPatterns:
                        description: >-
                          Patterns to be matched in the interface message. If
                          provided, only messages that match all the values
                          provided in the sub-attributes shall be logged. An API
                          consumer can provide more than one "matchingPattern"
                          if combinations of patterns are to be considered to
                          match diverse sets of interface messages.
                        type: array
                        items:
                          type: object
                          anyOf:
                            - required:
                                - srcIpAddress
                            - required:
                                - dstIpAddress
                            - required:
                                - requestMethod
                            - required:
                                - requestUriPattern
                            - required:
                                - responseCodes
                          properties:
                            srcIpAddress:
                              description: >
                                An IPV4 or IPV6 address. Representation: In case
                                of an IPV4 address, string that consists of four
                                decimal integers separated by dots, each integer
                                ranging from 0 to 255. In case of an IPV6
                                address, string that consists of groups of zero
                                to four hexadecimal digits, separated by colons.
                              type: string
                              format: IP
                            requestMethod:
                              description: >-
                                HTTP request method to be matched. To match, the
                                HTTP request method of the message shall be the
                                same as the value of this attribute. Valid
                                values are specified in IETF RFC 7231. The API
                                producer shall support this attribute.
                              type: string
                            requestUriPattern:
                              description: >-
                                Substring to be matched in the request URI. To
                                match, the request URI shall include the value
                                of
                                 this attribute as a substring. This is typically used to match messages which associate to RESTful
                                 resources, or to a specific API (e.g., by using the "apiName" of the API). The API producer shall
                                 support this attribute.
                              type: string
                            dstIpAddress:
                              description: >
                                An IPV4 or IPV6 address. Representation: In case
                                of an IPV4 address, string that consists of four
                                decimal integers separated by dots, each integer
                                ranging from 0 to 255. In case of an IPV6
                                address, string that consists of groups of zero
                                to four hexadecimal digits, separated by colons.
                              type: string
                              format: IP
                            responseCodes:
                              description: >-
                                HTTP response codes or patterns to match. A list
                                of all valid HTTP response codes and their
                                specification documents can be obtained from the
                                HTTP status code registry. In addition, if
                                supported, the following patterns may be used
                                (case-insensitive): - "1XX": for matching any
                                kind of informational response. - "2XX": for
                                matching any kind of success response. - "3XX":
                                for matching any kind redirection response. -
                                "4XX": for matching any kind of client error
                                response. - "5XX": for matching any kind of
                                server error response.

                                The API producer shall support this attribute
                              type: array
                              items:
                                type: string
                            headerField:
                              description: >-
                                Name of the header field to be matched. The
                                header field name shall be one of the supported
                                fields in a request message as defined in clause
                                4.2.2 of ETSI GS NFV-SOL 013 or in a response
                                message as defined in clause 4.2.3 of ETSI GS
                                NFV-SOL 013, in accordance with the "direction"
                                criteria input. The API producer may support
                                this attribute.
                              type: string
                            headerValue:
                              description: >-
                                Value in the header to be matched. To match, the
                                value in the header field indicated by
                                "headerField" shall be the same as in this
                                attribute. Shall be provided if a "headerField"
                                is provided. The API producer may support this
                                attribute.
                              type: string
                            bodyValues:
                              description: >-
                                A list of strings to be matched in the body part
                                of the interface message (e.g., the body of an
                                HTTP message). If provided, only messages with
                                text in the body part containing all the values
                                from the list shall match the filter. In
                                addition to a matching filter for the body of
                                the message, a corresponding "headerField"
                                filter shall also be provided, with
                                "headerField" set to "Content-Type", to restrict
                                matching to appropriate textual payloads such as
                                "application/json" or "text/plain". The API
                                producer may support this attribute
                              type: string
                  servicesLogDetail:
                    description: >-
                      This type represents criteria for logging jobs to collect
                      logged messages about processes pertaining to NFV-MANO
                      services. It shall comply with the provisions defined in
                      table 8.6.3.4-1.
                    type: object
                    properties:
                      logGarbageCollection:
                        description: >-
                          Indicates to collect logged information about garbage
                          collection processes associated to NFV-MANO services.
                        type: boolean
                  systemLogDetail:
                    description: >-
                      This type represents criteria for logging jobs to collect
                      logged system events of the NFV-MANO functional entity. It
                      shall comply with the provisions defined in table
                      8.6.3.5-1.
                    type: object
                    required:
                      - systemLogs
                      - severityLevel
                    properties:
                      systemLogs:
                        description: >
                          This type represents a list of key-value pairs. The
                          order of the pairs in the list is not significant. In
                          JSON, a set of keyvalue pairs is represented as an
                          object. It shall comply with the provisions defined in
                          clause 4 of IETF RFC 8259. In the following example, a
                          list of key-value pairs with four keys ("aString",
                          "aNumber", "anArray" and "anObject") is provided to
                          illustrate that the values associated with different
                          keys can be of different type.
                        type: object
                      severityLevelScheme:
                        description: >-
                          Identifies a severity level scheme. The default value
                          is "rfc5424", which represents the set of values
                          specified in the clause 6.2.1, table 2 of IETF RFC
                          5424. Other values may be used to signal different
                          schemes.
                        type: string
                      severityLevel:
                        description: >-
                          The severity level, which determines the severity of
                          the system messages to collect. The NFV-MANO
                          functional entity shall collect system log messages,
                          as indicated by the "systemLogs" attribute, with
                          severity levels lower (i.e., more severe) or equal to
                          the value provided by this present attribute.
                        type: number
              jobConfig:
                description: >-
                  This type represents configuration data for a logging job. It
                  shall comply with the provisions defined in table 8.6.3.6-1.
                  NOTE: The present document version does not specify the
                  support for "log compilation and reporting based on events" as
                  specified in clause 6.6.2.2 of ETSI GS NFV-IFA 031.
                type: object
                required:
                  - reportingCondition
                  - securityConf
                properties:
                  startTime:
                    description: >
                      Date-time stamp. Representation: String formatted
                      according to IETF RFC 3339.
                    type: string
                    format: date-time
                  endTime:
                    description: >
                      Date-time stamp. Representation: String formatted
                      according to IETF RFC 3339.
                    type: string
                    format: date-time
                  reportingCondition:
                    description: >-
                      Specifies the condition under which the producer will
                      report to the consumer about the compiled log data.
                    required:
                      - reportingType
                    properties:
                      reportingType:
                        description: >-
                          Specifies the type of reporting condition. Permitted
                          values: - REPORTING_ON_COMPILATION: the producer shall
                          notify the consumer once the compilation of the
                                          collected logging data into a file is completed and a new log report is available.
                          - NO_REPORTING: no reporting is requested (the
                          consumer can query the logging jobs to know about the
                                          availability of new log reports).
                        type: string
                        enum:
                          - REPORTING_ON_COMPILATION
                          - NO_REPORTING
                      minimumReportingPeriod:
                        description: >-
                          Specifies the minimum periodicity at which the
                          producer will report to the consumer about the
                          collected log information, in seconds.
                        type: integer
                        format: int32
                  compileBySizeValue:
                    description: >-
                      An indicative size threshold for compiling the collected
                      log data, in bytes. It is used when the compilation is
                      based on the size of the collected log data. If not
                      present, a default value as specified with the
                      "defaultLogCompileBySizeValue" configuration in the
                      "ManoEntityConfigurableParams" shall be used
                    type: integer
                    format: int32
                  compileByTimerValue:
                    description: >-
                      The periodicity threshold for compiling the filtered log,
                      in seconds. It is used when the compilation is based on a
                      timer (e.g., every 24 hours). If not present, a default
                      value as specified with the
                      "defaultLogCompileByTimerValue" configuration in the
                      "ManoEntityConfigurableParams" shall be used
                    type: integer
                    format: int32
                  securityConf:
                    description: >-
                      Configuration about the security aspects of the logging
                      job.
                    type: object
                    properties:
                      logFileEncryption:
                        description: >-
                          Information about the encryption of the compiled log
                          files. Shall be present if the log file is requested
                          to be encrypted.
                        required:
                          - encryptionCertificate
                          - cipherAlgorithm
                        type: object
                        properties:
                          encryptionCertificate:
                            description: >-
                              X.509 certificate with the public key to use for
                              the encryption of the compiled log file.
                            type: string
                          cipherAlgorithm:
                            description: >-
                              Cryptographic algorithm to be used for the
                              encryption of the compiled log file. More than one
                              algorithm can be provided from higher (lower array
                              index) to lower (higher array index) precedence.
                              Valid values are: "AES-CBC-128", "AES-GCM-128",
                              "AES-CBC-256", and "AES-GCM-256", as specified in
                              clause 6.5 of ETSI GS NFV-SEC 012
                            type: array
                            items:
                              type: string
                              minItems: 1
                          encryptAndSignOrder:
                            description: >-
                              Indication about the order in signing and
                              encrypting the compiled log file. Valid values
                              are: "encryptFirst", to apply the order "first
                              encrypt, then sign", and "signFirst" for the order
                              "first sign, then encrypt". Default value is
                              "encryptFirst".
                            type: string
                      logTransferSecurity:
                        description: >-
                          Information about the security measures for
                          retrieving/accessing the compiled log files.
                        type: object
                        properties:
                          publicKey:
                            description: >-
                              The public key of the API consumer used for the
                              client authentication with the file server. Shall
                              be provided if required by the type of transfer
                              protocol. May be omitted if the key has been
                              provided to the API producer by other means, or if
                              it has already been provided in some previous
                              CreateLoggingJobRequest issued by the same API
                              consumer, whose public key has not changed.
                            type: string
      required: true
    CompileLogRequest:
      description: Log compilation request.
      content:
        application/json:
          schema:
            description: >
              This type represents a request to compile the logged data
              associated to an object instance. It shall comply with the
              provisions defined in table 8.6.2.8-1.
            type: object
            properties:
              objectInstanceId:
                description: >
                  This type represents the identifier to reference a managed
                  object of a  particular type. 
                type: object
                properties:
                  type:
                    description: >
                      Indicates the type of managed object. Permitted values:
                        - MANO_ENTITY
                        - MANO_SERVICE
                        - MANO_SERVICE_IF
                        - CONSUMED_MANO_IF
                        - MANO_ENTITY_COMPONENT

                      The "MANO_ENTITY COMPONENT" is only applicable if
                      attribute "manoEntityComponents" in "ManoEntity" is
                      supported by the API producer.
                    type: string
                    enum:
                      - MANO_ENTITY
                      - MANO_SERVICE
                      - MANO_SERVICE_IF
                      - CONSUMED_MANO_IF
                      - MANO_ENTITY_COMPONENT
                  objectId:
                    description: |
                      An identifier with the intention of being globally unique.
                    type: string
                  subObjectId:
                    description: >
                      An identifier that is unique for the respective type
                      within a NFV-MANO functional entity, but that need not be
                      globally unique. Representation: string of variable
                      length..
                    type: string
                required:
                  - type
                  - objectId
      required: true
    LogReportAvailableNotification:
      description: Notification about the availability of a log report.
      content:
        application/json:
          schema:
            description: >-
              This notification informs the receiver that the log report of the
              NFV-MANO functional entity is available. It shall comply with the
              provisions defined in table 8.6.2.4-1. The notification shall be
              triggered by the NFV-MANO functional entity when log information
              has been collected by the logging job and the log report is
              available.
            type: object
            required:
              - id
              - notificationType
              - subscriptionId
              - timeStamp
              - objectInstanceId
              - _links
            properties:
              id:
                description: |
                  An identifier with the intention of being globally unique.
                type: string
              notificationType:
                description: >-
                  Discriminator for the different notification types. Shall be
                  set to "LogReportAvailableNotification" for this notification
                  type.
                type: string
              subscriptionId:
                description: |
                  An identifier with the intention of being globally unique.
                type: string
              timeStamp:
                description: >
                  Date-time stamp. Representation: String formatted according to
                  IETF RFC 3339.
                type: string
                format: date-time
              objectInstanceId:
                description: >
                  This type represents the identifier to reference a managed
                  object of a  particular type. 
                type: object
                properties:
                  type:
                    description: >
                      Indicates the type of managed object. Permitted values:
                        - MANO_ENTITY
                        - MANO_SERVICE
                        - MANO_SERVICE_IF
                        - CONSUMED_MANO_IF
                        - MANO_ENTITY_COMPONENT

                      The "MANO_ENTITY COMPONENT" is only applicable if
                      attribute "manoEntityComponents" in "ManoEntity" is
                      supported by the API producer.
                    type: string
                    enum:
                      - MANO_ENTITY
                      - MANO_SERVICE
                      - MANO_SERVICE_IF
                      - CONSUMED_MANO_IF
                      - MANO_ENTITY_COMPONENT
                  objectId:
                    description: |
                      An identifier with the intention of being globally unique.
                    type: string
                  subObjectId:
                    description: >
                      An identifier that is unique for the respective type
                      within a NFV-MANO functional entity, but that need not be
                      globally unique. Representation: string of variable
                      length..
                    type: string
                required:
                  - type
                  - objectId
              _links:
                description: Links to resources related to this notification.
                type: object
                required:
                  - subscription
                  - logReports
                properties:
                  subscription:
                    description: >
                      This type represents a link to a resource in a
                      notification, using an absolute or relative URI.
                    type: object
                    required:
                      - href
                    properties:
                      href:
                        description: |
                          String formatted according to IETF RFC 3986.
                        type: string
                  objectInstance:
                    description: >
                      This type represents a link to a resource in a
                      notification, using an absolute or relative URI.
                    type: object
                    required:
                      - href
                    properties:
                      href:
                        description: |
                          String formatted according to IETF RFC 3986.
                        type: string
                  LoggingJob:
                    description: >
                      This type represents a link to a resource in a
                      notification, using an absolute or relative URI.
                    type: object
                    required:
                      - href
                    properties:
                      href:
                        description: |
                          String formatted according to IETF RFC 3986.
                        type: string
                  logReports:
                    description: >-
                      Link from which the available log report can be obtained.
                      Due to the relationship of the logging job compilation and
                      the logging information availability reporting, more than
                      one logReport notification link can be provided.
                    type: array
                    items:
                      description: >
                        This type represents a link to a resource in a
                        notification, using an absolute or relative URI.
                      type: object
                      required:
                        - href
                      properties:
                        href:
                          description: |
                            String formatted according to IETF RFC 3986.
                          type: string
  responses:
    subscription.delete.204:
      description: >-
        Shall be returned when the "Individual subscription" resource has been
        deleted successfully. The response body shall be empty.
      headers:
        Content-Type:
          description: The MIME type of the body of the response.
          schema:
            type: string
        WWW-Authenticate:
          description: >
            Challenge if the corresponding HTTP request has not provided
            authorization, or error details if the corresponding HTTP request
            has provided an invalid authorization token.
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
    subscription.get.200:
      description: >-
        Shall be returned when the subscription has been read successfully. The
        response body shall contain a representation of the "Individual
        subscription" resource, as defined in clause 8.6.2.3.
      headers:
        Content-Type:
          description: The MIME type of the body of the response.
          schema:
            type: string
        WWW-Authenticate:
          description: >
            Challenge if the corresponding HTTP request has not provided
            authorization, or error details if the corresponding HTTP request
            has provided an invalid authorization token.
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
      content:
        application/json:
          schema:
            description: >-
              This type represents a subscription. It shall comply with the
              provisions defined in table 8.6.2.3-1.
            type: object
            required:
              - id
              - callbackUri
              - _links
            properties:
              id:
                description: |
                  An identifier with the intention of being globally unique.
                type: string
              filter:
                description: >-
                  This type represents a filter that can be used to subscribe
                  for notifications related to log management events. It shall
                  comply with the provisions defined in table 8.6.3.7-1. At a
                  particular nesting level in the filter structure, the
                  following applies: All attributes shall match in order for the
                  filter to match (logical "and" between different filter
                  attributes). If an attribute is an array, the attribute shall
                  match if at least one of the values in the array matches
                  (logical "or" between the values of one filter attribute).
                type: object
                properties:
                  objectInstanceFilter:
                    description: >-
                      This type represents subscription filter criteria to match
                      NFV-MANO functional entities and their associated managed
                      objects. It shall comply with the provisions defined in
                      Table 4.3.2.2-1.
                    type: object
                    anyOf:
                      - oneOf:
                          - required:
                              - manoServiceIds
                          - required:
                              - manoServiceNames
                      - oneOf:
                          - required:
                              - manoServiceInterfaceIds
                          - required:
                              - manoServiceInterfaceNames
                      - oneOf:
                          - required:
                              - consumedManoInterfaceIds
                          - required:
                              - consumedManoInterfaceNames
                    properties:
                      manoEntityId:
                        description: >
                          An identifier with the intention of being globally
                          unique.
                        type: string
                      manoServiceIds:
                        description: >-
                          If present, match NFV-MANO services with an instance
                          identifier listed in this attribute.
                        type: array
                        items:
                          description: >
                            An identifier that is unique for the respective type
                            within a NFV-MANO functional entity, but that need
                            not be globally unique. Representation: string of
                            variable length..
                          type: string
                      manoServiceNames:
                        description: >-
                          If present, match NFV-MANO services with an NFV-MANO
                          service name listed in this attribute.
                        type: array
                        items:
                          type: string
                      manoServiceInterfaceIds:
                        description: >-
                          If present, match NFV-MANO functional entity produced
                          interfaces with an instance identifier listed in this
                          attribute.
                        type: array
                        items:
                          description: >
                            An identifier that is unique for the respective type
                            within a NFV-MANO functional entity, but that need
                            not be globally unique. Representation: string of
                            variable length..
                          type: string
                      manoServiceInterfaceNames:
                        description: >-
                          If present, match NFV-MANO functional entity produced
                          interfaces with an instance Name listed in this
                          attribute.
                        type: array
                        items:
                          type: string
                      consumedManoInterfaceIds:
                        description: >-
                          If present, match NFV-MANO functional entity consumed
                          interfaces with an instance identifier listed in this
                          attribute.
                        type: array
                        items:
                          description: >
                            An identifier with the intention of being globally
                            unique.
                          type: string
                      consumedManoInterfaceNames:
                        description: >-
                          If present, match NFV-MANO functional entity consumed
                          interfaces with an instance Name listed in this
                          attribute.
                        type: array
                        items:
                          type: string
                  notificationTypes:
                    description: >-
                      Match particular notification types. Permitted values: -
                      LogReportAvailableNotification
                    type: string
                    enum:
                      - LogReportAvailableNotification
              callbackUri:
                description: |
                  String formatted according to IETF RFC 3986.
                type: string
              _links:
                description: Links to resources related to this resource.
                type: object
                required:
                  - self
                properties:
                  self:
                    description: >
                      This type represents a link to a resource using an
                      absolute URI.
                    type: object
                    required:
                      - href
                    properties:
                      href:
                        description: |
                          String formatted according to IETF RFC 3986.
                        type: string
    subscriptions.get.200:
      description: >-
        Shall be returned when the list of subscriptions has been queried
        successfully. The response body shall contain in an array the
        representations of all active subscriptions of the functional block that
        invokes the method, i.e. zero or more representations of log management
        subscriptions as defined in clause 8.6.2.3. If the "filter" URI
        parameter was supplied in the request, the data in the response body
        shall have been transformed according to the rules specified in clause
        5.2.2 of ETSI GS NFV-SOL 013. If the NFV-MANO functional entity supports
        alternative 2 (paging) according to clause 5.4.2.1 of ETSI GS NFV-SOL
        013 for this resource, inclusion of the Link HTTP header in this
        response shall follow the provisions in clause 5.4.2.3 of ETSI GS
        NFV-SOL 013 .
      headers:
        Content-Type:
          description: The MIME type of the body of the response.
          schema:
            type: string
        WWW-Authenticate:
          description: >
            Challenge if the corresponding HTTP request has not provided
            authorization, or error details if the corresponding HTTP request
            has provided an invalid authorization token.
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
      content:
        application/json:
          schema:
            type: array
            items:
              description: >-
                This type represents a subscription. It shall comply with the
                provisions defined in table 8.6.2.3-1.
              type: object
              required:
                - id
                - callbackUri
                - _links
              properties:
                id:
                  description: |
                    An identifier with the intention of being globally unique.
                  type: string
                filter:
                  description: >-
                    This type represents a filter that can be used to subscribe
                    for notifications related to log management events. It shall
                    comply with the provisions defined in table 8.6.3.7-1. At a
                    particular nesting level in the filter structure, the
                    following applies: All attributes shall match in order for
                    the filter to match (logical "and" between different filter
                    attributes). If an attribute is an array, the attribute
                    shall match if at least one of the values in the array
                    matches (logical "or" between the values of one filter
                    attribute).
                  type: object
                  properties:
                    objectInstanceFilter:
                      description: >-
                        This type represents subscription filter criteria to
                        match NFV-MANO functional entities and their associated
                        managed objects. It shall comply with the provisions
                        defined in Table 4.3.2.2-1.
                      type: object
                      anyOf:
                        - oneOf:
                            - required:
                                - manoServiceIds
                            - required:
                                - manoServiceNames
                        - oneOf:
                            - required:
                                - manoServiceInterfaceIds
                            - required:
                                - manoServiceInterfaceNames
                        - oneOf:
                            - required:
                                - consumedManoInterfaceIds
                            - required:
                                - consumedManoInterfaceNames
                      properties:
                        manoEntityId:
                          description: >
                            An identifier with the intention of being globally
                            unique.
                          type: string
                        manoServiceIds:
                          description: >-
                            If present, match NFV-MANO services with an instance
                            identifier listed in this attribute.
                          type: array
                          items:
                            description: >
                              An identifier that is unique for the respective
                              type within a NFV-MANO functional entity, but that
                              need not be globally unique. Representation:
                              string of variable length..
                            type: string
                        manoServiceNames:
                          description: >-
                            If present, match NFV-MANO services with an NFV-MANO
                            service name listed in this attribute.
                          type: array
                          items:
                            type: string
                        manoServiceInterfaceIds:
                          description: >-
                            If present, match NFV-MANO functional entity
                            produced interfaces with an instance identifier
                            listed in this attribute.
                          type: array
                          items:
                            description: >
                              An identifier that is unique for the respective
                              type within a NFV-MANO functional entity, but that
                              need not be globally unique. Representation:
                              string of variable length..
                            type: string
                        manoServiceInterfaceNames:
                          description: >-
                            If present, match NFV-MANO functional entity
                            produced interfaces with an instance Name listed in
                            this attribute.
                          type: array
                          items:
                            type: string
                        consumedManoInterfaceIds:
                          description: >-
                            If present, match NFV-MANO functional entity
                            consumed interfaces with an instance identifier
                            listed in this attribute.
                          type: array
                          items:
                            description: >
                              An identifier with the intention of being globally
                              unique.
                            type: string
                        consumedManoInterfaceNames:
                          description: >-
                            If present, match NFV-MANO functional entity
                            consumed interfaces with an instance Name listed in
                            this attribute.
                          type: array
                          items:
                            type: string
                    notificationTypes:
                      description: >-
                        Match particular notification types. Permitted values: -
                        LogReportAvailableNotification
                      type: string
                      enum:
                        - LogReportAvailableNotification
                callbackUri:
                  description: |
                    String formatted according to IETF RFC 3986.
                  type: string
                _links:
                  description: Links to resources related to this resource.
                  type: object
                  required:
                    - self
                  properties:
                    self:
                      description: >
                        This type represents a link to a resource using an
                        absolute URI.
                      type: object
                      required:
                        - href
                      properties:
                        href:
                          description: |
                            String formatted according to IETF RFC 3986.
                          type: string
    subscriptions.post.201:
      description: >-
        Shall be returned when the subscription has been created successfully. A
        representation of the created "Individual subscription" resource shall
        be returned in the response body, as defined in clause 8.6.2.3. The HTTP
        response shall include a "Location" HTTP header that contains the
        resource URI of the created "Individual subscription" resource.
      headers:
        Content-Type:
          description: The MIME type of the body of the response.
          schema:
            type: string
        WWW-Authenticate:
          description: >
            Challenge if the corresponding HTTP request has not provided
            authorization, or error details if the corresponding HTTP request
            has provided an invalid authorization token.
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
        Location:
          description: |
            URI of the "Individual log report" resource just created
          schema:
            type: string
      content:
        application/json:
          schema:
            description: >-
              This type represents a subscription. It shall comply with the
              provisions defined in table 8.6.2.3-1.
            type: object
            required:
              - id
              - callbackUri
              - _links
            properties:
              id:
                description: |
                  An identifier with the intention of being globally unique.
                type: string
              filter:
                description: >-
                  This type represents a filter that can be used to subscribe
                  for notifications related to log management events. It shall
                  comply with the provisions defined in table 8.6.3.7-1. At a
                  particular nesting level in the filter structure, the
                  following applies: All attributes shall match in order for the
                  filter to match (logical "and" between different filter
                  attributes). If an attribute is an array, the attribute shall
                  match if at least one of the values in the array matches
                  (logical "or" between the values of one filter attribute).
                type: object
                properties:
                  objectInstanceFilter:
                    description: >-
                      This type represents subscription filter criteria to match
                      NFV-MANO functional entities and their associated managed
                      objects. It shall comply with the provisions defined in
                      Table 4.3.2.2-1.
                    type: object
                    anyOf:
                      - oneOf:
                          - required:
                              - manoServiceIds
                          - required:
                              - manoServiceNames
                      - oneOf:
                          - required:
                              - manoServiceInterfaceIds
                          - required:
                              - manoServiceInterfaceNames
                      - oneOf:
                          - required:
                              - consumedManoInterfaceIds
                          - required:
                              - consumedManoInterfaceNames
                    properties:
                      manoEntityId:
                        description: >
                          An identifier with the intention of being globally
                          unique.
                        type: string
                      manoServiceIds:
                        description: >-
                          If present, match NFV-MANO services with an instance
                          identifier listed in this attribute.
                        type: array
                        items:
                          description: >
                            An identifier that is unique for the respective type
                            within a NFV-MANO functional entity, but that need
                            not be globally unique. Representation: string of
                            variable length..
                          type: string
                      manoServiceNames:
                        description: >-
                          If present, match NFV-MANO services with an NFV-MANO
                          service name listed in this attribute.
                        type: array
                        items:
                          type: string
                      manoServiceInterfaceIds:
                        description: >-
                          If present, match NFV-MANO functional entity produced
                          interfaces with an instance identifier listed in this
                          attribute.
                        type: array
                        items:
                          description: >
                            An identifier that is unique for the respective type
                            within a NFV-MANO functional entity, but that need
                            not be globally unique. Representation: string of
                            variable length..
                          type: string
                      manoServiceInterfaceNames:
                        description: >-
                          If present, match NFV-MANO functional entity produced
                          interfaces with an instance Name listed in this
                          attribute.
                        type: array
                        items:
                          type: string
                      consumedManoInterfaceIds:
                        description: >-
                          If present, match NFV-MANO functional entity consumed
                          interfaces with an instance identifier listed in this
                          attribute.
                        type: array
                        items:
                          description: >
                            An identifier with the intention of being globally
                            unique.
                          type: string
                      consumedManoInterfaceNames:
                        description: >-
                          If present, match NFV-MANO functional entity consumed
                          interfaces with an instance Name listed in this
                          attribute.
                        type: array
                        items:
                          type: string
                  notificationTypes:
                    description: >-
                      Match particular notification types. Permitted values: -
                      LogReportAvailableNotification
                    type: string
                    enum:
                      - LogReportAvailableNotification
              callbackUri:
                description: |
                  String formatted according to IETF RFC 3986.
                type: string
              _links:
                description: Links to resources related to this resource.
                type: object
                required:
                  - self
                properties:
                  self:
                    description: >
                      This type represents a link to a resource using an
                      absolute URI.
                    type: object
                    required:
                      - href
                    properties:
                      href:
                        description: |
                          String formatted according to IETF RFC 3986.
                        type: string
    subscriptions.post.303:
      description: >-
        Shall be returned when a subscription with the same callbackURI and the
        same filter already exists and the policy of the NFV-MANO functional
        entity is to not create redundant subscriptions. The HTTP response shall
        include a "Location" HTTP header that contains the resource URI of the
        existing "Individual subscription" resource. The response body shall be
        empty.
      headers:
        Content-Type:
          description: The MIME type of the body of the response.
          schema:
            type: string
        WWW-Authenticate:
          description: >
            Challenge if the corresponding HTTP request has not provided
            authorization, or error details if the corresponding HTTP request
            has provided an invalid authorization token.
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
        Location:
          description: |
            URI of the "Individual log report" resource just created
          schema:
            type: string
    LogReportCompiled.Post.200:
      description: >-
        Shall be returned for a successful compilation of the log data and
        creation of the associated log report (synchronous mode). The response
        body shall contain a representation of the log report resource, as
        defined in clause 8.6.2.7. The HTTP response shall include a "Location"
        HTTP header that indicate the URI of the "Individual log report"
        resource just created
      headers:
        Content-Type:
          description: The MIME type of the body of the response.
          schema:
            type: string
        WWW-Authenticate:
          description: >
            Challenge if the corresponding HTTP request has not provided
            authorization, or error details if the corresponding HTTP request
            has provided an invalid authorization token.
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
        Location:
          description: |
            URI of the "Individual log report" resource just created
          schema:
            type: string
      content:
        application/json:
          schema:
            description: >
              This type represents a log report, which provides information
              about a compiled log and how to obtain it. It shall comply with
              the provisions defined in table 8.6.2.7-1.
            type: object
            required:
              - id
              - objectInstanceId
              - compilationTrigger
              - readyTime
              - fileFormat
              - fileLocationInfo
              - securityAndIntegrityInfo
              - _links
            properties:
              id:
                description: |
                  An identifier with the intention of being globally unique.
                type: string
              objectInstanceId:
                description: >
                  This type represents the identifier to reference a managed
                  object of a  particular type. 
                type: object
                properties:
                  type:
                    description: >
                      Indicates the type of managed object. Permitted values:
                        - MANO_ENTITY
                        - MANO_SERVICE
                        - MANO_SERVICE_IF
                        - CONSUMED_MANO_IF
                        - MANO_ENTITY_COMPONENT

                      The "MANO_ENTITY COMPONENT" is only applicable if
                      attribute "manoEntityComponents" in "ManoEntity" is
                      supported by the API producer.
                    type: string
                    enum:
                      - MANO_ENTITY
                      - MANO_SERVICE
                      - MANO_SERVICE_IF
                      - CONSUMED_MANO_IF
                      - MANO_ENTITY_COMPONENT
                  objectId:
                    description: |
                      An identifier with the intention of being globally unique.
                    type: string
                  subObjectId:
                    description: >
                      An identifier that is unique for the respective type
                      within a NFV-MANO functional entity, but that need not be
                      globally unique. Representation: string of variable
                      length..
                    type: string
                required:
                  - type
                  - objectId
              compilationTrigger:
                description: >-
                  The trigger for the compilation of the log file.

                  Permitted values: - ON_DEMAND: created based on explicit
                  request by a client. - AUTOMATIC: created according to the
                  logging job compilation configuration.
                type: string
                enum:
                  - ON_DEMAND
                  - AUTOMATIC
              readyTime:
                description: >
                  Date-time stamp. Representation: String formatted according to
                  IETF RFC 3339.
                type: string
                format: date-time
              expiryTime:
                description: >
                  Date-time stamp. Representation: String formatted according to
                  IETF RFC 3339.
                type: string
                format: date-time
              fileSize:
                description: 'The size of the compiled log file in bytes, if known.'
                type: integer
                format: int32
              fileFormat:
                description: The encoding used by the file.
                type: string
              fileLocationInfo:
                description: >-
                  Location and address information of the compiled log file. The
                  consumer can use this information to obtain the compiled log
                  file.
                type: object
                required:
                  - protocol
                  - fileEndpoint
                properties:
                  protocol:
                    description: >-
                      Protocol over which the compiled log file can be
                      retrieved.

                      Permitted values: - HTTPS: transmission over HTTP Secure
                      (HTTPS). - SFTP: transmission over SSH file transfer
                      protocol (SFTP). - SCP: transmission over secure copy
                      protocol (SCP). - FTPS: transmission over file transfer
                      protocol secure (FTPS), as specified in IETF RFC 2228
                      [i.11],
                           using explicit mode as specified in IETF RFC 4217 [i.12]. If FTPS is supported, "private" protection level shall be used.

                      HTTPS shall be supported, and other protocols may be
                      supported.
                    type: string
                    enum:
                      - HTTPS
                      - SFTP
                      - SCP
                      - FTPS
                  fileEndpoint:
                    description: >-
                      The host name (or IP address), optionally a port number
                      (if the host with the compile log file uses a non-standard
                      port number as per the supported transmission protocol), a
                      valid file directory path, and the file name of the
                      compiled log file, or a valid URL.
                    type: string
                    format: URI
              securityAndIntegrityInfo:
                description: >-
                  Security and integrity information for the compilation of the
                  log files.
                type: object
                required:
                  - algorithm
                  - hash
                  - logFileSignature
                  - signingCertificate
                properties:
                  algorithm:
                    description: >-
                      Algorithm used to generate the hash of the compiled log
                      file. Only SHA-256 and SHA-512 shall be used
                    type: string
                  hash:
                    description: >-
                      The hexadecimal value of the hash of the compiled log
                      file. The hash shall be computed from the encrypted
                      compiled log file, in case the encryption applies.
                    type: string
                  encryptionPublicKey:
                    description: >-
                      Public key used for the encryption of the compiled log
                      file. Shall be present if the compiled log file is
                      encrypted.
                    type: string
                  cipherAlgorithm:
                    description: >-
                      The cryptographic algorithm used for the encryption. Shall
                      be present if the compiled log file is encrypted. Valid
                      values are: "AES-CBC-128", "AES-GCM-128", "AES-CBC-256",
                      and "AES-GCM-256", as specified in clause 6.5 of ETSI GS
                      NFV-SEC 012 [14].
                    type: string
                  logFileSignature:
                    description: >-
                      Signature to the compiled log file generated with the
                      NFV-MANO functional entity’s private key, which is used to
                      ensure the authenticity of the compiled log file. The
                      signature shall be applied according to the
                      "encryptAndSignOrder" of the "LoggingJobConfig".
                    type: string
                  signingCertificate:
                    description: >-
                      X.509 certificate with the NFV-MANO functional entity’s
                      public key used for verifying the log report and compiled
                      log file signatures.
                    type: string
              _links:
                description: Links for this resource.
                type: object
                required:
                  - self
                properties:
                  self:
                    description: >
                      This type represents a link to a resource using an
                      absolute URI.
                    type: object
                    required:
                      - href
                    properties:
                      href:
                        description: |
                          String formatted according to IETF RFC 3986.
                        type: string
                  objects:
                    description: >-
                      Links to resources representing the object instances that
                      are logged. Shall be present if the logged object instance
                      information is accessible as a resource.
                    type: array
                    items:
                      description: >
                        This type represents a link to a resource using an
                        absolute URI.
                      type: object
                      required:
                        - href
                      properties:
                        href:
                          description: |
                            String formatted according to IETF RFC 3986.
                          type: string
    LogReportCompiled.Post.202:
      description: >-
        Shall be returned when the request has been accepted for processing, and
        it is expected to take some time to compile the log file and create the
        associated log report (asynchronous mode). The response body shall be
        empty. The HTTP response shall include a "Location" HTTP header that
        indicates the URI of the "Individual log report" resource that will be
        created once the log file compilation is completed.
      headers:
        Content-Type:
          description: The MIME type of the body of the response.
          schema:
            type: string
        WWW-Authenticate:
          description: >
            Challenge if the corresponding HTTP request has not provided
            authorization, or error details if the corresponding HTTP request
            has provided an invalid authorization token.
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
        Location:
          description: >
            The URI of the "Individual log report" resource that will be created
            once the log file compilation is completed.
          schema:
            type: string
    LogReportCompiled.Post.303:
      description: >-
        Shall be returned when a log data compilation and report creation is
        already ongoing, or a log report has just been created, for the
        specified logging job at the time of processing the request. The
        response body shall be empty. The HTTP response shall include a
        "Location" HTTP header that contains the resource URI of the log report
        resource just created, or to be created by the ongoing compilation and
        report creation.
      headers:
        Content-Type:
          description: The MIME type of the body of the response.
          schema:
            type: string
        WWW-Authenticate:
          description: >
            Challenge if the corresponding HTTP request has not provided
            authorization, or error details if the corresponding HTTP request
            has provided an invalid authorization token.
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
        Location:
          description: >
            The URI of the log report resource just created, or to be created by
            the ongoing compilation and report creation
          schema:
            type: string
    LogReportCompiled.Post.422:
      description: >-
        The general cause for this error and its handling is specified in clause
        6.4 of ETSI GS NFV-SOL 013, including rules for the presence of the
        response body. Specifically, in case of this task resource, the response
        code 422 shall also be returned if the "objectInstanceId" value provided
        in the payload body of the request does not correspond to an object
        instance for which log data is being collected by the logging job
        represented by this resource. The response body shall contain a
        ProblemDetails structure, in which the "detail" attribute should convey
        more information about the error.
      headers:
        Content-Type:
          description: The MIME type of the body of the response.
          schema:
            type: string
        WWW-Authenticate:
          description: >
            Challenge if the corresponding HTTP request has not provided
            authorization, or error details if the corresponding HTTP request
            has provided an invalid authorization token.
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
      content:
        application/json:
          schema:
            description: >
              The definition of the general "ProblemDetails" data structure from
              IETF RFC 7807 [19] is reproduced inthis structure. Compared to the
              general framework defined in IETF RFC 7807 [19], the "status" and
              "detail" attributes are mandated to be included by the present
              document, to ensure that the response contains additional textual
              information about an error. IETF RFC 7807 [19] foresees
              extensibility of the "ProblemDetails" type. It is possible that
              particular APIs in the present document, or particular
              implementations, define extensions to define additional attributes
              that provide more information about the error. The description
              column only provides some explanation of the meaning to Facilitate
              understanding of the design. For a full description, see IETF RFC
              7807 [19].
            type: object
            required:
              - status
              - detail
            properties:
              type:
                description: >
                  A URI reference according to IETF RFC 3986 [5] that identifies
                  the problem type. It is encouraged that the URI provides
                  human-readable documentation for the problem (e.g. using HTML)
                  when dereferenced. When this member is not present, its value
                  is assumed to be "about:blank".
                type: string
                format: URI
              title:
                description: >
                  A short, human-readable summary of the problem type. It should
                  not change from occurrence to occurrence of the problem,
                  except for purposes of localization. If type is given and
                  other than "about:blank", this attribute shall also be
                  provided. A short, human-readable summary of the problem
                  type.  It SHOULD NOT change from occurrence to occurrence of
                  the problem, except for purposes of localization (e.g., using
                  proactive content negotiation; see [RFC7231], Section 3.4).
                type: string
              status:
                description: >
                  The HTTP status code for this occurrence of the problem. The
                  HTTP status code ([RFC7231], Section 6) generated by the
                  origin server for this occurrence of the problem.
                type: integer
              detail:
                description: >
                  A human-readable explanation specific to this occurrence of
                  the problem.
                type: string
              instance:
                description: >
                  A URI reference that identifies the specific occurrence of the
                  problem. It may yield further information if dereferenced.
                type: string
                format: URI
    LogReport.Get.200:
      description: >-
        Shall be returned when information of an individual log report has been
        read successfully. The response body shall contain a representation of
        the "Individual log report" resource, as defined in clause 8.6.2.7.
      headers:
        Content-Type:
          description: The MIME type of the body of the response.
          schema:
            type: string
        WWW-Authenticate:
          description: >
            Challenge if the corresponding HTTP request has not provided
            authorization, or error details if the corresponding HTTP request
            has provided an invalid authorization token.
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
      content:
        application/json:
          schema:
            description: >
              This type represents a log report, which provides information
              about a compiled log and how to obtain it. It shall comply with
              the provisions defined in table 8.6.2.7-1.
            type: object
            required:
              - id
              - objectInstanceId
              - compilationTrigger
              - readyTime
              - fileFormat
              - fileLocationInfo
              - securityAndIntegrityInfo
              - _links
            properties:
              id:
                description: |
                  An identifier with the intention of being globally unique.
                type: string
              objectInstanceId:
                description: >
                  This type represents the identifier to reference a managed
                  object of a  particular type. 
                type: object
                properties:
                  type:
                    description: >
                      Indicates the type of managed object. Permitted values:
                        - MANO_ENTITY
                        - MANO_SERVICE
                        - MANO_SERVICE_IF
                        - CONSUMED_MANO_IF
                        - MANO_ENTITY_COMPONENT

                      The "MANO_ENTITY COMPONENT" is only applicable if
                      attribute "manoEntityComponents" in "ManoEntity" is
                      supported by the API producer.
                    type: string
                    enum:
                      - MANO_ENTITY
                      - MANO_SERVICE
                      - MANO_SERVICE_IF
                      - CONSUMED_MANO_IF
                      - MANO_ENTITY_COMPONENT
                  objectId:
                    description: |
                      An identifier with the intention of being globally unique.
                    type: string
                  subObjectId:
                    description: >
                      An identifier that is unique for the respective type
                      within a NFV-MANO functional entity, but that need not be
                      globally unique. Representation: string of variable
                      length..
                    type: string
                required:
                  - type
                  - objectId
              compilationTrigger:
                description: >-
                  The trigger for the compilation of the log file.

                  Permitted values: - ON_DEMAND: created based on explicit
                  request by a client. - AUTOMATIC: created according to the
                  logging job compilation configuration.
                type: string
                enum:
                  - ON_DEMAND
                  - AUTOMATIC
              readyTime:
                description: >
                  Date-time stamp. Representation: String formatted according to
                  IETF RFC 3339.
                type: string
                format: date-time
              expiryTime:
                description: >
                  Date-time stamp. Representation: String formatted according to
                  IETF RFC 3339.
                type: string
                format: date-time
              fileSize:
                description: 'The size of the compiled log file in bytes, if known.'
                type: integer
                format: int32
              fileFormat:
                description: The encoding used by the file.
                type: string
              fileLocationInfo:
                description: >-
                  Location and address information of the compiled log file. The
                  consumer can use this information to obtain the compiled log
                  file.
                type: object
                required:
                  - protocol
                  - fileEndpoint
                properties:
                  protocol:
                    description: >-
                      Protocol over which the compiled log file can be
                      retrieved.

                      Permitted values: - HTTPS: transmission over HTTP Secure
                      (HTTPS). - SFTP: transmission over SSH file transfer
                      protocol (SFTP). - SCP: transmission over secure copy
                      protocol (SCP). - FTPS: transmission over file transfer
                      protocol secure (FTPS), as specified in IETF RFC 2228
                      [i.11],
                           using explicit mode as specified in IETF RFC 4217 [i.12]. If FTPS is supported, "private" protection level shall be used.

                      HTTPS shall be supported, and other protocols may be
                      supported.
                    type: string
                    enum:
                      - HTTPS
                      - SFTP
                      - SCP
                      - FTPS
                  fileEndpoint:
                    description: >-
                      The host name (or IP address), optionally a port number
                      (if the host with the compile log file uses a non-standard
                      port number as per the supported transmission protocol), a
                      valid file directory path, and the file name of the
                      compiled log file, or a valid URL.
                    type: string
                    format: URI
              securityAndIntegrityInfo:
                description: >-
                  Security and integrity information for the compilation of the
                  log files.
                type: object
                required:
                  - algorithm
                  - hash
                  - logFileSignature
                  - signingCertificate
                properties:
                  algorithm:
                    description: >-
                      Algorithm used to generate the hash of the compiled log
                      file. Only SHA-256 and SHA-512 shall be used
                    type: string
                  hash:
                    description: >-
                      The hexadecimal value of the hash of the compiled log
                      file. The hash shall be computed from the encrypted
                      compiled log file, in case the encryption applies.
                    type: string
                  encryptionPublicKey:
                    description: >-
                      Public key used for the encryption of the compiled log
                      file. Shall be present if the compiled log file is
                      encrypted.
                    type: string
                  cipherAlgorithm:
                    description: >-
                      The cryptographic algorithm used for the encryption. Shall
                      be present if the compiled log file is encrypted. Valid
                      values are: "AES-CBC-128", "AES-GCM-128", "AES-CBC-256",
                      and "AES-GCM-256", as specified in clause 6.5 of ETSI GS
                      NFV-SEC 012 [14].
                    type: string
                  logFileSignature:
                    description: >-
                      Signature to the compiled log file generated with the
                      NFV-MANO functional entity’s private key, which is used to
                      ensure the authenticity of the compiled log file. The
                      signature shall be applied according to the
                      "encryptAndSignOrder" of the "LoggingJobConfig".
                    type: string
                  signingCertificate:
                    description: >-
                      X.509 certificate with the NFV-MANO functional entity’s
                      public key used for verifying the log report and compiled
                      log file signatures.
                    type: string
              _links:
                description: Links for this resource.
                type: object
                required:
                  - self
                properties:
                  self:
                    description: >
                      This type represents a link to a resource using an
                      absolute URI.
                    type: object
                    required:
                      - href
                    properties:
                      href:
                        description: |
                          String formatted according to IETF RFC 3986.
                        type: string
                  objects:
                    description: >-
                      Links to resources representing the object instances that
                      are logged. Shall be present if the logged object instance
                      information is accessible as a resource.
                    type: array
                    items:
                      description: >
                        This type represents a link to a resource using an
                        absolute URI.
                      type: object
                      required:
                        - href
                      properties:
                        href:
                          description: |
                            String formatted according to IETF RFC 3986.
                          type: string
    LogReport.Get.202:
      description: >-
        Shall be returned if the creation of the log report is ongoing and no
        log report is available yet (applicable in asynchronous mode of the
        "Compile log task" resource). The response body shall be empty.
      headers:
        Content-Type:
          description: The MIME type of the body of the response.
          schema:
            type: string
        WWW-Authenticate:
          description: >
            Challenge if the corresponding HTTP request has not provided
            authorization, or error details if the corresponding HTTP request
            has provided an invalid authorization token.
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
    LoggingJob.Get:
      description: >-
        Shall be returned when information about an individual logging job has
        been read successfully. The response body shall contain a representation
        of the "Individual logging job" resource, as defined in clause 8.6.2.6.
      headers:
        Content-Type:
          description: The MIME type of the body of the response.
          schema:
            type: string
        WWW-Authenticate:
          description: >
            Challenge if the corresponding HTTP request has not provided
            authorization, or error details if the corresponding HTTP request
            has provided an invalid authorization token.
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
      content:
        application/json:
          schema:
            description: >-
              This type represents a logging job. It shall comply with the
              provisions defined in table 8.6.2.6-1.
            type: object
            required:
              - id
              - objectInstanceIds
              - jobCriteria
              - jobConfig
              - _links
            properties:
              id:
                description: |
                  An identifier with the intention of being globally unique.
                type: string
              objectInstanceIds:
                description: >-
                  Identifiers of the object instance for which logging
                  information is collected. This attribute shall contain the
                  identifier of the instance of the object that is logged
                  according to their type.
                type: array
                items:
                  description: >
                    This type represents the identifier to reference a managed
                    object of a  particular type. 
                  type: object
                  properties:
                    type:
                      description: >
                        Indicates the type of managed object. Permitted values:
                          - MANO_ENTITY
                          - MANO_SERVICE
                          - MANO_SERVICE_IF
                          - CONSUMED_MANO_IF
                          - MANO_ENTITY_COMPONENT

                        The "MANO_ENTITY COMPONENT" is only applicable if
                        attribute "manoEntityComponents" in "ManoEntity" is
                        supported by the API producer.
                      type: string
                      enum:
                        - MANO_ENTITY
                        - MANO_SERVICE
                        - MANO_SERVICE_IF
                        - CONSUMED_MANO_IF
                        - MANO_ENTITY_COMPONENT
                    objectId:
                      description: >
                        An identifier with the intention of being globally
                        unique.
                      type: string
                    subObjectId:
                      description: >
                        An identifier that is unique for the respective type
                        within a NFV-MANO functional entity, but that need not
                        be globally unique. Representation: string of variable
                        length..
                      type: string
                  required:
                    - type
                    - objectId
              jobCriteria:
                description: >-
                  This type represents collection criteria for logging jobs. It
                  shall comply with the provisions defined in table 8.6.3.2-1.
                type: object
                required:
                  - loggingType
                properties:
                  loggingType:
                    description: >-
                      Type of logging. This defines the types of logged
                      information to collect.

                      Permitted values: - MESSAGES: logged NFV-MANO service
                      interface messages. - SERVICES: logged messages about
                      processes pertaining to NFV-MANO services. - SYSTEM:
                      logged messages about the NFV-MANO functional entity’s
                      system enabled by the provider.
                    type: string
                    enum:
                      - MESSAGES
                      - SERVICES
                      - SYSTEM
                  messagesLogDetail:
                    description: >-
                      This type represents criteria for logging jobs to collect
                      logged messages on NFV-MANO service interfaces. It shall
                      comply with the provisions defined in table 8.6.3.3-1.
                    type: object
                    required:
                      - direction
                    properties:
                      direction:
                        description: >-
                          The direction of the interface messages to match.

                          Permitted values: - IN: input messages into the
                          interface. - OUT: output messages from the interface.
                          - ALL: both input and output messages into/from the
                          interface.
                        type: string
                        enum:
                          - IN
                          - OUT
                          - ALL
                      matchingPatterns:
                        description: >-
                          Patterns to be matched in the interface message. If
                          provided, only messages that match all the values
                          provided in the sub-attributes shall be logged. An API
                          consumer can provide more than one "matchingPattern"
                          if combinations of patterns are to be considered to
                          match diverse sets of interface messages.
                        type: array
                        items:
                          type: object
                          anyOf:
                            - required:
                                - srcIpAddress
                            - required:
                                - dstIpAddress
                            - required:
                                - requestMethod
                            - required:
                                - requestUriPattern
                            - required:
                                - responseCodes
                          properties:
                            srcIpAddress:
                              description: >
                                An IPV4 or IPV6 address. Representation: In case
                                of an IPV4 address, string that consists of four
                                decimal integers separated by dots, each integer
                                ranging from 0 to 255. In case of an IPV6
                                address, string that consists of groups of zero
                                to four hexadecimal digits, separated by colons.
                              type: string
                              format: IP
                            requestMethod:
                              description: >-
                                HTTP request method to be matched. To match, the
                                HTTP request method of the message shall be the
                                same as the value of this attribute. Valid
                                values are specified in IETF RFC 7231. The API
                                producer shall support this attribute.
                              type: string
                            requestUriPattern:
                              description: >-
                                Substring to be matched in the request URI. To
                                match, the request URI shall include the value
                                of
                                 this attribute as a substring. This is typically used to match messages which associate to RESTful
                                 resources, or to a specific API (e.g., by using the "apiName" of the API). The API producer shall
                                 support this attribute.
                              type: string
                            dstIpAddress:
                              description: >
                                An IPV4 or IPV6 address. Representation: In case
                                of an IPV4 address, string that consists of four
                                decimal integers separated by dots, each integer
                                ranging from 0 to 255. In case of an IPV6
                                address, string that consists of groups of zero
                                to four hexadecimal digits, separated by colons.
                              type: string
                              format: IP
                            responseCodes:
                              description: >-
                                HTTP response codes or patterns to match. A list
                                of all valid HTTP response codes and their
                                specification documents can be obtained from the
                                HTTP status code registry. In addition, if
                                supported, the following patterns may be used
                                (case-insensitive): - "1XX": for matching any
                                kind of informational response. - "2XX": for
                                matching any kind of success response. - "3XX":
                                for matching any kind redirection response. -
                                "4XX": for matching any kind of client error
                                response. - "5XX": for matching any kind of
                                server error response.

                                The API producer shall support this attribute
                              type: array
                              items:
                                type: string
                            headerField:
                              description: >-
                                Name of the header field to be matched. The
                                header field name shall be one of the supported
                                fields in a request message as defined in clause
                                4.2.2 of ETSI GS NFV-SOL 013 or in a response
                                message as defined in clause 4.2.3 of ETSI GS
                                NFV-SOL 013, in accordance with the "direction"
                                criteria input. The API producer may support
                                this attribute.
                              type: string
                            headerValue:
                              description: >-
                                Value in the header to be matched. To match, the
                                value in the header field indicated by
                                "headerField" shall be the same as in this
                                attribute. Shall be provided if a "headerField"
                                is provided. The API producer may support this
                                attribute.
                              type: string
                            bodyValues:
                              description: >-
                                A list of strings to be matched in the body part
                                of the interface message (e.g., the body of an
                                HTTP message). If provided, only messages with
                                text in the body part containing all the values
                                from the list shall match the filter. In
                                addition to a matching filter for the body of
                                the message, a corresponding "headerField"
                                filter shall also be provided, with
                                "headerField" set to "Content-Type", to restrict
                                matching to appropriate textual payloads such as
                                "application/json" or "text/plain". The API
                                producer may support this attribute
                              type: string
                  servicesLogDetail:
                    description: >-
                      This type represents criteria for logging jobs to collect
                      logged messages about processes pertaining to NFV-MANO
                      services. It shall comply with the provisions defined in
                      table 8.6.3.4-1.
                    type: object
                    properties:
                      logGarbageCollection:
                        description: >-
                          Indicates to collect logged information about garbage
                          collection processes associated to NFV-MANO services.
                        type: boolean
                  systemLogDetail:
                    description: >-
                      This type represents criteria for logging jobs to collect
                      logged system events of the NFV-MANO functional entity. It
                      shall comply with the provisions defined in table
                      8.6.3.5-1.
                    type: object
                    required:
                      - systemLogs
                      - severityLevel
                    properties:
                      systemLogs:
                        description: >
                          This type represents a list of key-value pairs. The
                          order of the pairs in the list is not significant. In
                          JSON, a set of keyvalue pairs is represented as an
                          object. It shall comply with the provisions defined in
                          clause 4 of IETF RFC 8259. In the following example, a
                          list of key-value pairs with four keys ("aString",
                          "aNumber", "anArray" and "anObject") is provided to
                          illustrate that the values associated with different
                          keys can be of different type.
                        type: object
                      severityLevelScheme:
                        description: >-
                          Identifies a severity level scheme. The default value
                          is "rfc5424", which represents the set of values
                          specified in the clause 6.2.1, table 2 of IETF RFC
                          5424. Other values may be used to signal different
                          schemes.
                        type: string
                      severityLevel:
                        description: >-
                          The severity level, which determines the severity of
                          the system messages to collect. The NFV-MANO
                          functional entity shall collect system log messages,
                          as indicated by the "systemLogs" attribute, with
                          severity levels lower (i.e., more severe) or equal to
                          the value provided by this present attribute.
                        type: number
              jobConfig:
                description: >-
                  This type represents configuration data for a logging job. It
                  shall comply with the provisions defined in table 8.6.3.6-1.
                  NOTE: The present document version does not specify the
                  support for "log compilation and reporting based on events" as
                  specified in clause 6.6.2.2 of ETSI GS NFV-IFA 031.
                type: object
                required:
                  - reportingCondition
                  - securityConf
                properties:
                  startTime:
                    description: >
                      Date-time stamp. Representation: String formatted
                      according to IETF RFC 3339.
                    type: string
                    format: date-time
                  endTime:
                    description: >
                      Date-time stamp. Representation: String formatted
                      according to IETF RFC 3339.
                    type: string
                    format: date-time
                  reportingCondition:
                    description: >-
                      Specifies the condition under which the producer will
                      report to the consumer about the compiled log data.
                    required:
                      - reportingType
                    properties:
                      reportingType:
                        description: >-
                          Specifies the type of reporting condition. Permitted
                          values: - REPORTING_ON_COMPILATION: the producer shall
                          notify the consumer once the compilation of the
                                          collected logging data into a file is completed and a new log report is available.
                          - NO_REPORTING: no reporting is requested (the
                          consumer can query the logging jobs to know about the
                                          availability of new log reports).
                        type: string
                        enum:
                          - REPORTING_ON_COMPILATION
                          - NO_REPORTING
                      minimumReportingPeriod:
                        description: >-
                          Specifies the minimum periodicity at which the
                          producer will report to the consumer about the
                          collected log information, in seconds.
                        type: integer
                        format: int32
                  compileBySizeValue:
                    description: >-
                      An indicative size threshold for compiling the collected
                      log data, in bytes. It is used when the compilation is
                      based on the size of the collected log data. If not
                      present, a default value as specified with the
                      "defaultLogCompileBySizeValue" configuration in the
                      "ManoEntityConfigurableParams" shall be used
                    type: integer
                    format: int32
                  compileByTimerValue:
                    description: >-
                      The periodicity threshold for compiling the filtered log,
                      in seconds. It is used when the compilation is based on a
                      timer (e.g., every 24 hours). If not present, a default
                      value as specified with the
                      "defaultLogCompileByTimerValue" configuration in the
                      "ManoEntityConfigurableParams" shall be used
                    type: integer
                    format: int32
                  securityConf:
                    description: >-
                      Configuration about the security aspects of the logging
                      job.
                    type: object
                    properties:
                      logFileEncryption:
                        description: >-
                          Information about the encryption of the compiled log
                          files. Shall be present if the log file is requested
                          to be encrypted.
                        required:
                          - encryptionCertificate
                          - cipherAlgorithm
                        type: object
                        properties:
                          encryptionCertificate:
                            description: >-
                              X.509 certificate with the public key to use for
                              the encryption of the compiled log file.
                            type: string
                          cipherAlgorithm:
                            description: >-
                              Cryptographic algorithm to be used for the
                              encryption of the compiled log file. More than one
                              algorithm can be provided from higher (lower array
                              index) to lower (higher array index) precedence.
                              Valid values are: "AES-CBC-128", "AES-GCM-128",
                              "AES-CBC-256", and "AES-GCM-256", as specified in
                              clause 6.5 of ETSI GS NFV-SEC 012
                            type: array
                            items:
                              type: string
                              minItems: 1
                          encryptAndSignOrder:
                            description: >-
                              Indication about the order in signing and
                              encrypting the compiled log file. Valid values
                              are: "encryptFirst", to apply the order "first
                              encrypt, then sign", and "signFirst" for the order
                              "first sign, then encrypt". Default value is
                              "encryptFirst".
                            type: string
                      logTransferSecurity:
                        description: >-
                          Information about the security measures for
                          retrieving/accessing the compiled log files.
                        type: object
                        properties:
                          publicKey:
                            description: >-
                              The public key of the API consumer used for the
                              client authentication with the file server. Shall
                              be provided if required by the type of transfer
                              protocol. May be omitted if the key has been
                              provided to the API producer by other means, or if
                              it has already been provided in some previous
                              CreateLoggingJobRequest issued by the same API
                              consumer, whose public key has not changed.
                            type: string
              logReports:
                description: >-
                  Information about available log reports created by the logging
                  job.
                type: array
                items:
                  type: object
                  required:
                    - logReportId
                    - logReportLoc
                  properties:
                    logReportId:
                      description: >
                        An identifier with the intention of being globally
                        unique.
                      type: string
                    logReportLoc:
                      description: >
                        This type represents a link to a resource using an
                        absolute URI.
                      type: object
                      required:
                        - href
                      properties:
                        href:
                          description: |
                            String formatted according to IETF RFC 3986.
                          type: string
              _links:
                description: Links for this resource.
                type: object
                required:
                  - self
                properties:
                  self:
                    description: >
                      This type represents a link to a resource using an
                      absolute URI.
                    type: object
                    required:
                      - href
                    properties:
                      href:
                        description: |
                          String formatted according to IETF RFC 3986.
                        type: string
                  objects:
                    description: >-
                      Links to resources representing the object instances that
                      are logged. Shall be present if the logged object instance
                      information is accessible as a resource.
                    type: array
                    items:
                      description: >
                        This type represents a link to a resource using an
                        absolute URI.
                      type: object
                      required:
                        - href
                      properties:
                        href:
                          description: |
                            String formatted according to IETF RFC 3986.
                          type: string
    LoggingJob.Delete:
      description: >-
        Shall be returned when the logging job has been deleted successfully.
        The response body shall be empty.
      headers:
        WWW-Authenticate:
          description: >
            Challenge if the corresponding HTTP request has not provided
            authorization, or error details if the corresponding HTTP request
            has provided an invalid authorization token.
          schema:
            type: string
        Version:
          description: Version of the API used in the response.
          schema:
            type: string
    LoggingJob.Post:
      description: >-
        The response body contains the Application Context as it was created by
        the MEC system
      headers:
        Content-Type:
          description: The MIME type of the body of the response.
          schema:
            type: string
        WWW-Authenticate:
          description: >
            Challenge if the corresponding HTTP request has not provided
            authorization, or error details if the corresponding HTTP request
            has provided an invalid authorization token.
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
      content:
        application/json:
          schema:
            description: >-
              This type represents a logging job. It shall comply with the
              provisions defined in table 8.6.2.6-1.
            type: object
            required:
              - id
              - objectInstanceIds
              - jobCriteria
              - jobConfig
              - _links
            properties:
              id:
                description: |
                  An identifier with the intention of being globally unique.
                type: string
              objectInstanceIds:
                description: >-
                  Identifiers of the object instance for which logging
                  information is collected. This attribute shall contain the
                  identifier of the instance of the object that is logged
                  according to their type.
                type: array
                items:
                  description: >
                    This type represents the identifier to reference a managed
                    object of a  particular type. 
                  type: object
                  properties:
                    type:
                      description: >
                        Indicates the type of managed object. Permitted values:
                          - MANO_ENTITY
                          - MANO_SERVICE
                          - MANO_SERVICE_IF
                          - CONSUMED_MANO_IF
                          - MANO_ENTITY_COMPONENT

                        The "MANO_ENTITY COMPONENT" is only applicable if
                        attribute "manoEntityComponents" in "ManoEntity" is
                        supported by the API producer.
                      type: string
                      enum:
                        - MANO_ENTITY
                        - MANO_SERVICE
                        - MANO_SERVICE_IF
                        - CONSUMED_MANO_IF
                        - MANO_ENTITY_COMPONENT
                    objectId:
                      description: >
                        An identifier with the intention of being globally
                        unique.
                      type: string
                    subObjectId:
                      description: >
                        An identifier that is unique for the respective type
                        within a NFV-MANO functional entity, but that need not
                        be globally unique. Representation: string of variable
                        length..
                      type: string
                  required:
                    - type
                    - objectId
              jobCriteria:
                description: >-
                  This type represents collection criteria for logging jobs. It
                  shall comply with the provisions defined in table 8.6.3.2-1.
                type: object
                required:
                  - loggingType
                properties:
                  loggingType:
                    description: >-
                      Type of logging. This defines the types of logged
                      information to collect.

                      Permitted values: - MESSAGES: logged NFV-MANO service
                      interface messages. - SERVICES: logged messages about
                      processes pertaining to NFV-MANO services. - SYSTEM:
                      logged messages about the NFV-MANO functional entity’s
                      system enabled by the provider.
                    type: string
                    enum:
                      - MESSAGES
                      - SERVICES
                      - SYSTEM
                  messagesLogDetail:
                    description: >-
                      This type represents criteria for logging jobs to collect
                      logged messages on NFV-MANO service interfaces. It shall
                      comply with the provisions defined in table 8.6.3.3-1.
                    type: object
                    required:
                      - direction
                    properties:
                      direction:
                        description: >-
                          The direction of the interface messages to match.

                          Permitted values: - IN: input messages into the
                          interface. - OUT: output messages from the interface.
                          - ALL: both input and output messages into/from the
                          interface.
                        type: string
                        enum:
                          - IN
                          - OUT
                          - ALL
                      matchingPatterns:
                        description: >-
                          Patterns to be matched in the interface message. If
                          provided, only messages that match all the values
                          provided in the sub-attributes shall be logged. An API
                          consumer can provide more than one "matchingPattern"
                          if combinations of patterns are to be considered to
                          match diverse sets of interface messages.
                        type: array
                        items:
                          type: object
                          anyOf:
                            - required:
                                - srcIpAddress
                            - required:
                                - dstIpAddress
                            - required:
                                - requestMethod
                            - required:
                                - requestUriPattern
                            - required:
                                - responseCodes
                          properties:
                            srcIpAddress:
                              description: >
                                An IPV4 or IPV6 address. Representation: In case
                                of an IPV4 address, string that consists of four
                                decimal integers separated by dots, each integer
                                ranging from 0 to 255. In case of an IPV6
                                address, string that consists of groups of zero
                                to four hexadecimal digits, separated by colons.
                              type: string
                              format: IP
                            requestMethod:
                              description: >-
                                HTTP request method to be matched. To match, the
                                HTTP request method of the message shall be the
                                same as the value of this attribute. Valid
                                values are specified in IETF RFC 7231. The API
                                producer shall support this attribute.
                              type: string
                            requestUriPattern:
                              description: >-
                                Substring to be matched in the request URI. To
                                match, the request URI shall include the value
                                of
                                 this attribute as a substring. This is typically used to match messages which associate to RESTful
                                 resources, or to a specific API (e.g., by using the "apiName" of the API). The API producer shall
                                 support this attribute.
                              type: string
                            dstIpAddress:
                              description: >
                                An IPV4 or IPV6 address. Representation: In case
                                of an IPV4 address, string that consists of four
                                decimal integers separated by dots, each integer
                                ranging from 0 to 255. In case of an IPV6
                                address, string that consists of groups of zero
                                to four hexadecimal digits, separated by colons.
                              type: string
                              format: IP
                            responseCodes:
                              description: >-
                                HTTP response codes or patterns to match. A list
                                of all valid HTTP response codes and their
                                specification documents can be obtained from the
                                HTTP status code registry. In addition, if
                                supported, the following patterns may be used
                                (case-insensitive): - "1XX": for matching any
                                kind of informational response. - "2XX": for
                                matching any kind of success response. - "3XX":
                                for matching any kind redirection response. -
                                "4XX": for matching any kind of client error
                                response. - "5XX": for matching any kind of
                                server error response.

                                The API producer shall support this attribute
                              type: array
                              items:
                                type: string
                            headerField:
                              description: >-
                                Name of the header field to be matched. The
                                header field name shall be one of the supported
                                fields in a request message as defined in clause
                                4.2.2 of ETSI GS NFV-SOL 013 or in a response
                                message as defined in clause 4.2.3 of ETSI GS
                                NFV-SOL 013, in accordance with the "direction"
                                criteria input. The API producer may support
                                this attribute.
                              type: string
                            headerValue:
                              description: >-
                                Value in the header to be matched. To match, the
                                value in the header field indicated by
                                "headerField" shall be the same as in this
                                attribute. Shall be provided if a "headerField"
                                is provided. The API producer may support this
                                attribute.
                              type: string
                            bodyValues:
                              description: >-
                                A list of strings to be matched in the body part
                                of the interface message (e.g., the body of an
                                HTTP message). If provided, only messages with
                                text in the body part containing all the values
                                from the list shall match the filter. In
                                addition to a matching filter for the body of
                                the message, a corresponding "headerField"
                                filter shall also be provided, with
                                "headerField" set to "Content-Type", to restrict
                                matching to appropriate textual payloads such as
                                "application/json" or "text/plain". The API
                                producer may support this attribute
                              type: string
                  servicesLogDetail:
                    description: >-
                      This type represents criteria for logging jobs to collect
                      logged messages about processes pertaining to NFV-MANO
                      services. It shall comply with the provisions defined in
                      table 8.6.3.4-1.
                    type: object
                    properties:
                      logGarbageCollection:
                        description: >-
                          Indicates to collect logged information about garbage
                          collection processes associated to NFV-MANO services.
                        type: boolean
                  systemLogDetail:
                    description: >-
                      This type represents criteria for logging jobs to collect
                      logged system events of the NFV-MANO functional entity. It
                      shall comply with the provisions defined in table
                      8.6.3.5-1.
                    type: object
                    required:
                      - systemLogs
                      - severityLevel
                    properties:
                      systemLogs:
                        description: >
                          This type represents a list of key-value pairs. The
                          order of the pairs in the list is not significant. In
                          JSON, a set of keyvalue pairs is represented as an
                          object. It shall comply with the provisions defined in
                          clause 4 of IETF RFC 8259. In the following example, a
                          list of key-value pairs with four keys ("aString",
                          "aNumber", "anArray" and "anObject") is provided to
                          illustrate that the values associated with different
                          keys can be of different type.
                        type: object
                      severityLevelScheme:
                        description: >-
                          Identifies a severity level scheme. The default value
                          is "rfc5424", which represents the set of values
                          specified in the clause 6.2.1, table 2 of IETF RFC
                          5424. Other values may be used to signal different
                          schemes.
                        type: string
                      severityLevel:
                        description: >-
                          The severity level, which determines the severity of
                          the system messages to collect. The NFV-MANO
                          functional entity shall collect system log messages,
                          as indicated by the "systemLogs" attribute, with
                          severity levels lower (i.e., more severe) or equal to
                          the value provided by this present attribute.
                        type: number
              jobConfig:
                description: >-
                  This type represents configuration data for a logging job. It
                  shall comply with the provisions defined in table 8.6.3.6-1.
                  NOTE: The present document version does not specify the
                  support for "log compilation and reporting based on events" as
                  specified in clause 6.6.2.2 of ETSI GS NFV-IFA 031.
                type: object
                required:
                  - reportingCondition
                  - securityConf
                properties:
                  startTime:
                    description: >
                      Date-time stamp. Representation: String formatted
                      according to IETF RFC 3339.
                    type: string
                    format: date-time
                  endTime:
                    description: >
                      Date-time stamp. Representation: String formatted
                      according to IETF RFC 3339.
                    type: string
                    format: date-time
                  reportingCondition:
                    description: >-
                      Specifies the condition under which the producer will
                      report to the consumer about the compiled log data.
                    required:
                      - reportingType
                    properties:
                      reportingType:
                        description: >-
                          Specifies the type of reporting condition. Permitted
                          values: - REPORTING_ON_COMPILATION: the producer shall
                          notify the consumer once the compilation of the
                                          collected logging data into a file is completed and a new log report is available.
                          - NO_REPORTING: no reporting is requested (the
                          consumer can query the logging jobs to know about the
                                          availability of new log reports).
                        type: string
                        enum:
                          - REPORTING_ON_COMPILATION
                          - NO_REPORTING
                      minimumReportingPeriod:
                        description: >-
                          Specifies the minimum periodicity at which the
                          producer will report to the consumer about the
                          collected log information, in seconds.
                        type: integer
                        format: int32
                  compileBySizeValue:
                    description: >-
                      An indicative size threshold for compiling the collected
                      log data, in bytes. It is used when the compilation is
                      based on the size of the collected log data. If not
                      present, a default value as specified with the
                      "defaultLogCompileBySizeValue" configuration in the
                      "ManoEntityConfigurableParams" shall be used
                    type: integer
                    format: int32
                  compileByTimerValue:
                    description: >-
                      The periodicity threshold for compiling the filtered log,
                      in seconds. It is used when the compilation is based on a
                      timer (e.g., every 24 hours). If not present, a default
                      value as specified with the
                      "defaultLogCompileByTimerValue" configuration in the
                      "ManoEntityConfigurableParams" shall be used
                    type: integer
                    format: int32
                  securityConf:
                    description: >-
                      Configuration about the security aspects of the logging
                      job.
                    type: object
                    properties:
                      logFileEncryption:
                        description: >-
                          Information about the encryption of the compiled log
                          files. Shall be present if the log file is requested
                          to be encrypted.
                        required:
                          - encryptionCertificate
                          - cipherAlgorithm
                        type: object
                        properties:
                          encryptionCertificate:
                            description: >-
                              X.509 certificate with the public key to use for
                              the encryption of the compiled log file.
                            type: string
                          cipherAlgorithm:
                            description: >-
                              Cryptographic algorithm to be used for the
                              encryption of the compiled log file. More than one
                              algorithm can be provided from higher (lower array
                              index) to lower (higher array index) precedence.
                              Valid values are: "AES-CBC-128", "AES-GCM-128",
                              "AES-CBC-256", and "AES-GCM-256", as specified in
                              clause 6.5 of ETSI GS NFV-SEC 012
                            type: array
                            items:
                              type: string
                              minItems: 1
                          encryptAndSignOrder:
                            description: >-
                              Indication about the order in signing and
                              encrypting the compiled log file. Valid values
                              are: "encryptFirst", to apply the order "first
                              encrypt, then sign", and "signFirst" for the order
                              "first sign, then encrypt". Default value is
                              "encryptFirst".
                            type: string
                      logTransferSecurity:
                        description: >-
                          Information about the security measures for
                          retrieving/accessing the compiled log files.
                        type: object
                        properties:
                          publicKey:
                            description: >-
                              The public key of the API consumer used for the
                              client authentication with the file server. Shall
                              be provided if required by the type of transfer
                              protocol. May be omitted if the key has been
                              provided to the API producer by other means, or if
                              it has already been provided in some previous
                              CreateLoggingJobRequest issued by the same API
                              consumer, whose public key has not changed.
                            type: string
              logReports:
                description: >-
                  Information about available log reports created by the logging
                  job.
                type: array
                items:
                  type: object
                  required:
                    - logReportId
                    - logReportLoc
                  properties:
                    logReportId:
                      description: >
                        An identifier with the intention of being globally
                        unique.
                      type: string
                    logReportLoc:
                      description: >
                        This type represents a link to a resource using an
                        absolute URI.
                      type: object
                      required:
                        - href
                      properties:
                        href:
                          description: |
                            String formatted according to IETF RFC 3986.
                          type: string
              _links:
                description: Links for this resource.
                type: object
                required:
                  - self
                properties:
                  self:
                    description: >
                      This type represents a link to a resource using an
                      absolute URI.
                    type: object
                    required:
                      - href
                    properties:
                      href:
                        description: |
                          String formatted according to IETF RFC 3986.
                        type: string
                  objects:
                    description: >-
                      Links to resources representing the object instances that
                      are logged. Shall be present if the logged object instance
                      information is accessible as a resource.
                    type: array
                    items:
                      description: >
                        This type represents a link to a resource using an
                        absolute URI.
                      type: object
                      required:
                        - href
                      properties:
                        href:
                          description: |
                            String formatted according to IETF RFC 3986.
                          type: string
    LoggingJobs.Get:
      description: >-
        Shall be returned when information about zero or more logging jobs has
        been queried successfully.

        The response body shall contain in an array the representations of zero
        or more logging jobs, as defined in clause 8.6.2.6.

        If the "filter" URI parameter or one of the "all_fields", "fields" (if
        supported), "exclude_fields" (if supported) or "exclude_default" URI
        parameters was supplied in the request, the data in the response body
        shall have been transformed according to the rules specified in clauses
        5.2.2 and 5.3.2 of ETSI GS NFV-SOL 013, respectively.

        If the NFV-MANO functional entity supports alternative 2 (paging)
        according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 for this resource,
        inclusion of the Link HTTP header in this response shall follow the
        provisions in clause 5.4.2.3 of ETSI GS NFV-SOL 013.
      headers:
        Content-Type:
          description: The MIME type of the body of the response.
          schema:
            type: string
        WWW-Authenticate:
          description: >
            Challenge if the corresponding HTTP request has not provided
            authorization, or error details if the corresponding HTTP request
            has provided an invalid authorization token.
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
      content:
        application/json:
          schema:
            type: array
            items:
              description: >-
                This type represents a logging job. It shall comply with the
                provisions defined in table 8.6.2.6-1.
              type: object
              required:
                - id
                - objectInstanceIds
                - jobCriteria
                - jobConfig
                - _links
              properties:
                id:
                  description: |
                    An identifier with the intention of being globally unique.
                  type: string
                objectInstanceIds:
                  description: >-
                    Identifiers of the object instance for which logging
                    information is collected. This attribute shall contain the
                    identifier of the instance of the object that is logged
                    according to their type.
                  type: array
                  items:
                    description: >
                      This type represents the identifier to reference a managed
                      object of a  particular type. 
                    type: object
                    properties:
                      type:
                        description: >
                          Indicates the type of managed object. Permitted
                          values:
                            - MANO_ENTITY
                            - MANO_SERVICE
                            - MANO_SERVICE_IF
                            - CONSUMED_MANO_IF
                            - MANO_ENTITY_COMPONENT

                          The "MANO_ENTITY COMPONENT" is only applicable if
                          attribute "manoEntityComponents" in "ManoEntity" is
                          supported by the API producer.
                        type: string
                        enum:
                          - MANO_ENTITY
                          - MANO_SERVICE
                          - MANO_SERVICE_IF
                          - CONSUMED_MANO_IF
                          - MANO_ENTITY_COMPONENT
                      objectId:
                        description: >
                          An identifier with the intention of being globally
                          unique.
                        type: string
                      subObjectId:
                        description: >
                          An identifier that is unique for the respective type
                          within a NFV-MANO functional entity, but that need not
                          be globally unique. Representation: string of variable
                          length..
                        type: string
                    required:
                      - type
                      - objectId
                jobCriteria:
                  description: >-
                    This type represents collection criteria for logging jobs.
                    It shall comply with the provisions defined in table
                    8.6.3.2-1.
                  type: object
                  required:
                    - loggingType
                  properties:
                    loggingType:
                      description: >-
                        Type of logging. This defines the types of logged
                        information to collect.

                        Permitted values: - MESSAGES: logged NFV-MANO service
                        interface messages. - SERVICES: logged messages about
                        processes pertaining to NFV-MANO services. - SYSTEM:
                        logged messages about the NFV-MANO functional entity’s
                        system enabled by the provider.
                      type: string
                      enum:
                        - MESSAGES
                        - SERVICES
                        - SYSTEM
                    messagesLogDetail:
                      description: >-
                        This type represents criteria for logging jobs to
                        collect logged messages on NFV-MANO service interfaces.
                        It shall comply with the provisions defined in table
                        8.6.3.3-1.
                      type: object
                      required:
                        - direction
                      properties:
                        direction:
                          description: >-
                            The direction of the interface messages to match.

                            Permitted values: - IN: input messages into the
                            interface. - OUT: output messages from the
                            interface. - ALL: both input and output messages
                            into/from the interface.
                          type: string
                          enum:
                            - IN
                            - OUT
                            - ALL
                        matchingPatterns:
                          description: >-
                            Patterns to be matched in the interface message. If
                            provided, only messages that match all the values
                            provided in the sub-attributes shall be logged. An
                            API consumer can provide more than one
                            "matchingPattern" if combinations of patterns are to
                            be considered to match diverse sets of interface
                            messages.
                          type: array
                          items:
                            type: object
                            anyOf:
                              - required:
                                  - srcIpAddress
                              - required:
                                  - dstIpAddress
                              - required:
                                  - requestMethod
                              - required:
                                  - requestUriPattern
                              - required:
                                  - responseCodes
                            properties:
                              srcIpAddress:
                                description: >
                                  An IPV4 or IPV6 address. Representation: In
                                  case of an IPV4 address, string that consists
                                  of four decimal integers separated by dots,
                                  each integer ranging from 0 to 255. In case of
                                  an IPV6 address, string that consists of
                                  groups of zero to four hexadecimal digits,
                                  separated by colons.
                                type: string
                                format: IP
                              requestMethod:
                                description: >-
                                  HTTP request method to be matched. To match,
                                  the HTTP request method of the message shall
                                  be the same as the value of this attribute.
                                  Valid values are specified in IETF RFC 7231.
                                  The API producer shall support this attribute.
                                type: string
                              requestUriPattern:
                                description: >-
                                  Substring to be matched in the request URI. To
                                  match, the request URI shall include the value
                                  of
                                   this attribute as a substring. This is typically used to match messages which associate to RESTful
                                   resources, or to a specific API (e.g., by using the "apiName" of the API). The API producer shall
                                   support this attribute.
                                type: string
                              dstIpAddress:
                                description: >
                                  An IPV4 or IPV6 address. Representation: In
                                  case of an IPV4 address, string that consists
                                  of four decimal integers separated by dots,
                                  each integer ranging from 0 to 255. In case of
                                  an IPV6 address, string that consists of
                                  groups of zero to four hexadecimal digits,
                                  separated by colons.
                                type: string
                                format: IP
                              responseCodes:
                                description: >-
                                  HTTP response codes or patterns to match. A
                                  list of all valid HTTP response codes and
                                  their specification documents can be obtained
                                  from the HTTP status code registry. In
                                  addition, if supported, the following patterns
                                  may be used (case-insensitive): - "1XX": for
                                  matching any kind of informational response. -
                                  "2XX": for matching any kind of success
                                  response. - "3XX": for matching any kind
                                  redirection response. - "4XX": for matching
                                  any kind of client error response. - "5XX":
                                  for matching any kind of server error
                                  response.

                                  The API producer shall support this attribute
                                type: array
                                items:
                                  type: string
                              headerField:
                                description: >-
                                  Name of the header field to be matched. The
                                  header field name shall be one of the
                                  supported fields in a request message as
                                  defined in clause 4.2.2 of ETSI GS NFV-SOL 013
                                  or in a response message as defined in clause
                                  4.2.3 of ETSI GS NFV-SOL 013, in accordance
                                  with the "direction" criteria input. The API
                                  producer may support this attribute.
                                type: string
                              headerValue:
                                description: >-
                                  Value in the header to be matched. To match,
                                  the value in the header field indicated by
                                  "headerField" shall be the same as in this
                                  attribute. Shall be provided if a
                                  "headerField" is provided. The API producer
                                  may support this attribute.
                                type: string
                              bodyValues:
                                description: >-
                                  A list of strings to be matched in the body
                                  part of the interface message (e.g., the body
                                  of an HTTP message). If provided, only
                                  messages with text in the body part containing
                                  all the values from the list shall match the
                                  filter. In addition to a matching filter for
                                  the body of the message, a corresponding
                                  "headerField" filter shall also be provided,
                                  with "headerField" set to "Content-Type", to
                                  restrict matching to appropriate textual
                                  payloads such as "application/json" or
                                  "text/plain". The API producer may support
                                  this attribute
                                type: string
                    servicesLogDetail:
                      description: >-
                        This type represents criteria for logging jobs to
                        collect logged messages about processes pertaining to
                        NFV-MANO services. It shall comply with the provisions
                        defined in table 8.6.3.4-1.
                      type: object
                      properties:
                        logGarbageCollection:
                          description: >-
                            Indicates to collect logged information about
                            garbage collection processes associated to NFV-MANO
                            services.
                          type: boolean
                    systemLogDetail:
                      description: >-
                        This type represents criteria for logging jobs to
                        collect logged system events of the NFV-MANO functional
                        entity. It shall comply with the provisions defined in
                        table 8.6.3.5-1.
                      type: object
                      required:
                        - systemLogs
                        - severityLevel
                      properties:
                        systemLogs:
                          description: >
                            This type represents a list of key-value pairs. The
                            order of the pairs in the list is not significant.
                            In JSON, a set of keyvalue pairs is represented as
                            an object. It shall comply with the provisions
                            defined in clause 4 of IETF RFC 8259. In the
                            following example, a list of key-value pairs with
                            four keys ("aString", "aNumber", "anArray" and
                            "anObject") is provided to illustrate that the
                            values associated with different keys can be of
                            different type.
                          type: object
                        severityLevelScheme:
                          description: >-
                            Identifies a severity level scheme. The default
                            value is "rfc5424", which represents the set of
                            values specified in the clause 6.2.1, table 2 of
                            IETF RFC 5424. Other values may be used to signal
                            different schemes.
                          type: string
                        severityLevel:
                          description: >-
                            The severity level, which determines the severity of
                            the system messages to collect. The NFV-MANO
                            functional entity shall collect system log messages,
                            as indicated by the "systemLogs" attribute, with
                            severity levels lower (i.e., more severe) or equal
                            to the value provided by this present attribute.
                          type: number
                jobConfig:
                  description: >-
                    This type represents configuration data for a logging job.
                    It shall comply with the provisions defined in table
                    8.6.3.6-1. NOTE: The present document version does not
                    specify the support for "log compilation and reporting based
                    on events" as specified in clause 6.6.2.2 of ETSI GS NFV-IFA
                    031.
                  type: object
                  required:
                    - reportingCondition
                    - securityConf
                  properties:
                    startTime:
                      description: >
                        Date-time stamp. Representation: String formatted
                        according to IETF RFC 3339.
                      type: string
                      format: date-time
                    endTime:
                      description: >
                        Date-time stamp. Representation: String formatted
                        according to IETF RFC 3339.
                      type: string
                      format: date-time
                    reportingCondition:
                      description: >-
                        Specifies the condition under which the producer will
                        report to the consumer about the compiled log data.
                      required:
                        - reportingType
                      properties:
                        reportingType:
                          description: >-
                            Specifies the type of reporting condition. Permitted
                            values: - REPORTING_ON_COMPILATION: the producer
                            shall notify the consumer once the compilation of
                            the
                                            collected logging data into a file is completed and a new log report is available.
                            - NO_REPORTING: no reporting is requested (the
                            consumer can query the logging jobs to know about
                            the
                                            availability of new log reports).
                          type: string
                          enum:
                            - REPORTING_ON_COMPILATION
                            - NO_REPORTING
                        minimumReportingPeriod:
                          description: >-
                            Specifies the minimum periodicity at which the
                            producer will report to the consumer about the
                            collected log information, in seconds.
                          type: integer
                          format: int32
                    compileBySizeValue:
                      description: >-
                        An indicative size threshold for compiling the collected
                        log data, in bytes. It is used when the compilation is
                        based on the size of the collected log data. If not
                        present, a default value as specified with the
                        "defaultLogCompileBySizeValue" configuration in the
                        "ManoEntityConfigurableParams" shall be used
                      type: integer
                      format: int32
                    compileByTimerValue:
                      description: >-
                        The periodicity threshold for compiling the filtered
                        log, in seconds. It is used when the compilation is
                        based on a timer (e.g., every 24 hours). If not present,
                        a default value as specified with the
                        "defaultLogCompileByTimerValue" configuration in the
                        "ManoEntityConfigurableParams" shall be used
                      type: integer
                      format: int32
                    securityConf:
                      description: >-
                        Configuration about the security aspects of the logging
                        job.
                      type: object
                      properties:
                        logFileEncryption:
                          description: >-
                            Information about the encryption of the compiled log
                            files. Shall be present if the log file is requested
                            to be encrypted.
                          required:
                            - encryptionCertificate
                            - cipherAlgorithm
                          type: object
                          properties:
                            encryptionCertificate:
                              description: >-
                                X.509 certificate with the public key to use for
                                the encryption of the compiled log file.
                              type: string
                            cipherAlgorithm:
                              description: >-
                                Cryptographic algorithm to be used for the
                                encryption of the compiled log file. More than
                                one algorithm can be provided from higher (lower
                                array index) to lower (higher array index)
                                precedence. Valid values are: "AES-CBC-128",
                                "AES-GCM-128", "AES-CBC-256", and "AES-GCM-256",
                                as specified in clause 6.5 of ETSI GS NFV-SEC
                                012
                              type: array
                              items:
                                type: string
                                minItems: 1
                            encryptAndSignOrder:
                              description: >-
                                Indication about the order in signing and
                                encrypting the compiled log file. Valid values
                                are: "encryptFirst", to apply the order "first
                                encrypt, then sign", and "signFirst" for the
                                order "first sign, then encrypt". Default value
                                is "encryptFirst".
                              type: string
                        logTransferSecurity:
                          description: >-
                            Information about the security measures for
                            retrieving/accessing the compiled log files.
                          type: object
                          properties:
                            publicKey:
                              description: >-
                                The public key of the API consumer used for the
                                client authentication with the file server.
                                Shall be provided if required by the type of
                                transfer protocol. May be omitted if the key has
                                been provided to the API producer by other
                                means, or if it has already been provided in
                                some previous CreateLoggingJobRequest issued by
                                the same API consumer, whose public key has not
                                changed.
                              type: string
                logReports:
                  description: >-
                    Information about available log reports created by the
                    logging job.
                  type: array
                  items:
                    type: object
                    required:
                      - logReportId
                      - logReportLoc
                    properties:
                      logReportId:
                        description: >
                          An identifier with the intention of being globally
                          unique.
                        type: string
                      logReportLoc:
                        description: >
                          This type represents a link to a resource using an
                          absolute URI.
                        type: object
                        required:
                          - href
                        properties:
                          href:
                            description: |
                              String formatted according to IETF RFC 3986.
                            type: string
                _links:
                  description: Links for this resource.
                  type: object
                  required:
                    - self
                  properties:
                    self:
                      description: >
                        This type represents a link to a resource using an
                        absolute URI.
                      type: object
                      required:
                        - href
                      properties:
                        href:
                          description: |
                            String formatted according to IETF RFC 3986.
                          type: string
                    objects:
                      description: >-
                        Links to resources representing the object instances
                        that are logged. Shall be present if the logged object
                        instance information is accessible as a resource.
                      type: array
                      items:
                        description: >
                          This type represents a link to a resource using an
                          absolute URI.
                        type: object
                        required:
                          - href
                        properties:
                          href:
                            description: |
                              String formatted according to IETF RFC 3986.
                            type: string
    LogReportAvailableNotification.Post:
      description: Shall be returned when the notification has been delivered successfully.
      headers:
        Content-Type:
          description: The MIME type of the body of the response.
          schema:
            type: string
        WWW-Authenticate:
          description: >
            Challenge if the corresponding HTTP request has not provided
            authorization, or error details if the corresponding HTTP request
            has provided an invalid authorization token.
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
    LogReportNotification.Get:
      description: >-
        Shall be returned to indicate that the notification endpoint has been
        tested successfully. The response body shall be empty.
      headers:
        Content-Type:
          description: The MIME type of the body of the response.
          schema:
            type: string
        WWW-Authenticate:
          description: >
            Challenge if the corresponding HTTP request has not provided
            authorization, or error details if the corresponding HTTP request
            has provided an invalid authorization token.
          schema:
            type: string
        Version:
          description: |
            Version of the API used in the response.
          schema:
            type: string
  schemas:
    LogmSubscription:
      description: >-
        This type represents a subscription. It shall comply with the provisions
        defined in table 8.6.2.3-1.
      type: object
      required:
        - id
        - callbackUri
        - _links
      properties:
        id:
          description: |
            An identifier with the intention of being globally unique.
          type: string
        filter:
          description: >-
            This type represents a filter that can be used to subscribe for
            notifications related to log management events. It shall comply with
            the provisions defined in table 8.6.3.7-1. At a particular nesting
            level in the filter structure, the following applies: All attributes
            shall match in order for the filter to match (logical "and" between
            different filter attributes). If an attribute is an array, the
            attribute shall match if at least one of the values in the array
            matches (logical "or" between the values of one filter attribute).
          type: object
          properties:
            objectInstanceFilter:
              description: >-
                This type represents subscription filter criteria to match
                NFV-MANO functional entities and their associated managed
                objects. It shall comply with the provisions defined in Table
                4.3.2.2-1.
              type: object
              anyOf:
                - oneOf:
                    - required:
                        - manoServiceIds
                    - required:
                        - manoServiceNames
                - oneOf:
                    - required:
                        - manoServiceInterfaceIds
                    - required:
                        - manoServiceInterfaceNames
                - oneOf:
                    - required:
                        - consumedManoInterfaceIds
                    - required:
                        - consumedManoInterfaceNames
              properties:
                manoEntityId:
                  description: |
                    An identifier with the intention of being globally unique.
                  type: string
                manoServiceIds:
                  description: >-
                    If present, match NFV-MANO services with an instance
                    identifier listed in this attribute.
                  type: array
                  items:
                    description: >
                      An identifier that is unique for the respective type
                      within a NFV-MANO functional entity, but that need not be
                      globally unique. Representation: string of variable
                      length..
                    type: string
                manoServiceNames:
                  description: >-
                    If present, match NFV-MANO services with an NFV-MANO service
                    name listed in this attribute.
                  type: array
                  items:
                    type: string
                manoServiceInterfaceIds:
                  description: >-
                    If present, match NFV-MANO functional entity produced
                    interfaces with an instance identifier listed in this
                    attribute.
                  type: array
                  items:
                    description: >
                      An identifier that is unique for the respective type
                      within a NFV-MANO functional entity, but that need not be
                      globally unique. Representation: string of variable
                      length..
                    type: string
                manoServiceInterfaceNames:
                  description: >-
                    If present, match NFV-MANO functional entity produced
                    interfaces with an instance Name listed in this attribute.
                  type: array
                  items:
                    type: string
                consumedManoInterfaceIds:
                  description: >-
                    If present, match NFV-MANO functional entity consumed
                    interfaces with an instance identifier listed in this
                    attribute.
                  type: array
                  items:
                    description: |
                      An identifier with the intention of being globally unique.
                    type: string
                consumedManoInterfaceNames:
                  description: >-
                    If present, match NFV-MANO functional entity consumed
                    interfaces with an instance Name listed in this attribute.
                  type: array
                  items:
                    type: string
            notificationTypes:
              description: >-
                Match particular notification types. Permitted values: -
                LogReportAvailableNotification
              type: string
              enum:
                - LogReportAvailableNotification
        callbackUri:
          description: |
            String formatted according to IETF RFC 3986.
          type: string
        _links:
          description: Links to resources related to this resource.
          type: object
          required:
            - self
          properties:
            self:
              description: |
                This type represents a link to a resource using an absolute URI.
              type: object
              required:
                - href
              properties:
                href:
                  description: |
                    String formatted according to IETF RFC 3986.
                  type: string
    LogmNotificationsFilter:
      description: >-
        This type represents a filter that can be used to subscribe for
        notifications related to log management events. It shall comply with the
        provisions defined in table 8.6.3.7-1. At a particular nesting level in
        the filter structure, the following applies: All attributes shall match
        in order for the filter to match (logical "and" between different filter
        attributes). If an attribute is an array, the attribute shall match if
        at least one of the values in the array matches (logical "or" between
        the values of one filter attribute).
      type: object
      properties:
        objectInstanceFilter:
          description: >-
            This type represents subscription filter criteria to match NFV-MANO
            functional entities and their associated managed objects. It shall
            comply with the provisions defined in Table 4.3.2.2-1.
          type: object
          anyOf:
            - oneOf:
                - required:
                    - manoServiceIds
                - required:
                    - manoServiceNames
            - oneOf:
                - required:
                    - manoServiceInterfaceIds
                - required:
                    - manoServiceInterfaceNames
            - oneOf:
                - required:
                    - consumedManoInterfaceIds
                - required:
                    - consumedManoInterfaceNames
          properties:
            manoEntityId:
              description: |
                An identifier with the intention of being globally unique.
              type: string
            manoServiceIds:
              description: >-
                If present, match NFV-MANO services with an instance identifier
                listed in this attribute.
              type: array
              items:
                description: >
                  An identifier that is unique for the respective type within a
                  NFV-MANO functional entity, but that need not be globally
                  unique. Representation: string of variable length..
                type: string
            manoServiceNames:
              description: >-
                If present, match NFV-MANO services with an NFV-MANO service
                name listed in this attribute.
              type: array
              items:
                type: string
            manoServiceInterfaceIds:
              description: >-
                If present, match NFV-MANO functional entity produced interfaces
                with an instance identifier listed in this attribute.
              type: array
              items:
                description: >
                  An identifier that is unique for the respective type within a
                  NFV-MANO functional entity, but that need not be globally
                  unique. Representation: string of variable length..
                type: string
            manoServiceInterfaceNames:
              description: >-
                If present, match NFV-MANO functional entity produced interfaces
                with an instance Name listed in this attribute.
              type: array
              items:
                type: string
            consumedManoInterfaceIds:
              description: >-
                If present, match NFV-MANO functional entity consumed interfaces
                with an instance identifier listed in this attribute.
              type: array
              items:
                description: |
                  An identifier with the intention of being globally unique.
                type: string
            consumedManoInterfaceNames:
              description: >-
                If present, match NFV-MANO functional entity consumed interfaces
                with an instance Name listed in this attribute.
              type: array
              items:
                type: string
        notificationTypes:
          description: >-
            Match particular notification types. Permitted values: -
            LogReportAvailableNotification
          type: string
          enum:
            - LogReportAvailableNotification
    ManoEntitySubscriptionFilter:
      description: >-
        This type represents subscription filter criteria to match NFV-MANO
        functional entities and their associated managed objects. It shall
        comply with the provisions defined in Table 4.3.2.2-1.
      type: object
      anyOf:
        - oneOf:
            - required:
                - manoServiceIds
            - required:
                - manoServiceNames
        - oneOf:
            - required:
                - manoServiceInterfaceIds
            - required:
                - manoServiceInterfaceNames
        - oneOf:
            - required:
                - consumedManoInterfaceIds
            - required:
                - consumedManoInterfaceNames
      properties:
        manoEntityId:
          description: |
            An identifier with the intention of being globally unique.
          type: string
        manoServiceIds:
          description: >-
            If present, match NFV-MANO services with an instance identifier
            listed in this attribute.
          type: array
          items:
            description: >
              An identifier that is unique for the respective type within a
              NFV-MANO functional entity, but that need not be globally unique.
              Representation: string of variable length..
            type: string
        manoServiceNames:
          description: >-
            If present, match NFV-MANO services with an NFV-MANO service name
            listed in this attribute.
          type: array
          items:
            type: string
        manoServiceInterfaceIds:
          description: >-
            If present, match NFV-MANO functional entity produced interfaces
            with an instance identifier listed in this attribute.
          type: array
          items:
            description: >
              An identifier that is unique for the respective type within a
              NFV-MANO functional entity, but that need not be globally unique.
              Representation: string of variable length..
            type: string
        manoServiceInterfaceNames:
          description: >-
            If present, match NFV-MANO functional entity produced interfaces
            with an instance Name listed in this attribute.
          type: array
          items:
            type: string
        consumedManoInterfaceIds:
          description: >-
            If present, match NFV-MANO functional entity consumed interfaces
            with an instance identifier listed in this attribute.
          type: array
          items:
            description: |
              An identifier with the intention of being globally unique.
            type: string
        consumedManoInterfaceNames:
          description: >-
            If present, match NFV-MANO functional entity consumed interfaces
            with an instance Name listed in this attribute.
          type: array
          items:
            type: string
    CompileLogRequest:
      description: >
        This type represents a request to compile the logged data associated to
        an object instance. It shall comply with the provisions defined in table
        8.6.2.8-1.
      type: object
      properties:
        objectInstanceId:
          description: >
            This type represents the identifier to reference a managed object of
            a  particular type. 
          type: object
          properties:
            type:
              description: >
                Indicates the type of managed object. Permitted values:
                  - MANO_ENTITY
                  - MANO_SERVICE
                  - MANO_SERVICE_IF
                  - CONSUMED_MANO_IF
                  - MANO_ENTITY_COMPONENT

                The "MANO_ENTITY COMPONENT" is only applicable if attribute
                "manoEntityComponents" in "ManoEntity" is supported by the API
                producer.
              type: string
              enum:
                - MANO_ENTITY
                - MANO_SERVICE
                - MANO_SERVICE_IF
                - CONSUMED_MANO_IF
                - MANO_ENTITY_COMPONENT
            objectId:
              description: |
                An identifier with the intention of being globally unique.
              type: string
            subObjectId:
              description: >
                An identifier that is unique for the respective type within a
                NFV-MANO functional entity, but that need not be globally
                unique. Representation: string of variable length..
              type: string
          required:
            - type
            - objectId
    LogReport:
      description: >
        This type represents a log report, which provides information about a
        compiled log and how to obtain it. It shall comply with the provisions
        defined in table 8.6.2.7-1.
      type: object
      required:
        - id
        - objectInstanceId
        - compilationTrigger
        - readyTime
        - fileFormat
        - fileLocationInfo
        - securityAndIntegrityInfo
        - _links
      properties:
        id:
          description: |
            An identifier with the intention of being globally unique.
          type: string
        objectInstanceId:
          description: >
            This type represents the identifier to reference a managed object of
            a  particular type. 
          type: object
          properties:
            type:
              description: >
                Indicates the type of managed object. Permitted values:
                  - MANO_ENTITY
                  - MANO_SERVICE
                  - MANO_SERVICE_IF
                  - CONSUMED_MANO_IF
                  - MANO_ENTITY_COMPONENT

                The "MANO_ENTITY COMPONENT" is only applicable if attribute
                "manoEntityComponents" in "ManoEntity" is supported by the API
                producer.
              type: string
              enum:
                - MANO_ENTITY
                - MANO_SERVICE
                - MANO_SERVICE_IF
                - CONSUMED_MANO_IF
                - MANO_ENTITY_COMPONENT
            objectId:
              description: |
                An identifier with the intention of being globally unique.
              type: string
            subObjectId:
              description: >
                An identifier that is unique for the respective type within a
                NFV-MANO functional entity, but that need not be globally
                unique. Representation: string of variable length..
              type: string
          required:
            - type
            - objectId
        compilationTrigger:
          description: >-
            The trigger for the compilation of the log file.

            Permitted values: - ON_DEMAND: created based on explicit request by
            a client. - AUTOMATIC: created according to the logging job
            compilation configuration.
          type: string
          enum:
            - ON_DEMAND
            - AUTOMATIC
        readyTime:
          description: >
            Date-time stamp. Representation: String formatted according to IETF
            RFC 3339.
          type: string
          format: date-time
        expiryTime:
          description: >
            Date-time stamp. Representation: String formatted according to IETF
            RFC 3339.
          type: string
          format: date-time
        fileSize:
          description: 'The size of the compiled log file in bytes, if known.'
          type: integer
          format: int32
        fileFormat:
          description: The encoding used by the file.
          type: string
        fileLocationInfo:
          description: >-
            Location and address information of the compiled log file. The
            consumer can use this information to obtain the compiled log file.
          type: object
          required:
            - protocol
            - fileEndpoint
          properties:
            protocol:
              description: >-
                Protocol over which the compiled log file can be retrieved.

                Permitted values: - HTTPS: transmission over HTTP Secure
                (HTTPS). - SFTP: transmission over SSH file transfer protocol
                (SFTP). - SCP: transmission over secure copy protocol (SCP). -
                FTPS: transmission over file transfer protocol secure (FTPS), as
                specified in IETF RFC 2228 [i.11],
                     using explicit mode as specified in IETF RFC 4217 [i.12]. If FTPS is supported, "private" protection level shall be used.

                HTTPS shall be supported, and other protocols may be supported.
              type: string
              enum:
                - HTTPS
                - SFTP
                - SCP
                - FTPS
            fileEndpoint:
              description: >-
                The host name (or IP address), optionally a port number (if the
                host with the compile log file uses a non-standard port number
                as per the supported transmission protocol), a valid file
                directory path, and the file name of the compiled log file, or a
                valid URL.
              type: string
              format: URI
        securityAndIntegrityInfo:
          description: >-
            Security and integrity information for the compilation of the log
            files.
          type: object
          required:
            - algorithm
            - hash
            - logFileSignature
            - signingCertificate
          properties:
            algorithm:
              description: >-
                Algorithm used to generate the hash of the compiled log file.
                Only SHA-256 and SHA-512 shall be used
              type: string
            hash:
              description: >-
                The hexadecimal value of the hash of the compiled log file. The
                hash shall be computed from the encrypted compiled log file, in
                case the encryption applies.
              type: string
            encryptionPublicKey:
              description: >-
                Public key used for the encryption of the compiled log file.
                Shall be present if the compiled log file is encrypted.
              type: string
            cipherAlgorithm:
              description: >-
                The cryptographic algorithm used for the encryption. Shall be
                present if the compiled log file is encrypted. Valid values are:
                "AES-CBC-128", "AES-GCM-128", "AES-CBC-256", and "AES-GCM-256",
                as specified in clause 6.5 of ETSI GS NFV-SEC 012 [14].
              type: string
            logFileSignature:
              description: >-
                Signature to the compiled log file generated with the NFV-MANO
                functional entity’s private key, which is used to ensure the
                authenticity of the compiled log file. The signature shall be
                applied according to the "encryptAndSignOrder" of the
                "LoggingJobConfig".
              type: string
            signingCertificate:
              description: >-
                X.509 certificate with the NFV-MANO functional entity’s public
                key used for verifying the log report and compiled log file
                signatures.
              type: string
        _links:
          description: Links for this resource.
          type: object
          required:
            - self
          properties:
            self:
              description: |
                This type represents a link to a resource using an absolute URI.
              type: object
              required:
                - href
              properties:
                href:
                  description: |
                    String formatted according to IETF RFC 3986.
                  type: string
            objects:
              description: >-
                Links to resources representing the object instances that are
                logged. Shall be present if the logged object instance
                information is accessible as a resource.
              type: array
              items:
                description: >
                  This type represents a link to a resource using an absolute
                  URI.
                type: object
                required:
                  - href
                properties:
                  href:
                    description: |
                      String formatted according to IETF RFC 3986.
                    type: string
    LogmSubscriptionRequest:
      description: >-
        Information on application context created by the MEC system type:
        object
      required:
        - callbackUri
      type: object
      properties:
        filter:
          description: >-
            This type represents a filter that can be used to subscribe for
            notifications related to log management events. It shall comply with
            the provisions defined in table 8.6.3.7-1. At a particular nesting
            level in the filter structure, the following applies: All attributes
            shall match in order for the filter to match (logical "and" between
            different filter attributes). If an attribute is an array, the
            attribute shall match if at least one of the values in the array
            matches (logical "or" between the values of one filter attribute).
          type: object
          properties:
            objectInstanceFilter:
              description: >-
                This type represents subscription filter criteria to match
                NFV-MANO functional entities and their associated managed
                objects. It shall comply with the provisions defined in Table
                4.3.2.2-1.
              type: object
              anyOf:
                - oneOf:
                    - required:
                        - manoServiceIds
                    - required:
                        - manoServiceNames
                - oneOf:
                    - required:
                        - manoServiceInterfaceIds
                    - required:
                        - manoServiceInterfaceNames
                - oneOf:
                    - required:
                        - consumedManoInterfaceIds
                    - required:
                        - consumedManoInterfaceNames
              properties:
                manoEntityId:
                  description: |
                    An identifier with the intention of being globally unique.
                  type: string
                manoServiceIds:
                  description: >-
                    If present, match NFV-MANO services with an instance
                    identifier listed in this attribute.
                  type: array
                  items:
                    description: >
                      An identifier that is unique for the respective type
                      within a NFV-MANO functional entity, but that need not be
                      globally unique. Representation: string of variable
                      length..
                    type: string
                manoServiceNames:
                  description: >-
                    If present, match NFV-MANO services with an NFV-MANO service
                    name listed in this attribute.
                  type: array
                  items:
                    type: string
                manoServiceInterfaceIds:
                  description: >-
                    If present, match NFV-MANO functional entity produced
                    interfaces with an instance identifier listed in this
                    attribute.
                  type: array
                  items:
                    description: >
                      An identifier that is unique for the respective type
                      within a NFV-MANO functional entity, but that need not be
                      globally unique. Representation: string of variable
                      length..
                    type: string
                manoServiceInterfaceNames:
                  description: >-
                    If present, match NFV-MANO functional entity produced
                    interfaces with an instance Name listed in this attribute.
                  type: array
                  items:
                    type: string
                consumedManoInterfaceIds:
                  description: >-
                    If present, match NFV-MANO functional entity consumed
                    interfaces with an instance identifier listed in this
                    attribute.
                  type: array
                  items:
                    description: |
                      An identifier with the intention of being globally unique.
                    type: string
                consumedManoInterfaceNames:
                  description: >-
                    If present, match NFV-MANO functional entity consumed
                    interfaces with an instance Name listed in this attribute.
                  type: array
                  items:
                    type: string
            notificationTypes:
              description: >-
                Match particular notification types. Permitted values: -
                LogReportAvailableNotification
              type: string
              enum:
                - LogReportAvailableNotification
        callbackUri:
          description: |
            String formatted according to IETF RFC 3986.
          type: string
        authentication:
          type: object
          required:
            - authType
          properties:
            authType:
              description: >
                Defines the types of Authentication / Authorization which the
                API consumer is willing to accept when receiving a notification.
                Permitted values: * BASIC: In every HTTP request to the
                notification endpoint, use
                  HTTP Basic authentication with the client credentials.
                * OAUTH2_CLIENT_CREDENTIALS: In every HTTP request to the
                  notification endpoint, use an OAuth 2.0 Bearer token, obtained
                  using the client credentials grant type.
                * TLS_CERT: Every HTTP request to the notification endpoint is
                sent
                  over a mutually authenticated TLS session, i.e. not only the
                  server is authenticated, but also the client is authenticated
                  during the TLS tunnel setup.
              type: array
              items:
                type: string
                enum:
                  - BASIC
                  - OAUTH2_CLIENT_CREDENTIALS
                  - TLS_CERT
            paramsBasic:
              description: >
                Parameters for authentication/authorization using BASIC. Shall
                be present if authType is "BASIC" and the contained information
                has not been provisioned out of band. Shall be absent otherwise.
              type: object
              properties:
                userName:
                  description: >
                    Username to be used in HTTP Basic authentication. Shall be
                    present if it has not been provisioned out of band.
                  type: string
                password:
                  description: >
                    Password to be used in HTTP Basic authentication. Shall be
                    present if it has not been provisioned out of band.
                  type: string
            paramsOauth2ClientCredentials:
              description: >
                Parameters for authentication/authorization using
                OAUTH2_CLIENT_CREDENTIALS. Shall be present if authType is
                "OAUTH2_CLIENT_CREDENTIALS" and the contained information has
                not been provisioned out of band. Shall be absent otherwise.
              type: object
              properties:
                clientId:
                  description: >
                    Client identifier to be used in the access token request of
                    the OAuth 2.0 client credentials grant type. Shall be
                    present if it has not been provisioned out of band. The
                    clientId and clientPassword passed in a subscription shall
                    not be the same as the clientId and clientPassword that are
                    used to obtain authorization for API requests. Client
                    credentials may differ between subscriptions. The value of
                    clientPassword should be generated by a random process.
                  type: string
                clientPassword:
                  description: >
                    Client password to be used in the access token request of
                    the OAuth 2.0 client credentials grant type. Shall be
                    present if it has not been provisioned out of band. The
                    clientId and clientPassword passed in a subscription shall
                    not be the same as the clientId and clientPassword that are
                    used to obtain authorization for API requests. Client
                    credentials may differ between subscriptions. The value of
                    clientPassword should be generated by a random process.
                  type: string
                tokenEndpoint:
                  description: |
                    String formatted according to IETF RFC 3986.
                  type: string
    CreateLoggingJobRequest:
      description: Information on application context created by the MEC system
      type: object
      required:
        - objectInstanceIds
        - jobCriteria
        - jobConfig
      properties:
        objectInstanceIds:
          description: >-
            Identifiers of the object instance for which logging information is
            requested to be collected. This attribute shall contain the
            identifier of the instance of the object to be logged according to
            their type. If more than one identifier is provided, values shall
            all refer to object instances of the same type, for which the same
            criteria is then applicable.
          type: array
          minItems: 1
          items:
            description: >
              This type represents the identifier to reference a managed object
              of a  particular type. 
            type: object
            properties:
              type:
                description: >
                  Indicates the type of managed object. Permitted values:
                    - MANO_ENTITY
                    - MANO_SERVICE
                    - MANO_SERVICE_IF
                    - CONSUMED_MANO_IF
                    - MANO_ENTITY_COMPONENT

                  The "MANO_ENTITY COMPONENT" is only applicable if attribute
                  "manoEntityComponents" in "ManoEntity" is supported by the API
                  producer.
                type: string
                enum:
                  - MANO_ENTITY
                  - MANO_SERVICE
                  - MANO_SERVICE_IF
                  - CONSUMED_MANO_IF
                  - MANO_ENTITY_COMPONENT
              objectId:
                description: |
                  An identifier with the intention of being globally unique.
                type: string
              subObjectId:
                description: >
                  An identifier that is unique for the respective type within a
                  NFV-MANO functional entity, but that need not be globally
                  unique. Representation: string of variable length..
                type: string
            required:
              - type
              - objectId
        jobCriteria:
          description: >-
            This type represents collection criteria for logging jobs. It shall
            comply with the provisions defined in table 8.6.3.2-1.
          type: object
          required:
            - loggingType
          properties:
            loggingType:
              description: >-
                Type of logging. This defines the types of logged information to
                collect.

                Permitted values: - MESSAGES: logged NFV-MANO service interface
                messages. - SERVICES: logged messages about processes pertaining
                to NFV-MANO services. - SYSTEM: logged messages about the
                NFV-MANO functional entity’s system enabled by the provider.
              type: string
              enum:
                - MESSAGES
                - SERVICES
                - SYSTEM
            messagesLogDetail:
              description: >-
                This type represents criteria for logging jobs to collect logged
                messages on NFV-MANO service interfaces. It shall comply with
                the provisions defined in table 8.6.3.3-1.
              type: object
              required:
                - direction
              properties:
                direction:
                  description: >-
                    The direction of the interface messages to match.

                    Permitted values: - IN: input messages into the interface. -
                    OUT: output messages from the interface. - ALL: both input
                    and output messages into/from the interface.
                  type: string
                  enum:
                    - IN
                    - OUT
                    - ALL
                matchingPatterns:
                  description: >-
                    Patterns to be matched in the interface message. If
                    provided, only messages that match all the values provided
                    in the sub-attributes shall be logged. An API consumer can
                    provide more than one "matchingPattern" if combinations of
                    patterns are to be considered to match diverse sets of
                    interface messages.
                  type: array
                  items:
                    type: object
                    anyOf:
                      - required:
                          - srcIpAddress
                      - required:
                          - dstIpAddress
                      - required:
                          - requestMethod
                      - required:
                          - requestUriPattern
                      - required:
                          - responseCodes
                    properties:
                      srcIpAddress:
                        description: >
                          An IPV4 or IPV6 address. Representation: In case of an
                          IPV4 address, string that consists of four decimal
                          integers separated by dots, each integer ranging from
                          0 to 255. In case of an IPV6 address, string that
                          consists of groups of zero to four hexadecimal digits,
                          separated by colons.
                        type: string
                        format: IP
                      requestMethod:
                        description: >-
                          HTTP request method to be matched. To match, the HTTP
                          request method of the message shall be the same as the
                          value of this attribute. Valid values are specified in
                          IETF RFC 7231. The API producer shall support this
                          attribute.
                        type: string
                      requestUriPattern:
                        description: >-
                          Substring to be matched in the request URI. To match,
                          the request URI shall include the value of
                           this attribute as a substring. This is typically used to match messages which associate to RESTful
                           resources, or to a specific API (e.g., by using the "apiName" of the API). The API producer shall
                           support this attribute.
                        type: string
                      dstIpAddress:
                        description: >
                          An IPV4 or IPV6 address. Representation: In case of an
                          IPV4 address, string that consists of four decimal
                          integers separated by dots, each integer ranging from
                          0 to 255. In case of an IPV6 address, string that
                          consists of groups of zero to four hexadecimal digits,
                          separated by colons.
                        type: string
                        format: IP
                      responseCodes:
                        description: >-
                          HTTP response codes or patterns to match. A list of
                          all valid HTTP response codes and their specification
                          documents can be obtained from the HTTP status code
                          registry. In addition, if supported, the following
                          patterns may be used (case-insensitive): - "1XX": for
                          matching any kind of informational response. - "2XX":
                          for matching any kind of success response. - "3XX":
                          for matching any kind redirection response. - "4XX":
                          for matching any kind of client error response. -
                          "5XX": for matching any kind of server error response.

                          The API producer shall support this attribute
                        type: array
                        items:
                          type: string
                      headerField:
                        description: >-
                          Name of the header field to be matched. The header
                          field name shall be one of the supported fields in a
                          request message as defined in clause 4.2.2 of ETSI GS
                          NFV-SOL 013 or in a response message as defined in
                          clause 4.2.3 of ETSI GS NFV-SOL 013, in accordance
                          with the "direction" criteria input. The API producer
                          may support this attribute.
                        type: string
                      headerValue:
                        description: >-
                          Value in the header to be matched. To match, the value
                          in the header field indicated by "headerField" shall
                          be the same as in this attribute. Shall be provided if
                          a "headerField" is provided. The API producer may
                          support this attribute.
                        type: string
                      bodyValues:
                        description: >-
                          A list of strings to be matched in the body part of
                          the interface message (e.g., the body of an HTTP
                          message). If provided, only messages with text in the
                          body part containing all the values from the list
                          shall match the filter. In addition to a matching
                          filter for the body of the message, a corresponding
                          "headerField" filter shall also be provided, with
                          "headerField" set to "Content-Type", to restrict
                          matching to appropriate textual payloads such as
                          "application/json" or "text/plain". The API producer
                          may support this attribute
                        type: string
            servicesLogDetail:
              description: >-
                This type represents criteria for logging jobs to collect logged
                messages about processes pertaining to NFV-MANO services. It
                shall comply with the provisions defined in table 8.6.3.4-1.
              type: object
              properties:
                logGarbageCollection:
                  description: >-
                    Indicates to collect logged information about garbage
                    collection processes associated to NFV-MANO services.
                  type: boolean
            systemLogDetail:
              description: >-
                This type represents criteria for logging jobs to collect logged
                system events of the NFV-MANO functional entity. It shall comply
                with the provisions defined in table 8.6.3.5-1.
              type: object
              required:
                - systemLogs
                - severityLevel
              properties:
                systemLogs:
                  description: >
                    This type represents a list of key-value pairs. The order of
                    the pairs in the list is not significant. In JSON, a set of
                    keyvalue pairs is represented as an object. It shall comply
                    with the provisions defined in clause 4 of IETF RFC 8259. In
                    the following example, a list of key-value pairs with four
                    keys ("aString", "aNumber", "anArray" and "anObject") is
                    provided to illustrate that the values associated with
                    different keys can be of different type.
                  type: object
                severityLevelScheme:
                  description: >-
                    Identifies a severity level scheme. The default value is
                    "rfc5424", which represents the set of values specified in
                    the clause 6.2.1, table 2 of IETF RFC 5424. Other values may
                    be used to signal different schemes.
                  type: string
                severityLevel:
                  description: >-
                    The severity level, which determines the severity of the
                    system messages to collect. The NFV-MANO functional entity
                    shall collect system log messages, as indicated by the
                    "systemLogs" attribute, with severity levels lower (i.e.,
                    more severe) or equal to the value provided by this present
                    attribute.
                  type: number
        jobConfig:
          description: >-
            This type represents configuration data for a logging job. It shall
            comply with the provisions defined in table 8.6.3.6-1. NOTE: The
            present document version does not specify the support for "log
            compilation and reporting based on events" as specified in clause
            6.6.2.2 of ETSI GS NFV-IFA 031.
          type: object
          required:
            - reportingCondition
            - securityConf
          properties:
            startTime:
              description: >
                Date-time stamp. Representation: String formatted according to
                IETF RFC 3339.
              type: string
              format: date-time
            endTime:
              description: >
                Date-time stamp. Representation: String formatted according to
                IETF RFC 3339.
              type: string
              format: date-time
            reportingCondition:
              description: >-
                Specifies the condition under which the producer will report to
                the consumer about the compiled log data.
              required:
                - reportingType
              properties:
                reportingType:
                  description: >-
                    Specifies the type of reporting condition. Permitted values:
                    - REPORTING_ON_COMPILATION: the producer shall notify the
                    consumer once the compilation of the
                                    collected logging data into a file is completed and a new log report is available.
                    - NO_REPORTING: no reporting is requested (the consumer can
                    query the logging jobs to know about the
                                    availability of new log reports).
                  type: string
                  enum:
                    - REPORTING_ON_COMPILATION
                    - NO_REPORTING
                minimumReportingPeriod:
                  description: >-
                    Specifies the minimum periodicity at which the producer will
                    report to the consumer about the collected log information,
                    in seconds.
                  type: integer
                  format: int32
            compileBySizeValue:
              description: >-
                An indicative size threshold for compiling the collected log
                data, in bytes. It is used when the compilation is based on the
                size of the collected log data. If not present, a default value
                as specified with the "defaultLogCompileBySizeValue"
                configuration in the "ManoEntityConfigurableParams" shall be
                used
              type: integer
              format: int32
            compileByTimerValue:
              description: >-
                The periodicity threshold for compiling the filtered log, in
                seconds. It is used when the compilation is based on a timer
                (e.g., every 24 hours). If not present, a default value as
                specified with the "defaultLogCompileByTimerValue" configuration
                in the "ManoEntityConfigurableParams" shall be used
              type: integer
              format: int32
            securityConf:
              description: Configuration about the security aspects of the logging job.
              type: object
              properties:
                logFileEncryption:
                  description: >-
                    Information about the encryption of the compiled log files.
                    Shall be present if the log file is requested to be
                    encrypted.
                  required:
                    - encryptionCertificate
                    - cipherAlgorithm
                  type: object
                  properties:
                    encryptionCertificate:
                      description: >-
                        X.509 certificate with the public key to use for the
                        encryption of the compiled log file.
                      type: string
                    cipherAlgorithm:
                      description: >-
                        Cryptographic algorithm to be used for the encryption of
                        the compiled log file. More than one algorithm can be
                        provided from higher (lower array index) to lower
                        (higher array index) precedence. Valid values are:
                        "AES-CBC-128", "AES-GCM-128", "AES-CBC-256", and
                        "AES-GCM-256", as specified in clause 6.5 of ETSI GS
                        NFV-SEC 012
                      type: array
                      items:
                        type: string
                        minItems: 1
                    encryptAndSignOrder:
                      description: >-
                        Indication about the order in signing and encrypting the
                        compiled log file. Valid values are: "encryptFirst", to
                        apply the order "first encrypt, then sign", and
                        "signFirst" for the order "first sign, then encrypt".
                        Default value is "encryptFirst".
                      type: string
                logTransferSecurity:
                  description: >-
                    Information about the security measures for
                    retrieving/accessing the compiled log files.
                  type: object
                  properties:
                    publicKey:
                      description: >-
                        The public key of the API consumer used for the client
                        authentication with the file server. Shall be provided
                        if required by the type of transfer protocol. May be
                        omitted if the key has been provided to the API producer
                        by other means, or if it has already been provided in
                        some previous CreateLoggingJobRequest issued by the same
                        API consumer, whose public key has not changed.
                      type: string
    LoggingJob:
      description: >-
        This type represents a logging job. It shall comply with the provisions
        defined in table 8.6.2.6-1.
      type: object
      required:
        - id
        - objectInstanceIds
        - jobCriteria
        - jobConfig
        - _links
      properties:
        id:
          description: |
            An identifier with the intention of being globally unique.
          type: string
        objectInstanceIds:
          description: >-
            Identifiers of the object instance for which logging information is
            collected. This attribute shall contain the identifier of the
            instance of the object that is logged according to their type.
          type: array
          items:
            description: >
              This type represents the identifier to reference a managed object
              of a  particular type. 
            type: object
            properties:
              type:
                description: >
                  Indicates the type of managed object. Permitted values:
                    - MANO_ENTITY
                    - MANO_SERVICE
                    - MANO_SERVICE_IF
                    - CONSUMED_MANO_IF
                    - MANO_ENTITY_COMPONENT

                  The "MANO_ENTITY COMPONENT" is only applicable if attribute
                  "manoEntityComponents" in "ManoEntity" is supported by the API
                  producer.
                type: string
                enum:
                  - MANO_ENTITY
                  - MANO_SERVICE
                  - MANO_SERVICE_IF
                  - CONSUMED_MANO_IF
                  - MANO_ENTITY_COMPONENT
              objectId:
                description: |
                  An identifier with the intention of being globally unique.
                type: string
              subObjectId:
                description: >
                  An identifier that is unique for the respective type within a
                  NFV-MANO functional entity, but that need not be globally
                  unique. Representation: string of variable length..
                type: string
            required:
              - type
              - objectId
        jobCriteria:
          description: >-
            This type represents collection criteria for logging jobs. It shall
            comply with the provisions defined in table 8.6.3.2-1.
          type: object
          required:
            - loggingType
          properties:
            loggingType:
              description: >-
                Type of logging. This defines the types of logged information to
                collect.

                Permitted values: - MESSAGES: logged NFV-MANO service interface
                messages. - SERVICES: logged messages about processes pertaining
                to NFV-MANO services. - SYSTEM: logged messages about the
                NFV-MANO functional entity’s system enabled by the provider.
              type: string
              enum:
                - MESSAGES
                - SERVICES
                - SYSTEM
            messagesLogDetail:
              description: >-
                This type represents criteria for logging jobs to collect logged
                messages on NFV-MANO service interfaces. It shall comply with
                the provisions defined in table 8.6.3.3-1.
              type: object
              required:
                - direction
              properties:
                direction:
                  description: >-
                    The direction of the interface messages to match.

                    Permitted values: - IN: input messages into the interface. -
                    OUT: output messages from the interface. - ALL: both input
                    and output messages into/from the interface.
                  type: string
                  enum:
                    - IN
                    - OUT
                    - ALL
                matchingPatterns:
                  description: >-
                    Patterns to be matched in the interface message. If
                    provided, only messages that match all the values provided
                    in the sub-attributes shall be logged. An API consumer can
                    provide more than one "matchingPattern" if combinations of
                    patterns are to be considered to match diverse sets of
                    interface messages.
                  type: array
                  items:
                    type: object
                    anyOf:
                      - required:
                          - srcIpAddress
                      - required:
                          - dstIpAddress
                      - required:
                          - requestMethod
                      - required:
                          - requestUriPattern
                      - required:
                          - responseCodes
                    properties:
                      srcIpAddress:
                        description: >
                          An IPV4 or IPV6 address. Representation: In case of an
                          IPV4 address, string that consists of four decimal
                          integers separated by dots, each integer ranging from
                          0 to 255. In case of an IPV6 address, string that
                          consists of groups of zero to four hexadecimal digits,
                          separated by colons.
                        type: string
                        format: IP
                      requestMethod:
                        description: >-
                          HTTP request method to be matched. To match, the HTTP
                          request method of the message shall be the same as the
                          value of this attribute. Valid values are specified in
                          IETF RFC 7231. The API producer shall support this
                          attribute.
                        type: string
                      requestUriPattern:
                        description: >-
                          Substring to be matched in the request URI. To match,
                          the request URI shall include the value of
                           this attribute as a substring. This is typically used to match messages which associate to RESTful
                           resources, or to a specific API (e.g., by using the "apiName" of the API). The API producer shall
                           support this attribute.
                        type: string
                      dstIpAddress:
                        description: >
                          An IPV4 or IPV6 address. Representation: In case of an
                          IPV4 address, string that consists of four decimal
                          integers separated by dots, each integer ranging from
                          0 to 255. In case of an IPV6 address, string that
                          consists of groups of zero to four hexadecimal digits,
                          separated by colons.
                        type: string
                        format: IP
                      responseCodes:
                        description: >-
                          HTTP response codes or patterns to match. A list of
                          all valid HTTP response codes and their specification
                          documents can be obtained from the HTTP status code
                          registry. In addition, if supported, the following
                          patterns may be used (case-insensitive): - "1XX": for
                          matching any kind of informational response. - "2XX":
                          for matching any kind of success response. - "3XX":
                          for matching any kind redirection response. - "4XX":
                          for matching any kind of client error response. -
                          "5XX": for matching any kind of server error response.

                          The API producer shall support this attribute
                        type: array
                        items:
                          type: string
                      headerField:
                        description: >-
                          Name of the header field to be matched. The header
                          field name shall be one of the supported fields in a
                          request message as defined in clause 4.2.2 of ETSI GS
                          NFV-SOL 013 or in a response message as defined in
                          clause 4.2.3 of ETSI GS NFV-SOL 013, in accordance
                          with the "direction" criteria input. The API producer
                          may support this attribute.
                        type: string
                      headerValue:
                        description: >-
                          Value in the header to be matched. To match, the value
                          in the header field indicated by "headerField" shall
                          be the same as in this attribute. Shall be provided if
                          a "headerField" is provided. The API producer may
                          support this attribute.
                        type: string
                      bodyValues:
                        description: >-
                          A list of strings to be matched in the body part of
                          the interface message (e.g., the body of an HTTP
                          message). If provided, only messages with text in the
                          body part containing all the values from the list
                          shall match the filter. In addition to a matching
                          filter for the body of the message, a corresponding
                          "headerField" filter shall also be provided, with
                          "headerField" set to "Content-Type", to restrict
                          matching to appropriate textual payloads such as
                          "application/json" or "text/plain". The API producer
                          may support this attribute
                        type: string
            servicesLogDetail:
              description: >-
                This type represents criteria for logging jobs to collect logged
                messages about processes pertaining to NFV-MANO services. It
                shall comply with the provisions defined in table 8.6.3.4-1.
              type: object
              properties:
                logGarbageCollection:
                  description: >-
                    Indicates to collect logged information about garbage
                    collection processes associated to NFV-MANO services.
                  type: boolean
            systemLogDetail:
              description: >-
                This type represents criteria for logging jobs to collect logged
                system events of the NFV-MANO functional entity. It shall comply
                with the provisions defined in table 8.6.3.5-1.
              type: object
              required:
                - systemLogs
                - severityLevel
              properties:
                systemLogs:
                  description: >
                    This type represents a list of key-value pairs. The order of
                    the pairs in the list is not significant. In JSON, a set of
                    keyvalue pairs is represented as an object. It shall comply
                    with the provisions defined in clause 4 of IETF RFC 8259. In
                    the following example, a list of key-value pairs with four
                    keys ("aString", "aNumber", "anArray" and "anObject") is
                    provided to illustrate that the values associated with
                    different keys can be of different type.
                  type: object
                severityLevelScheme:
                  description: >-
                    Identifies a severity level scheme. The default value is
                    "rfc5424", which represents the set of values specified in
                    the clause 6.2.1, table 2 of IETF RFC 5424. Other values may
                    be used to signal different schemes.
                  type: string
                severityLevel:
                  description: >-
                    The severity level, which determines the severity of the
                    system messages to collect. The NFV-MANO functional entity
                    shall collect system log messages, as indicated by the
                    "systemLogs" attribute, with severity levels lower (i.e.,
                    more severe) or equal to the value provided by this present
                    attribute.
                  type: number
        jobConfig:
          description: >-
            This type represents configuration data for a logging job. It shall
            comply with the provisions defined in table 8.6.3.6-1. NOTE: The
            present document version does not specify the support for "log
            compilation and reporting based on events" as specified in clause
            6.6.2.2 of ETSI GS NFV-IFA 031.
          type: object
          required:
            - reportingCondition
            - securityConf
          properties:
            startTime:
              description: >
                Date-time stamp. Representation: String formatted according to
                IETF RFC 3339.
              type: string
              format: date-time
            endTime:
              description: >
                Date-time stamp. Representation: String formatted according to
                IETF RFC 3339.
              type: string
              format: date-time
            reportingCondition:
              description: >-
                Specifies the condition under which the producer will report to
                the consumer about the compiled log data.
              required:
                - reportingType
              properties:
                reportingType:
                  description: >-
                    Specifies the type of reporting condition. Permitted values:
                    - REPORTING_ON_COMPILATION: the producer shall notify the
                    consumer once the compilation of the
                                    collected logging data into a file is completed and a new log report is available.
                    - NO_REPORTING: no reporting is requested (the consumer can
                    query the logging jobs to know about the
                                    availability of new log reports).
                  type: string
                  enum:
                    - REPORTING_ON_COMPILATION
                    - NO_REPORTING
                minimumReportingPeriod:
                  description: >-
                    Specifies the minimum periodicity at which the producer will
                    report to the consumer about the collected log information,
                    in seconds.
                  type: integer
                  format: int32
            compileBySizeValue:
              description: >-
                An indicative size threshold for compiling the collected log
                data, in bytes. It is used when the compilation is based on the
                size of the collected log data. If not present, a default value
                as specified with the "defaultLogCompileBySizeValue"
                configuration in the "ManoEntityConfigurableParams" shall be
                used
              type: integer
              format: int32
            compileByTimerValue:
              description: >-
                The periodicity threshold for compiling the filtered log, in
                seconds. It is used when the compilation is based on a timer
                (e.g., every 24 hours). If not present, a default value as
                specified with the "defaultLogCompileByTimerValue" configuration
                in the "ManoEntityConfigurableParams" shall be used
              type: integer
              format: int32
            securityConf:
              description: Configuration about the security aspects of the logging job.
              type: object
              properties:
                logFileEncryption:
                  description: >-
                    Information about the encryption of the compiled log files.
                    Shall be present if the log file is requested to be
                    encrypted.
                  required:
                    - encryptionCertificate
                    - cipherAlgorithm
                  type: object
                  properties:
                    encryptionCertificate:
                      description: >-
                        X.509 certificate with the public key to use for the
                        encryption of the compiled log file.
                      type: string
                    cipherAlgorithm:
                      description: >-
                        Cryptographic algorithm to be used for the encryption of
                        the compiled log file. More than one algorithm can be
                        provided from higher (lower array index) to lower
                        (higher array index) precedence. Valid values are:
                        "AES-CBC-128", "AES-GCM-128", "AES-CBC-256", and
                        "AES-GCM-256", as specified in clause 6.5 of ETSI GS
                        NFV-SEC 012
                      type: array
                      items:
                        type: string
                        minItems: 1
                    encryptAndSignOrder:
                      description: >-
                        Indication about the order in signing and encrypting the
                        compiled log file. Valid values are: "encryptFirst", to
                        apply the order "first encrypt, then sign", and
                        "signFirst" for the order "first sign, then encrypt".
                        Default value is "encryptFirst".
                      type: string
                logTransferSecurity:
                  description: >-
                    Information about the security measures for
                    retrieving/accessing the compiled log files.
                  type: object
                  properties:
                    publicKey:
                      description: >-
                        The public key of the API consumer used for the client
                        authentication with the file server. Shall be provided
                        if required by the type of transfer protocol. May be
                        omitted if the key has been provided to the API producer
                        by other means, or if it has already been provided in
                        some previous CreateLoggingJobRequest issued by the same
                        API consumer, whose public key has not changed.
                      type: string
        logReports:
          description: Information about available log reports created by the logging job.
          type: array
          items:
            type: object
            required:
              - logReportId
              - logReportLoc
            properties:
              logReportId:
                description: |
                  An identifier with the intention of being globally unique.
                type: string
              logReportLoc:
                description: >
                  This type represents a link to a resource using an absolute
                  URI.
                type: object
                required:
                  - href
                properties:
                  href:
                    description: |
                      String formatted according to IETF RFC 3986.
                    type: string
        _links:
          description: Links for this resource.
          type: object
          required:
            - self
          properties:
            self:
              description: |
                This type represents a link to a resource using an absolute URI.
              type: object
              required:
                - href
              properties:
                href:
                  description: |
                    String formatted according to IETF RFC 3986.
                  type: string
            objects:
              description: >-
                Links to resources representing the object instances that are
                logged. Shall be present if the logged object instance
                information is accessible as a resource.
              type: array
              items:
                description: >
                  This type represents a link to a resource using an absolute
                  URI.
                type: object
                required:
                  - href
                properties:
                  href:
                    description: |
                      String formatted according to IETF RFC 3986.
                    type: string
    LoggingJobCriteria:
      description: >-
        This type represents collection criteria for logging jobs. It shall
        comply with the provisions defined in table 8.6.3.2-1.
      type: object
      required:
        - loggingType
      properties:
        loggingType:
          description: >-
            Type of logging. This defines the types of logged information to
            collect.

            Permitted values: - MESSAGES: logged NFV-MANO service interface
            messages. - SERVICES: logged messages about processes pertaining to
            NFV-MANO services. - SYSTEM: logged messages about the NFV-MANO
            functional entity’s system enabled by the provider.
          type: string
          enum:
            - MESSAGES
            - SERVICES
            - SYSTEM
        messagesLogDetail:
          description: >-
            This type represents criteria for logging jobs to collect logged
            messages on NFV-MANO service interfaces. It shall comply with the
            provisions defined in table 8.6.3.3-1.
          type: object
          required:
            - direction
          properties:
            direction:
              description: >-
                The direction of the interface messages to match.

                Permitted values: - IN: input messages into the interface. -
                OUT: output messages from the interface. - ALL: both input and
                output messages into/from the interface.
              type: string
              enum:
                - IN
                - OUT
                - ALL
            matchingPatterns:
              description: >-
                Patterns to be matched in the interface message. If provided,
                only messages that match all the values provided in the
                sub-attributes shall be logged. An API consumer can provide more
                than one "matchingPattern" if combinations of patterns are to be
                considered to match diverse sets of interface messages.
              type: array
              items:
                type: object
                anyOf:
                  - required:
                      - srcIpAddress
                  - required:
                      - dstIpAddress
                  - required:
                      - requestMethod
                  - required:
                      - requestUriPattern
                  - required:
                      - responseCodes
                properties:
                  srcIpAddress:
                    description: >
                      An IPV4 or IPV6 address. Representation: In case of an
                      IPV4 address, string that consists of four decimal
                      integers separated by dots, each integer ranging from 0 to
                      255. In case of an IPV6 address, string that consists of
                      groups of zero to four hexadecimal digits, separated by
                      colons.
                    type: string
                    format: IP
                  requestMethod:
                    description: >-
                      HTTP request method to be matched. To match, the HTTP
                      request method of the message shall be the same as the
                      value of this attribute. Valid values are specified in
                      IETF RFC 7231. The API producer shall support this
                      attribute.
                    type: string
                  requestUriPattern:
                    description: >-
                      Substring to be matched in the request URI. To match, the
                      request URI shall include the value of
                       this attribute as a substring. This is typically used to match messages which associate to RESTful
                       resources, or to a specific API (e.g., by using the "apiName" of the API). The API producer shall
                       support this attribute.
                    type: string
                  dstIpAddress:
                    description: >
                      An IPV4 or IPV6 address. Representation: In case of an
                      IPV4 address, string that consists of four decimal
                      integers separated by dots, each integer ranging from 0 to
                      255. In case of an IPV6 address, string that consists of
                      groups of zero to four hexadecimal digits, separated by
                      colons.
                    type: string
                    format: IP
                  responseCodes:
                    description: >-
                      HTTP response codes or patterns to match. A list of all
                      valid HTTP response codes and their specification
                      documents can be obtained from the HTTP status code
                      registry. In addition, if supported, the following
                      patterns may be used (case-insensitive): - "1XX": for
                      matching any kind of informational response. - "2XX": for
                      matching any kind of success response. - "3XX": for
                      matching any kind redirection response. - "4XX": for
                      matching any kind of client error response. - "5XX": for
                      matching any kind of server error response.

                      The API producer shall support this attribute
                    type: array
                    items:
                      type: string
                  headerField:
                    description: >-
                      Name of the header field to be matched. The header field
                      name shall be one of the supported fields in a request
                      message as defined in clause 4.2.2 of ETSI GS NFV-SOL 013
                      or in a response message as defined in clause 4.2.3 of
                      ETSI GS NFV-SOL 013, in accordance with the "direction"
                      criteria input. The API producer may support this
                      attribute.
                    type: string
                  headerValue:
                    description: >-
                      Value in the header to be matched. To match, the value in
                      the header field indicated by "headerField" shall be the
                      same as in this attribute. Shall be provided if a
                      "headerField" is provided. The API producer may support
                      this attribute.
                    type: string
                  bodyValues:
                    description: >-
                      A list of strings to be matched in the body part of the
                      interface message (e.g., the body of an HTTP message). If
                      provided, only messages with text in the body part
                      containing all the values from the list shall match the
                      filter. In addition to a matching filter for the body of
                      the message, a corresponding "headerField" filter shall
                      also be provided, with "headerField" set to
                      "Content-Type", to restrict matching to appropriate
                      textual payloads such as "application/json" or
                      "text/plain". The API producer may support this attribute
                    type: string
        servicesLogDetail:
          description: >-
            This type represents criteria for logging jobs to collect logged
            messages about processes pertaining to NFV-MANO services. It shall
            comply with the provisions defined in table 8.6.3.4-1.
          type: object
          properties:
            logGarbageCollection:
              description: >-
                Indicates to collect logged information about garbage collection
                processes associated to NFV-MANO services.
              type: boolean
        systemLogDetail:
          description: >-
            This type represents criteria for logging jobs to collect logged
            system events of the NFV-MANO functional entity. It shall comply
            with the provisions defined in table 8.6.3.5-1.
          type: object
          required:
            - systemLogs
            - severityLevel
          properties:
            systemLogs:
              description: >
                This type represents a list of key-value pairs. The order of the
                pairs in the list is not significant. In JSON, a set of keyvalue
                pairs is represented as an object. It shall comply with the
                provisions defined in clause 4 of IETF RFC 8259. In the
                following example, a list of key-value pairs with four keys
                ("aString", "aNumber", "anArray" and "anObject") is provided to
                illustrate that the values associated with different keys can be
                of different type.
              type: object
            severityLevelScheme:
              description: >-
                Identifies a severity level scheme. The default value is
                "rfc5424", which represents the set of values specified in the
                clause 6.2.1, table 2 of IETF RFC 5424. Other values may be used
                to signal different schemes.
              type: string
            severityLevel:
              description: >-
                The severity level, which determines the severity of the system
                messages to collect. The NFV-MANO functional entity shall
                collect system log messages, as indicated by the "systemLogs"
                attribute, with severity levels lower (i.e., more severe) or
                equal to the value provided by this present attribute.
              type: number
    LoggingJobMessagesCriteria:
      description: >-
        This type represents criteria for logging jobs to collect logged
        messages on NFV-MANO service interfaces. It shall comply with the
        provisions defined in table 8.6.3.3-1.
      type: object
      required:
        - direction
      properties:
        direction:
          description: >-
            The direction of the interface messages to match.

            Permitted values: - IN: input messages into the interface. - OUT:
            output messages from the interface. - ALL: both input and output
            messages into/from the interface.
          type: string
          enum:
            - IN
            - OUT
            - ALL
        matchingPatterns:
          description: >-
            Patterns to be matched in the interface message. If provided, only
            messages that match all the values provided in the sub-attributes
            shall be logged. An API consumer can provide more than one
            "matchingPattern" if combinations of patterns are to be considered
            to match diverse sets of interface messages.
          type: array
          items:
            type: object
            anyOf:
              - required:
                  - srcIpAddress
              - required:
                  - dstIpAddress
              - required:
                  - requestMethod
              - required:
                  - requestUriPattern
              - required:
                  - responseCodes
            properties:
              srcIpAddress:
                description: >
                  An IPV4 or IPV6 address. Representation: In case of an IPV4
                  address, string that consists of four decimal integers
                  separated by dots, each integer ranging from 0 to 255. In case
                  of an IPV6 address, string that consists of groups of zero to
                  four hexadecimal digits, separated by colons.
                type: string
                format: IP
              requestMethod:
                description: >-
                  HTTP request method to be matched. To match, the HTTP request
                  method of the message shall be the same as the value of this
                  attribute. Valid values are specified in IETF RFC 7231. The
                  API producer shall support this attribute.
                type: string
              requestUriPattern:
                description: >-
                  Substring to be matched in the request URI. To match, the
                  request URI shall include the value of
                   this attribute as a substring. This is typically used to match messages which associate to RESTful
                   resources, or to a specific API (e.g., by using the "apiName" of the API). The API producer shall
                   support this attribute.
                type: string
              dstIpAddress:
                description: >
                  An IPV4 or IPV6 address. Representation: In case of an IPV4
                  address, string that consists of four decimal integers
                  separated by dots, each integer ranging from 0 to 255. In case
                  of an IPV6 address, string that consists of groups of zero to
                  four hexadecimal digits, separated by colons.
                type: string
                format: IP
              responseCodes:
                description: >-
                  HTTP response codes or patterns to match. A list of all valid
                  HTTP response codes and their specification documents can be
                  obtained from the HTTP status code registry. In addition, if
                  supported, the following patterns may be used
                  (case-insensitive): - "1XX": for matching any kind of
                  informational response. - "2XX": for matching any kind of
                  success response. - "3XX": for matching any kind redirection
                  response. - "4XX": for matching any kind of client error
                  response. - "5XX": for matching any kind of server error
                  response.

                  The API producer shall support this attribute
                type: array
                items:
                  type: string
              headerField:
                description: >-
                  Name of the header field to be matched. The header field name
                  shall be one of the supported fields in a request message as
                  defined in clause 4.2.2 of ETSI GS NFV-SOL 013 or in a
                  response message as defined in clause 4.2.3 of ETSI GS NFV-SOL
                  013, in accordance with the "direction" criteria input. The
                  API producer may support this attribute.
                type: string
              headerValue:
                description: >-
                  Value in the header to be matched. To match, the value in the
                  header field indicated by "headerField" shall be the same as
                  in this attribute. Shall be provided if a "headerField" is
                  provided. The API producer may support this attribute.
                type: string
              bodyValues:
                description: >-
                  A list of strings to be matched in the body part of the
                  interface message (e.g., the body of an HTTP message). If
                  provided, only messages with text in the body part containing
                  all the values from the list shall match the filter. In
                  addition to a matching filter for the body of the message, a
                  corresponding "headerField" filter shall also be provided,
                  with "headerField" set to "Content-Type", to restrict matching
                  to appropriate textual payloads such as "application/json" or
                  "text/plain". The API producer may support this attribute
                type: string
    LoggingJobServicesCriteria:
      description: >-
        This type represents criteria for logging jobs to collect logged
        messages about processes pertaining to NFV-MANO services. It shall
        comply with the provisions defined in table 8.6.3.4-1.
      type: object
      properties:
        logGarbageCollection:
          description: >-
            Indicates to collect logged information about garbage collection
            processes associated to NFV-MANO services.
          type: boolean
    LoggingJobSystemCriteria:
      description: >-
        This type represents criteria for logging jobs to collect logged system
        events of the NFV-MANO functional entity. It shall comply with the
        provisions defined in table 8.6.3.5-1.
      type: object
      required:
        - systemLogs
        - severityLevel
      properties:
        systemLogs:
          description: >
            This type represents a list of key-value pairs. The order of the
            pairs in the list is not significant. In JSON, a set of keyvalue
            pairs is represented as an object. It shall comply with the
            provisions defined in clause 4 of IETF RFC 8259. In the following
            example, a list of key-value pairs with four keys ("aString",
            "aNumber", "anArray" and "anObject") is provided to illustrate that
            the values associated with different keys can be of different type.
          type: object
        severityLevelScheme:
          description: >-
            Identifies a severity level scheme. The default value is "rfc5424",
            which represents the set of values specified in the clause 6.2.1,
            table 2 of IETF RFC 5424. Other values may be used to signal
            different schemes.
          type: string
        severityLevel:
          description: >-
            The severity level, which determines the severity of the system
            messages to collect. The NFV-MANO functional entity shall collect
            system log messages, as indicated by the "systemLogs" attribute,
            with severity levels lower (i.e., more severe) or equal to the value
            provided by this present attribute.
          type: number
    LoggingJobConfig:
      description: >-
        This type represents configuration data for a logging job. It shall
        comply with the provisions defined in table 8.6.3.6-1. NOTE: The present
        document version does not specify the support for "log compilation and
        reporting based on events" as specified in clause 6.6.2.2 of ETSI GS
        NFV-IFA 031.
      type: object
      required:
        - reportingCondition
        - securityConf
      properties:
        startTime:
          description: >
            Date-time stamp. Representation: String formatted according to IETF
            RFC 3339.
          type: string
          format: date-time
        endTime:
          description: >
            Date-time stamp. Representation: String formatted according to IETF
            RFC 3339.
          type: string
          format: date-time
        reportingCondition:
          description: >-
            Specifies the condition under which the producer will report to the
            consumer about the compiled log data.
          required:
            - reportingType
          properties:
            reportingType:
              description: >-
                Specifies the type of reporting condition. Permitted values: -
                REPORTING_ON_COMPILATION: the producer shall notify the consumer
                once the compilation of the
                                collected logging data into a file is completed and a new log report is available.
                - NO_REPORTING: no reporting is requested (the consumer can
                query the logging jobs to know about the
                                availability of new log reports).
              type: string
              enum:
                - REPORTING_ON_COMPILATION
                - NO_REPORTING
            minimumReportingPeriod:
              description: >-
                Specifies the minimum periodicity at which the producer will
                report to the consumer about the collected log information, in
                seconds.
              type: integer
              format: int32
        compileBySizeValue:
          description: >-
            An indicative size threshold for compiling the collected log data,
            in bytes. It is used when the compilation is based on the size of
            the collected log data. If not present, a default value as specified
            with the "defaultLogCompileBySizeValue" configuration in the
            "ManoEntityConfigurableParams" shall be used
          type: integer
          format: int32
        compileByTimerValue:
          description: >-
            The periodicity threshold for compiling the filtered log, in
            seconds. It is used when the compilation is based on a timer (e.g.,
            every 24 hours). If not present, a default value as specified with
            the "defaultLogCompileByTimerValue" configuration in the
            "ManoEntityConfigurableParams" shall be used
          type: integer
          format: int32
        securityConf:
          description: Configuration about the security aspects of the logging job.
          type: object
          properties:
            logFileEncryption:
              description: >-
                Information about the encryption of the compiled log files.
                Shall be present if the log file is requested to be encrypted.
              required:
                - encryptionCertificate
                - cipherAlgorithm
              type: object
              properties:
                encryptionCertificate:
                  description: >-
                    X.509 certificate with the public key to use for the
                    encryption of the compiled log file.
                  type: string
                cipherAlgorithm:
                  description: >-
                    Cryptographic algorithm to be used for the encryption of the
                    compiled log file. More than one algorithm can be provided
                    from higher (lower array index) to lower (higher array
                    index) precedence. Valid values are: "AES-CBC-128",
                    "AES-GCM-128", "AES-CBC-256", and "AES-GCM-256", as
                    specified in clause 6.5 of ETSI GS NFV-SEC 012
                  type: array
                  items:
                    type: string
                    minItems: 1
                encryptAndSignOrder:
                  description: >-
                    Indication about the order in signing and encrypting the
                    compiled log file. Valid values are: "encryptFirst", to
                    apply the order "first encrypt, then sign", and "signFirst"
                    for the order "first sign, then encrypt". Default value is
                    "encryptFirst".
                  type: string
            logTransferSecurity:
              description: >-
                Information about the security measures for retrieving/accessing
                the compiled log files.
              type: object
              properties:
                publicKey:
                  description: >-
                    The public key of the API consumer used for the client
                    authentication with the file server. Shall be provided if
                    required by the type of transfer protocol. May be omitted if
                    the key has been provided to the API producer by other
                    means, or if it has already been provided in some previous
                    CreateLoggingJobRequest issued by the same API consumer,
                    whose public key has not changed.
                  type: string
    LogReportAvailableNotification:
      description: >-
        This notification informs the receiver that the log report of the
        NFV-MANO functional entity is available. It shall comply with the
        provisions defined in table 8.6.2.4-1. The notification shall be
        triggered by the NFV-MANO functional entity when log information has
        been collected by the logging job and the log report is available.
      type: object
      required:
        - id
        - notificationType
        - subscriptionId
        - timeStamp
        - objectInstanceId
        - _links
      properties:
        id:
          description: |
            An identifier with the intention of being globally unique.
          type: string
        notificationType:
          description: >-
            Discriminator for the different notification types. Shall be set to
            "LogReportAvailableNotification" for this notification type.
          type: string
        subscriptionId:
          description: |
            An identifier with the intention of being globally unique.
          type: string
        timeStamp:
          description: >
            Date-time stamp. Representation: String formatted according to IETF
            RFC 3339.
          type: string
          format: date-time
        objectInstanceId:
          description: >
            This type represents the identifier to reference a managed object of
            a  particular type. 
          type: object
          properties:
            type:
              description: >
                Indicates the type of managed object. Permitted values:
                  - MANO_ENTITY
                  - MANO_SERVICE
                  - MANO_SERVICE_IF
                  - CONSUMED_MANO_IF
                  - MANO_ENTITY_COMPONENT

                The "MANO_ENTITY COMPONENT" is only applicable if attribute
                "manoEntityComponents" in "ManoEntity" is supported by the API
                producer.
              type: string
              enum:
                - MANO_ENTITY
                - MANO_SERVICE
                - MANO_SERVICE_IF
                - CONSUMED_MANO_IF
                - MANO_ENTITY_COMPONENT
            objectId:
              description: |
                An identifier with the intention of being globally unique.
              type: string
            subObjectId:
              description: >
                An identifier that is unique for the respective type within a
                NFV-MANO functional entity, but that need not be globally
                unique. Representation: string of variable length..
              type: string
          required:
            - type
            - objectId
        _links:
          description: Links to resources related to this notification.
          type: object
          required:
            - subscription
            - logReports
          properties:
            subscription:
              description: >
                This type represents a link to a resource in a notification,
                using an absolute or relative URI.
              type: object
              required:
                - href
              properties:
                href:
                  description: |
                    String formatted according to IETF RFC 3986.
                  type: string
            objectInstance:
              description: >
                This type represents a link to a resource in a notification,
                using an absolute or relative URI.
              type: object
              required:
                - href
              properties:
                href:
                  description: |
                    String formatted according to IETF RFC 3986.
                  type: string
            LoggingJob:
              description: >
                This type represents a link to a resource in a notification,
                using an absolute or relative URI.
              type: object
              required:
                - href
              properties:
                href:
                  description: |
                    String formatted according to IETF RFC 3986.
                  type: string
            logReports:
              description: >-
                Link from which the available log report can be obtained. Due to
                the relationship of the logging job compilation and the logging
                information availability reporting, more than one logReport
                notification link can be provided.
              type: array
              items:
                description: >
                  This type represents a link to a resource in a notification,
                  using an absolute or relative URI.
                type: object
                required:
                  - href
                properties:
                  href:
                    description: |
                      String formatted according to IETF RFC 3986.
                    type: string
  callbacks:
    LogReportAvailableNotification:
      '{$request.body#/callbackUri}':
        description: >-
          This resource represents a notification endpoint for NFV-MANO log
          management. The API producer can use this resource to send
          notifications related to log management events to a subscribed API
          consumer, which has provided the URI of this resource during the
          subscription process.
        post:
          description: >-
            The POST method delivers a notification regarding a log management
            event from the API producer to the API consumer. The API consumer
            shall have previously created an "Individual subscription" resource
            with a matching filter. This method shall follow the provisions
            specified in the tables 8.5.9.3.1-1 and 8.5.9.3.1-2 for URI query
            parameters, request and response data structures, and response
            codes.
          parameters:
            - name: Version
              description: >
                Version of the API requested to use when responding to this
                request.
              in: header
              required: true
              schema:
                type: string
            - name: Authorization
              description: >
                The authorization token for the request. Reference: IETF RFC
                7235.
              in: header
              required: false
              schema:
                type: string
          requestBody:
            description: Notification about the availability of a log report.
            content:
              application/json:
                schema:
                  description: >-
                    This notification informs the receiver that the log report
                    of the NFV-MANO functional entity is available. It shall
                    comply with the provisions defined in table 8.6.2.4-1. The
                    notification shall be triggered by the NFV-MANO functional
                    entity when log information has been collected by the
                    logging job and the log report is available.
                  type: object
                  required:
                    - id
                    - notificationType
                    - subscriptionId
                    - timeStamp
                    - objectInstanceId
                    - _links
                  properties:
                    id:
                      description: >
                        An identifier with the intention of being globally
                        unique.
                      type: string
                    notificationType:
                      description: >-
                        Discriminator for the different notification types.
                        Shall be set to "LogReportAvailableNotification" for
                        this notification type.
                      type: string
                    subscriptionId:
                      description: >
                        An identifier with the intention of being globally
                        unique.
                      type: string
                    timeStamp:
                      description: >
                        Date-time stamp. Representation: String formatted
                        according to IETF RFC 3339.
                      type: string
                      format: date-time
                    objectInstanceId:
                      description: >
                        This type represents the identifier to reference a
                        managed object of a  particular type. 
                      type: object
                      properties:
                        type:
                          description: >
                            Indicates the type of managed object. Permitted
                            values:
                              - MANO_ENTITY
                              - MANO_SERVICE
                              - MANO_SERVICE_IF
                              - CONSUMED_MANO_IF
                              - MANO_ENTITY_COMPONENT

                            The "MANO_ENTITY COMPONENT" is only applicable if
                            attribute "manoEntityComponents" in "ManoEntity" is
                            supported by the API producer.
                          type: string
                          enum:
                            - MANO_ENTITY
                            - MANO_SERVICE
                            - MANO_SERVICE_IF
                            - CONSUMED_MANO_IF
                            - MANO_ENTITY_COMPONENT
                        objectId:
                          description: >
                            An identifier with the intention of being globally
                            unique.
                          type: string
                        subObjectId:
                          description: >
                            An identifier that is unique for the respective type
                            within a NFV-MANO functional entity, but that need
                            not be globally unique. Representation: string of
                            variable length..
                          type: string
                      required:
                        - type
                        - objectId
                    _links:
                      description: Links to resources related to this notification.
                      type: object
                      required:
                        - subscription
                        - logReports
                      properties:
                        subscription:
                          description: >
                            This type represents a link to a resource in a
                            notification, using an absolute or relative URI.
                          type: object
                          required:
                            - href
                          properties:
                            href:
                              description: |
                                String formatted according to IETF RFC 3986.
                              type: string
                        objectInstance:
                          description: >
                            This type represents a link to a resource in a
                            notification, using an absolute or relative URI.
                          type: object
                          required:
                            - href
                          properties:
                            href:
                              description: |
                                String formatted according to IETF RFC 3986.
                              type: string
                        LoggingJob:
                          description: >
                            This type represents a link to a resource in a
                            notification, using an absolute or relative URI.
                          type: object
                          required:
                            - href
                          properties:
                            href:
                              description: |
                                String formatted according to IETF RFC 3986.
                              type: string
                        logReports:
                          description: >-
                            Link from which the available log report can be
                            obtained. Due to the relationship of the logging job
                            compilation and the logging information availability
                            reporting, more than one logReport notification link
                            can be provided.
                          type: array
                          items:
                            description: >
                              This type represents a link to a resource in a
                              notification, using an absolute or relative URI.
                            type: object
                            required:
                              - href
                            properties:
                              href:
                                description: |
                                  String formatted according to IETF RFC 3986.
                                type: string
          responses:
            '204':
              description: >-
                Shall be returned when the notification has been delivered
                successfully.
              headers:
                Content-Type:
                  description: The MIME type of the body of the response.
                  schema:
                    type: string
                WWW-Authenticate:
                  description: >
                    Challenge if the corresponding HTTP request has not provided
                    authorization, or error details if the corresponding HTTP
                    request has provided an invalid authorization token.
                  schema:
                    type: string
                Version:
                  description: |
                    Version of the API used in the response.
                  schema:
                    type: string
            '400':
              description: >
                400 BAD REQUEST

                400 code can be returned in the following specified cases, the
                specific cause has to be proper specified in the
                "ProblemDetails" structure to be returned.

                If the request is malformed or syntactically incorrect (e.g. if
                the request URI contains incorrect query parameters or the
                payload body contains a syntactically incorrect data structure),
                the API producer shall respond with this response code. The
                "ProblemDetails" structure shall be provided, and should include
                in the "detail" attribute more information about the source of
                the problem.

                If the response to a GET request which queries a container
                resource would be so big that the performance of the API
                producer is adversely affected, and the API producer does not
                support paging for the affected resource, it shall respond with
                this response code. The "ProblemDetails" structure shall be
                provided, and should include in the "detail" attribute more
                information about the source of the problem.

                If there is an application error related to the client's input
                that cannot be easily mapped to any other HTTP response code
                ("catch all error"), the API producer shall respond with this
                response code. The "ProblemDetails" structure shall be provided,
                and shall include in the "detail" attribute more information
                about the source of the problem.

                If the request contains a malformed access token, the API
                producer should respond with this response. The details of the
                error shall be returned in the WWW Authenticate HTTP header, as
                defined in IETF RFC 6750 and IETF RFC 7235. The ProblemDetails
                structure may be provided.

                The use of this HTTP error response code described above is
                applicable to the use of the OAuth 2.0 for the authorization of
                API requests and notifications, as defined in clauses 4.5.3.3
                and 4.5.3.4.
              headers:
                Content-Type:
                  description: The MIME type of the body of the response.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 1
                WWW-Authenticate:
                  description: >
                    Challenge if the corresponding HTTP request has not provided
                    authorization, or error details if the corresponding HTTP
                    request has provided an invalid authorization token.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 0
                Version:
                  description: |
                    Version of the API used in the response.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 1
              content:
                application/json:
                  schema:
                    description: >
                      The definition of the general "ProblemDetails" data
                      structure from IETF RFC 7807 [19] is reproduced inthis
                      structure. Compared to the general framework defined in
                      IETF RFC 7807 [19], the "status" and "detail" attributes
                      are mandated to be included by the present document, to
                      ensure that the response contains additional textual
                      information about an error. IETF RFC 7807 [19] foresees
                      extensibility of the "ProblemDetails" type. It is possible
                      that particular APIs in the present document, or
                      particular implementations, define extensions to define
                      additional attributes that provide more information about
                      the error. The description column only provides some
                      explanation of the meaning to Facilitate understanding of
                      the design. For a full description, see IETF RFC 7807
                      [19].
                    type: object
                    required:
                      - status
                      - detail
                    properties:
                      type:
                        description: >
                          A URI reference according to IETF RFC 3986 [5] that
                          identifies the problem type. It is encouraged that the
                          URI provides human-readable documentation for the
                          problem (e.g. using HTML) when dereferenced. When this
                          member is not present, its value is assumed to be
                          "about:blank".
                        type: string
                        format: URI
                      title:
                        description: >
                          A short, human-readable summary of the problem type.
                          It should not change from occurrence to occurrence of
                          the problem, except for purposes of localization. If
                          type is given and other than "about:blank", this
                          attribute shall also be provided. A short,
                          human-readable summary of the problem type.  It SHOULD
                          NOT change from occurrence to occurrence of the
                          problem, except for purposes of localization (e.g.,
                          using proactive content negotiation; see [RFC7231],
                          Section 3.4).
                        type: string
                      status:
                        description: >
                          The HTTP status code for this occurrence of the
                          problem. The HTTP status code ([RFC7231], Section 6)
                          generated by the origin server for this occurrence of
                          the problem.
                        type: integer
                      detail:
                        description: >
                          A human-readable explanation specific to this
                          occurrence of the problem.
                        type: string
                      instance:
                        description: >
                          A URI reference that identifies the specific
                          occurrence of the problem. It may yield further
                          information if dereferenced.
                        type: string
                        format: URI
            '401':
              description: >
                401 UNAUTHORIZED

                If the request contains no access token even though one is
                required, or if the request contains an authorization token that
                is invalid (e.g. expired or revoked), the API producer should
                respond with this response. The details of the error shall be
                returned in the WWW-Authenticate HTTP header, as defined in IETF
                RFC 6750 and IETF RFC 7235. The ProblemDetails structure may be
                provided.
              headers:
                Content-Type:
                  description: The MIME type of the body of the response.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 1
                WWW-Authenticate:
                  description: >
                    Challenge if the corresponding HTTP request has not provided
                    authorization, or error details if the corresponding HTTP
                    request has provided an invalid authorization token.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 0
                Version:
                  description: |
                    Version of the API used in the response.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 1
              content:
                application/json:
                  schema:
                    description: >
                      The definition of the general "ProblemDetails" data
                      structure from IETF RFC 7807 [19] is reproduced inthis
                      structure. Compared to the general framework defined in
                      IETF RFC 7807 [19], the "status" and "detail" attributes
                      are mandated to be included by the present document, to
                      ensure that the response contains additional textual
                      information about an error. IETF RFC 7807 [19] foresees
                      extensibility of the "ProblemDetails" type. It is possible
                      that particular APIs in the present document, or
                      particular implementations, define extensions to define
                      additional attributes that provide more information about
                      the error. The description column only provides some
                      explanation of the meaning to Facilitate understanding of
                      the design. For a full description, see IETF RFC 7807
                      [19].
                    type: object
                    required:
                      - status
                      - detail
                    properties:
                      type:
                        description: >
                          A URI reference according to IETF RFC 3986 [5] that
                          identifies the problem type. It is encouraged that the
                          URI provides human-readable documentation for the
                          problem (e.g. using HTML) when dereferenced. When this
                          member is not present, its value is assumed to be
                          "about:blank".
                        type: string
                        format: URI
                      title:
                        description: >
                          A short, human-readable summary of the problem type.
                          It should not change from occurrence to occurrence of
                          the problem, except for purposes of localization. If
                          type is given and other than "about:blank", this
                          attribute shall also be provided. A short,
                          human-readable summary of the problem type.  It SHOULD
                          NOT change from occurrence to occurrence of the
                          problem, except for purposes of localization (e.g.,
                          using proactive content negotiation; see [RFC7231],
                          Section 3.4).
                        type: string
                      status:
                        description: >
                          The HTTP status code for this occurrence of the
                          problem. The HTTP status code ([RFC7231], Section 6)
                          generated by the origin server for this occurrence of
                          the problem.
                        type: integer
                      detail:
                        description: >
                          A human-readable explanation specific to this
                          occurrence of the problem.
                        type: string
                      instance:
                        description: >
                          A URI reference that identifies the specific
                          occurrence of the problem. It may yield further
                          information if dereferenced.
                        type: string
                        format: URI
            '403':
              description: >
                403 FORBIDDEN

                If the API consumer is not allowed to perform a particular
                request to a particular resource, the API producer shall respond
                with this response code. The "ProblemDetails" structure shall be
                provided. It should include in the "detail" attribute
                information about the source of the problem, and may indicate
                how to solve it.
              headers:
                Content-Type:
                  description: The MIME type of the body of the response.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 1
                WWW-Authenticate:
                  description: >
                    Challenge if the corresponding HTTP request has not provided
                    authorization, or error details if the corresponding HTTP
                    request has provided an invalid authorization token.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 0
                Version:
                  description: |
                    Version of the API used in the response.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 1
              content:
                application/json:
                  schema:
                    description: >
                      The definition of the general "ProblemDetails" data
                      structure from IETF RFC 7807 [19] is reproduced inthis
                      structure. Compared to the general framework defined in
                      IETF RFC 7807 [19], the "status" and "detail" attributes
                      are mandated to be included by the present document, to
                      ensure that the response contains additional textual
                      information about an error. IETF RFC 7807 [19] foresees
                      extensibility of the "ProblemDetails" type. It is possible
                      that particular APIs in the present document, or
                      particular implementations, define extensions to define
                      additional attributes that provide more information about
                      the error. The description column only provides some
                      explanation of the meaning to Facilitate understanding of
                      the design. For a full description, see IETF RFC 7807
                      [19].
                    type: object
                    required:
                      - status
                      - detail
                    properties:
                      type:
                        description: >
                          A URI reference according to IETF RFC 3986 [5] that
                          identifies the problem type. It is encouraged that the
                          URI provides human-readable documentation for the
                          problem (e.g. using HTML) when dereferenced. When this
                          member is not present, its value is assumed to be
                          "about:blank".
                        type: string
                        format: URI
                      title:
                        description: >
                          A short, human-readable summary of the problem type.
                          It should not change from occurrence to occurrence of
                          the problem, except for purposes of localization. If
                          type is given and other than "about:blank", this
                          attribute shall also be provided. A short,
                          human-readable summary of the problem type.  It SHOULD
                          NOT change from occurrence to occurrence of the
                          problem, except for purposes of localization (e.g.,
                          using proactive content negotiation; see [RFC7231],
                          Section 3.4).
                        type: string
                      status:
                        description: >
                          The HTTP status code for this occurrence of the
                          problem. The HTTP status code ([RFC7231], Section 6)
                          generated by the origin server for this occurrence of
                          the problem.
                        type: integer
                      detail:
                        description: >
                          A human-readable explanation specific to this
                          occurrence of the problem.
                        type: string
                      instance:
                        description: >
                          A URI reference that identifies the specific
                          occurrence of the problem. It may yield further
                          information if dereferenced.
                        type: string
                        format: URI
            '404':
              description: >
                404 NOT FOUND

                If the API producer did not find a current representation for
                the resource addressed by the URI passed in the request or is
                not willing to disclose that one exists, it shall respond with
                this response code. The "ProblemDetails" structure may be
                provided, including in the "detail" attribute information about
                the source of the problem, e.g. a wrong resource URI variable.

                This response code is not appropriate in case the resource
                addressed by the URI is a container resource which is designed
                to contain child resources, but does not contain any child
                resource at the time the request is received. For a GET request
                to an existing empty container resource, a typical response
                contains a 200 OK response code and a payload body with an empty
                array.
              headers:
                Content-Type:
                  description: The MIME type of the body of the response.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 1
                WWW-Authenticate:
                  description: >
                    Challenge if the corresponding HTTP request has not provided
                    authorization, or error details if the corresponding HTTP
                    request has provided an invalid authorization token.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 0
                Version:
                  description: |
                    Version of the API used in the response.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 1
              content:
                application/json:
                  schema:
                    description: >
                      The definition of the general "ProblemDetails" data
                      structure from IETF RFC 7807 [19] is reproduced inthis
                      structure. Compared to the general framework defined in
                      IETF RFC 7807 [19], the "status" and "detail" attributes
                      are mandated to be included by the present document, to
                      ensure that the response contains additional textual
                      information about an error. IETF RFC 7807 [19] foresees
                      extensibility of the "ProblemDetails" type. It is possible
                      that particular APIs in the present document, or
                      particular implementations, define extensions to define
                      additional attributes that provide more information about
                      the error. The description column only provides some
                      explanation of the meaning to Facilitate understanding of
                      the design. For a full description, see IETF RFC 7807
                      [19].
                    type: object
                    required:
                      - status
                      - detail
                    properties:
                      type:
                        description: >
                          A URI reference according to IETF RFC 3986 [5] that
                          identifies the problem type. It is encouraged that the
                          URI provides human-readable documentation for the
                          problem (e.g. using HTML) when dereferenced. When this
                          member is not present, its value is assumed to be
                          "about:blank".
                        type: string
                        format: URI
                      title:
                        description: >
                          A short, human-readable summary of the problem type.
                          It should not change from occurrence to occurrence of
                          the problem, except for purposes of localization. If
                          type is given and other than "about:blank", this
                          attribute shall also be provided. A short,
                          human-readable summary of the problem type.  It SHOULD
                          NOT change from occurrence to occurrence of the
                          problem, except for purposes of localization (e.g.,
                          using proactive content negotiation; see [RFC7231],
                          Section 3.4).
                        type: string
                      status:
                        description: >
                          The HTTP status code for this occurrence of the
                          problem. The HTTP status code ([RFC7231], Section 6)
                          generated by the origin server for this occurrence of
                          the problem.
                        type: integer
                      detail:
                        description: >
                          A human-readable explanation specific to this
                          occurrence of the problem.
                        type: string
                      instance:
                        description: >
                          A URI reference that identifies the specific
                          occurrence of the problem. It may yield further
                          information if dereferenced.
                        type: string
                        format: URI
            '405':
              description: >
                405 METHOD NOT ALLOWED

                If a particular HTTP method is not supported for a particular
                resource, the API producer shall respond with this response
                code. The "ProblemDetails" structure may be omitted.
              headers:
                Content-Type:
                  description: The MIME type of the body of the response.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 1
                WWW-Authenticate:
                  description: >
                    Challenge if the corresponding HTTP request has not provided
                    authorization, or error details if the corresponding HTTP
                    request has provided an invalid authorization token.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 0
                Version:
                  description: |
                    Version of the API used in the response.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 1
              content:
                application/json:
                  schema:
                    description: >
                      The definition of the general "ProblemDetails" data
                      structure from IETF RFC 7807 [19] is reproduced inthis
                      structure. Compared to the general framework defined in
                      IETF RFC 7807 [19], the "status" and "detail" attributes
                      are mandated to be included by the present document, to
                      ensure that the response contains additional textual
                      information about an error. IETF RFC 7807 [19] foresees
                      extensibility of the "ProblemDetails" type. It is possible
                      that particular APIs in the present document, or
                      particular implementations, define extensions to define
                      additional attributes that provide more information about
                      the error. The description column only provides some
                      explanation of the meaning to Facilitate understanding of
                      the design. For a full description, see IETF RFC 7807
                      [19].
                    type: object
                    required:
                      - status
                      - detail
                    properties:
                      type:
                        description: >
                          A URI reference according to IETF RFC 3986 [5] that
                          identifies the problem type. It is encouraged that the
                          URI provides human-readable documentation for the
                          problem (e.g. using HTML) when dereferenced. When this
                          member is not present, its value is assumed to be
                          "about:blank".
                        type: string
                        format: URI
                      title:
                        description: >
                          A short, human-readable summary of the problem type.
                          It should not change from occurrence to occurrence of
                          the problem, except for purposes of localization. If
                          type is given and other than "about:blank", this
                          attribute shall also be provided. A short,
                          human-readable summary of the problem type.  It SHOULD
                          NOT change from occurrence to occurrence of the
                          problem, except for purposes of localization (e.g.,
                          using proactive content negotiation; see [RFC7231],
                          Section 3.4).
                        type: string
                      status:
                        description: >
                          The HTTP status code for this occurrence of the
                          problem. The HTTP status code ([RFC7231], Section 6)
                          generated by the origin server for this occurrence of
                          the problem.
                        type: integer
                      detail:
                        description: >
                          A human-readable explanation specific to this
                          occurrence of the problem.
                        type: string
                      instance:
                        description: >
                          A URI reference that identifies the specific
                          occurrence of the problem. It may yield further
                          information if dereferenced.
                        type: string
                        format: URI
            '406':
              description: >
                406 NOT ACCEPTABLE

                If the "Accept" HTTP header does not contain at least one name
                of a content type that is acceptable to the API producer, the
                API producer shall respond with this response code. The
                "ProblemDetails" structure may be omitted.
              headers:
                Content-Type:
                  description: The MIME type of the body of the response.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 1
                WWW-Authenticate:
                  description: >
                    Challenge if the corresponding HTTP request has not provided
                    authorization, or error details if the corresponding HTTP
                    request has provided an invalid authorization token.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 0
                Version:
                  description: |
                    Version of the API used in the response.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 1
              content:
                application/json:
                  schema:
                    description: >
                      The definition of the general "ProblemDetails" data
                      structure from IETF RFC 7807 [19] is reproduced inthis
                      structure. Compared to the general framework defined in
                      IETF RFC 7807 [19], the "status" and "detail" attributes
                      are mandated to be included by the present document, to
                      ensure that the response contains additional textual
                      information about an error. IETF RFC 7807 [19] foresees
                      extensibility of the "ProblemDetails" type. It is possible
                      that particular APIs in the present document, or
                      particular implementations, define extensions to define
                      additional attributes that provide more information about
                      the error. The description column only provides some
                      explanation of the meaning to Facilitate understanding of
                      the design. For a full description, see IETF RFC 7807
                      [19].
                    type: object
                    required:
                      - status
                      - detail
                    properties:
                      type:
                        description: >
                          A URI reference according to IETF RFC 3986 [5] that
                          identifies the problem type. It is encouraged that the
                          URI provides human-readable documentation for the
                          problem (e.g. using HTML) when dereferenced. When this
                          member is not present, its value is assumed to be
                          "about:blank".
                        type: string
                        format: URI
                      title:
                        description: >
                          A short, human-readable summary of the problem type.
                          It should not change from occurrence to occurrence of
                          the problem, except for purposes of localization. If
                          type is given and other than "about:blank", this
                          attribute shall also be provided. A short,
                          human-readable summary of the problem type.  It SHOULD
                          NOT change from occurrence to occurrence of the
                          problem, except for purposes of localization (e.g.,
                          using proactive content negotiation; see [RFC7231],
                          Section 3.4).
                        type: string
                      status:
                        description: >
                          The HTTP status code for this occurrence of the
                          problem. The HTTP status code ([RFC7231], Section 6)
                          generated by the origin server for this occurrence of
                          the problem.
                        type: integer
                      detail:
                        description: >
                          A human-readable explanation specific to this
                          occurrence of the problem.
                        type: string
                      instance:
                        description: >
                          A URI reference that identifies the specific
                          occurrence of the problem. It may yield further
                          information if dereferenced.
                        type: string
                        format: URI
            '422':
              description: >
                422 UNPROCESSABLE ENTITY

                If the payload body of a request contains syntactically correct
                data (e.g. well-formed JSON) but the data cannot be processed
                (e.g. because it fails validation against a schema), the API
                producer shall respond with this response code. The
                "ProblemDetails" structure shall be provided, and should include
                in the "detail" attribute more information about the source of
                the problem.

                This error response code is only applicable for methods that
                have a request body.
              headers:
                Content-Type:
                  description: The MIME type of the body of the response.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 1
                WWW-Authenticate:
                  description: >
                    Challenge if the corresponding HTTP request has not provided
                    authorization, or error details if the corresponding HTTP
                    request has provided an invalid authorization token.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 0
                Version:
                  description: |
                    Version of the API used in the response.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 1
              content:
                application/json:
                  schema:
                    description: >
                      The definition of the general "ProblemDetails" data
                      structure from IETF RFC 7807 [19] is reproduced inthis
                      structure. Compared to the general framework defined in
                      IETF RFC 7807 [19], the "status" and "detail" attributes
                      are mandated to be included by the present document, to
                      ensure that the response contains additional textual
                      information about an error. IETF RFC 7807 [19] foresees
                      extensibility of the "ProblemDetails" type. It is possible
                      that particular APIs in the present document, or
                      particular implementations, define extensions to define
                      additional attributes that provide more information about
                      the error. The description column only provides some
                      explanation of the meaning to Facilitate understanding of
                      the design. For a full description, see IETF RFC 7807
                      [19].
                    type: object
                    required:
                      - status
                      - detail
                    properties:
                      type:
                        description: >
                          A URI reference according to IETF RFC 3986 [5] that
                          identifies the problem type. It is encouraged that the
                          URI provides human-readable documentation for the
                          problem (e.g. using HTML) when dereferenced. When this
                          member is not present, its value is assumed to be
                          "about:blank".
                        type: string
                        format: URI
                      title:
                        description: >
                          A short, human-readable summary of the problem type.
                          It should not change from occurrence to occurrence of
                          the problem, except for purposes of localization. If
                          type is given and other than "about:blank", this
                          attribute shall also be provided. A short,
                          human-readable summary of the problem type.  It SHOULD
                          NOT change from occurrence to occurrence of the
                          problem, except for purposes of localization (e.g.,
                          using proactive content negotiation; see [RFC7231],
                          Section 3.4).
                        type: string
                      status:
                        description: >
                          The HTTP status code for this occurrence of the
                          problem. The HTTP status code ([RFC7231], Section 6)
                          generated by the origin server for this occurrence of
                          the problem.
                        type: integer
                      detail:
                        description: >
                          A human-readable explanation specific to this
                          occurrence of the problem.
                        type: string
                      instance:
                        description: >
                          A URI reference that identifies the specific
                          occurrence of the problem. It may yield further
                          information if dereferenced.
                        type: string
                        format: URI
            '500':
              description: >
                500 INTERNAL SERVER ERROR

                If there is an application error not related to the client's
                input that cannot be easily mapped to any other HTTP response
                code ("catch all error"), the API producer shall respond with
                this response code. The "ProblemDetails" structure shall be
                provided, and shall include in the "detail" attribute more
                information about the source of the problem.
              headers:
                Content-Type:
                  description: The MIME type of the body of the response.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 1
                WWW-Authenticate:
                  description: >
                    Challenge if the corresponding HTTP request has not provided
                    authorization, or error details if the corresponding HTTP
                    request has provided an invalid authorization token.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 0
                Version:
                  description: |
                    Version of the API used in the response.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 1
              content:
                application/json:
                  schema:
                    description: >
                      The definition of the general "ProblemDetails" data
                      structure from IETF RFC 7807 [19] is reproduced inthis
                      structure. Compared to the general framework defined in
                      IETF RFC 7807 [19], the "status" and "detail" attributes
                      are mandated to be included by the present document, to
                      ensure that the response contains additional textual
                      information about an error. IETF RFC 7807 [19] foresees
                      extensibility of the "ProblemDetails" type. It is possible
                      that particular APIs in the present document, or
                      particular implementations, define extensions to define
                      additional attributes that provide more information about
                      the error. The description column only provides some
                      explanation of the meaning to Facilitate understanding of
                      the design. For a full description, see IETF RFC 7807
                      [19].
                    type: object
                    required:
                      - status
                      - detail
                    properties:
                      type:
                        description: >
                          A URI reference according to IETF RFC 3986 [5] that
                          identifies the problem type. It is encouraged that the
                          URI provides human-readable documentation for the
                          problem (e.g. using HTML) when dereferenced. When this
                          member is not present, its value is assumed to be
                          "about:blank".
                        type: string
                        format: URI
                      title:
                        description: >
                          A short, human-readable summary of the problem type.
                          It should not change from occurrence to occurrence of
                          the problem, except for purposes of localization. If
                          type is given and other than "about:blank", this
                          attribute shall also be provided. A short,
                          human-readable summary of the problem type.  It SHOULD
                          NOT change from occurrence to occurrence of the
                          problem, except for purposes of localization (e.g.,
                          using proactive content negotiation; see [RFC7231],
                          Section 3.4).
                        type: string
                      status:
                        description: >
                          The HTTP status code for this occurrence of the
                          problem. The HTTP status code ([RFC7231], Section 6)
                          generated by the origin server for this occurrence of
                          the problem.
                        type: integer
                      detail:
                        description: >
                          A human-readable explanation specific to this
                          occurrence of the problem.
                        type: string
                      instance:
                        description: >
                          A URI reference that identifies the specific
                          occurrence of the problem. It may yield further
                          information if dereferenced.
                        type: string
                        format: URI
            '503':
              description: >
                503 SERVICE UNAVAILABLE

                If the API producer encounters an internal overload situation of
                itself or of a system it relies on, it should respond with this
                response code, following the provisions in IETF RFC 7231 for the
                use of the "Retry-After" HTTP header and for the alternative to
                refuse the connection. The "ProblemDetails" structure may be
                omitted.
              headers:
                Content-Type:
                  description: The MIME type of the body of the response.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 1
                WWW-Authenticate:
                  description: >
                    Challenge if the corresponding HTTP request has not provided
                    authorization, or error details if the corresponding HTTP
                    request has provided an invalid authorization token.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 0
                Version:
                  description: |
                    Version of the API used in the response.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 1
              content:
                application/json:
                  schema:
                    description: >
                      The definition of the general "ProblemDetails" data
                      structure from IETF RFC 7807 [19] is reproduced inthis
                      structure. Compared to the general framework defined in
                      IETF RFC 7807 [19], the "status" and "detail" attributes
                      are mandated to be included by the present document, to
                      ensure that the response contains additional textual
                      information about an error. IETF RFC 7807 [19] foresees
                      extensibility of the "ProblemDetails" type. It is possible
                      that particular APIs in the present document, or
                      particular implementations, define extensions to define
                      additional attributes that provide more information about
                      the error. The description column only provides some
                      explanation of the meaning to Facilitate understanding of
                      the design. For a full description, see IETF RFC 7807
                      [19].
                    type: object
                    required:
                      - status
                      - detail
                    properties:
                      type:
                        description: >
                          A URI reference according to IETF RFC 3986 [5] that
                          identifies the problem type. It is encouraged that the
                          URI provides human-readable documentation for the
                          problem (e.g. using HTML) when dereferenced. When this
                          member is not present, its value is assumed to be
                          "about:blank".
                        type: string
                        format: URI
                      title:
                        description: >
                          A short, human-readable summary of the problem type.
                          It should not change from occurrence to occurrence of
                          the problem, except for purposes of localization. If
                          type is given and other than "about:blank", this
                          attribute shall also be provided. A short,
                          human-readable summary of the problem type.  It SHOULD
                          NOT change from occurrence to occurrence of the
                          problem, except for purposes of localization (e.g.,
                          using proactive content negotiation; see [RFC7231],
                          Section 3.4).
                        type: string
                      status:
                        description: >
                          The HTTP status code for this occurrence of the
                          problem. The HTTP status code ([RFC7231], Section 6)
                          generated by the origin server for this occurrence of
                          the problem.
                        type: integer
                      detail:
                        description: >
                          A human-readable explanation specific to this
                          occurrence of the problem.
                        type: string
                      instance:
                        description: >
                          A URI reference that identifies the specific
                          occurrence of the problem. It may yield further
                          information if dereferenced.
                        type: string
                        format: URI
            '504':
              description: >
                504 GATEWAY TIMEOUT

                If the API producer encounters a timeout while waiting for a
                response from an upstream server (i.e. a server that the API
                producer communicates with when fulfilling a request), it should
                respond with this response code.
              headers:
                Content-Type:
                  description: The MIME type of the body of the response.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 1
                WWW-Authenticate:
                  description: >
                    Challenge if the corresponding HTTP request has not provided
                    authorization, or error details if the corresponding HTTP
                    request has provided an invalid authorization token.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 0
                Version:
                  description: |
                    Version of the API used in the response.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 1
              content:
                application/json:
                  schema:
                    description: >
                      The definition of the general "ProblemDetails" data
                      structure from IETF RFC 7807 [19] is reproduced inthis
                      structure. Compared to the general framework defined in
                      IETF RFC 7807 [19], the "status" and "detail" attributes
                      are mandated to be included by the present document, to
                      ensure that the response contains additional textual
                      information about an error. IETF RFC 7807 [19] foresees
                      extensibility of the "ProblemDetails" type. It is possible
                      that particular APIs in the present document, or
                      particular implementations, define extensions to define
                      additional attributes that provide more information about
                      the error. The description column only provides some
                      explanation of the meaning to Facilitate understanding of
                      the design. For a full description, see IETF RFC 7807
                      [19].
                    type: object
                    required:
                      - status
                      - detail
                    properties:
                      type:
                        description: >
                          A URI reference according to IETF RFC 3986 [5] that
                          identifies the problem type. It is encouraged that the
                          URI provides human-readable documentation for the
                          problem (e.g. using HTML) when dereferenced. When this
                          member is not present, its value is assumed to be
                          "about:blank".
                        type: string
                        format: URI
                      title:
                        description: >
                          A short, human-readable summary of the problem type.
                          It should not change from occurrence to occurrence of
                          the problem, except for purposes of localization. If
                          type is given and other than "about:blank", this
                          attribute shall also be provided. A short,
                          human-readable summary of the problem type.  It SHOULD
                          NOT change from occurrence to occurrence of the
                          problem, except for purposes of localization (e.g.,
                          using proactive content negotiation; see [RFC7231],
                          Section 3.4).
                        type: string
                      status:
                        description: >
                          The HTTP status code for this occurrence of the
                          problem. The HTTP status code ([RFC7231], Section 6)
                          generated by the origin server for this occurrence of
                          the problem.
                        type: integer
                      detail:
                        description: >
                          A human-readable explanation specific to this
                          occurrence of the problem.
                        type: string
                      instance:
                        description: >
                          A URI reference that identifies the specific
                          occurrence of the problem. It may yield further
                          information if dereferenced.
                        type: string
                        format: URI
        get:
          description: >-
            The GET method allows the API producer to test the notification
            endpoint that is provided by the API consumer, e.g. during
            subscription. This method shall follow the provisions specified in
            the tables 8.5.9.3.2-1 and 8.5.9.3.2-2 for URI query parameters,
            request and response data structures, and response codes.
          parameters:
            - name: Version
              description: >
                Version of the API requested to use when responding to this
                request.
              in: header
              required: true
              schema:
                type: string
            - name: Accept
              description: >
                Content-Types that are acceptable for the response. Reference:
                IETF RFC 7231.
              in: header
              required: true
              schema:
                type: string
            - name: Authorization
              description: >
                The authorization token for the request. Reference: IETF RFC
                7235.
              in: header
              required: false
              schema:
                type: string
          responses:
            '204':
              description: >-
                Shall be returned to indicate that the notification endpoint has
                been tested successfully. The response body shall be empty.
              headers:
                Content-Type:
                  description: The MIME type of the body of the response.
                  schema:
                    type: string
                WWW-Authenticate:
                  description: >
                    Challenge if the corresponding HTTP request has not provided
                    authorization, or error details if the corresponding HTTP
                    request has provided an invalid authorization token.
                  schema:
                    type: string
                Version:
                  description: |
                    Version of the API used in the response.
                  schema:
                    type: string
            '400':
              description: >
                400 BAD REQUEST

                400 code can be returned in the following specified cases, the
                specific cause has to be proper specified in the
                "ProblemDetails" structure to be returned.

                If the request is malformed or syntactically incorrect (e.g. if
                the request URI contains incorrect query parameters or the
                payload body contains a syntactically incorrect data structure),
                the API producer shall respond with this response code. The
                "ProblemDetails" structure shall be provided, and should include
                in the "detail" attribute more information about the source of
                the problem.

                If the response to a GET request which queries a container
                resource would be so big that the performance of the API
                producer is adversely affected, and the API producer does not
                support paging for the affected resource, it shall respond with
                this response code. The "ProblemDetails" structure shall be
                provided, and should include in the "detail" attribute more
                information about the source of the problem.

                If there is an application error related to the client's input
                that cannot be easily mapped to any other HTTP response code
                ("catch all error"), the API producer shall respond with this
                response code. The "ProblemDetails" structure shall be provided,
                and shall include in the "detail" attribute more information
                about the source of the problem.

                If the request contains a malformed access token, the API
                producer should respond with this response. The details of the
                error shall be returned in the WWW Authenticate HTTP header, as
                defined in IETF RFC 6750 and IETF RFC 7235. The ProblemDetails
                structure may be provided.

                The use of this HTTP error response code described above is
                applicable to the use of the OAuth 2.0 for the authorization of
                API requests and notifications, as defined in clauses 4.5.3.3
                and 4.5.3.4.
              headers:
                Content-Type:
                  description: The MIME type of the body of the response.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 1
                WWW-Authenticate:
                  description: >
                    Challenge if the corresponding HTTP request has not provided
                    authorization, or error details if the corresponding HTTP
                    request has provided an invalid authorization token.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 0
                Version:
                  description: |
                    Version of the API used in the response.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 1
              content:
                application/json:
                  schema:
                    description: >
                      The definition of the general "ProblemDetails" data
                      structure from IETF RFC 7807 [19] is reproduced inthis
                      structure. Compared to the general framework defined in
                      IETF RFC 7807 [19], the "status" and "detail" attributes
                      are mandated to be included by the present document, to
                      ensure that the response contains additional textual
                      information about an error. IETF RFC 7807 [19] foresees
                      extensibility of the "ProblemDetails" type. It is possible
                      that particular APIs in the present document, or
                      particular implementations, define extensions to define
                      additional attributes that provide more information about
                      the error. The description column only provides some
                      explanation of the meaning to Facilitate understanding of
                      the design. For a full description, see IETF RFC 7807
                      [19].
                    type: object
                    required:
                      - status
                      - detail
                    properties:
                      type:
                        description: >
                          A URI reference according to IETF RFC 3986 [5] that
                          identifies the problem type. It is encouraged that the
                          URI provides human-readable documentation for the
                          problem (e.g. using HTML) when dereferenced. When this
                          member is not present, its value is assumed to be
                          "about:blank".
                        type: string
                        format: URI
                      title:
                        description: >
                          A short, human-readable summary of the problem type.
                          It should not change from occurrence to occurrence of
                          the problem, except for purposes of localization. If
                          type is given and other than "about:blank", this
                          attribute shall also be provided. A short,
                          human-readable summary of the problem type.  It SHOULD
                          NOT change from occurrence to occurrence of the
                          problem, except for purposes of localization (e.g.,
                          using proactive content negotiation; see [RFC7231],
                          Section 3.4).
                        type: string
                      status:
                        description: >
                          The HTTP status code for this occurrence of the
                          problem. The HTTP status code ([RFC7231], Section 6)
                          generated by the origin server for this occurrence of
                          the problem.
                        type: integer
                      detail:
                        description: >
                          A human-readable explanation specific to this
                          occurrence of the problem.
                        type: string
                      instance:
                        description: >
                          A URI reference that identifies the specific
                          occurrence of the problem. It may yield further
                          information if dereferenced.
                        type: string
                        format: URI
            '401':
              description: >
                401 UNAUTHORIZED

                If the request contains no access token even though one is
                required, or if the request contains an authorization token that
                is invalid (e.g. expired or revoked), the API producer should
                respond with this response. The details of the error shall be
                returned in the WWW-Authenticate HTTP header, as defined in IETF
                RFC 6750 and IETF RFC 7235. The ProblemDetails structure may be
                provided.
              headers:
                Content-Type:
                  description: The MIME type of the body of the response.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 1
                WWW-Authenticate:
                  description: >
                    Challenge if the corresponding HTTP request has not provided
                    authorization, or error details if the corresponding HTTP
                    request has provided an invalid authorization token.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 0
                Version:
                  description: |
                    Version of the API used in the response.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 1
              content:
                application/json:
                  schema:
                    description: >
                      The definition of the general "ProblemDetails" data
                      structure from IETF RFC 7807 [19] is reproduced inthis
                      structure. Compared to the general framework defined in
                      IETF RFC 7807 [19], the "status" and "detail" attributes
                      are mandated to be included by the present document, to
                      ensure that the response contains additional textual
                      information about an error. IETF RFC 7807 [19] foresees
                      extensibility of the "ProblemDetails" type. It is possible
                      that particular APIs in the present document, or
                      particular implementations, define extensions to define
                      additional attributes that provide more information about
                      the error. The description column only provides some
                      explanation of the meaning to Facilitate understanding of
                      the design. For a full description, see IETF RFC 7807
                      [19].
                    type: object
                    required:
                      - status
                      - detail
                    properties:
                      type:
                        description: >
                          A URI reference according to IETF RFC 3986 [5] that
                          identifies the problem type. It is encouraged that the
                          URI provides human-readable documentation for the
                          problem (e.g. using HTML) when dereferenced. When this
                          member is not present, its value is assumed to be
                          "about:blank".
                        type: string
                        format: URI
                      title:
                        description: >
                          A short, human-readable summary of the problem type.
                          It should not change from occurrence to occurrence of
                          the problem, except for purposes of localization. If
                          type is given and other than "about:blank", this
                          attribute shall also be provided. A short,
                          human-readable summary of the problem type.  It SHOULD
                          NOT change from occurrence to occurrence of the
                          problem, except for purposes of localization (e.g.,
                          using proactive content negotiation; see [RFC7231],
                          Section 3.4).
                        type: string
                      status:
                        description: >
                          The HTTP status code for this occurrence of the
                          problem. The HTTP status code ([RFC7231], Section 6)
                          generated by the origin server for this occurrence of
                          the problem.
                        type: integer
                      detail:
                        description: >
                          A human-readable explanation specific to this
                          occurrence of the problem.
                        type: string
                      instance:
                        description: >
                          A URI reference that identifies the specific
                          occurrence of the problem. It may yield further
                          information if dereferenced.
                        type: string
                        format: URI
            '403':
              description: >
                403 FORBIDDEN

                If the API consumer is not allowed to perform a particular
                request to a particular resource, the API producer shall respond
                with this response code. The "ProblemDetails" structure shall be
                provided. It should include in the "detail" attribute
                information about the source of the problem, and may indicate
                how to solve it.
              headers:
                Content-Type:
                  description: The MIME type of the body of the response.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 1
                WWW-Authenticate:
                  description: >
                    Challenge if the corresponding HTTP request has not provided
                    authorization, or error details if the corresponding HTTP
                    request has provided an invalid authorization token.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 0
                Version:
                  description: |
                    Version of the API used in the response.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 1
              content:
                application/json:
                  schema:
                    description: >
                      The definition of the general "ProblemDetails" data
                      structure from IETF RFC 7807 [19] is reproduced inthis
                      structure. Compared to the general framework defined in
                      IETF RFC 7807 [19], the "status" and "detail" attributes
                      are mandated to be included by the present document, to
                      ensure that the response contains additional textual
                      information about an error. IETF RFC 7807 [19] foresees
                      extensibility of the "ProblemDetails" type. It is possible
                      that particular APIs in the present document, or
                      particular implementations, define extensions to define
                      additional attributes that provide more information about
                      the error. The description column only provides some
                      explanation of the meaning to Facilitate understanding of
                      the design. For a full description, see IETF RFC 7807
                      [19].
                    type: object
                    required:
                      - status
                      - detail
                    properties:
                      type:
                        description: >
                          A URI reference according to IETF RFC 3986 [5] that
                          identifies the problem type. It is encouraged that the
                          URI provides human-readable documentation for the
                          problem (e.g. using HTML) when dereferenced. When this
                          member is not present, its value is assumed to be
                          "about:blank".
                        type: string
                        format: URI
                      title:
                        description: >
                          A short, human-readable summary of the problem type.
                          It should not change from occurrence to occurrence of
                          the problem, except for purposes of localization. If
                          type is given and other than "about:blank", this
                          attribute shall also be provided. A short,
                          human-readable summary of the problem type.  It SHOULD
                          NOT change from occurrence to occurrence of the
                          problem, except for purposes of localization (e.g.,
                          using proactive content negotiation; see [RFC7231],
                          Section 3.4).
                        type: string
                      status:
                        description: >
                          The HTTP status code for this occurrence of the
                          problem. The HTTP status code ([RFC7231], Section 6)
                          generated by the origin server for this occurrence of
                          the problem.
                        type: integer
                      detail:
                        description: >
                          A human-readable explanation specific to this
                          occurrence of the problem.
                        type: string
                      instance:
                        description: >
                          A URI reference that identifies the specific
                          occurrence of the problem. It may yield further
                          information if dereferenced.
                        type: string
                        format: URI
            '404':
              description: >
                404 NOT FOUND

                If the API producer did not find a current representation for
                the resource addressed by the URI passed in the request or is
                not willing to disclose that one exists, it shall respond with
                this response code. The "ProblemDetails" structure may be
                provided, including in the "detail" attribute information about
                the source of the problem, e.g. a wrong resource URI variable.

                This response code is not appropriate in case the resource
                addressed by the URI is a container resource which is designed
                to contain child resources, but does not contain any child
                resource at the time the request is received. For a GET request
                to an existing empty container resource, a typical response
                contains a 200 OK response code and a payload body with an empty
                array.
              headers:
                Content-Type:
                  description: The MIME type of the body of the response.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 1
                WWW-Authenticate:
                  description: >
                    Challenge if the corresponding HTTP request has not provided
                    authorization, or error details if the corresponding HTTP
                    request has provided an invalid authorization token.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 0
                Version:
                  description: |
                    Version of the API used in the response.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 1
              content:
                application/json:
                  schema:
                    description: >
                      The definition of the general "ProblemDetails" data
                      structure from IETF RFC 7807 [19] is reproduced inthis
                      structure. Compared to the general framework defined in
                      IETF RFC 7807 [19], the "status" and "detail" attributes
                      are mandated to be included by the present document, to
                      ensure that the response contains additional textual
                      information about an error. IETF RFC 7807 [19] foresees
                      extensibility of the "ProblemDetails" type. It is possible
                      that particular APIs in the present document, or
                      particular implementations, define extensions to define
                      additional attributes that provide more information about
                      the error. The description column only provides some
                      explanation of the meaning to Facilitate understanding of
                      the design. For a full description, see IETF RFC 7807
                      [19].
                    type: object
                    required:
                      - status
                      - detail
                    properties:
                      type:
                        description: >
                          A URI reference according to IETF RFC 3986 [5] that
                          identifies the problem type. It is encouraged that the
                          URI provides human-readable documentation for the
                          problem (e.g. using HTML) when dereferenced. When this
                          member is not present, its value is assumed to be
                          "about:blank".
                        type: string
                        format: URI
                      title:
                        description: >
                          A short, human-readable summary of the problem type.
                          It should not change from occurrence to occurrence of
                          the problem, except for purposes of localization. If
                          type is given and other than "about:blank", this
                          attribute shall also be provided. A short,
                          human-readable summary of the problem type.  It SHOULD
                          NOT change from occurrence to occurrence of the
                          problem, except for purposes of localization (e.g.,
                          using proactive content negotiation; see [RFC7231],
                          Section 3.4).
                        type: string
                      status:
                        description: >
                          The HTTP status code for this occurrence of the
                          problem. The HTTP status code ([RFC7231], Section 6)
                          generated by the origin server for this occurrence of
                          the problem.
                        type: integer
                      detail:
                        description: >
                          A human-readable explanation specific to this
                          occurrence of the problem.
                        type: string
                      instance:
                        description: >
                          A URI reference that identifies the specific
                          occurrence of the problem. It may yield further
                          information if dereferenced.
                        type: string
                        format: URI
            '405':
              description: >
                405 METHOD NOT ALLOWED

                If a particular HTTP method is not supported for a particular
                resource, the API producer shall respond with this response
                code. The "ProblemDetails" structure may be omitted.
              headers:
                Content-Type:
                  description: The MIME type of the body of the response.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 1
                WWW-Authenticate:
                  description: >
                    Challenge if the corresponding HTTP request has not provided
                    authorization, or error details if the corresponding HTTP
                    request has provided an invalid authorization token.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 0
                Version:
                  description: |
                    Version of the API used in the response.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 1
              content:
                application/json:
                  schema:
                    description: >
                      The definition of the general "ProblemDetails" data
                      structure from IETF RFC 7807 [19] is reproduced inthis
                      structure. Compared to the general framework defined in
                      IETF RFC 7807 [19], the "status" and "detail" attributes
                      are mandated to be included by the present document, to
                      ensure that the response contains additional textual
                      information about an error. IETF RFC 7807 [19] foresees
                      extensibility of the "ProblemDetails" type. It is possible
                      that particular APIs in the present document, or
                      particular implementations, define extensions to define
                      additional attributes that provide more information about
                      the error. The description column only provides some
                      explanation of the meaning to Facilitate understanding of
                      the design. For a full description, see IETF RFC 7807
                      [19].
                    type: object
                    required:
                      - status
                      - detail
                    properties:
                      type:
                        description: >
                          A URI reference according to IETF RFC 3986 [5] that
                          identifies the problem type. It is encouraged that the
                          URI provides human-readable documentation for the
                          problem (e.g. using HTML) when dereferenced. When this
                          member is not present, its value is assumed to be
                          "about:blank".
                        type: string
                        format: URI
                      title:
                        description: >
                          A short, human-readable summary of the problem type.
                          It should not change from occurrence to occurrence of
                          the problem, except for purposes of localization. If
                          type is given and other than "about:blank", this
                          attribute shall also be provided. A short,
                          human-readable summary of the problem type.  It SHOULD
                          NOT change from occurrence to occurrence of the
                          problem, except for purposes of localization (e.g.,
                          using proactive content negotiation; see [RFC7231],
                          Section 3.4).
                        type: string
                      status:
                        description: >
                          The HTTP status code for this occurrence of the
                          problem. The HTTP status code ([RFC7231], Section 6)
                          generated by the origin server for this occurrence of
                          the problem.
                        type: integer
                      detail:
                        description: >
                          A human-readable explanation specific to this
                          occurrence of the problem.
                        type: string
                      instance:
                        description: >
                          A URI reference that identifies the specific
                          occurrence of the problem. It may yield further
                          information if dereferenced.
                        type: string
                        format: URI
            '406':
              description: >
                406 NOT ACCEPTABLE

                If the "Accept" HTTP header does not contain at least one name
                of a content type that is acceptable to the API producer, the
                API producer shall respond with this response code. The
                "ProblemDetails" structure may be omitted.
              headers:
                Content-Type:
                  description: The MIME type of the body of the response.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 1
                WWW-Authenticate:
                  description: >
                    Challenge if the corresponding HTTP request has not provided
                    authorization, or error details if the corresponding HTTP
                    request has provided an invalid authorization token.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 0
                Version:
                  description: |
                    Version of the API used in the response.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 1
              content:
                application/json:
                  schema:
                    description: >
                      The definition of the general "ProblemDetails" data
                      structure from IETF RFC 7807 [19] is reproduced inthis
                      structure. Compared to the general framework defined in
                      IETF RFC 7807 [19], the "status" and "detail" attributes
                      are mandated to be included by the present document, to
                      ensure that the response contains additional textual
                      information about an error. IETF RFC 7807 [19] foresees
                      extensibility of the "ProblemDetails" type. It is possible
                      that particular APIs in the present document, or
                      particular implementations, define extensions to define
                      additional attributes that provide more information about
                      the error. The description column only provides some
                      explanation of the meaning to Facilitate understanding of
                      the design. For a full description, see IETF RFC 7807
                      [19].
                    type: object
                    required:
                      - status
                      - detail
                    properties:
                      type:
                        description: >
                          A URI reference according to IETF RFC 3986 [5] that
                          identifies the problem type. It is encouraged that the
                          URI provides human-readable documentation for the
                          problem (e.g. using HTML) when dereferenced. When this
                          member is not present, its value is assumed to be
                          "about:blank".
                        type: string
                        format: URI
                      title:
                        description: >
                          A short, human-readable summary of the problem type.
                          It should not change from occurrence to occurrence of
                          the problem, except for purposes of localization. If
                          type is given and other than "about:blank", this
                          attribute shall also be provided. A short,
                          human-readable summary of the problem type.  It SHOULD
                          NOT change from occurrence to occurrence of the
                          problem, except for purposes of localization (e.g.,
                          using proactive content negotiation; see [RFC7231],
                          Section 3.4).
                        type: string
                      status:
                        description: >
                          The HTTP status code for this occurrence of the
                          problem. The HTTP status code ([RFC7231], Section 6)
                          generated by the origin server for this occurrence of
                          the problem.
                        type: integer
                      detail:
                        description: >
                          A human-readable explanation specific to this
                          occurrence of the problem.
                        type: string
                      instance:
                        description: >
                          A URI reference that identifies the specific
                          occurrence of the problem. It may yield further
                          information if dereferenced.
                        type: string
                        format: URI
            '422':
              description: >
                422 UNPROCESSABLE ENTITY

                If the payload body of a request contains syntactically correct
                data (e.g. well-formed JSON) but the data cannot be processed
                (e.g. because it fails validation against a schema), the API
                producer shall respond with this response code. The
                "ProblemDetails" structure shall be provided, and should include
                in the "detail" attribute more information about the source of
                the problem.

                This error response code is only applicable for methods that
                have a request body.
              headers:
                Content-Type:
                  description: The MIME type of the body of the response.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 1
                WWW-Authenticate:
                  description: >
                    Challenge if the corresponding HTTP request has not provided
                    authorization, or error details if the corresponding HTTP
                    request has provided an invalid authorization token.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 0
                Version:
                  description: |
                    Version of the API used in the response.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 1
              content:
                application/json:
                  schema:
                    description: >
                      The definition of the general "ProblemDetails" data
                      structure from IETF RFC 7807 [19] is reproduced inthis
                      structure. Compared to the general framework defined in
                      IETF RFC 7807 [19], the "status" and "detail" attributes
                      are mandated to be included by the present document, to
                      ensure that the response contains additional textual
                      information about an error. IETF RFC 7807 [19] foresees
                      extensibility of the "ProblemDetails" type. It is possible
                      that particular APIs in the present document, or
                      particular implementations, define extensions to define
                      additional attributes that provide more information about
                      the error. The description column only provides some
                      explanation of the meaning to Facilitate understanding of
                      the design. For a full description, see IETF RFC 7807
                      [19].
                    type: object
                    required:
                      - status
                      - detail
                    properties:
                      type:
                        description: >
                          A URI reference according to IETF RFC 3986 [5] that
                          identifies the problem type. It is encouraged that the
                          URI provides human-readable documentation for the
                          problem (e.g. using HTML) when dereferenced. When this
                          member is not present, its value is assumed to be
                          "about:blank".
                        type: string
                        format: URI
                      title:
                        description: >
                          A short, human-readable summary of the problem type.
                          It should not change from occurrence to occurrence of
                          the problem, except for purposes of localization. If
                          type is given and other than "about:blank", this
                          attribute shall also be provided. A short,
                          human-readable summary of the problem type.  It SHOULD
                          NOT change from occurrence to occurrence of the
                          problem, except for purposes of localization (e.g.,
                          using proactive content negotiation; see [RFC7231],
                          Section 3.4).
                        type: string
                      status:
                        description: >
                          The HTTP status code for this occurrence of the
                          problem. The HTTP status code ([RFC7231], Section 6)
                          generated by the origin server for this occurrence of
                          the problem.
                        type: integer
                      detail:
                        description: >
                          A human-readable explanation specific to this
                          occurrence of the problem.
                        type: string
                      instance:
                        description: >
                          A URI reference that identifies the specific
                          occurrence of the problem. It may yield further
                          information if dereferenced.
                        type: string
                        format: URI
            '500':
              description: >
                500 INTERNAL SERVER ERROR

                If there is an application error not related to the client's
                input that cannot be easily mapped to any other HTTP response
                code ("catch all error"), the API producer shall respond with
                this response code. The "ProblemDetails" structure shall be
                provided, and shall include in the "detail" attribute more
                information about the source of the problem.
              headers:
                Content-Type:
                  description: The MIME type of the body of the response.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 1
                WWW-Authenticate:
                  description: >
                    Challenge if the corresponding HTTP request has not provided
                    authorization, or error details if the corresponding HTTP
                    request has provided an invalid authorization token.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 0
                Version:
                  description: |
                    Version of the API used in the response.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 1
              content:
                application/json:
                  schema:
                    description: >
                      The definition of the general "ProblemDetails" data
                      structure from IETF RFC 7807 [19] is reproduced inthis
                      structure. Compared to the general framework defined in
                      IETF RFC 7807 [19], the "status" and "detail" attributes
                      are mandated to be included by the present document, to
                      ensure that the response contains additional textual
                      information about an error. IETF RFC 7807 [19] foresees
                      extensibility of the "ProblemDetails" type. It is possible
                      that particular APIs in the present document, or
                      particular implementations, define extensions to define
                      additional attributes that provide more information about
                      the error. The description column only provides some
                      explanation of the meaning to Facilitate understanding of
                      the design. For a full description, see IETF RFC 7807
                      [19].
                    type: object
                    required:
                      - status
                      - detail
                    properties:
                      type:
                        description: >
                          A URI reference according to IETF RFC 3986 [5] that
                          identifies the problem type. It is encouraged that the
                          URI provides human-readable documentation for the
                          problem (e.g. using HTML) when dereferenced. When this
                          member is not present, its value is assumed to be
                          "about:blank".
                        type: string
                        format: URI
                      title:
                        description: >
                          A short, human-readable summary of the problem type.
                          It should not change from occurrence to occurrence of
                          the problem, except for purposes of localization. If
                          type is given and other than "about:blank", this
                          attribute shall also be provided. A short,
                          human-readable summary of the problem type.  It SHOULD
                          NOT change from occurrence to occurrence of the
                          problem, except for purposes of localization (e.g.,
                          using proactive content negotiation; see [RFC7231],
                          Section 3.4).
                        type: string
                      status:
                        description: >
                          The HTTP status code for this occurrence of the
                          problem. The HTTP status code ([RFC7231], Section 6)
                          generated by the origin server for this occurrence of
                          the problem.
                        type: integer
                      detail:
                        description: >
                          A human-readable explanation specific to this
                          occurrence of the problem.
                        type: string
                      instance:
                        description: >
                          A URI reference that identifies the specific
                          occurrence of the problem. It may yield further
                          information if dereferenced.
                        type: string
                        format: URI
            '503':
              description: >
                503 SERVICE UNAVAILABLE

                If the API producer encounters an internal overload situation of
                itself or of a system it relies on, it should respond with this
                response code, following the provisions in IETF RFC 7231 for the
                use of the "Retry-After" HTTP header and for the alternative to
                refuse the connection. The "ProblemDetails" structure may be
                omitted.
              headers:
                Content-Type:
                  description: The MIME type of the body of the response.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 1
                WWW-Authenticate:
                  description: >
                    Challenge if the corresponding HTTP request has not provided
                    authorization, or error details if the corresponding HTTP
                    request has provided an invalid authorization token.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 0
                Version:
                  description: |
                    Version of the API used in the response.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 1
              content:
                application/json:
                  schema:
                    description: >
                      The definition of the general "ProblemDetails" data
                      structure from IETF RFC 7807 [19] is reproduced inthis
                      structure. Compared to the general framework defined in
                      IETF RFC 7807 [19], the "status" and "detail" attributes
                      are mandated to be included by the present document, to
                      ensure that the response contains additional textual
                      information about an error. IETF RFC 7807 [19] foresees
                      extensibility of the "ProblemDetails" type. It is possible
                      that particular APIs in the present document, or
                      particular implementations, define extensions to define
                      additional attributes that provide more information about
                      the error. The description column only provides some
                      explanation of the meaning to Facilitate understanding of
                      the design. For a full description, see IETF RFC 7807
                      [19].
                    type: object
                    required:
                      - status
                      - detail
                    properties:
                      type:
                        description: >
                          A URI reference according to IETF RFC 3986 [5] that
                          identifies the problem type. It is encouraged that the
                          URI provides human-readable documentation for the
                          problem (e.g. using HTML) when dereferenced. When this
                          member is not present, its value is assumed to be
                          "about:blank".
                        type: string
                        format: URI
                      title:
                        description: >
                          A short, human-readable summary of the problem type.
                          It should not change from occurrence to occurrence of
                          the problem, except for purposes of localization. If
                          type is given and other than "about:blank", this
                          attribute shall also be provided. A short,
                          human-readable summary of the problem type.  It SHOULD
                          NOT change from occurrence to occurrence of the
                          problem, except for purposes of localization (e.g.,
                          using proactive content negotiation; see [RFC7231],
                          Section 3.4).
                        type: string
                      status:
                        description: >
                          The HTTP status code for this occurrence of the
                          problem. The HTTP status code ([RFC7231], Section 6)
                          generated by the origin server for this occurrence of
                          the problem.
                        type: integer
                      detail:
                        description: >
                          A human-readable explanation specific to this
                          occurrence of the problem.
                        type: string
                      instance:
                        description: >
                          A URI reference that identifies the specific
                          occurrence of the problem. It may yield further
                          information if dereferenced.
                        type: string
                        format: URI
            '504':
              description: >
                504 GATEWAY TIMEOUT

                If the API producer encounters a timeout while waiting for a
                response from an upstream server (i.e. a server that the API
                producer communicates with when fulfilling a request), it should
                respond with this response code.
              headers:
                Content-Type:
                  description: The MIME type of the body of the response.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 1
                WWW-Authenticate:
                  description: >
                    Challenge if the corresponding HTTP request has not provided
                    authorization, or error details if the corresponding HTTP
                    request has provided an invalid authorization token.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 0
                Version:
                  description: |
                    Version of the API used in the response.
                  schema:
                    type: string
                    maximum: 1
                    minimum: 1
              content:
                application/json:
                  schema:
                    description: >
                      The definition of the general "ProblemDetails" data
                      structure from IETF RFC 7807 [19] is reproduced inthis
                      structure. Compared to the general framework defined in
                      IETF RFC 7807 [19], the "status" and "detail" attributes
                      are mandated to be included by the present document, to
                      ensure that the response contains additional textual
                      information about an error. IETF RFC 7807 [19] foresees
                      extensibility of the "ProblemDetails" type. It is possible
                      that particular APIs in the present document, or
                      particular implementations, define extensions to define
                      additional attributes that provide more information about
                      the error. The description column only provides some
                      explanation of the meaning to Facilitate understanding of
                      the design. For a full description, see IETF RFC 7807
                      [19].
                    type: object
                    required:
                      - status
                      - detail
                    properties:
                      type:
                        description: >
                          A URI reference according to IETF RFC 3986 [5] that
                          identifies the problem type. It is encouraged that the
                          URI provides human-readable documentation for the
                          problem (e.g. using HTML) when dereferenced. When this
                          member is not present, its value is assumed to be
                          "about:blank".
                        type: string
                        format: URI
                      title:
                        description: >
                          A short, human-readable summary of the problem type.
                          It should not change from occurrence to occurrence of
                          the problem, except for purposes of localization. If
                          type is given and other than "about:blank", this
                          attribute shall also be provided. A short,
                          human-readable summary of the problem type.  It SHOULD
                          NOT change from occurrence to occurrence of the
                          problem, except for purposes of localization (e.g.,
                          using proactive content negotiation; see [RFC7231],
                          Section 3.4).
                        type: string
                      status:
                        description: >
                          The HTTP status code for this occurrence of the
                          problem. The HTTP status code ([RFC7231], Section 6)
                          generated by the origin server for this occurrence of
                          the problem.
                        type: integer
                      detail:
                        description: >
                          A human-readable explanation specific to this
                          occurrence of the problem.
                        type: string
                      instance:
                        description: >
                          A URI reference that identifies the specific
                          occurrence of the problem. It may yield further
                          information if dereferenced.
                        type: string
                        format: URI

