mirror of
https://github.com/oceanprotocol/docs.git
synced 2024-11-26 19:49:26 +01:00
Issue-#808: Change links
This commit is contained in:
parent
a5b40eb5d5
commit
b7258da91a
@ -24,6 +24,6 @@ The most basic scenario for a Publisher is to provide access to the datasets the
|
||||
|
||||
- [Compute-to-Data architecture](/tutorials/compute-to-data-architecture/)
|
||||
- [Tutorial: Writing Algorithms](/tutorials/compute-to-data-algorithms/)
|
||||
- [Tutorial: Set Up a Compute-to-Data Environment](/tutorials/compute-to-data/)
|
||||
- [Tutorial: Set Up a Compute-to-Data Environment](/tutorials/compute-to-data-minikube/)
|
||||
- [Compute-to-Data in Ocean Market](https://blog.oceanprotocol.com)
|
||||
- [(Old) Compute-to-Data specs](https://github.com/oceanprotocol-archive/OEPs/tree/master/12) (OEP12)
|
||||
|
@ -20,3 +20,8 @@ For each dataset, publishers can choose to allow various permission levels for a
|
||||
- allow raw algorithms, for advanced use cases circumventing algorithm as an asset type, but most prone to data escape
|
||||
|
||||
All implementations should set permissions to private by default: upon publishing a compute dataset, no algorithms should be allowed to run on it. This is to prevent data escape by a rogue algorithm being written in a way to extract all data from a dataset.
|
||||
|
||||
## DDO Links
|
||||
|
||||
- [Algorithm DDO](/concepts/ddo-metadata/#fields-when-attributesmaintype--algorithm)
|
||||
- [Compute DDO](/concepts/ddo-metadata/#fields-when-attributesmaintype--compute)
|
Loading…
Reference in New Issue
Block a user