Related to #3159.
When a local JSON Schema directory uses path-only $id values such as /schemas/v1/formats/canonical/_base.json, path-absolute $ref values in that URI space can be resolved as filesystem-root paths instead of paths under the local input root.
Minimal shape:
{
"$id": "/schemas/v1/formats/canonical/_base.json",
"properties": {
"platform_extensions": {
"items": { "$ref": "/schemas/v1/core/platform-extension-ref.json" }
}
}
}If the local input root contains formats/canonical/_base.json and core/platform-extension-ref.json, the ref should resolve to core/platform-extension-ref.json, not /schemas/v1/core/platform-extension-ref.json on the host filesystem.
This blocks local generation for schema trees like AdCP dist/schemas/3.1.0-beta.x.
Related to #3159.
When a local JSON Schema directory uses path-only
$idvalues such as/schemas/v1/formats/canonical/_base.json, path-absolute$refvalues in that URI space can be resolved as filesystem-root paths instead of paths under the local input root.Minimal shape:
{ "$id": "/schemas/v1/formats/canonical/_base.json", "properties": { "platform_extensions": { "items": { "$ref": "/schemas/v1/core/platform-extension-ref.json" } } } }If the local input root contains
formats/canonical/_base.jsonandcore/platform-extension-ref.json, the ref should resolve tocore/platform-extension-ref.json, not/schemas/v1/core/platform-extension-ref.jsonon the host filesystem.This blocks local generation for schema trees like AdCP
dist/schemas/3.1.0-beta.x.