Use overview images, or eliminate them from generated ontology documentation

[VladimirAlexiev]

https://opengeospatial.github.io/ogc-geosparql/geosparql11/index.html

https://opengeospatial.github.io/ogc-geosparql/geosparql11/functions.html https://opengeospatial.github.io/ogc-geosparql/geosparql11/functions.html https://opengeospatial.github.io/ogc-geosparql/geosparql11/rules.html https://opengeospatial.github.io/ogc-geosparql/geosparql11/reqs.html https://opengeospatial.github.io/ogc-geosparql/geosparql11/sf_geometries.html https://opengeospatial.github.io/ogc-geosparql/geosparql11/servicedescription_extensions.html https://opengeospatial.github.io/ogc-geosparql/geosparql11/servicedescription_conformanceclasses.html A black rectangle that results from a &nbsp sized to 500x500.

I guess it's not so easy to select or make overview images for GeoSPARQL and its related ontologies. Here are a couple of examples that perhaps could be adapted:

• "GeoSPARQL-geometry", I think from a CIDOC CRM presentation
• OpenGIS geometry class hierarchy

---

@nicholascar :

• Looking at https://github.com/RDFLib/pyLODE/blob/master/pylode/rdf_elements.py, I guess it's from embedded markdown in dct:description?
• I cannot find a label "Overview" in the pyLODE source: https://github.com/search?q=repo%3ARDFLib%2FpyLODE+overview&type=code
• I guess this issue is related https://github.com/RDFLib/pyLODE/issues/144

[situx]

As I recall, we want to rely on Pylode to create diagrams for us here, and I believe it is, in general, able to do that. We still use pylode 2.13 to generate the documentation, so maybe it could be an option to try pylode 3.x. In any case, an automated solution is probably preferred here. @nicholascar should know more

[VladimirAlexiev]

• WebVOWL can generate dynamic diagrams. But the index has separate links for such diagrams, and I don't thin they should be included in the PyLODE documentation.
• I don't think PyLODE can generate diagrams
• sec "11 CORE" (of version 1.3) has this:

[nicholascar]

@VladimirAlexiev I'm looking into all the diagrams for GeoSPARQL now and will try and tidy things up across all documentation shortly. Part of the solution is to get the OGC Naming Authority to do most of the vocabulary rendering for us and they auto-generate some diagrams.

I'll put results of this work in here shortly.