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.

Sign up for GitHub

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

Jump to bottom

Clarify that additional top-level fields in the JSON metadata are allowed #28

Merged
merged 1 commit into from
Mar 4, 2022
Merged

Clarify that additional top-level fields in the JSON metadata are allowed #28

merged 1 commit into from
Mar 4, 2022

Conversation

jorisvandenbossche
Copy link
Collaborator

Closes #17

@jorisvandenbossche jorisvandenbossche mentioned this pull request Mar 4, 2022
Closed
pomadchin
pomadchin approved these changes Mar 4, 2022
View reviewed changes
Copy link
Collaborator

@pomadchin pomadchin left a comment

Choose a reason for hiding this comment

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

👍

@cholmes cholmes merged commit 183a934 into opengeospatial:main Mar 4, 2022
@jorisvandenbossche jorisvandenbossche deleted the json-additional-fields branch March 4, 2022 21:07
@kylebarron kylebarron mentioned this pull request Apr 12, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@cholmes cholmes cholmes approved these changes

@pomadchin pomadchin pomadchin approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Make clear in the spec that additional fields are ok in JSON
3 participants
@jorisvandenbossche @cholmes @pomadchin