From 2ffd54e02a5454880a7a2e6c70f5c4b1ea24ba71 Mon Sep 17 00:00:00 2001 From: "Bofu Chen (bafu)" Date: Tue, 12 Sep 2023 18:37:19 +0800 Subject: [PATCH 01/22] docs(EIPS/eip-draft_on-chain-consent-for-ai-data-mining-of-digital-media.md): initial proposal Signed-off-by: Bofu Chen (bafu) --- ...ent-for-ai-data-mining-of-digital-media.md | 112 ++++++++++++++++++ 1 file changed, 112 insertions(+) create mode 100644 EIPS/eip-draft_on-chain-consent-for-ai-data-mining-of-digital-media.md diff --git a/EIPS/eip-draft_on-chain-consent-for-ai-data-mining-of-digital-media.md b/EIPS/eip-draft_on-chain-consent-for-ai-data-mining-of-digital-media.md new file mode 100644 index 0000000000000..b517f9972a1ad --- /dev/null +++ b/EIPS/eip-draft_on-chain-consent-for-ai-data-mining-of-digital-media.md @@ -0,0 +1,112 @@ +--- +eip: TBD +title: On-Chain Consent for AI Data Mining of Digital Media +description: Bridging the gap between AI workflows and digital asset permissions through a unified blockchain standard. +author: Bofu Chen (@bafu), Tammy Yang (@tammyyang) +discussions-to: https://ethereum-magicians.org/t//9999 +status: Draft +type: Standards Track +category: ERC +created: 2023-09-12 +--- + +## Abstract + +This EIP proposes a standardized approach to declaring mining preferences for digital media assets on the EVM-compatible blockchains. This extends digital media metadata standards like ERC-7053 and NFT metadata standards like ERC-721 and ERC-1155, allowing asset creators to specify how their assets are used in data mining, AI training, and machine learning workflows. + +## Motivation + +As digital assets become increasingly utilized in AI and machine learning workflows, it is critical that the rights and preferences of asset creators and license owners are respected, and the AI/ML creators can check and collect data easily and safely. This proposal aims to create a standardized method of declaring these preferences, giving the creators on both sides of AI/ML can communicate data utilization and build a sustainable data mining and AI/ML environment. + +## Specification + +The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 and RFC 8174. + +This EIP introduces a new property, `miningPreference`, to the metadata standards which signify the choices made by the asset creators or license owners regarding the suitability of their asset for inclusion in data mining or AI/ML training workflows. miningPreference is an array that can include one or more specific conditions. + +* `dataMining`: Allow the asset to be used in data mining for determining "patterns, trends, and correlations". +* `aiInference`: Allow the asset to be used as input to a trained AI/ML model for inferring a result. +* `aiGenerativeTraining`: Allow the asset to be used as training data for an AI/ML model that could produce derivative assets. +* `aiGenerativeTrainingWithAuthorship`: Same as `aiGenerativeTraining`, but requires that the authorship is disclosed. +* `aiTraining`: Allow the asset to be used as training data for generative and non-generative AI/ML models. +* `aiTrainingWithAuthorship`: Same as `aiTraining`, but requires that the authorship is disclosed. + +### Schema + +```json +{ + "type": "object", + "properties": { + "allowed": { + "enum": [ "dataMining", "aiTraining", "aiTrainingWithAuthorship", "aiGenerativeTraining", "aiGenerativeTrainingWithAuthorship", "aiInference" ], + "description": "The asset may be used for training an AI/ML model or mined for its data (or both)." + }, + "constrainted": { + "enum": [ "dataMining", "aiTraining", "aiTrainingWithAuthorship", "aiGenerativeTraining", "aiGenerativeTrainingWithAuthorship", "aiInference" ], + "description": "The asset may be used for training an AI/ML model or mined for its data (or both) followed the license." + }, + "notAllowed": { + "enum": [ "dataMining", "aiTraining", "aiTrainingWithAuthorship", "aiGenerativeTraining", "aiGenerativeTrainingWithAuthorship", "aiInference" ], + "description": "The asset may not be used for training an AI/ML model or mined for its data (or both)." + } + }, + "required": [ "allowed", "constrainted", "notAllowed" ] +} +``` + +### Examples + +The mining preference example for not allowing generative AI training: + +```json +{ + "miningPreference": { + "allowed": [ "dataMining", "aiTrainingWithAuthorship", "aiInference" ], + "contrained": [], + "notAllowed": [ "aiGenerativeTraining" ] + } +} +``` + +The mining preference example for only allowing for AI inference: + +```json +{ + "miningPreference": { + "allowed": [ "aiInference" ], + "contrained": [], + "notAllowed": [ "aiTraining", "aiGenerativeTraining" ] + } +} +``` + +The mining preference example for allowing generative AI training if mentioning authorship and follow license: + +```json +{ + "miningPreference": { + "allowed": [ "dataMining", "aiTrainingWithAuthorship", "aiInference" ], + "contrained": [ "aiGenerativeTrainingWithAuthorship" ], + "notAllowed": [] + } +} +``` + +## Rationale + +The introduction of the `miningPreference` property in digital asset metadata covers the considerations including + +Accessibility: A clear and easily accessible method with human-readibility and machine-readibility for digital asset creators and license owners to express their preferences for how their assets are used in data mining and AI/ML training workflows. The AI/ML creators can check and collect data systematically. +Adoption: To leverage the transparent metadata registration and representation EIPs, and the industrial metadata standards including C2PA (Coalation for Content Provenance and Authenticity). + +## Security Considerations + +When adopting this EIP, it’s essential to address several security aspects to ensure the safety and integrity of adoption: + +* Data Integrity: Since this EIP facilitates the declaration of mining preferences for digital media assets, the integrity of the data should be assured. Any tampering with the miningPreference property can lead to unauthorized data mining usage. Blockchain's immutability will play a significant role here, but additional security layers, such as cryptographic signatures, can further ensure data integrity. +* Verifiable Authenticity: Ensure that the individual or entity setting the miningPreference is the legitimate owner or authorized representative of the digital asset. Unauthorized changes to preferences can lead to data misuse. Cross-checking asset provenance and ownership becomes paramount. Services or smart contracts should be implemented to verify the authenticity of assets before trusting the miningPreference. +* Data Privacy: Ensure that the process of recording preferences doesn't inadvertently expose sensitive information about the asset creators or owners. Although the Ethereum blockchain is public, careful consideration is required to ensure no unintended data leakage. + +## Copyright + +Copyright and related rights waived via [CC0](../LICENSE.md). From 6e303cb7a115d1862b46bfb55eb58ff7edaaa0ac Mon Sep 17 00:00:00 2001 From: "Bofu Chen (bafu)" Date: Tue, 12 Sep 2023 18:47:19 +0800 Subject: [PATCH 02/22] docs(EIPS/eip-7682.md): add eip number Signed-off-by: Bofu Chen (bafu) --- ...nsent-for-ai-data-mining-of-digital-media.md => eip-7682.md} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename EIPS/{eip-draft_on-chain-consent-for-ai-data-mining-of-digital-media.md => eip-7682.md} (99%) diff --git a/EIPS/eip-draft_on-chain-consent-for-ai-data-mining-of-digital-media.md b/EIPS/eip-7682.md similarity index 99% rename from EIPS/eip-draft_on-chain-consent-for-ai-data-mining-of-digital-media.md rename to EIPS/eip-7682.md index b517f9972a1ad..e4f1a8df3d0f4 100644 --- a/EIPS/eip-draft_on-chain-consent-for-ai-data-mining-of-digital-media.md +++ b/EIPS/eip-7682.md @@ -1,5 +1,5 @@ --- -eip: TBD +eip: 7682 title: On-Chain Consent for AI Data Mining of Digital Media description: Bridging the gap between AI workflows and digital asset permissions through a unified blockchain standard. author: Bofu Chen (@bafu), Tammy Yang (@tammyyang) From bab62bd365037d3f51a8355a33bf63876a010f56 Mon Sep 17 00:00:00 2001 From: "Bofu Chen (bafu)" Date: Tue, 12 Sep 2023 18:59:50 +0800 Subject: [PATCH 03/22] fix(EIPS/eip-7682.md): fix EIP Walidator errors 1. preamble header `title` value is too long (max 44) 2. preamble header `description` should not contain `standard` (or similar words.) 3. the first match of the given pattern must be a link Signed-off-by: Bofu Chen (bafu) --- EIPS/eip-7682.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/EIPS/eip-7682.md b/EIPS/eip-7682.md index e4f1a8df3d0f4..b8432f4a05b48 100644 --- a/EIPS/eip-7682.md +++ b/EIPS/eip-7682.md @@ -1,9 +1,9 @@ --- eip: 7682 -title: On-Chain Consent for AI Data Mining of Digital Media -description: Bridging the gap between AI workflows and digital asset permissions through a unified blockchain standard. +title: On-Chain Consent for AI Data Mining +description: Bridging the gap between AI workflows and digital asset permissions through a unified blockchain consent. author: Bofu Chen (@bafu), Tammy Yang (@tammyyang) -discussions-to: https://ethereum-magicians.org/t//9999 +discussions-to: https://ethereum-magicians.org/t/add-eip-on-chain-consent-for-ai-data-mining/15755 status: Draft type: Standards Track category: ERC @@ -12,7 +12,7 @@ created: 2023-09-12 ## Abstract -This EIP proposes a standardized approach to declaring mining preferences for digital media assets on the EVM-compatible blockchains. This extends digital media metadata standards like ERC-7053 and NFT metadata standards like ERC-721 and ERC-1155, allowing asset creators to specify how their assets are used in data mining, AI training, and machine learning workflows. +This EIP proposes a standardized approach to declaring mining preferences for digital media assets on the EVM-compatible blockchains. This extends digital media metadata standards like [ERC-7053](https://eips.ethereum.org/EIPS/eip-7053) and NFT metadata standards like [ERC-721](https://eips.ethereum.org/EIPS/eip-721) and [ERC-1155](https://eips.ethereum.org/EIPS/eip-1155), allowing asset creators to specify how their assets are used in data mining, AI training, and machine learning workflows. ## Motivation From 5afdb9b3a594fd4d1bcf5c8e0f2392df7a5cecb6 Mon Sep 17 00:00:00 2001 From: "Bofu Chen (bafu)" Date: Tue, 12 Sep 2023 19:14:57 +0800 Subject: [PATCH 04/22] fix(EIPS/eip-7682.md): use EIP relative links instead of URLs Signed-off-by: Bofu Chen (bafu) --- EIPS/eip-7682.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/EIPS/eip-7682.md b/EIPS/eip-7682.md index b8432f4a05b48..f8c31f13de5f8 100644 --- a/EIPS/eip-7682.md +++ b/EIPS/eip-7682.md @@ -12,7 +12,7 @@ created: 2023-09-12 ## Abstract -This EIP proposes a standardized approach to declaring mining preferences for digital media assets on the EVM-compatible blockchains. This extends digital media metadata standards like [ERC-7053](https://eips.ethereum.org/EIPS/eip-7053) and NFT metadata standards like [ERC-721](https://eips.ethereum.org/EIPS/eip-721) and [ERC-1155](https://eips.ethereum.org/EIPS/eip-1155), allowing asset creators to specify how their assets are used in data mining, AI training, and machine learning workflows. +This EIP proposes a standardized approach to declaring mining preferences for digital media assets on the EVM-compatible blockchains. This extends digital media metadata standards like [ERC-7053](eip-7053.md) and NFT metadata standards like [ERC-721](eip-721.md) and [ERC-1155](eip-1155.md), allowing asset creators to specify how their assets are used in data mining, AI training, and machine learning workflows. ## Motivation From 818d6ae355c85671baf90a8e4f355fd17ecfb532 Mon Sep 17 00:00:00 2001 From: Bofu Chen Date: Wed, 13 Sep 2023 15:49:04 +0800 Subject: [PATCH 05/22] fix(EIPs/eip-7517): update EIP number from PR number to the next sequential number EIP/ERC numbering changed to sequential from 7500 and is no longer the PR number. Co-authored-by: Andrew B Coathup <28278242+abcoathup@users.noreply.github.com> --- EIPS/eip-7682.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/EIPS/eip-7682.md b/EIPS/eip-7682.md index f8c31f13de5f8..1f190681ff309 100644 --- a/EIPS/eip-7682.md +++ b/EIPS/eip-7682.md @@ -1,5 +1,5 @@ --- -eip: 7682 +eip: 7517 title: On-Chain Consent for AI Data Mining description: Bridging the gap between AI workflows and digital asset permissions through a unified blockchain consent. author: Bofu Chen (@bafu), Tammy Yang (@tammyyang) From 34009aeefb7d41e1059edd8ae2fcc7452f1eae11 Mon Sep 17 00:00:00 2001 From: Bofu Chen Date: Wed, 13 Sep 2023 15:51:10 +0800 Subject: [PATCH 06/22] docs(EIPs/eip-7517): reviewer suggests to use Onchain instead of On-Chain Co-authored-by: Andrew B Coathup <28278242+abcoathup@users.noreply.github.com> --- EIPS/eip-7682.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/EIPS/eip-7682.md b/EIPS/eip-7682.md index 1f190681ff309..ffb8809987e71 100644 --- a/EIPS/eip-7682.md +++ b/EIPS/eip-7682.md @@ -1,6 +1,6 @@ --- eip: 7517 -title: On-Chain Consent for AI Data Mining +title: Onchain Consent for AI Data Mining description: Bridging the gap between AI workflows and digital asset permissions through a unified blockchain consent. author: Bofu Chen (@bafu), Tammy Yang (@tammyyang) discussions-to: https://ethereum-magicians.org/t/add-eip-on-chain-consent-for-ai-data-mining/15755 From a205c56c7ebbbf05d0589af90b0c2b16f7130539 Mon Sep 17 00:00:00 2001 From: Bofu Chen Date: Wed, 13 Sep 2023 15:52:46 +0800 Subject: [PATCH 07/22] fix(EIPs/eip-7517.md): rename file to the renewed EIP number --- EIPS/{eip-7682.md => eip-7517.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename EIPS/{eip-7682.md => eip-7517.md} (100%) diff --git a/EIPS/eip-7682.md b/EIPS/eip-7517.md similarity index 100% rename from EIPS/eip-7682.md rename to EIPS/eip-7517.md From 83d4bd2852254546fad1eadf1cac68ef5922bbcd Mon Sep 17 00:00:00 2001 From: "Bofu Chen (bafu)" Date: Wed, 13 Sep 2023 23:47:59 +0800 Subject: [PATCH 08/22] fix(EIPS/eip-7517.md): update internal EIP links Internal links should be [XXX](./yyy), not [XXX](yyy) Signed-off-by: Bofu Chen (bafu) --- EIPS/eip-7517.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/EIPS/eip-7517.md b/EIPS/eip-7517.md index ffb8809987e71..16ee0288ae20c 100644 --- a/EIPS/eip-7517.md +++ b/EIPS/eip-7517.md @@ -12,7 +12,7 @@ created: 2023-09-12 ## Abstract -This EIP proposes a standardized approach to declaring mining preferences for digital media assets on the EVM-compatible blockchains. This extends digital media metadata standards like [ERC-7053](eip-7053.md) and NFT metadata standards like [ERC-721](eip-721.md) and [ERC-1155](eip-1155.md), allowing asset creators to specify how their assets are used in data mining, AI training, and machine learning workflows. +This EIP proposes a standardized approach to declaring mining preferences for digital media assets on the EVM-compatible blockchains. This extends digital media metadata standards like [ERC-7053](./eip-7053.md) and NFT metadata standards like [ERC-721](./eip-721.md) and [ERC-1155](./eip-1155.md), allowing asset creators to specify how their assets are used in data mining, AI training, and machine learning workflows. ## Motivation From ed19e2159577b8d7b5b3fbeef515758728f13439 Mon Sep 17 00:00:00 2001 From: "Bofu Chen (bafu)" Date: Thu, 14 Sep 2023 15:00:25 +0800 Subject: [PATCH 09/22] docs(EIPS/eip-7517.md): update Motivation and Rationale Signed-off-by: Bofu Chen (bafu) --- EIPS/eip-7517.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/EIPS/eip-7517.md b/EIPS/eip-7517.md index 16ee0288ae20c..52a6f9da521bd 100644 --- a/EIPS/eip-7517.md +++ b/EIPS/eip-7517.md @@ -12,11 +12,15 @@ created: 2023-09-12 ## Abstract -This EIP proposes a standardized approach to declaring mining preferences for digital media assets on the EVM-compatible blockchains. This extends digital media metadata standards like [ERC-7053](./eip-7053.md) and NFT metadata standards like [ERC-721](./eip-721.md) and [ERC-1155](./eip-1155.md), allowing asset creators to specify how their assets are used in data mining, AI training, and machine learning workflows. +This EIP proposes a standardized approach to declaring mining preferences for digital media content on the EVM-compatible blockchains. This extends digital media metadata standards like [ERC-7053](./eip-7053.md) and NFT metadata standards like [ERC-721](./eip-721.md) and [ERC-1155](./eip-1155.md), allowing asset creators to specify how their assets are used in data mining, AI training, and machine learning workflows. ## Motivation -As digital assets become increasingly utilized in AI and machine learning workflows, it is critical that the rights and preferences of asset creators and license owners are respected, and the AI/ML creators can check and collect data easily and safely. This proposal aims to create a standardized method of declaring these preferences, giving the creators on both sides of AI/ML can communicate data utilization and build a sustainable data mining and AI/ML environment. +As digital assets become increasingly utilized in AI and machine learning workflows, it is critical that the rights and preferences of asset creators and license owners are respected, and the AI/ML creators can check and collect data easily and safely. Similar to robot.txt to websites, content owners and creators are looking for more direct control over how their creativities are used. + +This proposal aims to propose a standardized method of declaring these preferences. Adding "miningPreference" in the content metadata allows creators to include the information about how they want their work whether the asset may be used as part of a data mining or AI/ML training workflow. This ensures the original intent of the content is maintained. + +For AI-focused applications, this information serves as a guideline, facilitating the ethical and efficient use of content while respecting the creator's rights and building a sustainable data mining and AI/ML environment. ## Specification @@ -97,7 +101,7 @@ The mining preference example for allowing generative AI training if mentioning The introduction of the `miningPreference` property in digital asset metadata covers the considerations including Accessibility: A clear and easily accessible method with human-readibility and machine-readibility for digital asset creators and license owners to express their preferences for how their assets are used in data mining and AI/ML training workflows. The AI/ML creators can check and collect data systematically. -Adoption: To leverage the transparent metadata registration and representation EIPs, and the industrial metadata standards including C2PA (Coalation for Content Provenance and Authenticity). +Adoption: As Coalition for Content Provenance and Authenticity (C2PA) already outlines guidelines for indicating whether an asset may be used in data mining or AI/ML training, it's crucial that onchain metadata aligns with these standards. This ensures compatibility between in-media metadata and onchain records. ## Security Considerations From 9aac04b9f34f427a546b62e081d1db3803556dae Mon Sep 17 00:00:00 2001 From: "Bofu Chen (bafu)" Date: Thu, 14 Sep 2023 17:02:32 +0800 Subject: [PATCH 10/22] docs(EIPS/eip-7517.md): update title Signed-off-by: Bofu Chen (bafu) --- EIPS/eip-7517.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/EIPS/eip-7517.md b/EIPS/eip-7517.md index 52a6f9da521bd..aed30c717d5b8 100644 --- a/EIPS/eip-7517.md +++ b/EIPS/eip-7517.md @@ -1,6 +1,6 @@ --- eip: 7517 -title: Onchain Consent for AI Data Mining +title: Content mining preference for AI/ML training description: Bridging the gap between AI workflows and digital asset permissions through a unified blockchain consent. author: Bofu Chen (@bafu), Tammy Yang (@tammyyang) discussions-to: https://ethereum-magicians.org/t/add-eip-on-chain-consent-for-ai-data-mining/15755 From 5423f0bb7c7f00ec564c162498781da7fd899e31 Mon Sep 17 00:00:00 2001 From: "Bofu Chen (bafu)" Date: Thu, 14 Sep 2023 17:13:02 +0800 Subject: [PATCH 11/22] docs(EIPS/eip-7517.md): update description Signed-off-by: Bofu Chen (bafu) --- EIPS/eip-7517.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/EIPS/eip-7517.md b/EIPS/eip-7517.md index aed30c717d5b8..265055ce202b0 100644 --- a/EIPS/eip-7517.md +++ b/EIPS/eip-7517.md @@ -1,7 +1,7 @@ --- eip: 7517 title: Content mining preference for AI/ML training -description: Bridging the gap between AI workflows and digital asset permissions through a unified blockchain consent. +description: A proposal adding "miningPreference" in the metadata to preserve the digital content's original intent and respect creator’s rights. author: Bofu Chen (@bafu), Tammy Yang (@tammyyang) discussions-to: https://ethereum-magicians.org/t/add-eip-on-chain-consent-for-ai-data-mining/15755 status: Draft From 4d2453c1dfa6fa2e859d606d5a23a8a8d1662e25 Mon Sep 17 00:00:00 2001 From: "Bofu Chen (bafu)" Date: Thu, 14 Sep 2023 17:17:58 +0800 Subject: [PATCH 12/22] docs(EIPS/eip-7517.md): update title Signed-off-by: Bofu Chen (bafu) --- EIPS/eip-7517.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/EIPS/eip-7517.md b/EIPS/eip-7517.md index 265055ce202b0..fe19045acef61 100644 --- a/EIPS/eip-7517.md +++ b/EIPS/eip-7517.md @@ -1,6 +1,6 @@ --- eip: 7517 -title: Content mining preference for AI/ML training +title: Content Consent for AI/ML Data Mining description: A proposal adding "miningPreference" in the metadata to preserve the digital content's original intent and respect creator’s rights. author: Bofu Chen (@bafu), Tammy Yang (@tammyyang) discussions-to: https://ethereum-magicians.org/t/add-eip-on-chain-consent-for-ai-data-mining/15755 From 37b6ec01bf8a12acf87ada393a1c38a61827812a Mon Sep 17 00:00:00 2001 From: "Bofu Chen (bafu)" Date: Thu, 14 Sep 2023 17:21:55 +0800 Subject: [PATCH 13/22] docs(EIPS/eip-7517.md): update discussion-to link Signed-off-by: Bofu Chen (bafu) --- EIPS/eip-7517.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/EIPS/eip-7517.md b/EIPS/eip-7517.md index fe19045acef61..f9d8f6e386f9c 100644 --- a/EIPS/eip-7517.md +++ b/EIPS/eip-7517.md @@ -3,7 +3,7 @@ eip: 7517 title: Content Consent for AI/ML Data Mining description: A proposal adding "miningPreference" in the metadata to preserve the digital content's original intent and respect creator’s rights. author: Bofu Chen (@bafu), Tammy Yang (@tammyyang) -discussions-to: https://ethereum-magicians.org/t/add-eip-on-chain-consent-for-ai-data-mining/15755 +discussions-to: https://ethereum-magicians.org/t/eip-7517-content-consent-for-ai-ml-data-mining/15755 status: Draft type: Standards Track category: ERC From deb875173622787016b297561842991a794ee5e8 Mon Sep 17 00:00:00 2001 From: Bofu Chen Date: Mon, 2 Oct 2023 17:12:07 +0800 Subject: [PATCH 14/22] docs(EIPS/eip-7517.md): use conventional single quote Co-authored-by: Sam Wilson <57262657+SamWilsn@users.noreply.github.com> --- EIPS/eip-7517.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/EIPS/eip-7517.md b/EIPS/eip-7517.md index f9d8f6e386f9c..e2d25a266c003 100644 --- a/EIPS/eip-7517.md +++ b/EIPS/eip-7517.md @@ -1,7 +1,7 @@ --- eip: 7517 title: Content Consent for AI/ML Data Mining -description: A proposal adding "miningPreference" in the metadata to preserve the digital content's original intent and respect creator’s rights. +description: A proposal adding "miningPreference" in the metadata to preserve the digital content's original intent and respect creator's rights. author: Bofu Chen (@bafu), Tammy Yang (@tammyyang) discussions-to: https://ethereum-magicians.org/t/eip-7517-content-consent-for-ai-ml-data-mining/15755 status: Draft From b0a72a271339c1a31074f14a9cd1acfca4ac6ec5 Mon Sep 17 00:00:00 2001 From: "Bofu Chen (bafu)" Date: Mon, 2 Oct 2023 18:59:52 +0800 Subject: [PATCH 15/22] docs(EIPS/eip-7517.md): update schema and examples Signed-off-by: Bofu Chen (bafu) --- EIPS/eip-7517.md | 102 +++++++++++++++++++++++++++++++++++------------ 1 file changed, 76 insertions(+), 26 deletions(-) diff --git a/EIPS/eip-7517.md b/EIPS/eip-7517.md index e2d25a266c003..22e3a02995d38 100644 --- a/EIPS/eip-7517.md +++ b/EIPS/eip-7517.md @@ -39,22 +39,47 @@ This EIP introduces a new property, `miningPreference`, to the metadata standard ```json { - "type": "object", - "properties": { - "allowed": { - "enum": [ "dataMining", "aiTraining", "aiTrainingWithAuthorship", "aiGenerativeTraining", "aiGenerativeTrainingWithAuthorship", "aiInference" ], - "description": "The asset may be used for training an AI/ML model or mined for its data (or both)." - }, - "constrainted": { - "enum": [ "dataMining", "aiTraining", "aiTrainingWithAuthorship", "aiGenerativeTraining", "aiGenerativeTrainingWithAuthorship", "aiInference" ], - "description": "The asset may be used for training an AI/ML model or mined for its data (or both) followed the license." + "type": "object", + "properties": { + "dataMining": { + "$ref": "#/definitions/training-mining-map-entry" + }, + "aiInference": { + "$ref": "#/definitions/training-mining-map-entry" + }, + "aiTraining": { + "$ref": "#/definitions/training-mining-map-entry" + }, + "aiGenerativeTraining": { + "$ref": "#/definitions/training-mining-map-entry" + }, + "aiTrainingWithAuthorship": { + "$ref": "#/definitions/training-mining-map-entry" + }, + "aiGenerativeTrainingWithAuthorship": { + "$ref": "#/definitions/training-mining-map-entry" + } + }, + "additionalProperties": true, + "definitions": { + "training-mining-map-entry": { + "type": "object", + "properties": { + "use": { + "type": "string", + "enum": ["allowed", "notAllowed", "constrained"], + "description": "specifying whether the associated asset and its data may be used for training an AI/ML model or mined for its data (or both)" }, - "notAllowed": { - "enum": [ "dataMining", "aiTraining", "aiTrainingWithAuthorship", "aiGenerativeTraining", "aiGenerativeTrainingWithAuthorship", "aiInference" ], - "description": "The asset may not be used for training an AI/ML model or mined for its data (or both)." + "constraint_info": { + "type": "string", + "minLength": 1, + "description": "information about the use of 'constrained'" } - }, - "required": [ "allowed", "constrainted", "notAllowed" ] + }, + "required": ["use"] + } + }, + "required": [] } ``` @@ -64,11 +89,20 @@ The mining preference example for not allowing generative AI training: ```json { - "miningPreference": { - "allowed": [ "dataMining", "aiTrainingWithAuthorship", "aiInference" ], - "contrained": [], - "notAllowed": [ "aiGenerativeTraining" ] + "miningPreference": { + "dataMining": { + "use": "allowed" + }, + "aiInference": { + "use": "allowed" + }, + "aiTrainingWithAuthorship": { + "use": "allowed" + }, + "aiGenerativeTraining": { + "use": "notAllowed" } + } } ``` @@ -76,11 +110,17 @@ The mining preference example for only allowing for AI inference: ```json { - "miningPreference": { - "allowed": [ "aiInference" ], - "contrained": [], - "notAllowed": [ "aiTraining", "aiGenerativeTraining" ] + "miningPreference": { + "aiInference": { + "use": "allowed" + }, + "aiTraining": { + "use": "notAllowed" + }, + "aiGenerativeTraining": { + "use": "notAllowed" } + } } ``` @@ -88,11 +128,21 @@ The mining preference example for allowing generative AI training if mentioning ```json { - "miningPreference": { - "allowed": [ "dataMining", "aiTrainingWithAuthorship", "aiInference" ], - "contrained": [ "aiGenerativeTrainingWithAuthorship" ], - "notAllowed": [] + "miningPreference": { + "dataMining": { + "use": "allowed" + }, + "aiInference": { + "use": "allowed" + }, + "aiTrainingWithAuthorship": { + "use": "allowed" + }, + "aiGenerativeTrainingWithAuthorship": { + "use": "constrained", + "constraint_info": "Under the license: CC-BY-4.0" } + } } ``` From d06ae6af30db2979264e21b6126f721bebfbc46d Mon Sep 17 00:00:00 2001 From: "Bofu Chen (bafu)" Date: Mon, 2 Oct 2023 19:21:50 +0800 Subject: [PATCH 16/22] docs(EIPS/eip-7517.md): update schema and examples Signed-off-by: Bofu Chen (bafu) --- EIPS/eip-7517.md | 84 ++++++++++++++---------------------------------- 1 file changed, 24 insertions(+), 60 deletions(-) diff --git a/EIPS/eip-7517.md b/EIPS/eip-7517.md index 22e3a02995d38..6056b9d209ecf 100644 --- a/EIPS/eip-7517.md +++ b/EIPS/eip-7517.md @@ -42,44 +42,31 @@ This EIP introduces a new property, `miningPreference`, to the metadata standard "type": "object", "properties": { "dataMining": { - "$ref": "#/definitions/training-mining-map-entry" + "type": "string", + "enum": ["allowed", "notAllowed", "constrained"] }, "aiInference": { - "$ref": "#/definitions/training-mining-map-entry" + "type": "string", + "enum": ["allowed", "notAllowed", "constrained"] }, "aiTraining": { - "$ref": "#/definitions/training-mining-map-entry" + "type": "string", + "enum": ["allowed", "notAllowed", "constrained"] }, "aiGenerativeTraining": { - "$ref": "#/definitions/training-mining-map-entry" + "type": "string", + "enum": ["allowed", "notAllowed", "constrained"] }, "aiTrainingWithAuthorship": { - "$ref": "#/definitions/training-mining-map-entry" + "type": "string", + "enum": ["allowed", "notAllowed", "constrained"] }, "aiGenerativeTrainingWithAuthorship": { - "$ref": "#/definitions/training-mining-map-entry" + "type": "string", + "enum": ["allowed", "notAllowed", "constrained"] } }, - "additionalProperties": true, - "definitions": { - "training-mining-map-entry": { - "type": "object", - "properties": { - "use": { - "type": "string", - "enum": ["allowed", "notAllowed", "constrained"], - "description": "specifying whether the associated asset and its data may be used for training an AI/ML model or mined for its data (or both)" - }, - "constraint_info": { - "type": "string", - "minLength": 1, - "description": "information about the use of 'constrained'" - } - }, - "required": ["use"] - } - }, - "required": [] + "additionalProperties": true } ``` @@ -90,18 +77,10 @@ The mining preference example for not allowing generative AI training: ```json { "miningPreference": { - "dataMining": { - "use": "allowed" - }, - "aiInference": { - "use": "allowed" - }, - "aiTrainingWithAuthorship": { - "use": "allowed" - }, - "aiGenerativeTraining": { - "use": "notAllowed" - } + "dataMining": "allowed", + "aiInference": "allowed", + "aiTrainingWithAuthorship": "allowed", + "aiGenerativeTraining": "notAllowed" } } ``` @@ -111,15 +90,9 @@ The mining preference example for only allowing for AI inference: ```json { "miningPreference": { - "aiInference": { - "use": "allowed" - }, - "aiTraining": { - "use": "notAllowed" - }, - "aiGenerativeTraining": { - "use": "notAllowed" - } + "aiInference": "allowed", + "aiTraining": "notAllowed", + "aiGenerativeTraining": "notAllowed" } } ``` @@ -129,19 +102,10 @@ The mining preference example for allowing generative AI training if mentioning ```json { "miningPreference": { - "dataMining": { - "use": "allowed" - }, - "aiInference": { - "use": "allowed" - }, - "aiTrainingWithAuthorship": { - "use": "allowed" - }, - "aiGenerativeTrainingWithAuthorship": { - "use": "constrained", - "constraint_info": "Under the license: CC-BY-4.0" - } + "dataMining": "allowed", + "aiInference": "allowed", + "aiTrainingWithAuthorship": "allowed", + "aiGenerativeTrainingWithAuthorship": "constrained" } } ``` From 225f393af45c04b28c6e30b5c2d514bb2b74d3d4 Mon Sep 17 00:00:00 2001 From: "Bofu Chen (bafu)" Date: Mon, 2 Oct 2023 19:29:18 +0800 Subject: [PATCH 17/22] docs(EIPS/eip-7517.md): update the Rationale section based on reviewers' inputs Signed-off-by: Bofu Chen (bafu) --- EIPS/eip-7517.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/EIPS/eip-7517.md b/EIPS/eip-7517.md index 6056b9d209ecf..3ed258c3f4b03 100644 --- a/EIPS/eip-7517.md +++ b/EIPS/eip-7517.md @@ -112,10 +112,13 @@ The mining preference example for allowing generative AI training if mentioning ## Rationale -The introduction of the `miningPreference` property in digital asset metadata covers the considerations including +The technical decisions behind this EIP have been carefully considered to address specific challenges and requirements in the digital asset landscape. Here are the clarifications for the rationale behind: -Accessibility: A clear and easily accessible method with human-readibility and machine-readibility for digital asset creators and license owners to express their preferences for how their assets are used in data mining and AI/ML training workflows. The AI/ML creators can check and collect data systematically. -Adoption: As Coalition for Content Provenance and Authenticity (C2PA) already outlines guidelines for indicating whether an asset may be used in data mining or AI/ML training, it's crucial that onchain metadata aligns with these standards. This ensures compatibility between in-media metadata and onchain records. +1. Adoption of JSON schema: The use of JSON facilitates ease of integration and interaction, both manually and programmatically, with the metadata. +2. Detailed control with training types: The different categories like `aiGenerativeTraining`, `aiTraining`, and `aiInference` let creators control in detail, considering both ethics and computer resource needs. +3. Authorship options included: Options like `aiGenerativeTrainingWithAuthorship` and `aiTrainingWithAuthorship` make sure creators get credit, addressing ethical and legal issues. +4. Introduction of `constrained` category: The introduction of `constrained` category serves as an intermediary between `allowed` and `notAllowed`. It signals that additional permissions or clarifications may be required, defaulting to `notAllowed` in the absence of such information. +5. C2PA alignment for interoperability: The standard aligns with Coalition for Content Provenance and Authenticity (C2PA) guidelines, ensuring seamless mapping between onchain metadata and existing offchain standards. ## Security Considerations From b2df3aa0eb1a8798c8530ff423005822c346a9c3 Mon Sep 17 00:00:00 2001 From: "Bofu Chen (bafu)" Date: Mon, 2 Oct 2023 20:19:27 +0800 Subject: [PATCH 18/22] docs(EIPS/eip-7517.md): add category description for the Specification section Signed-off-by: Bofu Chen (bafu) --- EIPS/eip-7517.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/EIPS/eip-7517.md b/EIPS/eip-7517.md index 3ed258c3f4b03..d6248f79c4bca 100644 --- a/EIPS/eip-7517.md +++ b/EIPS/eip-7517.md @@ -35,6 +35,16 @@ This EIP introduces a new property, `miningPreference`, to the metadata standard * `aiTraining`: Allow the asset to be used as training data for generative and non-generative AI/ML models. * `aiTrainingWithAuthorship`: Same as `aiTraining`, but requires that the authorship is disclosed. +Each category is defined by a set of permissions that can take on one of three values: `allowed`, `notAllowed`, and `constraint`. + +* `allowed` indicates that the asset can be freely used for the specific purpose without any limitations or restrictions. +* `notAllowed` means that the use of the asset for that particular purpose is strictly prohibited. +* `constrained` suggests that the use of the asset is permitted, but with certain conditions or restrictions that must be adhered to. + +For instance, the `aiInference` property indicates whether the asset can be used as input for an AI/ML model to derive results. If set to `allowed`, the asset can be utilized without restrictions. If `notAllowed`, the asset is prohibited from AI inference. + +If marked as `constrained`, certain conditions, detailed in the license document, must be met. When `constraint` is selected, parties intending to use the media files should respect the rules specified in the license. To avoid discrepancies with the content license, the specifics of these constraints are not detailed within the schema, but the license reference should be included in the content metadata. + ### Schema ```json From 7ad48387e9ab71b7f05e778469d7d6a3f54285fe Mon Sep 17 00:00:00 2001 From: "Bofu Chen (bafu)" Date: Mon, 2 Oct 2023 20:20:26 +0800 Subject: [PATCH 19/22] docs(EIPS/eip-7517.md): add short description in the Schema sub-section Signed-off-by: Bofu Chen (bafu) --- EIPS/eip-7517.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/EIPS/eip-7517.md b/EIPS/eip-7517.md index d6248f79c4bca..ec64e37ccefef 100644 --- a/EIPS/eip-7517.md +++ b/EIPS/eip-7517.md @@ -47,6 +47,8 @@ If marked as `constrained`, certain conditions, detailed in the license document ### Schema +The JSON schema of `miningPreference` is defined as follows: + ```json { "type": "object", From 0515f676bbdc00123c4cc55cd8aefb623833e362 Mon Sep 17 00:00:00 2001 From: "Bofu Chen (bafu)" Date: Mon, 2 Oct 2023 20:24:59 +0800 Subject: [PATCH 20/22] docs(EIPS/eip-7517.md): add contents to the Motivation section Signed-off-by: Bofu Chen (bafu) --- EIPS/eip-7517.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/EIPS/eip-7517.md b/EIPS/eip-7517.md index ec64e37ccefef..49b80425d9777 100644 --- a/EIPS/eip-7517.md +++ b/EIPS/eip-7517.md @@ -22,6 +22,11 @@ This proposal aims to propose a standardized method of declaring these preferenc For AI-focused applications, this information serves as a guideline, facilitating the ethical and efficient use of content while respecting the creator's rights and building a sustainable data mining and AI/ML environment. +The introduction of the `miningPreference` property in digital asset metadata covers the considerations including + +* Accessibility: A clear and easily accessible method with human-readibility and machine-readibility for digital asset creators and license owners to express their preferences for how their assets are used in data mining and AI/ML training workflows. The AI/ML creators can check and collect data systematically. +* Adoption: As Coalition for Content Provenance and Authenticity (C2PA) already outlines guidelines for indicating whether an asset may be used in data mining or AI/ML training, it's crucial that onchain metadata aligns with these standards. This ensures compatibility between in-media metadata and onchain records. + ## Specification The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 and RFC 8174. @@ -130,7 +135,7 @@ The technical decisions behind this EIP have been carefully considered to addres 2. Detailed control with training types: The different categories like `aiGenerativeTraining`, `aiTraining`, and `aiInference` let creators control in detail, considering both ethics and computer resource needs. 3. Authorship options included: Options like `aiGenerativeTrainingWithAuthorship` and `aiTrainingWithAuthorship` make sure creators get credit, addressing ethical and legal issues. 4. Introduction of `constrained` category: The introduction of `constrained` category serves as an intermediary between `allowed` and `notAllowed`. It signals that additional permissions or clarifications may be required, defaulting to `notAllowed` in the absence of such information. -5. C2PA alignment for interoperability: The standard aligns with Coalition for Content Provenance and Authenticity (C2PA) guidelines, ensuring seamless mapping between onchain metadata and existing offchain standards. +5. C2PA alignment for interoperability: The standard aligns with C2PA guidelines, ensuring seamless mapping between onchain metadata and existing offchain standards. ## Security Considerations From af4cf65373ec11f5e883cc12cb40276598e142f7 Mon Sep 17 00:00:00 2001 From: "Bofu Chen (bafu)" Date: Tue, 3 Oct 2023 15:49:10 +0800 Subject: [PATCH 21/22] docs(EIPS/eip-7517.md): add examples for ERC-721 and ERC-7053 Signed-off-by: Bofu Chen (bafu) --- EIPS/eip-7517.md | 61 +++++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 60 insertions(+), 1 deletion(-) diff --git a/EIPS/eip-7517.md b/EIPS/eip-7517.md index 49b80425d9777..2a76abb78246c 100644 --- a/EIPS/eip-7517.md +++ b/EIPS/eip-7517.md @@ -31,7 +31,7 @@ The introduction of the `miningPreference` property in digital asset metadata co The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 and RFC 8174. -This EIP introduces a new property, `miningPreference`, to the metadata standards which signify the choices made by the asset creators or license owners regarding the suitability of their asset for inclusion in data mining or AI/ML training workflows. miningPreference is an array that can include one or more specific conditions. +This EIP introduces a new property, `miningPreference`, to the metadata standards which signify the choices made by the asset creators or license owners regarding the suitability of their asset for inclusion in data mining or AI/ML training workflows. `miningPreference` is an object that can include one or more specific conditions. * `dataMining`: Allow the asset to be used in data mining for determining "patterns, trends, and correlations". * `aiInference`: Allow the asset to be used as input to a trained AI/ML model for inferring a result. @@ -127,6 +127,65 @@ The mining preference example for allowing generative AI training if mentioning } ``` +### Example Usage with ERC-721 + +The example using the `miningPreference` property in NFT defined in [ERC-721](./eip-721.md). + +We can put the `miningPreference` field in the NFT metadata below. The `license` field is an example for specifying how to use a constrained condition. A NFT has its way to describe its license. + +```json +{ + ... + "miningPreference": { + "dataMining": "allowed", + "aiInference": "allowed", + "aiTrainingWithAuthorship": "allowed", + "aiGenerativeTrainingWithAuthorship": "constrained" + }, + "license": { + "name": "CC-BY-4.0", + "document": "https://creativecommons.org/licenses/by/4.0/legalcode" + } + ... +} +``` + +### Example Usage with ERC-7053 + +The example using the `miningPreference` property in onchain media provenance registration defined in [ERC-7053](./eip-7053.md). + +Assuming the Decentralized Content Identifier (CID) is `bafyaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa`. After following up the CID, got the Commit data: + +```json +{ + "assetTreeCid": "bafyaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa", + "assetTreeSha256": "bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb", + "assetTreeSignature": "0xcccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccc", + "author": "0xdddddddddddddddddddddddddddddddddddddddd", + "committer": "0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee", + "timestampCreated": 1691576790, +} +``` + +Following up the `assetTreeCid` which describes the properties of the registered asset: + +```json +{ + ... + "miningPreference": { + "dataMining": "allowed", + "aiInference": "allowed", + "aiTrainingWithAuthorship": "allowed", + "aiGenerativeTrainingWithAuthorship": "constrained" + }, + "license": { + "name": "CC-BY-4.0", + "document": "https://creativecommons.org/licenses/by/4.0/legalcode" + } + ... +} +``` + ## Rationale The technical decisions behind this EIP have been carefully considered to address specific challenges and requirements in the digital asset landscape. Here are the clarifications for the rationale behind: From 78a58924f22a926fecacf7cf0e005370a1a06b82 Mon Sep 17 00:00:00 2001 From: "Bofu Chen (bafu)" Date: Tue, 3 Oct 2023 16:49:53 +0800 Subject: [PATCH 22/22] docs(EIPS/eip-7517.md): update miningPreference to dataMiningPreference to avoid ambiguity Signed-off-by: Bofu Chen (bafu) --- EIPS/eip-7517.md | 30 +++++++++++++++--------------- 1 file changed, 15 insertions(+), 15 deletions(-) diff --git a/EIPS/eip-7517.md b/EIPS/eip-7517.md index 2a76abb78246c..d9802095c2574 100644 --- a/EIPS/eip-7517.md +++ b/EIPS/eip-7517.md @@ -1,7 +1,7 @@ --- eip: 7517 title: Content Consent for AI/ML Data Mining -description: A proposal adding "miningPreference" in the metadata to preserve the digital content's original intent and respect creator's rights. +description: A proposal adding "dataMiningPreference" in the metadata to preserve the digital content's original intent and respect creator's rights. author: Bofu Chen (@bafu), Tammy Yang (@tammyyang) discussions-to: https://ethereum-magicians.org/t/eip-7517-content-consent-for-ai-ml-data-mining/15755 status: Draft @@ -18,11 +18,11 @@ This EIP proposes a standardized approach to declaring mining preferences for di As digital assets become increasingly utilized in AI and machine learning workflows, it is critical that the rights and preferences of asset creators and license owners are respected, and the AI/ML creators can check and collect data easily and safely. Similar to robot.txt to websites, content owners and creators are looking for more direct control over how their creativities are used. -This proposal aims to propose a standardized method of declaring these preferences. Adding "miningPreference" in the content metadata allows creators to include the information about how they want their work whether the asset may be used as part of a data mining or AI/ML training workflow. This ensures the original intent of the content is maintained. +This proposal aims to propose a standardized method of declaring these preferences. Adding `dataMiningPreference` in the content metadata allows creators to include the information about how they want their work whether the asset may be used as part of a data mining or AI/ML training workflow. This ensures the original intent of the content is maintained. For AI-focused applications, this information serves as a guideline, facilitating the ethical and efficient use of content while respecting the creator's rights and building a sustainable data mining and AI/ML environment. -The introduction of the `miningPreference` property in digital asset metadata covers the considerations including +The introduction of the `dataMiningPreference` property in digital asset metadata covers the considerations including * Accessibility: A clear and easily accessible method with human-readibility and machine-readibility for digital asset creators and license owners to express their preferences for how their assets are used in data mining and AI/ML training workflows. The AI/ML creators can check and collect data systematically. * Adoption: As Coalition for Content Provenance and Authenticity (C2PA) already outlines guidelines for indicating whether an asset may be used in data mining or AI/ML training, it's crucial that onchain metadata aligns with these standards. This ensures compatibility between in-media metadata and onchain records. @@ -31,7 +31,7 @@ The introduction of the `miningPreference` property in digital asset metadata co The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 and RFC 8174. -This EIP introduces a new property, `miningPreference`, to the metadata standards which signify the choices made by the asset creators or license owners regarding the suitability of their asset for inclusion in data mining or AI/ML training workflows. `miningPreference` is an object that can include one or more specific conditions. +This EIP introduces a new property, `dataMiningPreference`, to the metadata standards which signify the choices made by the asset creators or license owners regarding the suitability of their asset for inclusion in data mining or AI/ML training workflows. `dataMiningPreference` is an object that can include one or more specific conditions. * `dataMining`: Allow the asset to be used in data mining for determining "patterns, trends, and correlations". * `aiInference`: Allow the asset to be used as input to a trained AI/ML model for inferring a result. @@ -52,7 +52,7 @@ If marked as `constrained`, certain conditions, detailed in the license document ### Schema -The JSON schema of `miningPreference` is defined as follows: +The JSON schema of `dataMiningPreference` is defined as follows: ```json { @@ -93,7 +93,7 @@ The mining preference example for not allowing generative AI training: ```json { - "miningPreference": { + "dataMiningPreference": { "dataMining": "allowed", "aiInference": "allowed", "aiTrainingWithAuthorship": "allowed", @@ -106,7 +106,7 @@ The mining preference example for only allowing for AI inference: ```json { - "miningPreference": { + "dataMiningPreference": { "aiInference": "allowed", "aiTraining": "notAllowed", "aiGenerativeTraining": "notAllowed" @@ -118,7 +118,7 @@ The mining preference example for allowing generative AI training if mentioning ```json { - "miningPreference": { + "dataMiningPreference": { "dataMining": "allowed", "aiInference": "allowed", "aiTrainingWithAuthorship": "allowed", @@ -129,14 +129,14 @@ The mining preference example for allowing generative AI training if mentioning ### Example Usage with ERC-721 -The example using the `miningPreference` property in NFT defined in [ERC-721](./eip-721.md). +The example using the `dataMiningPreference` property in NFT defined in [ERC-721](./eip-721.md). -We can put the `miningPreference` field in the NFT metadata below. The `license` field is an example for specifying how to use a constrained condition. A NFT has its way to describe its license. +We can put the `dataMiningPreference` field in the NFT metadata below. The `license` field is an example for specifying how to use a constrained condition. A NFT has its way to describe its license. ```json { ... - "miningPreference": { + "dataMiningPreference": { "dataMining": "allowed", "aiInference": "allowed", "aiTrainingWithAuthorship": "allowed", @@ -152,7 +152,7 @@ We can put the `miningPreference` field in the NFT metadata below. The `license` ### Example Usage with ERC-7053 -The example using the `miningPreference` property in onchain media provenance registration defined in [ERC-7053](./eip-7053.md). +The example using the `dataMiningPreference` property in onchain media provenance registration defined in [ERC-7053](./eip-7053.md). Assuming the Decentralized Content Identifier (CID) is `bafyaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa`. After following up the CID, got the Commit data: @@ -172,7 +172,7 @@ Following up the `assetTreeCid` which describes the properties of the registered ```json { ... - "miningPreference": { + "dataMiningPreference": { "dataMining": "allowed", "aiInference": "allowed", "aiTrainingWithAuthorship": "allowed", @@ -200,8 +200,8 @@ The technical decisions behind this EIP have been carefully considered to addres When adopting this EIP, it’s essential to address several security aspects to ensure the safety and integrity of adoption: -* Data Integrity: Since this EIP facilitates the declaration of mining preferences for digital media assets, the integrity of the data should be assured. Any tampering with the miningPreference property can lead to unauthorized data mining usage. Blockchain's immutability will play a significant role here, but additional security layers, such as cryptographic signatures, can further ensure data integrity. -* Verifiable Authenticity: Ensure that the individual or entity setting the miningPreference is the legitimate owner or authorized representative of the digital asset. Unauthorized changes to preferences can lead to data misuse. Cross-checking asset provenance and ownership becomes paramount. Services or smart contracts should be implemented to verify the authenticity of assets before trusting the miningPreference. +* Data Integrity: Since this EIP facilitates the declaration of mining preferences for digital media assets, the integrity of the data should be assured. Any tampering with the `dataMiningPreference` property can lead to unauthorized data mining usage. Blockchain's immutability will play a significant role here, but additional security layers, such as cryptographic signatures, can further ensure data integrity. +* Verifiable Authenticity: Ensure that the individual or entity setting the `dataMiningPreference` is the legitimate owner or authorized representative of the digital asset. Unauthorized changes to preferences can lead to data misuse. Cross-checking asset provenance and ownership becomes paramount. Services or smart contracts should be implemented to verify the authenticity of assets before trusting the `dataMiningPreference`. * Data Privacy: Ensure that the process of recording preferences doesn't inadvertently expose sensitive information about the asset creators or owners. Although the Ethereum blockchain is public, careful consideration is required to ensure no unintended data leakage. ## Copyright