Skip to content

Commit

Permalink
Update ERC-7208: minor wording improvement
Browse files Browse the repository at this point in the history
Merged by EIP-Bot.
  • Loading branch information
galimba authored Nov 18, 2024
1 parent 60efd58 commit 1316d6e
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions ERCS/erc-7208.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ requires: 165
## Abstract


This ERC defines a series of interfaces for the abstraction of storage of on-chain data by implementing the logic functions that govern such data on independent smart contracts. "On-chain Data Containers" (ODCs) refer to the separation and indexing of data storage away from data management. We propose that on-chain data can be abstracted and stored in smart contracts called "Data Objects" (DO), which answer to external data indexing mechanisms named "Data Points" (DP). This data can be accessed and modified by implementing (one or many) separate smart contracts identified as "Data Managers" (DM). We introduce two mechanisms for access management: first, through a "Data Index" (DI) implementation, the "Data Managers" (DM) can be gated from accessing "Data Objects" (DO); second, a "Data Point Registry" (DPR) implementation manages the issuance of "Data Points" (DP). Lastly, we introduce the concept of data portability (horizontal data mobility) between different deployments of compatible "Data Points" (DP), enabling massive updates to the logic without affecting the underlying data storage.
This ERC defines a series of interfaces for the abstraction of storage of on-chain data by implementing the logic functions that govern such data on independent smart contracts. "On-chain Data Containers" (ODCs) refer to the separation and indexing of data storage away from data management. We propose that on-chain data can be abstracted and stored in smart contracts called "Data Objects" (DO), which answer to external data indexing mechanisms named "Data Points" (DP). This data can be accessed and modified by implementing (one or many) separate smart contracts identified as "Data Managers" (DM). We introduce two mechanisms for access management: first, through a "Data Index" (DI) implementation, the "Data Managers" (DM) can be gated from accessing "Data Objects" (DO); second, a "Data Point Registry" (DPR) implementation manages the issuance of "Data Points" (DP). Lastly, we introduce the concept of data portability (horizontal data mobility) between implementations of "Data Index" (DI), enabling massive updates to the logic without affecting the underlying data storage.


## Motivation
Expand Down Expand Up @@ -132,8 +132,8 @@ As such, **Data Objects** respond to a gating mechanism given by a single **Data

### Data Manager Contract

* Data Manager MAY use read() or DataObject.read() to read data from **Data Objects**
* Data Manager MAY use write() to write data to **Data Objects**
* Data Manager MAY use `IDataIndex.read()` or `IDataObject.read()` to read data from **Data Objects**
* Data Manager MAY use `IDataIndex.write()` to write data to **Data Objects**
* Data Manager MAY share **Data Point** with other **Data Managers**
* Data Manager MAY use multiple **Data Points**
* Data Manager MAY implement the logic for requesting **Data Points** from a **Data Point Registry**.
Expand Down

0 comments on commit 1316d6e

Please sign in to comment.