property for presenting private/public dataset needs renaming

[andrecastro0o]

using the property status is not a good way to describe public/private. It is too vague. Can mean a lot of things besides public/private, like active/inactive,

[andrecastro0o]

I feel that the best is to use dcat:accessService property to indicate that it is a public / private dataset.

Looking at the definition of dcat:accessService in DCAT2.0 https://www.w3.org/TR/vocab-dcat-2/#Property:distribution_access_service

RDF Property: dcat:accessService Definition: A data service that gives access to the distribution of the dataset Range: dcat:DataService Usage note: dcat:accessService SHOULD be used to link to a description of a dcat:DataService that can provide access to this distribution.

dcat:DataService https://www.w3.org/TR/vocab-dcat-2/#Class:Data_Service

RDF Class: dcat:DataService Definition: A collection of operations that provides access to one or more datasets or data processing functions. Sub-class of: dcat:Resource Sub-class of: dctype:Service Usage note: If a dcat:DataService is bound to one or more specified Datasets, they are indicated by the dcat:servesDataset property.

This means that if I use dcat:accessService it will have to have as value and instance of the class dcat:DataService, which could be our data repository services (KDP, 4TU, ICOS, Cloudnet, etc) for the public repositories and for 1 common "Private Repository" page, or by defining private instances of dcat:DataService . I tend to favor the latter.

Example:

• dcat:Dataset: TU-Delft Disdrometer (get info from excell file submitted to KDP)

  • dcat:accessService = TU-Delft Project Drive

• dcat:DataService: TU-Delft Project Drive

  • contact
  • access: public, private

Although this will be distorting the author's intended meaning behind dcat:DataService definition. But hacking its allowed, might not be pretty but if it works, it works

[andrecastro0o]

As a side note also check more in detail DATS - datatagsuite @andrecastro0o

[andrecastro0o]

current implementation described in Help:Data_Catalog_Schema#Category:DataService using the dcterms:accessRights property, with possible value being either "public" or "private"