adding change #39
adding change #39
Conversation
| A{Person 1} --->|rdf:type| B[BFO_0000001] | ||
| A --->|participates in BFO_0000056| F{Change 1} | ||
|
|
||
| F --->|rdf:type| G[Change ont00000824] |
There was a problem hiding this comment.
Should there not be a more explicit connection between 'change', 'temporal interval' and the actual changes of temperature?
There was a problem hiding this comment.
Such as, something stronger than participation?
| H --->|rdf:type| I[Temporal Interval BFO_0000202] | ||
|
|
||
|
|
||
| A -->|bearer of BFO_0000177| K{Temperature 1} |
There was a problem hiding this comment.
Only one temperature listed as an instance, but there are two measurements.
There was a problem hiding this comment.
Does an individual quality stop existing when its magnitude changes? If yes, then we have very rigid identity conditions for qualities, and I have for example a new height instance every day. But I think we don't have to do that, and we can just say that I have the same height qualities but with new measurements over time. Curious to hear what other people think here. @Finn1928 @johnbeve
|
Some changes: |
| F -->|occupies temporal region BFO_0000199| H{Temporal Interval 1} | ||
| H --->|rdf:type| I[Temporal Interval BFO_0000202] | ||
|
|
||
| A -->|bearer of BFO_0000196| K{Temperature 1} |
There was a problem hiding this comment.
Change this to "Person 1's temperature"
| @@ -0,0 +1,46 @@ | |||
| flowchart TB | |||
| A{Person 1} --->|rdf:type| B[BFO_0000001] | |||
There was a problem hiding this comment.
add name for "entity" class
3 participants
@johnbeve I think having to go through the IBE to add the info for measurements in examples like this shows the need for shortcut properties. This is supposed to be about change but if I want to show two measurements at two times and god forbid add temporal measurement info the graph overblows.