Remove overly vague medical health properties (issue 2429)#2448
Merged
danbri merged 1 commit intoschemaorg:masterfrom Jan 27, 2020
Merged
Remove overly vague medical health properties (issue 2429)#2448danbri merged 1 commit intoschemaorg:masterfrom
danbri merged 1 commit intoschemaorg:masterfrom
Conversation
Contributor
|
Thanks @tjann! I've merged this for our next release. (Thanks for adding /subtype). Let's also find some way of recording the names of deleted terms in the RDFS representation in case tools want to use that information to help people know when they're using outdated terms. I'll make something up. |
|
Isn't there some kind of status property on terms in schema.org to indicate proposed/adopted/supercededby/deprecated |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.