Generate documentation pages for properties

[Raphael-Gazzotti]

Related to #44

We should start to generate individual pages for each property. This will help us document them properly and make sure their URLs can be resolved in the future when we need to link to them.

The idea is to give each property its own space with the relevant info (like name, description, type, etc.). This information is already available in the central repository of OpenMINDS in the vocab (i.e., properties.json file).

[lzehl]

I would suggest to make a new page in the navigation menu ("Properties" or "Property specifications" or "Property vocabularies").

Then we need to decide if each property gets its own subpage or if each property is defined as subsection on the same page (cf. instance libraries). I tend to the latter. We could also do a mix of both and group alphabetically.

@openMetadataInitiative/openminds-developers your preferences??

[lzehl]

Let's do a "vocab specification" in the side menu with 3 subsections: categories, types, properties and gather for each for now only minimal information. If considering all info this will include the following:

categories:

• each category in a subheader (category name)
• below subheader all schema types (with links to their docu) organized alphabetically (maybe in a compact way e.g. in a table?)

types:

• each type in a subheader (type label) [AgeCategory]
  (- preferred display color) [optional is not really yet well defined]
• display label: XXX [age category]
• description: XXX
• semantic name: (namespace info) namespace, version(s)
• version compatibility info (combine?):
  • backwards compatibility, version(s) [list per statement?: latest is ... to v4]
  • is identical, version(s) [list per statement?: latest is ... to v4]
• occurrence/used in: version(s)

properties:

• each type in a subheader (type label) [ageCategory]
• plural label: XXX (maybe combine with singular label) [ageCategories]
• display label: XXX [age category]
• plural display label: XXX (maybe combine with singular display label) [age categories]
• description: XXX
• semantic name: (namespace info) namespace, version(s)
• formatting: format, version(s) [as string vs as edge (vs number !missing in vocab)]
• occurrence/used in: version(s) + type(s) or category ?

Any suggestion for displaying this in a nice, compact way are welcome. Double check also the naming in the existing docu parts (for consistency).

[lzehl]

Let's split the resolution of the property namespace to another issue. (these are two PRs anyway no?)