> For the complete documentation index, see [llms.txt](https://mims.oascities.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mims.oascities.org/mims-specification-v9.0/interlinking-data/capabilities-and-requirements.md).

# Capabilities and Requirements

## C1: Entities are identified using unique identifiers

**​Requirements:**

* R1.1: Every entity within the system has a unique identifier
* R1.2: There exists a way to retrieve information about an entity by looking up the identifier within a system
* R1.3: if a unique identifier points to the same entity within multiple systems, it is possible to derive the way to look up information about it in each of these systems
* R1.4: if a multiple unique identifiers point to the same entity, it is possible to map them
* R1.5: It is possible to create identifiers that are persistent over time

​

## C2: Entities can be typed

When retrieving information about an entity, it should be possible to retrieve the semantics describing that information

> Questions: 
>
> * Should this retrieval of semantics be possible in an automated way or may it be manual?
> * Can an entity have multiple Types (should this be included in this capability?)

**Requirements:**​

* R2.1: There is a way to retreive the semantics of an entity, only using its unique identifier
* R2.2: These semantics are described in a machine-readable format

## ​C3: Entities can be (de)referenced

{% hint style="info" %}
Definition: *dereferencing.* To dereference is to access a value or object located in a memory location stored in a pointer—the pointer directs you to the stored value. In the context of Linked Data (LD), dereferencing is used in relation to Uniform Resource Identifiers (URIs) and whether or not they are dereferenceable.
{% endhint %}

**Requirements:**

* R3.1: There exists a way to dereference a relation defined on an entity
* R3.2: There exists a way to apply additional semantics to an existing ontology


---

# 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://mims.oascities.org/mims-specification-v9.0/interlinking-data/capabilities-and-requirements.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.