Re: [dxwg] referencing named graph of endpoint or RDF quad file (#1241)

Hi @andrea-perego !

I have not been following the DCAT progress too close lately. Is there now a modeling approach for the referencing of named graphs in quadstores and RDF quad files? If this is not yet done but still wanted, I'll share below the final modeling approach I took in my research, using a self-made extension of DCAT, i.e. [CDC]( The modeling would be done as follows for default graph and specific named graph distributions (either served via an RDF quad file or quadstore service):

@prefix dcat: <> .
@prefix void: <> .
@prefix cdc: <> .

:dataset1 a dcat:Dataset ;
   dcat:distribution :dataset1_quadStoreDistr , :dataset1_quadFileDistr .
:dataset1_quadStoreDistr a cdc:DefaultGraphDistribution ; # the content of :dataset1 is available in the default graph of this SPARQL endpoint service
   dcat:accessService :mysparqlEndpoint .
:dataset1_quadFileDistr a cdc:NamedGraphDistribution ; # the content of :dataset1 is available in the named graph :myNamedGraph of the TriG file
   cdc:graphURI :myNamedGraph ;
   dcat:downloadURL <> ;
   dcat:mediaType <> .
:mysparqlEndpoint a dcat:DataService ;
    dcat:endpointURL <> ;
    dct:conformsTo <> ;
    dcat:servesDataset :dataset1 .

`cdc:DefaultGraphDistribution` and `cdc:NamedGraphDistribution` are subclasses of `dcat:Distribution`. If no such specific class is used on a distribution and the RDF file or data service supports quads, the content of the dataset should be assumed to be located in all named graphs and the default graph.

Thus instead of creating different datasets, one `dcat:Dataset` with optionally different distributions suffices as the content of the reflected RDF dataset remains the same. Each distribution then indicates if the content of the dataset is spread over the entire triplestore/quadstore or RDF triple/quad file, or if it's located in a specific named graph or the default graph of a quadstore or RDF quad file. I refrained from reusing SD (SPARQL Description) terminology as I wanted to have a solution that is applicable beyond SPARQL endpoint services, e.g. for quad RDF files and quad pattern fragment servers (triple pattern fragment servers with quad support, such as [this]( one). The SD modeling patterns are also relatively ackward to use in combination with the concept of `dcat:Distribution`.

Personally, I would be in favor to see the concepts `cdc:DefaultGraphDistribution`, `cdc:NamedGraphDistribtion` and `cdc:graphURI` to be included in DCAT as I believe this can be useful for others who want to indicate the used named/default graphs in distributions as well!

GitHub Notification of comment by mathib
Please view or discuss this issue at using your GitHub account

Sent via github-notify-ml as configured in

Received on Thursday, 11 March 2021 16:06:59 UTC