search

zhengj2007 / bfo-export

Automatically exported from code.google.com/p/bfo
0 stars 0 forks source link

Obsolete terms - documentation and owl file #55

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
During the bfo-owl working group TC on June 15th, it was proposed to document 
terms that would become obsolete in BFO2. 

Proposal is to have this be an annex of the BFO2 reference document which would 
be automatically translated into an OWL file by the lisp script. This 
obsolete.owl file is to be distributed independently of the main bfo.owl 
(rationale is that it would prevent label confusion for users when an obsoleted 
term has a label similar to a new one, as well as past experience in which 
users prefer to not have obsolete terms included when file released)
Obsolete terms should include annotation properties (replaced by, obsolescence 
reason) and possibly pointer to extra documentation as to why such a change was 
made.

Original issue reported on code.google.com by mcour...@gmail.com on 15 Jun 2012 at 10:05