From 2daab3a2e6b4601b8c1f4fb52a7b2cf8e782a474 Mon Sep 17 00:00:00 2001 From: Matthias Kretschmann <m@kretschmann.io> Date: Thu, 12 Sep 2019 11:57:50 +0200 Subject: [PATCH] copy updates --- content/concepts/components.md | 18 ++++++++++++++---- content/concepts/terminology.md | 10 ++++++---- data/repositories.yml | 2 +- 3 files changed, 21 insertions(+), 9 deletions(-) diff --git a/content/concepts/components.md b/content/concepts/components.md index f329779e..37f53000 100644 --- a/content/concepts/components.md +++ b/content/concepts/components.md @@ -42,7 +42,11 @@ Aquarius supports several options for the off-chain database (OceanDB), includin <repo name="oceandb-elasticsearch-driver"></repo> <repo name="oceandb-mongodb-driver"></repo> -Note: There is also a BigchainDB driver but it hasn't been maintained. +> There is also a [BigchainDB driver](https://github.com/oceanprotocol/oceandb-bigchaindb-driver) but it hasn't been maintained. + +You can create your own OceanDB drivers by extending on the `oceandb-driver-interface`. + +<repo name="oceandb-driver-interface"></repo> ## Brizo @@ -54,11 +58,13 @@ The most basic scenario for a publisher is to provide access to the [assets](/co ### Events Handler -Brizo communicates with the Events Handler, which is an agent dealing with Keeper Contracts events... +Brizo communicates with the Events Handler, which is an agent dealing with Keeper Contracts events. -... +It monitors Service Execution Agreement (SEA) events and acts as a provider agent to grant access and release rewards for the publisher/provider. This is a critical part in the process of consuming data sets in the Ocean Protocol network. -<repo name="events-handler-py"></repo> +Every provider in the network must run some sort of an events-handler to be able to fulfill the access condition of an `Access` service in a Service Execution Agreement. + +<repo name="events-handler"></repo> ### Osmosis Drivers @@ -68,6 +74,10 @@ Brizo supports several options for file storage, including Azure Storage, Amazon <repo name="osmosis-aws-driver"></repo> <repo name="osmosis-on-premise-driver"></repo> +You can create your own Osmosis drivers by extending on the `osmosis-driver-interface`. + +<repo name="osmosis-driver-interface"></repo> + ## Squid Libraries Client libraries used by applications (such as Pleuston or Jupyter notebooks) to interact with Ocean components, including Keepers, Aquarius nodes, Brizo nodes, etc. diff --git a/content/concepts/terminology.md b/content/concepts/terminology.md index d46a57b7..c952c500 100644 --- a/content/concepts/terminology.md +++ b/content/concepts/terminology.md @@ -8,7 +8,7 @@ description: Terminology specific to Ocean Protocol. Any EVM-compatible network where all[^1] the Ocean Protocol smart contracts ([keeper contracts](https://github.com/oceanprotocol/keeper-contracts)) are deployed. There can be many Ocean networks and you can use the Ocean Protocol in several EVM-compatible networks, including: - the Ethereum Mainnet (also called the Main Ethereum Network) -- the Ocean [Pacific Network](/concepts/pacific-network/) +- the Ocean [Pacific Main Network](/concepts/pacific-network/) - various Ocean [test networks](/concepts/testnets/) ## Asset or Data Asset @@ -43,11 +43,13 @@ A person or a software service that checks some steps in transactions. For examp A contract-like agreement between a publisher, a consumer, and a verifier, specifying what assets are to be delivered (from publisher to consumer), the conditions that must be met, and the rewards for fulfilling the conditions. -We published an [Ocean Protocol blog post that explains SEAs in more detail](https://blog.oceanprotocol.com/exploring-the-sea-service-execution-agreements-65f7523d85e2). +We published a blog post that explains SEAs in more detail: + +- [Blog: Exploring the SEA: Service Execution Agreements](https://blog.oceanprotocol.com/exploring-the-sea-service-execution-agreements-65f7523d85e2) ## More Terminology -- See [the page about Ocean's Software Components](/concepts/components/). -- See [the page about wallets (and other Ethereum terminology)](/concepts/wallets/). +- See the page about Ocean's [Software Components](/concepts/components/). +- See the page about [wallets (and other Ethereum terminology)](/concepts/wallets/). [^1]: The _Dispenser_ smart contract should only be deployed to testnets. diff --git a/data/repositories.yml b/data/repositories.yml index 65e9a455..f3312466 100644 --- a/data/repositories.yml +++ b/data/repositories.yml @@ -14,7 +14,7 @@ links: - name: API reference url: /references/brizo/ - - name: events-handler-py + - name: events-handler - name: pleuston - name: commons