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

check domain of has energy participant #1534

Open
5 tasks
stap-m opened this issue May 5, 2023 · 11 comments
Open
5 tasks

check domain of has energy participant #1534

stap-m opened this issue May 5, 2023 · 11 comments
Assignees
Labels
[B] restructure Restructuring existing parts of the ontology

Comments

@stap-m
Copy link
Contributor

stap-m commented May 5, 2023

Description of the issue

On a tangential thread. I think it makes little sense that artificial objects have inputs and outputs. I these are properties of processes, this is expressed explicitely in the definition of has input 1 I am searching the issue where the decision is explained but I can't find it. I think this can lead to incongruences down the road and that is cleaner to have I/O exclusively in processes.

Originally posted by @areleu in #737 (comment)

Agreed. ROs has participant and subrelations are reserved for processes. Yet, we opened OEOs has energy participant to artificial objects. This is confusing and proper documentation is missing. I'll open a separate issue.

Originally posted by @stap-m in #737 (comment)

Ideas of solution

I see the following options:

  1. Document that the domain of has energy participant is intentionally extended to artificial object and explain why, despite the common restriction of has participant and subrelationd to processes only.
  2. Create separate relations for the involvement of energy for processes and artificial objects. This would imply some restructuring of axioms.
  3. Rename the relation has energy participant such that it won't be confused with has participant.

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 a definition
  • classes should arise from concepts rather than from words

Footnotes

  1. p has input c iff: p is a process, c is a material entity, c is a participant in p, c is present at the start of p, and the state of c is modified during p.

@stap-m stap-m added [B] restructure Restructuring existing parts of the ontology To do Issues that haven't got discussed yet labels May 5, 2023
@l-emele
Copy link
Contributor

l-emele commented May 8, 2023

We explicitely implemented has energy participant (and its subproperties) because we wanted to express the relation between artificial objects and energies. Before that we used e.g. produces but we wanted to replace that.

In #994 we were talking about introducing a special object property to relate artificial objects and energy:

As the produces relation is so often used wrongly, we might think about introducing a very obvious relation for this case. Something like has energy output as subproperty of has physical output. Likewise has energy input as subproperty of has physical input.

And also:

The relation between artificial objects and processes on one hand and energies on the other hand is a core concept of the domain and thus we should have a simple and easily understandable axiom for that. Therefore, we propose the following solution: Introduce a new top-property has energy participant and make has energy input and has energy output subproperties of this new property instead of has physical input and has physical output.

If we cannot axiomatise that a power plant produces electrical energy, then we are abstracting too much from the need of the domain!

@stap-m
Copy link
Contributor Author

stap-m commented May 11, 2023

If we cannot axiomatise that a power plant produces electrical energy, then we are abstracting too much from the need of the domain!

Ok, I see. Does it have to be necessarily the same relation for processes and artificial objects?

I added a third option to the ideas of solution above to avoid the described confusion. Can you comment on them @l-emele @areleu please?

@l-emele
Copy link
Contributor

l-emele commented May 11, 2023

Does it have to be necessarily the same relation for processes and artificial objects?

No, it does not. I would be fine with having distinct object properties for:

  1. Relations from energy to artificial objects.
  2. Relations from energy to processes. These would then be subproperties of has participant, has input and has output.

I added a third option to the ideas of solution above to avoid the described confusion.

I agree that the labels add confusion because one thinks that has energy participant and so on are subproperties of has participant and so on. So we definitely should find better labels.

@github-actions github-actions bot removed the To do Issues that haven't got discussed yet label May 11, 2023
@l-emele l-emele added this to the oeo-release-1.15.0 milestone May 12, 2023
@stap-m
Copy link
Contributor Author

stap-m commented May 19, 2023

  1. Relations from energy to artificial objects.

Any ideas for a lable?
I took produces as inspiration for a proposal:

  • replace has energy input for artificial objects:
    • a some relation 1 b, if some process p that occurs_in a has energy input b, where a is an artificial object and b is a material entity.
    • Or more "human understandable": A relation between an artificial object a and a material entity b, where there is a process p that occurs in a and that has energy input b.
  • replace has energy output for artificial objects:
    • a some relation 2 b, if some process p that occurs_in a has energy output b, where a is an artificial object and b is a material entity. (sould also be simplified as above)
  1. Relations from energy to processes. These would then be subproperties of has participant, has input and has output.

Agreed.

@stap-m
Copy link
Contributor Author

stap-m commented May 30, 2023

Any comment on my proposal @l-emele @areleu ?

@l-emele
Copy link
Contributor

l-emele commented May 30, 2023

I am fine with the human understandable definition proposal. However, I still have no idea about labels if we want to avoid the terms input and output.

@stap-m
Copy link
Contributor Author

stap-m commented Jun 6, 2023

produces energy and consumes energy?!
Both get domain artificial object and range energy

@l-emele
Copy link
Contributor

l-emele commented Jun 7, 2023

I am not super happy the proposed labels produces energy and consumes energy because for some artificial objects the axioms per se would look a bit strange, e.g. 'power line' 'produces energy' some 'electrical energy'. But as I do not have better proposals either, I am okay with using these labels.

@stap-m
Copy link
Contributor Author

stap-m commented Jun 7, 2023

Maybe supplies energy instead?

@stap-m
Copy link
Contributor Author

stap-m commented Jun 22, 2023

For power line etc. we should probably use the has sink/has source relations instead .

@stale stale bot added the stale already discussed issues that haven't got worked on for a while label Sep 16, 2023
@stale stale bot removed the stale already discussed issues that haven't got worked on for a while label Nov 28, 2023
@l-emele
Copy link
Contributor

l-emele commented Jun 27, 2024

I just read this stale issue.,

For power line etc. we should probably use the has sink/has source relations instead .

The object properties has sink/has source are meant to axiomatise the relations between a supply grid and a grid node. Something like 'electricity grid' 'has sink' some 'transformer station'. That is a different relation than power line supplies some electrical energy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[B] restructure Restructuring existing parts of the ontology
Projects
None yet
Development

No branches or pull requests

6 participants