Added spec entry class #1161
Draft
Added spec entry class #1161
Conversation
This file contains 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.
Closes #527.
INTENDED AS DRAFT FOR DISCUSSION
Added
SpecEntryclass, by importing the operators ontology. Below is an example usage that uses some gist units reference data. Note how the possible values for aspects that are not magnitudes are specified by pointing to a collection. This allows different combinations of colors to be used in different contexts (e.g. warm colors vs. cool colors) w/o needing new category classes.If we want to use
gist:isPartOf, the diagram gets a bit ugly.