> For the complete documentation index, see [llms.txt](https://docs.intersectmbo.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intersectmbo.org/intersect-knowledge-base/archive/cardano-governance-archive/key-terms/metadata.md).

# Metadata

{% hint style="danger" %}
**ARCHIVED**

This page has been archived. It's content might be outdated.
{% endhint %}

In the CIP-1694 Governance Metadata refers to any Off-Chain extra data submitted On-Chain to provide extra context.\
\
These include:

* **DRep Metadata:**\
  These are optionally submitted during DRep registration and should allow DRep to provide more context about themselves.
* **Governance Actions Metadata:**\
  These are optionally submitted during Governance Action submission and allow proposers to provide extra context about their Governance Action to the voters to allow them to make an informed decision.
* **Vote Metadata:**\
  These are optionally submitted when any of the voting bodies (DReps, SPOs, Constitutional Committee Members) submit their vote to provide extra context about their decision. For Constitutionally Committee Members is mandatory to submit a rationale about their vote and so to submit metadata with their vote.

Note: When submitted On-Chain, Metadata will be made of a URL where a .JSONLD file is stored and a Hash of that URL. (More info can be found here in CIP-1694)

***

Currently the structure of these metadata is in progress of being defined by the community in [CIP-100?](https://github.com/cardano-foundation/CIPs/pull/556)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.intersectmbo.org/intersect-knowledge-base/archive/cardano-governance-archive/key-terms/metadata.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.