[Feature] Profile-guided Conversion #10
Description
Currently there are two flavours of GeoJSON output, being the JSONLD-inspired default form that has namespaced keys, a context dict, and nested property values. And the "human-readable" form that uses the property's annotation for keys, and completely flattened graph shapes for values.
The flavour is selected using the "kind" argument, where "human" denotes the human-readable flattened form, and anything else causes the default form to be returned.
With the recent discussions around needing to make the rdf2geojson converter more EMSA-aware, in order to deliver more deep-traversal properties, we are going to need a way of selecting more than just "human" or "normal". This is going to need to be a break away from the as-generic-as-possible rdf2geojson approach, with some baked-in EMSA-aware profiles for each of the different EMSA protocols.
The first step in that direction would be to swap out the "kind" argument for a "profile" argument, where it can refer to a known baked-in rdf2geojson conversion profile.