Evolve the glossary generation II

[cristianvasquez]

I'm creating this task to keep track of requirements for ePO.
continues: #103

Currently, the glossary is built from an XMI that is transformed into an HTML output.

The task is to update the glossary to read the OWL/SHACL files directly, so the information shown is accurate.

• Features
  • Metadata
    • display dcterms:, vann:, owl: metadata
  • Classes
    • display broader/narrower concepts
    • display disjoint/equivalent classes
    • display relationships (both object and datatype)
    • display inherited relationships from broader concepts
      • (probably requires inference or CONSTRUCT over the OWL/RDF)
    • Display deprecation status and notes
  • Properties
    • Usage (i.e which classes)
      • Expected values and cardinality
    • display broader/narrower properties
  • Filtering:
    • Filter by module
      • That is, an entity has rdfs:isDefinedBy :module
    • By status
  • Labels
    • Display all labels and definitions (for example multiple languages)
  • Cross-referencing:
    • Provide links to related concepts
    • Show usage examples or instance data if available

The schema vocabulary HTML representation could serve as inspiration