---
seo:
    title: "Descriptive Sections"
    description: "The FinSpec structure array defines the ordered table of contents and HTML content for rendered documentation."
llm_context: "Reference for the FinSpec structure key - the ordered array of labelled sections with HTML content that drives the rendered documentation table of contents."
category: "reference"
related:
    - "/finspec/reference"
    - "/finspec/reference/fieldsets"
---

## Descriptive Sections

:::warning FixSpec-Specific Vendor Extension
The descriptive section presented here is specific to FixSpec software and may not be supported by other implementations.
:::

`structure` is the **table of contents** for the rendered documentation. It is an optional,
ordered array of section objects. Each section has a label and an HTML `content` string.

```json
"structure": [
  {
    "label": "Session Messages",
    "uri": "session-messages",
    "content": "<finspec data-type=\"message\" data-ref=\"abc123\"></finspec>"
  },
  {
    "label": "Application Messages",
    "content": "<p>The following messages are supported for order management.</p><finspec data-type=\"message\" data-ref=\"def456\"></finspec>"
  },
  {
    "label": "Re-usable Components",
    "content": "<finspec data-type=\"component\" data-ref=\"ghi789\"></finspec>"
  }
]
```

```jsonSchema protocol=finspec version=5.2-internal def=structure
{
    "type": "array",
    "minItems": 1,
    "uniqueItems": true,
    "description": "The ordered array of descriptive sections. FixSpec software only.",
    "items": {
        "type": "object",
        "required": [
            "label",
            "content"
        ],
        "description": "A single descriptive section (page) within the overall document structure. FixSpec software only.",
        "additionalProperties": false,
        "patternProperties": {
            "^x-": {
                "$refName": "vendorExtension",
                "$refResolved": false
            }
        },
        "properties": {
            "label": {
                "type": "string",
                "description": "The label for the descriptive section (used for the navigation menu)."
            },
            "content": {
                "type": "string",
                "description": "The HTML content for the descriptive section."
            },
            "uri": {
                "type": "string",
                "description": "The URI fragment for the descriptive section, used for navigation. Generated from `label` if missing."
            }
        },
        "$refName": "structureSection",
        "$refResolved": true
    }
}
```

### Embedding Fieldsets

:::warning FixSpec Conformance Software Only!
Note that this reference to embedding fieldsets related **only** to FixSpec's conformance software. For information on how to reference fieldsets in this portal software, see [Inlined API & Schema References](/portal/reference/endpoints_schemas#inlined-api-schema-references).
:::

Within `content`, a custom HTML element of `<finspec>` is used to embed FIX messages (described elsewhere in the FinSpec). To achieve this, the renderer needs two, mandatory `data-` attributes:

| Attribute   | Description                                                                         |
| ----------- | ----------------------------------------------------------------------------------- |
| `data-type` | The type of fieldset to render. Valid values are `message`, `view`, or `component`. |
| `data-ref`  | The unique `key` of the entry within the FinSpec.                                   |

Note that the `<finspec>` element typically has no internal content.
