An asset domain is a domain that stands for a resource with measurable value: a building, a piece of land, a vehicle, a device, a dataset or a piece of software. It is a kind of digital twin domain, and like every domain it has an ownable entity, a DID, an on-chain record (its IID document) and the other parts listed in Core concepts.
Read this page to see how assets are represented and grouped. For the record's fields and how to create one, use Digital twins.
Kinds of asset
| Kind | Examples |
|---|---|
| Physical | Buildings, land, vehicles, infrastructure |
| Digital | Software, datasets, digital media |
| Mixed | Assets that combine physical and digital parts |
What an asset domain holds
| Part | What it does for an asset |
|---|---|
| Entity | An NFT that can be owned and transferred, so ownership of the asset is recorded on chain |
| DID and IID document | The asset's identifier, and its record of keys, controllers and service endpoints |
| Services | Endpoints that take in data from sensors, remote feeds or people |
| Matrix space and VFS | An encrypted data store for the asset's data, built on the Matrix protocol, which can be shared with other domains |
| Linked claims | Signed records of events and data about the asset |
Claims about an asset are decided like any other claim: a decision oracle produces the facts and the IXO decision engine applies the rules. A decided outcome can be issued as a verifiable credential. A signed claim about an asset shows who said what about it. It does not show that it is true. See What each record proves.
Asset collections
Assets can be grouped into collections, and a collection is itself a domain. Collections are used for portfolios, projects, funds and programmes; for geographic groups such as countries, regions, cities and neighbourhoods; for infrastructure such as buildings, facilities, equipment and vehicles; and for digital resources such as software, data, media and design assets.