zhengj2007 / bfo-trunk

0 stars 0 forks source link

participates in at some time URI re-used with different meaning #162

Closed zhengj2007 closed 9 years ago

zhengj2007 commented 9 years ago

From cmung...@gmail.com on April 23, 2013 15:09:05

BFO_0000056 was re-used in BFO2 for "participates in at some time". This URI was previously used for atemporal participates_in.

I request that BFO2 mints a new URI for this as the meaning may be different depending on how atemporal relations are ultimately interpreted.

Original issue: http://code.google.com/p/bfo/issues/detail?id=163

zhengj2007 commented 9 years ago

From alanruttenberg@gmail.com on April 23, 2013 12:12:58

If we changed the temporalization we would mint a new id anyways. So I think should only be evaluated based on the current temporalization.

zhengj2007 commented 9 years ago

From cmung...@gmail.com on April 23, 2013 12:20:31

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.

zhengj2007 commented 9 years ago

From alanruttenberg@gmail.com on April 23, 2013 13:19:49

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.

zhengj2007 commented 9 years ago

From alanruttenberg@gmail.com on June 26, 2013 13:03:40

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.

Status: WontFix