> For the complete documentation index, see [llms.txt](https://docs.openbrim.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openbrim.org/developers/paramml-developer-guide/what-are-object-and-parameter.md).

# What are Object and Parameter?

In ParamML, each object is defined by its own set of parameters. Objects are defined using "O" statements, while parameters are defined using "P" statements. Each object and parameter has a start and end statement.

For example, for an object named "group," the starting expression would be and the closing expression would be .

Similarly, for a parameter named "length," the starting expression would be

and the closing expression would be

.

Everything between the beginning and end statements is considered to be part of the parameter or object to which it belongs. For an object to have meaning, it must be defined with parameters that are compatible with the type of the object. Similarly, a parameter's meaning can depend on the hierarchical position in which it is defined. If an expression does not contain other expressions, abbreviations may be used.

**Example**

**Object:**

```
<O N="group" T="Group">
....
....
</O>
```

**Parameter:**

```
<P N="length" V="10"/>
```


---

# 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.openbrim.org/developers/paramml-developer-guide/what-are-object-and-parameter.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.