{
  "title": "BodyLike",
  "description": "Each response MAY contain a body property, which conforms to the same structure as request body properties (see Body). Responses that can return more than one response code MAY therefore have multiple bodies defined. For APIs without a priori knowledge of the response types for their responses, `*/*` MAY be used to indicate that responses that do not matching other defined data types MUST be accepted. Processing applications MUST match the most descriptive media type first if `*/*` is used.",
  "type": null,
  "children": [
    {
      "title": "name",
      "description": "Mime type of the request or response body",
      "type": "ATTRIBUTETEXT",
      "children": [],
      "valueText": "application/raml+yaml",
      "id": "./resource.get.200.application/raml+yaml#name"
    },
    {
      "title": "General",
      "description": "",
      "type": "CATEGORY",
      "children": [
        {
          "title": "example",
          "description": "Documentation generators MUST use body properties' example attributes to generate example invocations.",
          "type": "ATTRIBUTETEXT",
          "children": [],
          "valueText": null,
          "id": "./resource.get.200.application/raml+yaml#example"
        },
        {
          "title": "schema",
          "description": "The structure of a request or response body MAY be further specified by the schema property under the appropriate media type. The schema key CANNOT be specified if a body's media type is application/x-www-form-urlencoded or multipart/form-data. All parsers of RAML MUST be able to interpret JSON Schema and XML Schema. Schema MAY be declared inline or in an external file. However, if the schema is sufficiently large so as to make it difficult for a person to read the API definition, or the schema is reused across multiple APIs or across multiple miles in the same API, the !include user-defined data type SHOULD be used instead of including the content inline. Alternatively, the value of the schema field MAY be the name of a schema specified in the root-level schemas property, or it MAY be declared in an external file and included by using the by using the RAML !include user-defined data type.",
          "type": "ATTRIBUTETEXT",
          "children": [],
          "valueText": null,
          "id": "./resource.get.200.application/raml+yaml#schema"
        },
        {
          "title": "formParameters",
          "description": "Insert formParameters",
          "type": "DETAILS_ACTION",
          "children": [],
          "id": "./resource.get.200.application/raml+yaml#formParameters#",
          "subType": "INSERT"
        },
        {
          "title": "Delete",
          "description": "",
          "type": "DETAILS_ACTION",
          "children": [],
          "id": "./resource.get.200.application/raml+yaml#DELETE_DETAILS_ACTION",
          "subType": "DELETE"
        }
      ],
      "valueText": null,
      "id": "Category#General"
    },
    {
      "title": "Documentation",
      "description": "",
      "type": "CATEGORY",
      "children": [
        {
          "title": "description",
          "description": "Human readable description of the body",
          "type": "MARKDOWN",
          "children": [],
          "valueText": null,
          "id": "./resource.get.200.application/raml+yaml#description"
        }
      ],
      "valueText": null,
      "id": "Category#Documentation"
    }
  ],
  "valueText": null,
  "id": "Category#BodyLike"
}