Is your feature request related to a problem? Please describe.
It was unclear to reviewers (of the DDE's initial paper submission), bioschemas users, and bioschemas programmers trying to use the JSON LD from the DDE how cardinality is expressed. We are explicit about it in the tutorial for bioschemas users, but it should be made more intuitive/obvious. Currently, the only way to even guess it is to see the difference between the string and string(s) option in the validation editor.
Describe the solution you'd like
Create a tab for one validation options and many validation options. Automatically add owl:cardinality:one or owl:cardinality:many to a property whenever a validation rule is used from the corresponding tab.
Describe alternatives you've considered
Explained cardinality encoding in the paper and in tutorials, but it's still not immediately obvious to users.
Additional context
Potentially something like this:
Is your feature request related to a problem? Please describe. It was unclear to reviewers (of the DDE's initial paper submission), bioschemas users, and bioschemas programmers trying to use the JSON LD from the DDE how cardinality is expressed. We are explicit about it in the tutorial for bioschemas users, but it should be made more intuitive/obvious. Currently, the only way to even guess it is to see the difference between the
string
andstring(s)
option in the validation editor.Describe the solution you'd like Create a tab for
one
validation options andmany
validation options. Automatically addowl:cardinality
:one
orowl:cardinality
:many
to a property whenever a validation rule is used from the corresponding tab.Describe alternatives you've considered Explained cardinality encoding in the paper and in tutorials, but it's still not immediately obvious to users.
Additional context Potentially something like this: