AlasdairGray
commented
11 months ago In the current model the obligation of a property is not necessarily consistent across all usages of a property. For example, issued is recommended for a DataService but optional for a Dataset.
It seems that the obligation is only shown if it is consistent across all usages but I don't see how this is programmed in the style sheet.
Testing with changing the cardinality did not seem to change whether the value is shown or not.
cyberdudeuk
Is your feature request related to a problem? Please describe. Currently the information on whether a property is Required (i.e. Mandatory) or Recommended, and its Cardinality is displayed as a line at the bottom of the first section (currently untitled) which contains the definition of the property, its URI and and the applicable range. It's somewhat easy to miss as it's slightly obscured by the preceding content. What is displayed for Obligation and Cardinality is actually a Boolean Value, i.e. True or False (in this case only those that are True).
Describe the solution you'd like A clearer way for providing this information to make it more evident and visible would be to single it out into a separate section and replace the values by Yes or No, which might be more meaningful to a greater, more diverse range of users.
Describe alternatives you've considered Creating a separate section is a neater, more user-friendly way of displaying this content, another option would be to make it Bold so it is more evident from the preceding content. The first option above however is the preferable outcome. It would be even better if the 2 values were shown in 2 separate boxes in just the one line, like a row in a table.
Additional context