GITBOOK-644: Added Ocean101 diagram

contribute/code-of-conduct.md

@@ -3,48 +3,30 @@ title: Contributor Code of Conduct
 description: Be excellent to each other.
 ---
 
-As contributors and maintainers of this project, and in the interest of
+# Contributor Code of Conduct
-fostering an open and welcoming community, we pledge to respect all people who
-contribute to the project.
 
-We are committed to making participation in this project a harassment-free
+As contributors and maintainers of this project, and in the interest of fostering an open and welcoming community, we pledge to respect all people who contribute to the project.
-experience for everyone, regardless of level of experience, gender, gender
+
-identity and expression, sexual orientation, disability, personal appearance,
+We are committed to making participation in this project a harassment-free experience for everyone, regardless of level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, nationality, or species.
-body size, race, ethnicity, age, religion, nationality, or species.
 
 Examples of unacceptable behavior by participants include:
 
-- The use of sexualized language or imagery
+* The use of sexualized language or imagery
-- Personal attacks
+* Personal attacks
-- Trolling or insulting/derogatory comments
+* Trolling or insulting/derogatory comments
-- Public or private harassment
+* Public or private harassment
-- Publishing other's private information, such as physical or electronic
+* Publishing other's private information, such as physical or electronic addresses, without explicit permission
-  addresses, without explicit permission
+* Deliberate intimidation
-- Deliberate intimidation
+* Other unethical or unprofessional conduct
-- Other unethical or unprofessional conduct
 
-Project maintainers have the right and responsibility to remove, edit, or
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
 
-By adopting this Code of Conduct, project maintainers commit themselves to
+By adopting this Code of Conduct, project maintainers commit themselves to fairly and consistently applying these principles to every aspect of managing this project. Project maintainers who do not follow or enforce the Code of Conduct may be permanently removed from the project team.
-fairly and consistently applying these principles to every aspect of managing
-this project. Project maintainers who do not follow or enforce the Code of
-Conduct may be permanently removed from the project team.
 
-This Code of Conduct applies both within project spaces and in public spaces
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community.
-when an individual is representing the project or its community.
 
-Instances of abusive, harassing, or otherwise unacceptable behavior directed at yourself or another community member may be reported by contacting a project maintainer at [conduct@oceanprotocol.com](mailto:conduct@oceanprotocol.com). All
+Instances of abusive, harassing, or otherwise unacceptable behavior directed at yourself or another community member may be reported by contacting a project maintainer at [conduct@oceanprotocol.com](mailto:conduct@oceanprotocol.com). All complaints will be reviewed and investigated and will result in a response that is appropriate to the circumstances. Maintainers are obligated to maintain confidentiality with regard to the reporter of an incident.
-complaints will be reviewed and investigated and will result in a response that
-is appropriate to the circumstances. Maintainers are obligated to maintain confidentiality with regard to the reporter of an incident.
 
----
 
-<small>This Code of Conduct is adapted from the [Contributor Covenant][homepage],
-version 1.3.0, available at [contributor-covenant.org/version/1/3/0/][version]</small>
 
-[homepage]: http://contributor-covenant.org
+This Code of Conduct is adapted from the [Contributor Covenant](http://contributor-covenant.org), version 1.3.0, available at [contributor-covenant.org/version/1/3/0/](http://contributor-covenant.org/version/1/3/0/)
-[version]: http://contributor-covenant.org/version/1/3/0/

developers/ocean.js/configuration.md

@@ -1,6 +1,6 @@
 # Configuration
 
-For obtaining the API keys for blockchain access and setting the correct environment variables, please consult [this section](http://localhost:5000/o/mTcjMqA4ylf55anucjH8/s/zQlpIJEeu8x5yl0OLuXn/) first and proceed with the next steps.
+For obtaining the API keys for blockchain access and setting the correct environment variables, please consult [this section](http://127.0.0.1:5000/o/mTcjMqA4ylf55anucjH8/s/zQlpIJEeu8x5yl0OLuXn/) first and proceed with the next steps.
 
 ### Create a directory
 

developers/ocean.py/remote-setup.md

@@ -83,7 +83,7 @@ For all users: to use EWC, add the following to network-config.yaml:
 
 #### 1.5 RPCs and Infura
 
-In order to obtain API keys for blockchain access, follow up [this document](http://localhost:5000/o/mTcjMqA4ylf55anucjH8/s/zQlpIJEeu8x5yl0OLuXn/) for tips & tricks.
+In order to obtain API keys for blockchain access, follow up [this document](http://127.0.0.1:5000/o/mTcjMqA4ylf55anucjH8/s/zQlpIJEeu8x5yl0OLuXn/) for tips & tricks.
 
 The config file's default RPCs point to Infura, which require you to have an Infura account with corresponding token `WEB3_INFURA_PROJECT_ID`.
 

discover/ocean-101.md

@@ -10,10 +10,12 @@ Ocean Protocol utilizes a combination of blockchain technology, decentralized ne
 2. **Discovery and Access Control**: Data consumers can discover available data assets through decentralized metadata services like Aquarius. Access control mechanisms, such as smart contracts, verify the consumer's permissions and handle the transfer of data access tokens.
 3. **Secure Data Exchange**: When a data consumer purchases access to a data asset, the asset's metadata, and access instructions are encrypted by the data provider using the Provider service. The encrypted asset is then securely transferred to the consumer, who can decrypt and utilize it without revealing the asset's URL.
 4. [**Compute-to-Data**](../developers/compute-to-data/) **(C2D)**: Ocean Protocol supports C2D capabilities, allowing data consumers to perform computations on data assets without direct access to the underlying data. The compute operations are executed in a secure and controlled environment, ensuring data privacy and compliance.
-5. **Incentives and Governance**: Ocean Protocol incorporates tokeconomics and a governance framework to incentivize participants and ensure the sustainability and evolution of the ecosystem. Participants can earn and stake Ocean tokens (OCEAN) for veOCEANs, curate data, contribute to the network, and participate in governance decisions.
+5. **Incentives and Governance**: Ocean Protocol incorporates tokenomics and a governance framework to incentivize participants and ensure the sustainability and evolution of the ecosystem. Participants can earn and stake Ocean tokens (OCEAN) for veOCEANs, curate data, contribute to the network and participate in governance decisions.
 
 Ocean Protocol also combines advanced technologies and web components to create a robust and efficient data ecosystem.
 
+<figure><img src="../.gitbook/assets/Ocean101.png" alt=""><figcaption><p>Ocean architectural overview </p></figcaption></figure>
+
 Powerful libraries such as [Ocean.js](../developers/ocean.js/) (JavaScript) and [Ocean.py](../developers/ocean.py/) (Python) facilitate seamless integration and interaction with the protocol, offering a wide range of functionalities.
 
 Ocean Protocol incorporates middleware components that enhance efficiency and streamline interactions. Components such as [Aquarius](../developers/aquarius/) act as a metadata cache, improving search efficiency by caching on-chain data into Elasticsearch while [Provider](../developers/provider/) plays a crucial role in various ecosystem operations, assisting in asset downloading, handling encryption of [Decentralized Data Objects](../developers/ddo-specification.md) (DDOs), and facilitating communication with the operator-service for Compute-to-Data jobs. And finally, the [Subgraph](../developers/subgraph/), an off-chain service leveraging GraphQL, offers efficient access to information related to datatokens, users, and balances.