The example schemas use bare relative $id (e.g. Person.schema.json), no x-oold-uuid, and no
x-oold-version. The spec's Identification/Versioning sections recommend resolvable absolute $id
(optionally UUID-based), x-oold-uuid, and x-oold-version, with instances referencing a
versioned schema URL.
The tutorial therefore diverges from the spec's identity model on first contact.
Ask:
- Provide at least one example using a resolvable absolute
$id, x-oold-uuid, and
x-oold-version, with an instance that references the versioned URL.
- Should version be encoded in the URL e.g. oo-ld.org/schema/v0.0.1/Person.oo-ld-schema.json?
@context and $schema references should always be an explicit URL, not a relative path- Optionally show a v1.0.0 → v1.1.0 bump with
x-oold-prior-version / backward-compatible-with.
Acceptance: new example follows the spec's identification & versioning conventions.
The example schemas use bare relative
$id(e.g.Person.schema.json), nox-oold-uuid, and nox-oold-version. The spec's Identification/Versioning sections recommend resolvable absolute$id(optionally UUID-based),
x-oold-uuid, andx-oold-version, with instances referencing aversioned schema URL.
The tutorial therefore diverges from the spec's identity model on first contact.
Ask:
$id,x-oold-uuid, andx-oold-version, with an instance that references the versioned URL.@contextand$schemareferences should always be an explicit URL, not a relative pathx-oold-prior-version/backward-compatible-with.Acceptance: new example follows the spec's identification & versioning conventions.