I have developed several tools in the last year which required me to define a feature style for certain geometry representations modelled with GeoSPARQL.
I ended up defining:

• A style property which links a geo:Geometry to a style description instance with
  • point/lineString/Polygon style properties with CSS literals
  • pointImage/lineStringImage/polygonImage properties with URIs pointing to Icons or SVG definitions (SVG literals)
  • hatch: Whether to draw the geometry in a hatched style
  • lineStringImageStyle: How the image behaves in the lineString (how often it is repeated etc.)

There may be several style representations per geometry and there could be constraints attached to each of these styles which link to certain semantic classes (for now modelled as text literals by me).
So there could be the possibility for reasoning eligible styles for a Geometry representation according to the data given.

What I currently do with these style representations is to downlift them to GeoJSONCSS (https://github.com/albburtsev/Leaflet.geojsonCSS) and then add them to a Leaflet view.

My questions are therefore:

• Is the GeoSPARQL ontology the right place to standardize feature style descriptions?
• Is there any other related work known to members of the group or best practices I have overlooked?