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
I'm trying to update my validator to 2019-09 and looking for precise info about how to handle new keyword $anchor.
I searched for $ahcnor references in the 2019-09 spec that I have.
"When an implementation encounters the <#/$defs/single> schema, it resolves the "$id" URI reference against the current base URI to form https://example.net/root.json#item."
Yeah, that looks wrong. Probably something that slipped through the cracks when $anchor was split off of $id.
Prior to draft 2019-09, "$anchor": "item" from that example would have been "$id": "#item". In that form, the description makes sense. $anchor should behave exactly like an $id starting with a fragment did in previous drafts. The only difference is that the leading # is no longer used.
I'm trying to update my validator to 2019-09 and looking for precise info about how to handle new keyword $anchor.
I searched for $ahcnor references in the 2019-09 spec that I have.
"When an implementation encounters the <#/$defs/single> schema, it resolves the "$id" URI reference against the current base URI to form https://example.net/root.json#item."
json-schema-spec/jsonschema-core.xml
Line 1712 in 30f3158
However the snippet above does not include an $id property at defs/single; it has an $anchor property.
Is that incorrect or have I misunderstood?
The text was updated successfully, but these errors were encountered: