Skip to content
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

This url - https://json-schema.org/draft/2019-09/vocab/core doesn't work #815

Closed
opethe1st opened this issue Oct 20, 2019 · 4 comments
Closed

Comments

@opethe1st
Copy link

opethe1st commented Oct 20, 2019

This url in the latest draft as defined here https://json-schema.org/draft/2019-09/schema. You can go to the url and check that this is one of the urls under "$vocabulary"

@opethe1st
Copy link
Author

I could work on a PR if that works too.

@notEthan
Copy link
Contributor

this URL is just an identifier which does not correspond to a document. it sort of corresponds to the meta document at https://json-schema.org/draft/2019-09/meta/core (referenced in the allOf property of the metaschema), though I can't quite explain the relationship.

I was confused by this for a while too. I think it needs improved clarification in the spec.

@opethe1st
Copy link
Author

opethe1st commented Oct 20, 2019

I know from the spec it doesn't have to correspond to a retrievable document but this particular case looked like an oversight to me.
Plus it is actually better developer UX to be able to click in an editor on the url and get the document being referenced.

RIght now, I would have to jump through hoops to find the validation schema. Took me like 5 minutes to locate when it should have been just a click.

@handrews
Copy link
Contributor

I know from the spec it doesn't have to correspond to a retrievable document but this particular case looked like an oversight to me.

It doesn't correspond to a retrievable document because we don't know what to put in the document until people try to implement the vocabulary feature and tell us what should go there.

Some of the inconclusive discussions involved can be found at #602 and at #563 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants