# Components

Most extensions include additional concepts, descriptions and/or relationships. It is therefore important for extension producers to understand the logical design of these components, and any extension-specific rule related to these components.

The following subsections present logical design rules and considerations for components in an extension:

* Common Attributes
* Concepts
* Descriptions
* Relationships

For information about the process of authoring extension components, please refer to [Authoring](https://github.com/SNOMED-Documents/extension-guide/blob/main/5%20key-steps/5.4%20authoring). For a full list of RF2 component tables and their attributes, please refer to the [SNOMED CT Release File Specifications](https://app.gitbook.com/o/h8Z6qGxuQrzM9vbx5bPT/s/irKbJsZG57nSWZA4GT0M/).

<a href="https://docs.google.com/forms/d/e/1FAIpQLScTmbZIf0UEQwYDkY27EEWBkaiYkHSbR0_9DmFrMLXoQLyL7Q/viewform?usp=pp_url&#x26;entry.1767247133=Extension+Guide&#x26;entry.670899847=Components" class="button primary">Provide Feedback</a>


---

# Agent Instructions: 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:

```
GET https://docs.snomed.org/snomed-ct-practical-guides/snomed-ct-extension-guide/4-logical-design/4.3-extensions/4.3.1-components.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
