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
The root schema of a JSON Schema document SHOULD contain an "$id" keyword with an absolute-URI [RFC3986] (containing a scheme, but no fragment).
So these $ids should probably be changed to be an absolute URI.
While it might technically be valid to use an 'arbitrary' URI, this should probably be synchronized with publishing these schemas at https://schema.khronos.org/ . The schema files are not part of the normative specification, so it should even be possible to change this without any issues of ratification.
The text was updated successfully, but these errors were encountered:
I knew that this had been mentioned somewhere earlier, and just found it: #2049 (comment) - it may make sense to still track this specific point about the $id here.
Currently, the
$id
in the schemas just consist of a file name - for example, inaccessor.schema.json
Section 8.2.1.1 of draft 2020-12 says
So these
$id
s should probably be changed to be an absolute URI.While it might technically be valid to use an 'arbitrary' URI, this should probably be synchronized with publishing these schemas at https://schema.khronos.org/ . The schema files are not part of the normative specification, so it should even be possible to change this without any issues of ratification.
The text was updated successfully, but these errors were encountered: