Now that the support for the more complex configuration files is
in place, we should consider allowing user to limit the arcs
produced by the modules that typically produce many, possibly
unrelated, ones; i. e.: ‘gdalinfo’, ‘gdal’, ‘grib’, and ‘stat’.
IOW, the user should be given an option to selectively disable
an arc, or to enable only a specific set of arcs.

In the configuration graph, such options may be expressed
roughly as follows (using the Turtle notation).

    @prefix ex:
        <uuid:dd853b74-e0c6-11df-8626-00195b7187be#> .
    @prefix fdrdf:
        <uuid:0c953d4c-cb8c-11df-a381-4040a5e6bfa3#cf.> .
    @prefix stat:
        <uuid:2e22aa82-b550-11df-9d5c-4040a5e6bfa3#stat.> .
    @prefix statmod:
        <uuid:21624fe2-b54f-11df-b9c0-4040a5e6bfa3> .
    @prefix gdalinfo:
        <uuid:4a48ad14-bbd2-11df-b186-4040a5e6bfa3#cf.> .
    @prefix gdalinfomod:
        <uuid:ea1a00f1-68ba-4739-aa7e-f74967ce5eb8#gdalinfo.> .

    ex:default
        fdrdf:default true ;
        fdrdf:arcsLimit [
            ## limit to a specific set of arcs
            fdrdf:module      statmod: ;
            fdrdf:arcEnable   stat:n.mode ;
            fdrdf:arcEnable   stat:n.size
        ] ;
        fdrdf:arcsLimit [
            ## remove an unwanted arc
            fdrdf:module      gdalinfomod: ;
            fdrdf:arcDisable  gdalinfo:PGEVERSION
        ] .