-
Notifications
You must be signed in to change notification settings - Fork 11
Initial commit of new places taxonomy #420
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
Conversation
jenningsanderson
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 Pydantic changes look good, too!
packages/overture-schema-places-theme/src/overture/schema/places/place.py
Outdated
Show resolved
Hide resolved
packages/overture-schema-places-theme/src/overture/schema/places/place.py
Outdated
Show resolved
Hide resolved
packages/overture-schema-places-theme/src/overture/schema/places/place.py
Outdated
Show resolved
Hide resolved
packages/overture-schema-places-theme/src/overture/schema/places/place.py
Show resolved
Hide resolved
packages/overture-schema-places-theme/src/overture/schema/places/place.py
Show resolved
Hide resolved
vcschapp
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks pretty good. I picked a few nits and also called out the sad and sorry need to duplicate the examples/counterexamples.
28846c2
danabauer
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
packages/overture-schema-places-theme/src/overture/schema/places/place.py
Show resolved
Hide resolved
packages/overture-schema-places-theme/src/overture/schema/places/place.py
Outdated
Show resolved
Hide resolved
* Initial commit of new places taxonomy * Fix TX region * Add operating_status to bad-categories-value * Fix mistakenly change alternate -> alternates * Revert change to bad categories counterexample * Add pydantic model for new taxonomy * Fix up place baseline schema json * Copy examples/couterexamples to references. Update docs * Update main place.yaml file to reflect unique/minItems constraints * Add backtick and reference to Places doc page * Update baseline json
* Initial commit of new places taxonomy * Fix TX region * Add operating_status to bad-categories-value * Fix mistakenly change alternate -> alternates * Revert change to bad categories counterexample * Add pydantic model for new taxonomy * Fix up place baseline schema json * Copy examples/couterexamples to references. Update docs * Update main place.yaml file to reflect unique/minItems constraints * Add backtick and reference to Places doc page * Update baseline json
B. Related MINOR change steps
C. Public documentation and messaging plan
TODO.
Description
Brief description of the business purpose and effect of the pull request.
Adds the new categorization description for Overture's new taxonomy. This includes
specifying the primary category and the hierarchy from most general to most specific. The
schema includes the ability to specify alternates, but those are only the strings.
Reference
List of relevant links to GitHub issues, PRs, and other documentation.
Testing
Brief description of the testing done for this change showing why you are confident it works as expected and does not introduce regressions. Provide sample output data where appropriate.
TODO.
Checklist
Checklist of tasks commonly-associated with schema pull requests. Please review the relevant checklists and ensure you do all the tasks that are required for the change you made.
Abut is not intended to test propertyA's validity, and you made a schema change that invalidates propertyAin that counterexample, fix the counterexample to align it with your schema change.Documentation website
Update the hyperlink below to put the pull request number in.
[Docs preview for this PR.](https://dfhx9f55j8eg5.cloudfront.net/pr/<PUT THE PR # HERE>)