> For the complete documentation index, see [llms.txt](https://relationlabs.gitbook.io/protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://relationlabs.gitbook.io/protocol/protocol-zh/contract-open-standard/overview.md).

# 概述

Contract Open Standard是Relation Protocol约定的智能合约标准，标准包含一下两部分约定：

* 合约需要符合[Open Standard API](/protocol/protocol-zh/open-standard-api/introduction.md)中所定义的数据格式和接口规范
* 合约构建的RDF数据需要符合[Schema Standard](/protocol/protocol-zh/schema-standard/overview.md)

基于Contract Open Standard，Relation Protocol预制了一组Base Contracts，主要应用于以下三种场景：

**Identity**：通过SBT合约描述用户的个人身份

* Name Service合约

**Relationships**：通过SBT合约描述人与人之间的联系

* Follow
* DAO

**Publication**：通过SBT描述用户向大众或特定对象公开发布的内容

* Content
* Privacy Content

<figure><img src="/files/DI35bJNoQXnkCit68B98" alt=""><figcaption><p>图 5-1 Base Contracts</p></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://relationlabs.gitbook.io/protocol/protocol-zh/contract-open-standard/overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
