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

Linked Data Subject pages: distributions or data services or non-of-both? #1390

Open
bertvannuffelen opened this issue Jul 12, 2021 · 4 comments
Labels
dcat:DataService dcat:Distribution dcat feedback Issues stemming from external feedback to the WG future-work issue deferred to the next standardization round

Comments

@bertvannuffelen
Copy link

I have the following discussion on which I have no clue about how to categorize them.

Online consultation of data is that a distribution, a data service or non-of-both?

Consider Linked Data subject pages:

if one dereferences a URI then a document URI is returned. This html document can be nicely styled, having the data organized in such a way that I as a reader find it pleasant to read it.

The collection of all subjectpages for URIs in a dataset is that a distribution of a dataset? Or is it a data service because it renders the data in a pleasant reading way?

When the subject page shows also the location on a nice map, and offers additional further exploration links based on the location and the associated properties, can it then still be considered a distribution?

As we consider Linked Data Does if the subject page shows the labels of the codes and organisations by dereferencing the URIs ,
can it then still be considered a distribution?

If Linked Data Subject pages is categorized as a distribution, is then a map viewer also a distribution?

Are Linked Data Subject page data services because they use HTTP as protocol? Thus is using http as protocol sufficient to categorize it as a dataservice?

This discussion is probably related to many issues such as #1242, but as it is a concrete case I have registered it separately.

@andrea-perego andrea-perego added the feedback Issues stemming from external feedback to the WG label Jul 16, 2021
@andrea-perego andrea-perego added this to the DCAT3 3PWD milestone Jul 16, 2021
@andrea-perego
Copy link
Contributor

@bertvannuffelen , you're touching a number of different aspects which, although interrelated, may need to be addressed separately.

It would be beneficial to the discussion if you could break down the issues you're raising, and complement your comments with (ideally, real-world) examples.

@bertvannuffelen
Copy link
Author

A more concrete example: the collection of all html pages of DBPedia is that a distribution of the DBpedia dataset? E.g. https://dbpedia.org/page/Belgium

To my knowledge, this collection of all html pages is not downloadable, only online consultable. (It is not listed on https://www.dbpedia.org/resources/)

Observe that the html rendering has been done some "data interpretation": namely the flag is shown next to the abstract. The same information, not interpreted, can be found in the data below.

If that is not a distribution, is the html rendering then a dataservice? Namely a nice html rendering service of the data available at http://dbpedia.org/data/Belgium.ttl

@smrgeoinfo
Copy link
Contributor

If all of DBPedia were accessible as a single download consisting of a set of individually identifiable html documents, that would constitute a kind of distribution. But it doesn't exist. A dataset can exist independent of any distribution.
http://dbpedia.org/sparql is a data service that allows one to extract data from DBPedia.

An html (or ttl) page that renders a single DBPedia record could be considered a dataset whose subject is the subject of that DBPedia record, and its distribution would be a data download.

@davebrowning
Copy link
Contributor

Project/Milestone modified.

Explanation: As DCAT v3 moves through review and hopefully ratification, we want to make sure that open issues and feedback that have yet to be completely addressed are properly recorded and tagged/assigned in github to both clarify their status and to help review and prioritise as a source of improvements and new requirements in future DCAT versions

@davebrowning davebrowning added the future-work issue deferred to the next standardization round label Feb 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dcat:DataService dcat:Distribution dcat feedback Issues stemming from external feedback to the WG future-work issue deferred to the next standardization round
Projects
None yet
Development

No branches or pull requests

4 participants