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

daQ - Ontology for Dataset Quality Information #16

Closed
Ludee opened this issue Aug 13, 2018 · 8 comments
Closed

daQ - Ontology for Dataset Quality Information #16

Ludee opened this issue Aug 13, 2018 · 8 comments
Assignees
Labels
enhancement New feature or request external ontology external ontologies that could be included oeo dev meeting Discuss issue at oeo dev meeting specification_sheet Lastenheft

Comments

@Ludee
Copy link
Member

Ludee commented Aug 13, 2018

I was made aware of the existing daQ ontology.
It aims at describing quality criteria for datasets and sounds interesting.
There are Sldies and a publication.

This is also highly interesting for the "review process" we are working on OpenEnergyPlatform/data-preprocessing#2

@Ludee Ludee added enhancement New feature or request help wanted labels Aug 13, 2018
@akleinau akleinau added the external ontology external ontologies that could be included label Jan 10, 2020
@akleinau
Copy link
Contributor

link to download rdf or ttl file

  • Classes are: Category, Metric, Dimension, Quality Observation, QualityMeasurement, QualityMeasurementDataset, Quality Graph Statistics
  • does not use bfo

@l-emele
Copy link
Contributor

l-emele commented Aug 19, 2020

Anything important for the next release from this issue? Else I move it to an other milestone.

@akleinau akleinau added the To do Issues that haven't got discussed yet label Aug 31, 2020
@akleinau
Copy link
Contributor

akleinau commented Oct 7, 2020

This sounds useful as we want to describe datasets. But it's not using bfo, which means we have to treat it like the economic ontology of #476: use the ontology as a knowledge source, don't import it.
So:

  1. choose which classes are needed
  2. adapt the definitions to the bfo and our domain
  3. implement

we can choose between doing that through an excel sheet like with #476 or through the normal github process

@github-actions github-actions bot removed the To do Issues that haven't got discussed yet label Oct 7, 2020
@stale stale bot added the stale already discussed issues that haven't got worked on for a while label Oct 21, 2020
@stap-m stap-m added the oeo dev meeting Discuss issue at oeo dev meeting label Oct 27, 2020
@stale stale bot removed the stale already discussed issues that haven't got worked on for a while label Oct 27, 2020
@stap-m
Copy link
Contributor

stap-m commented Oct 27, 2020

@akleinau would you prepare a spreadsheet and preselect classes, so that we can discuss this in the next dev meeting?

@akleinau
Copy link
Contributor

akleinau commented Nov 3, 2020

@akleinau would you prepare a spreadsheet and preselect classes, so that we can discuss this in the next dev meeting?

yes I can do that :)

@akleinau akleinau self-assigned this Nov 6, 2020
@l-emele
Copy link
Contributor

l-emele commented Nov 11, 2020

From OEO Dev meeting: Inlude daQ in our https://github.com/OpenEnergyPlatform/ontology/wiki/Use-of-external-ontologies and then close the issue.

@akleinau
Copy link
Contributor

I described our solution in the wiki and therefore close this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request external ontology external ontologies that could be included oeo dev meeting Discuss issue at oeo dev meeting specification_sheet Lastenheft
Projects
None yet
Development

No branches or pull requests

7 participants