mirror of
https://github.com/oceanprotocol/docs.git
synced 2024-11-26 19:49:26 +01:00
fb1fb5eaa3
@dgossen said he's not comfortable using "tribe" and I agree. @aaitor When I asked Trent about this, he said we might use "tribe" internally and informally, but it shouldn't be used in official communications.
33 lines
1.0 KiB
Markdown
33 lines
1.0 KiB
Markdown
---
|
|
title: Terminology
|
|
description: Terminology specific to Ocean Protocol.
|
|
---
|
|
|
|
## Asset or Data Asset
|
|
|
|
A data set or data service.
|
|
|
|
## Data Owner or Data Service Provider
|
|
|
|
Someone who has assets that they want to sell (or give away freely). An example is an almond distributor with 30 years of data about almond sales.
|
|
|
|
Note: Initially, most data owners or data service providers will also be the publishers of their own assets.
|
|
|
|
## Publisher
|
|
|
|
A service which mediates access to assets on behalf of data owners or data service providers.
|
|
|
|
Note: Initially, most publishers will also be the owners of the data assets they publish.
|
|
|
|
## Consumer
|
|
|
|
Someone who wants assets. An example is a data scientist working at an economic think tank.
|
|
|
|
## Marketplace
|
|
|
|
A service where publishers can list what assets they have, and consumers can see what's available then buy it (or get it for free). The Ocean network supports many marketplaces/tribes.
|
|
|
|
## More Terminology
|
|
|
|
See the page about Ocean's [Software Components](/concepts/components/).
|