-
-
Notifications
You must be signed in to change notification settings - Fork 216
format 'uri' and URI-references #58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
One old |
ok so in draft4 an exception is made for |
@fd in Draft 4 the "uri" format included relative references. This was corrected in Draft 5 which has both "uri" and "uriref" formats, where any "uri" is a valid "uriref", but "uriref" can include relative-references which are not valid under "uri". See json-schema-org/json-schema-org.github.io#57 which shows the proposed draft 5 meta-schema where "id" is format "uriref" while "$schema" is format "uri". Since issue #136 is already tracking creating tests for the new draft(s), I think this issue can be closed? |
Plenty of confusion still about Draft 3/4's URI, but that's already being addressed in Draft 6. After this PR, the tests here are at least internally consistent (at this point they all consider only URIs not URI references). Refs: #58, #77, #156 * awwright/master: Flip protocol-relative URI Reference (not a URI)
If this is invalid and
id
is supposted to be auri
(and not a relative reference). Then why is this valid?The text was updated successfully, but these errors were encountered: