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

Don't override external specifications. See #20. #26

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

ioggstream
Copy link
Collaborator

This PR

References external spec instead of overriding them

Note

If $schema is defined into JSONSchema, probably we should just reference it.

@ioggstream
Copy link
Collaborator Author

cc: @jdesrosiers @Relequestual

@jdesrosiers
Copy link
Contributor

I don't think this is the right approach. See #20 (comment)

Copy link
Collaborator Author

@ioggstream ioggstream left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can this work?

schema to change within the same Schema Resource.
A dialect defining the `$schema` keyword:

* MUST do it according to the content of this section;
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jdesrosiers ensure that $schema is defined consistently btw various dialects

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this is quite the right perspective. $schema is not a keyword that dialects can define. It's a media type construct. So, we probably need to say something like, $schema is a reserved property that belongs to the media type and dialects MUST NOT define keywords that conflict with that name.

* SHOULD define where the `$schema` keyword is allowed and/or
recognized in a schema;
* SHOULD not allow the
schema to change within the same Schema Resource.
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Schema resource" should probably be referenced .

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed. Schema Reference and Schema Document need to be defined.

@darrelmiller darrelmiller linked an issue Mar 19, 2022 that may be closed by this pull request
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

jsonschema: dialect identification
2 participants