> For the complete documentation index, see [llms.txt](https://docs.b2ihealthcare.com/snow-owl-authoring-platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.b2ihealthcare.com/snow-owl-authoring-platform/concept-model/editing-mrcm/attribute.md).
# Attribute
The tree at the bottom left quadrant of the editor represents all the allowed attributes for the current domain selection. If the current domain selection has parent domains the attribute members connected to that domain are also listed here. The attributes explicitly assigned to the selected domain are shown in bold to distinguish these from those inherited from the parent domain.
MRCM Attributes
Example
In the picture above *Laterality* is shown in bold because there is an MRCM attribute domain member that links this attribute with the Lateralisable body structure domain. No MRCM attribute domain member links '*Proper part of '* with the same domain, so it's not in bold. It does have a member that links it with its parent domain, *Body structure*, so it is still applicable within the *Lateralizable body structure* domain.
The attributes in the tree are arranged by their relative relationship within the SNOMED CT tree.
{% hint style="info" %}
Selecting a node displays its details on the right side of the editor in the Attribute tab.
{% endhint %}
MRCM Attributes
You can add a new attribute member by using the  *Create new attribute rule* button in the top right corner of the Attributes section. It will open the wizard below. The first field will let you choose the referenced component of the MRCM attribute domain member. It is limited to concepts within the attribute hierarchy. The second field is auto-populated with the current domain selection.
The third field allows you to specify if this attribute is meant to be in a relationship group.
The attribute cardinality fields allow you to set the overall cardinality limits for this attribute on a concept while the in-group cardinality fields allow you to set cardinality limits applicable per relationship group. Note that Attribute in-group cardinality can only be applied if the attribute is grouped.
The *Rule strength* and *Content type* can be specified as well. These fields are auto-filled with the most common values.
Create new attribute rule wizard
{% hint style="info" %}
Cardinality, rule strength, and content type settings serve as guidance and do not factor into validation.
{% endhint %}
{% hint style="info" %}
The grouped setting will affect the OWL axiom members of concepts that use this attribute.
{% endhint %}
You can also add a new attribute member by right-clicking one of the nodes in the attribute tree and choosing  *Add new attribute member*. Deleting a member is also accessible from the same context menu through the *Delete attribute member* action. Released members will be inactivated, unpublished members will be removed by this action.
Remove attribute member action
{% hint style="info" %}
You can only remove/inactivate members if they are in your extension's module.
{% endhint %}
{% hint style="info" %}
If you choose to remove an attribute domain member with associated attribute range members the range members will be removed as well, as long as they are in your extension's module.
{% endhint %}
The attribute members in your extension can also be modified on the details page on the right under the Attribute tab.
Attribute details tab
---
# 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://docs.b2ihealthcare.com/snow-owl-authoring-platform/concept-model/editing-mrcm/attribute.md?ask=&goal=
```
`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.