Ontology: Project and Study are falsely classified as Reference

Created on 17 Feb 2020  路  11Comments  路  Source: OpenEnergyPlatform/ontology

Description of the issue

Project and Study are subclasses of Reference right now. A reference can reference to a study or a project, but they themself are more.

Ideas of solution

reclassify as textual entity? Or document? Or just information content entity?

they also need defs.

Workflow checklist

  • [ ] I discussed the issue with someone else than me before working on a solution
  • [ ] I already read the latest version of the workflow for this repository
  • [ ] The goal of this ontology is clear to me

I am aware that

  • [ ] every entry in the ontology should have an annotation
  • [ ] classes should arise from concepts rather than from words
  • [ ] class or property names should follow the UpperCamelCase
[B] restructure [C] definition update oeo-model

Most helpful comment

  • Project: "A process to achieve a specified goal that's unique in the sum of it's conditions like it's goal, time and cost budget and it's organisation." ?

All 11 comments

first question is do we want to define project and study just as the final documents or the whole undertaking/ activity?

notes from the 5th dev meeting:

  • There is the process and an object describing the process at the end. What do we need? We see both as Occurents
  • to avoid ambiguity between the 'study' process and the 'study' report we can call the latter 'study report'
  • We have report imported already as document, therefore study is not needed?
  • study as a synonym for report?
  • Project: "A process to achieve a specified goal that's unique in the sum of it's conditions like it's goal, time and cost budget and it's organisation." ?

I don't think study really is a synonym for report.
Not every report is a study, e.g. a damage report would certainly not be called a study.
I'm not sure if every study is a report though? Then it could become a subclass

Every study report is a report and every report is a document.

Implement project and delete study temporarily.

We should reinclude study and distinguish between study and study report, classify and find proper definitions for both.

I like the def proposal for project from @akleinau.
We could make study a subclass of it, with the specification that the goal of the project investigates something. Study = research project?
study report could be a subclass of report and the relation "study has output some study report"

For the record: the def of report (imported from OBI): a document assembled by an author for the purpose of providing information for the audience. A report is the output of a documenting process and has the objective to be consumed by a specific audience. Topic of the report is on something that has completed. A report is not a single figure. Examples of reports are journal article, patent application, grant progress report, case report (not patient record)

yes sounds good and solves the project/ process vs document problem by implementing both

@stap-m so defs would/could be:

project: "A process to achieve a specified goal that's unique in the sum of it's conditions like it's goal, time and cost budget and it's organisation."
study: "A project with the goal to investigate sth."
study report: "A report that is the output from some study."

ok, I'll implement.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

sfluegel05 picture sfluegel05  路  7Comments

sfluegel05 picture sfluegel05  路  8Comments

fabianneuhaus picture fabianneuhaus  路  4Comments

akleinau picture akleinau  路  8Comments

han-f picture han-f  路  6Comments