You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|`isOwner`|<https://assets.envited-x.net/Asset-CID>| CID v1, signed URLs, asset credential |
69
69
|`isRegistered`|<https://metadata.envited-x.net/Asset-CID>| CID v1, signed URLs, DEMIM credential |
@@ -81,12 +81,15 @@ The following process is implemented in the [ENVITED-X Data Space][12] portal de
81
81
2. Verify all referenced files exist locally or remotely as specified.
82
82
3. Locate the `domainMetadata.json` file.
83
83
- Validate the `domainMetadata.json`:
84
-
1. Extract SHACL constraints from the `domainMetadata.json` context.
85
-
2. Validate JSON structure against domain-specific SHACLs.
84
+
1. Extract SHACL constraints from the `domainMetadata.json` context,
85
+
2. Validate JSON structure against domain-specific SHACLs,
86
+
3. Check if the `@id` is unique within the ENVITED-X Data Space,
87
+
4. If the asset `@id` is already existing the validator SHALL throw an error.
86
88
- Validate if items in `hasReferencedArtifacts` are available:
87
-
1. Check if access role is `isPublic`, OPTIONALLY check if filePath resolves.
88
-
2. Check if access role is `isOwner` or `isRegistered` and if `@id` of asset is known in the database.
89
-
3. It is RECOMMENDED to warn the user if references do not exist.
89
+
1. Check if `@id` of asset is known in the database,
90
+
2. OPTIONALLY check if filePath resolves if the access role is `isPublic`,
91
+
3. It is RECOMMENDED to warn the user if references do not exist,
92
+
4. It is strongly RECOMMENDED to add the `CID` as a user to the Manifest metadata.
90
93
91
94
#### Step 2: Upload Asset to ENVITED-X Data Space
92
95
@@ -96,9 +99,9 @@ The following process is implemented in the [ENVITED-X Data Space][12] portal de
96
99
- Store `isRegistered` metadata at `https://metadata.envited-x.net/Asset-CID`.
97
100
- Store `isPublic` metadata at `https://ipfs.envited-x.net/Asset-CID/Data-CID`.
98
101
- Calculate CIDs for all `isPublic` data.
99
-
- Create `tzip21_manifest.json` by replacing relative paths in `manifest_reference.json` with IPFS/envited-x.net URLs.
102
+
- Create `envited-x_manifest.json` by replacing relative paths in `manifest_reference.json` with IPFS/envited-x.net URLs.
100
103
- Replace the paths of items in `hasReferencedArtifacts` to the correct filePaths.
101
-
- Replace `@id` from `manifest_reference.json` with generated database `UUID` in `tzip21_manifest.json`.
104
+
- Replace `@id` from `manifest_reference.json` with generated database `UUID` in `envited-x_manifest.json`. This also applies for referenced artifacts.
102
105
- Create `tzip21_token_metadata.json` and map the metadata fields OPTIONALLY use an application/ld+json conform to the [tzip21 ontology][19].
103
106
104
107
#### Step 3: Preview Data
@@ -109,7 +112,7 @@ The following process is implemented in the [ENVITED-X Data Space][12] portal de
109
112
#### Step 4: Mint Token
110
113
111
114
- It is RECOMMENDED to use signed CIDs for the upload to IPFS according to [EIP-712][13].
112
-
- Upload `isPublic` information and `tzip21_manifest.json` to IPFS.
115
+
- Upload `isPublic` information and `envited-x_manifest.json` to IPFS.
113
116
- It is RECOMMENDED to verify that CIDs from the IPFS service or software returns the same CIDs as the pre-calculation.
114
117
- Upload `tzip21_token_metadata.json` to IPFS.
115
118
- Mint token with linked metadata.
@@ -134,7 +137,7 @@ The following process is implemented in the [ENVITED-X Data Space][12] portal de
134
137
- The CID of the uploaded `asset.zip` serves as the unique identifier detecting identical datasets across all systems.
135
138
- In addition the unique identifier `@id` of the `envied-x:SimulationAsset` in the `domainMetadata.json` SHALL be used for identification of the digital assets.
136
139
- The CIDs MAY be signed by the user according to EIP-712.
137
-
- A UUID MUST be generated for the `tzip21_manifest.json` pre-mint to link the asset with the ENVITED-X database securely.
140
+
- A UUID MUST be generated for the `envited-x_manifest.json` pre-mint to link the asset with the ENVITED-X database securely.
138
141
- The DID of the member associated with the user minting the asset MUST be known.
139
142
- DID of the user minting the asset SHALL be stored pre-mint in the database.
140
143
@@ -160,22 +163,22 @@ The synchronization between the smart contract as in the [Marketplace Contract R
160
163
Attributes not in the table are static and the same for every mint as in the 📁 `example/tzip21_token_metadata.json`.
161
164
Examples are the first five tags or "publishers", which is always ENVITED-X and the ASCS if the mint is conducted through the [website][12].
0 commit comments