Is your feature request related to a problem? Please describe.
When extending from NIAID schema (which has cardinality encoded via owl:cardinality, and the cardinality toggle is enabled, preload the existing cardinality from the parent schema so that it's easy to see right away. Here, you can see the cardinality selector is empty even though the parent class has a cardinality information saved for the property:
Describe the solution you'd like
Have the cardinality preloaded if user toggles the cardinality editor. So in the previous example, it would look like this by default:
Describe alternatives you've considered
Ask users to scroll through the preloaded validation rules, identifying the owl:cardinality portion and selecting a cardinality based on the value. But, the preloaded json validation rules are working nicely--seems like preloading this makes sense.
Is your feature request related to a problem? Please describe. When extending from NIAID schema (which has cardinality encoded via
owl:cardinality
, and the cardinality toggle is enabled, preload the existing cardinality from the parent schema so that it's easy to see right away. Here, you can see the cardinality selector is empty even though the parent class has a cardinality information saved for the property:Describe the solution you'd like Have the cardinality preloaded if user toggles the cardinality editor. So in the previous example, it would look like this by default:
Describe alternatives you've considered Ask users to scroll through the preloaded validation rules, identifying the
owl:cardinality
portion and selecting a cardinality based on the value. But, the preloaded json validation rules are working nicely--seems like preloading this makes sense.