Present Prez Profile system config

[nicholascar]

In Prez docco

<system>
    ex:hasProfiledClass [
        ex:class geo:Feature ;
        ex:profile  # inverse of <Profile> constrains <Class>
            <http://www.opengis.net/def/geosparql> ,
            <http://www.opengis.net/spec/ogcapi-features-1/1.0/req/oas30> ;
        ex:defaultProfile <http://www.opengis.net/def/geosparql> ;
    ] ;
    ex:formats [
        ex:class geo:Feature ;
        ex:profile <http://www.opengis.net/def/geosparql> ;
        dcterms:format
            "application/ld+json" ,
            "application/rdf+xml" ,
            "text/html" ,
            "text/turtle" ,
            "application/geo+json" ,
        ex:defaultFormat "text/html" ;
    ] ,
    [
        ex:class geo:Feature ;
        ex:profile <http://www.opengis.net/spec/ogcapi-features-1/1.0/req/oas30> ;
        dcterms:format "application/geo+json" ;
        ex:defaultFormat "application/geo+json" ;
    ] ,
.

ex:hasConstrainingProfile can be derived from the constrains <Class> details presented by all loaded profiles.

ex:hasDefaultConstrainingProfile is a per-system configuration with Prez shipping with defaults, e.g. as per above, GeoSPARQL is the default for geo:Feature.

Decide where to put this config: is it just another RDF file in the Profiles dir?

[recalcitrantsupplant]

This is a profiled view of classes (i.e. a "class" profile), where we are after inbound links to classes e.g. profile X constrainsClass Y. So it can be created with the current profiling mechanisms

[recalcitrantsupplant]

would make sense to add /classes and /classes/{class} endpoints, even if they're not exposed in the frontend