dlr-ve-esy / charging-ontology

A Charging Infrastructure Ontology
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

CQ 1.3: A charging point is compatible with some plugs #2

Open areleu opened 5 months ago

areleu commented 5 months ago

Plugs and sockets

Summary

We need an implementation that deals with https://github.com/OpenEnergyPlatform/ontology/issues/1597

The solution is not trivial since connections are a weird construct. I really think there is a higher order concept that should be defined in an ontology such as the CCO but for matter of scope we will constraint this application to electrical plugs.

Current status

What we have so far is the general structure: connector with its sub-classes plug and socket which I consider are fiat object parts of some other component/device.

For definitions sources I have:

Both are pretty restrictive in their terms of usage, I am not taking their definitions as they are but I would like to offer some mappings where I consider suitable, is inspiration considered fair use?

Then there is the connection types. My idea is to implement something like connection pattern that should be the quality inherent to the particular objects. This pattern then should be associated to its respective specification using the appropriate is about relation. After that is where it gets weird, should I then implement a bunch of specification instances that can then be used as range of different connection pattern classes? or is it better to associate the connection patterns per device instance? (Reminder: link this issue in CCO when the repository is open)

areleu commented 4 months ago

Question: "Is it necessary to double the connection pattern(qualities) for male and female, or can the pattern refer to both types of connectors?"

areleu commented 4 months ago

We need to figure out how to addres the association between charging modes and connectors, if that is ever necessary.

areleu commented 4 months ago

How does one express "compatibility" in BFO?

areleu commented 2 months ago

Try to articulate how our model can deal with https://github.com/openchargemap/ocm-system/issues/131