MetaContainer

 Function: returns the first-stage LD Platform list of contained URIs and the dataset metadata.
 Args    : $starting_at_record : this will be passed-in to tell you what record to start with (for paginated responses)
 $path : the webserver's PATH_INFO environment value (used to modify the behaviour of REST services)
 Returns : JSON encoded listref of 'meta URIs' representing individual records
 Note    :  meta URIs are generally URIs that point back to this same server; calling GET on a meta URI will
            return an RDF description of the set of DCAT distributions for that record.\
            this can be handled by the

Distributions

 Function: returns the second-stage LD Platform metadata describing the DCAT distributions, formats, and URLs
           for a particular record
 Args    : $ID : the desired ID number, as determined by the Accessor.pm module
           $PATH_INFO : the webserver's PATH_INFO environment value (in case the $ID best-guess is wrong... then you're on your own!)
 Returns : JSON encoded hashref of 'meta URIs' representing individual DCAT distributions and their mime-type (mime-type is the hash key)
            The format for this response is (note that values are always allowed to be lists, if you wish):
            
            {"metadata":
                {"rdf:type": ["edam:data_0006","sio:SIO_000088"],
                 "my:metadatathingy":  "some value",
                 "external:metadatatype":  "some other value"
                },
            "distributions":
                {"application/rdf+xml" : "http://myserver.org/ThisScript/record/479-467-29X.rdf",
                 "text/html" : "http://myserver.org/ThisScript/record/479-467-29X.html"
                }
            }