Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add void:rootResource as property of dcat:Resource ? #292

Closed
dr-shorthair opened this issue Jun 28, 2018 · 9 comments

Comments

5 participants
@dr-shorthair
Copy link
Contributor

commented Jun 28, 2018

Comment received by email from Nuno Friere suggests that void:rootResource might be a useful property to a dataset 'manifest'.

@dr-shorthair dr-shorthair added this to To do in DCAT revision via automation Jul 9, 2018

@jakubklimek

This comment has been minimized.

Copy link
Contributor

commented Jul 11, 2018

Actually, this is not accurately specified.
void:rootResource (see specification)

  1. only applies to void:Datasets, which are RDF datasets, not any datasets, which correspond (and this should be discussed as well, although we use it this way in Czechia) to RDF dcat:Distributions of a dcat:Dataset.
  2. the object of the property should be an RDF resource belonging to the dataset. A manifest would be metadata about a dataset, not belonging to the dataset.

Therefore I would suggest not using this property for attaching a manifest.

A related question - how would a manifest look like? Is there a specification for such manifests? If not, I would suggest trying to cover whatever would be in the manifest directly in DCAT.

@nfreire

This comment has been minimized.

Copy link

commented Jan 26, 2019

(Note: I do not have a complete knowledge of DCAT. I'm participating in the discussion from a DCAT user point of view, thus presenting my use cases for DCAT)

My original request for void:rootResource originated from a use case of Europeana, and was indeed having RDF datasets in mind. I'm working on a crawler for aggregating linked data into Europeana, and I wanted to use DCAT as the way to allow data providers to provide all technical details for allowing the crawler to start the process of crawling all the dataset's RDF resources.

But actually, the use case of the 'manifest' is also relevant to for Europeana. It can also allow the RDF crawling, and may fulfill also another use case where data providers specify their dataset to Europeana using a Sitemap.

@agbeltran

This comment has been minimized.

Copy link
Member

commented Jan 30, 2019

Including here a link to the discussion in the comments list: https://lists.w3.org/Archives/Public/public-dxwg-comments/2019Jan/0007.html

Also, in this DCAT revision we've added a way to represent loosely structured catalogues, where a dataset is form by a set of files. In this case, we are using dct:relation to connect the dataset with the different files that compose it (see the property description: https://w3c.github.io/dxwg/dcat/#Property:resource_relation, see the examples at: https://w3c.github.io/dxwg/dcat/#bag-of-files, and see discussion about this in the issue #253)

We also have an open issue about representing the multiple files that are part of a dcat:Distribution (see #482).

So, do you agree that by considering those two points above, we will provide a way to navigate all the files corresponding to a distribution and to a dataset?

@nfreire

This comment has been minimized.

Copy link

commented Jan 30, 2019

I agree.
Using that solution along with the use of dct:conformsTo and ideally, along with http://usefulinc.com/ns/doap#implements, should provide the full technical details a robot would need for the Europeana use cases.

Question: Is doap:implements included in DCAT (or its use under discussion)?

@agbeltran

This comment has been minimized.

Copy link
Member

commented Jan 30, 2019

doap:implements associates Projects to the Specifications the project implements. Where would this fit in the use case? Europeana as the project that implements DCAT?

Currently, we associate dcat:Resources associated with dct:Standards via dct:conformsTo (see https://w3c.github.io/dxwg/dcat/#Property:resource_conformsto)

@nfreire

This comment has been minimized.

Copy link

commented Jan 30, 2019

I believe you're right, Alejandra. i was mixing up standards/semantics in my mind...
Having multiple files in a dcat:Distribution along with the use of dct:conformsTo should fulfill the Europeana use cases.

(I'll discuss it with my colleagues an give further feedback, if something relevant is identified)

@davebrowning

This comment has been minimized.

Copy link
Contributor

commented Mar 14, 2019

Is this issue now closable?

@nfreire

This comment has been minimized.

Copy link

commented Mar 14, 2019

From my point of view, yes, the ticket may be closed, since the requirement is being addressed in the other tickets.

@davebrowning

This comment has been minimized.

Copy link
Contributor

commented Mar 15, 2019

Thanks, @nfreire

DCAT revision automation moved this from To do to Done Mar 15, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.