Closed GoogleCodeExporter closed 9 years ago
If we changed the temporalization we would mint a new id anyways. So I think
should only be evaluated based on the current temporalization.
Original comment by alanruttenberg@gmail.com
on 23 Apr 2013 at 7:12
I'm not sure I understand.
Basically I would like to keep using BFO_0000056 for "participates in"
(atemporal). This is problematic at the moment. I don't think it would cause
too much churn to use a different URI for the temporalized form - I think only
hdot uses BFO2.
However, if BFO2 really wants to claim BFO_0000056 I will mint a RO ID for the
atemporal one.
Original comment by cmung...@gmail.com
on 23 Apr 2013 at 7:20
To clarify: We generally commit to create new ids when the meaning changes. If
we used a different temporalization scheme then the meaning would change.
Therefore there isn't a possibility of the meaning shifting under your feet.
If one of us has to change ids, it is less churn to change BFO 2.
I think it appropriate, however, to offer at least a plausibility argument
about why that semantics isn't consistent with the atemporal version.
Original comment by alanruttenberg@gmail.com
on 23 Apr 2013 at 8:19
As Jie has verified that RO has already redefined these relations with RO ids,
We will keep this IRI in BFO.
(Alan)It is a shame to have this divergence which has no clear benefit.
Original comment by alanruttenberg@gmail.com
on 26 Jun 2013 at 8:03
Original issue reported on code.google.com by
cmung...@gmail.com
on 23 Apr 2013 at 7:09