Skip to content

Commit 9c94518

Browse files
davisiondavision
committed
Update schema links
1 parent 08b43f7 commit 9c94518

12 files changed

+26
-26
lines changed

‎api/api/certification.md‎

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ A `string` representing asset imprint or `null` when metadata doesn't match.
6262
```ts
6363
// arbitrary data
6464
const evidence = {
65-
$schema: 'https://0xcert.org/conventions/87-asset-evidence-schema.json',
65+
$schema: 'https://conventions.0xcert.org/87-asset-evidence.json',
6666
data: [...],
6767
};
6868
const metadata = {
@@ -245,7 +245,7 @@ Asset evidence represents a JSON object which holds information of the disclosed
245245

246246
```ts
247247
const evidence = {
248-
$schema: 'https://0xcert.org/conventions/87-asset-evidence-schema.json',
248+
$schema: 'https://conventions.0xcert.org/87-asset-evidence.json',
249249
data: [
250250
{
251251
path: [],
@@ -278,10 +278,10 @@ Yes, the 0xcert Conventions are simply JSON objects, and you could create them y
278278

279279
| Issue | Id | Description
280280
|-|-|-
281-
| [xcert](https://0xcert.org/conventions/xcert-schema.html) | e1823a17bb5dd039e2aff7d997223efed50dbeebb0fcb60cf7bba2a9b6f90140 | JSON Schema definition describing asset schema capabilities.
282-
| [86](https://0xcert.org/conventions/86-base-asset-schema.html) | 9a7531dd7ac3ed4e3d2fa61d20a825cfd4be7f3e6bc540c82d9dc94b526c5123 | Basic asset data schema.
283-
| [87](https://0xcert.org/conventions/87-asset-evidence-schema.html) | 02edbb4f2d07017d0ae9148af683a63d4b86d0d357a5019dd794d377a1523e9e | Asset evidence data schema.
284-
| [88](https://0xcert.org/conventions/88-crypto-collectible-schema.html) | cd3d7fce94669724f964061572f42ae0391996b0e348c7431251f9ab1bab0f49 | Schema describing digital collectible item.
281+
| [xcert](https://docs.0xcert.org/framework/v2/schemas/xcert-schema.html) | e1823a17bb5dd039e2aff7d997223efed50dbeebb0fcb60cf7bba2a9b6f90140 | JSON Schema definition describing asset schema capabilities.
282+
| [86](https://docs.0xcert.org/framework/v2/schemas/86-base-asset-schema.html) | 9a7531dd7ac3ed4e3d2fa61d20a825cfd4be7f3e6bc540c82d9dc94b526c5123 | Basic asset data schema.
283+
| [87](https://docs.0xcert.org/framework/v2/schemas/87-asset-evidence-schema.html) | 02edbb4f2d07017d0ae9148af683a63d4b86d0d357a5019dd794d377a1523e9e | Asset evidence data schema.
284+
| [88](https://docs.0xcert.org/framework/v2/schemas/88-crypto-collectible-schema.html) | cd3d7fce94669724f964061572f42ae0391996b0e348c7431251f9ab1bab0f49 | Schema describing digital collectible item.
285285

286286
**Example:**
287287

@@ -324,7 +324,7 @@ const metadata = {
324324
},
325325
};
326326
const evidence = {
327-
'$schema': 'https://conventions.0xcert.org/87-asset-evidence-schema.json',
327+
'$schema': 'https://conventions.0xcert.org/87-asset-evidence.json',
328328
'data': [],
329329
};
330330
```
@@ -461,7 +461,7 @@ Let's see how this works in practice with a simple schema.
461461

462462
```ts
463463
const schema = {
464-
'$schema': 'https://0xcert.org/conventions/xcert-schema.json',
464+
'$schema': 'https://conventions.0xcert.org/xcert-schema.json',
465465
'properties': {
466466
'$schema': {
467467
'type': 'string',
@@ -491,7 +491,7 @@ The algorithm first sorts all the keys in alphabetic order.
491491

492492
```ts
493493
const schema = {
494-
'$schema': 'https://0xcert.org/conventions/xcert-schema.json',
494+
'$schema': 'https://conventions.0xcert.org/xcert-schema.json',
495495
'properties': {
496496
'$evidence': { ... },
497497
'$schema': { ... },

‎api/guides/certification.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -81,13 +81,13 @@ By adding metadata schema information, we enable automatic machine-level interpr
8181

8282
Within the 0xcert Protocol, a digital asset employs a JSON Schema to describe asset context and data object structure. The asset schema allows for machine-level processing of asset information and thus makes each asset interoperable at the application layer.
8383

84-
Asset schema is a specifically designed JSON object, which conforms to [RFC-7159](https://en.wikipedia.org/wiki/JSON) and follows the mapping format defined by the [JSON Schema](http://json-schema.org) specification. The 0xcert Protocol supports only a subset of JSON Schema specification, which is described by the [Xcert JSON Schema](https://0xcert.org/conventions/xcert-schema.json). You should always refer to this JSON Schema subset when writing asset schemas for your projects.
84+
Asset schema is a specifically designed JSON object, which conforms to [RFC-7159](https://en.wikipedia.org/wiki/JSON) and follows the mapping format defined by the [JSON Schema](http://json-schema.org) specification. The 0xcert Protocol supports only a subset of JSON Schema specification, which is described by the [Xcert JSON Schema](https://conventions.0xcert.org/xcert-schema.json). You should always refer to this JSON Schema subset when writing asset schemas for your projects.
8585

8686
We incentivize the community to agree on standard schema conventions. Schema conventions should be proposed and included in the official 0xcert repository on GitHub. The 0xcert Framework already provides some basic schema conventions for you to use. For the purpose of this guide, we will define a minimal custom asset schema that describes the context and properties of the metadata created earlier.
8787

8888
```json
8989
{
90-
"$schema": "https://0xcert.org/conventions/xcert-schema.json",
90+
"$schema": "https://conventions.0xcert.org/xcert-schema.json",
9191
"properties": {
9292
"$evidence": {
9393
"type": "string"

‎api/schemas/86-base-asset-schema.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ A more human-friendly description of the above specification follows. This is pr
7777
```json
7878
{
7979
"$evidence": "https://troopersgame.com/dog/evidence.json",
80-
"$schema": "https://0xcert.org/conventions/86-base-asset-schema.json",
80+
"$schema": "https://conventions.0xcert.org/86-base-asset.json",
8181
"name": "Magic Sword",
8282
"description": "A weapon for the Troopers game that can severely injure the enemy.",
8383
"image": "https://troopersgame.com/dog.jpg"

‎api/schemas/87-asset-evidence-schema.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -92,7 +92,7 @@ The 0xcert framework provides an algorithm for creating proofs from asset data o
9292

9393
```json
9494
{
95-
"$schema": "https://0xcert.org/conventions/87-asset-evidence-schema.json",
95+
"$schema": "https://conventions.0xcert.org/87-asset-evidence.json",
9696
"data": [
9797
{
9898
"path": [],

‎api/schemas/88-crypto-collectible-schema.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,7 @@ This convention constitutes a digital asset that represents a crypto-collectible
5656
```json
5757
{
5858
"$evidence": "https://troopersgame.com/dog/evidence.json",
59-
"$schema": "https://0xcert.org/conventions/88-crypto-collectible-schema.json",
59+
"$schema": "https://conventions.0xcert.org/88-crypto-collectible.json",
6060
"name": "Magic Sword",
6161
"description": "A weapon for the Troopers game that can severely injure the enemy.",
6262
"image": "https://troopersgame.com/dog.jpg"

‎api/schemas/xcert-schema.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -158,7 +158,7 @@ This specification is provided in a machine-readable format using the JSON Schem
158158

159159
```json
160160
{
161-
"$schema": "https://0xcert.org/conventions/json-schema.json",
161+
"$schema": "https://conventions.0xcert.org/json-schema.json",
162162
"properties": {
163163
"fullName": {
164164
"description": "",

‎framework/v2/api/certification.md‎

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ A `string` representing asset imprint or `null` when metadata doesn't match.
6262
```ts
6363
// arbitrary data
6464
const evidence = {
65-
$schema: 'https://0xcert.org/conventions/87-asset-evidence-schema.json',
65+
$schema: 'https://conventions.0xcert.org/87-asset-evidence.json',
6666
data: [...],
6767
};
6868
const metadata = {
@@ -245,7 +245,7 @@ Asset evidence represents a JSON object which holds information of the disclosed
245245

246246
```ts
247247
const evidence = {
248-
$schema: 'https://0xcert.org/conventions/87-asset-evidence-schema.json',
248+
$schema: 'https://conventions.0xcert.org/87-asset-evidence.json',
249249
data: [
250250
{
251251
path: [],
@@ -324,7 +324,7 @@ const metadata = {
324324
},
325325
};
326326
const evidence = {
327-
'$schema': 'https://conventions.0xcert.org/87-asset-evidence-schema.json',
327+
'$schema': 'https://conventions.0xcert.org/87-asset-evidence.json',
328328
'data': [],
329329
};
330330
```
@@ -461,7 +461,7 @@ Let's see how this works in practice with a simple schema.
461461

462462
```ts
463463
const schema = {
464-
'$schema': 'https://0xcert.org/conventions/xcert-schema.json',
464+
'$schema': 'https://conventions.0xcert.org/xcert-schema.json',
465465
'properties': {
466466
'$schema': {
467467
'type': 'string',
@@ -491,7 +491,7 @@ The algorithm first sorts all the keys in alphabetic order.
491491

492492
```ts
493493
const schema = {
494-
'$schema': 'https://0xcert.org/conventions/xcert-schema.json',
494+
'$schema': 'https://conventions.0xcert.org/xcert-schema.json',
495495
'properties': {
496496
'$evidence': { ... },
497497
'$schema': { ... },

‎framework/v2/guides/certification.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -81,13 +81,13 @@ By adding metadata schema information, we enable automatic machine-level interpr
8181

8282
Within the 0xcert Protocol, a digital asset employs a JSON Schema to describe asset context and data object structure. The asset schema allows for machine-level processing of asset information and thus makes each asset interoperable at the application layer.
8383

84-
Asset schema is a specifically designed JSON object, which conforms to [RFC-7159](https://en.wikipedia.org/wiki/JSON) and follows the mapping format defined by the [JSON Schema](http://json-schema.org) specification. The 0xcert Protocol supports only a subset of JSON Schema specification, which is described by the [Xcert JSON Schema](https://0xcert.org/conventions/xcert-schema.json). You should always refer to this JSON Schema subset when writing asset schemas for your projects.
84+
Asset schema is a specifically designed JSON object, which conforms to [RFC-7159](https://en.wikipedia.org/wiki/JSON) and follows the mapping format defined by the [JSON Schema](http://json-schema.org) specification. The 0xcert Protocol supports only a subset of JSON Schema specification, which is described by the [Xcert JSON Schema](https://conventions.0xcert.org/xcert-schema.json). You should always refer to this JSON Schema subset when writing asset schemas for your projects.
8585

8686
We incentivize the community to agree on standard schema conventions. Schema conventions should be proposed and included in the official 0xcert repository on GitHub. The 0xcert Framework already provides some basic schema conventions for you to use. For the purpose of this guide, we will define a minimal custom asset schema that describes the context and properties of the metadata created earlier.
8787

8888
```json
8989
{
90-
"$schema": "https://0xcert.org/conventions/xcert-schema.json",
90+
"$schema": "https://conventions.0xcert.org/xcert-schema.json",
9191
"properties": {
9292
"$evidence": {
9393
"type": "string"

‎framework/v2/schemas/86-base-asset-schema.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ A more human-friendly description of the above specification follows. This is pr
7777
```json
7878
{
7979
"$evidence": "https://troopersgame.com/dog/evidence.json",
80-
"$schema": "https://0xcert.org/conventions/86-base-asset-schema.json",
80+
"$schema": "https://conventions.0xcert.org/86-base-asset.json",
8181
"name": "Magic Sword",
8282
"description": "A weapon for the Troopers game that can severely injure the enemy.",
8383
"image": "https://troopersgame.com/dog.jpg"

‎framework/v2/schemas/87-asset-evidence-schema.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -92,7 +92,7 @@ The 0xcert framework provides an algorithm for creating proofs from asset data o
9292

9393
```json
9494
{
95-
"$schema": "https://0xcert.org/conventions/87-asset-evidence-schema.json",
95+
"$schema": "https://conventions.0xcert.org/87-asset-evidence.json",
9696
"data": [
9797
{
9898
"path": [],

0 commit comments

Comments
 (0)