The elements of the imx platform tend to follow a simple hierarchical structure.
| Root server | A registry of discoverable domains, users and content; with simple store-and-forward feature for notifications during off-times and provides content notary/timestamping and user / content authentication. |
|---|---|
| Domain | An instance (single deployment) of imx. A domain can serve one or more spaces. |
| Space | A department in the domain that serves a special interest. A space has multiple sections. A section has a hierarchy of folders and entries. Each data space maintains its own access-control configuration. |
| Section | A top-level folder in the space that is designated a specific function or meaning. |
| Folder | File-system based arbitrary structure to help organize the data. |
| Entry | Self-contained digital asset with it's belongings such as metadata, attachments, user interactions, change history …etc. Persisted in the form of hierarchical structure of files and folders (aka flat-file). |
| Attachment | A belonging to the entry. Such as binary attachments, documents, images …etc |
| Interaction | Users' interactions with the entry such as comments, shares, reactions (like/dislike …) |
| Metadata | Additional metal data associated with the entity such as tags, description, publish-status and so on. |
| History | Detailed traceable history log of activities and changes |