Annotation properties for Elucidation/Definition

[GoogleCodeExporter]

Do we need another property for elucidations? Some options:

1) Add a new object property
2) Rename definition -> Elucidation
3) Add elucidations as editor notes and don't have definitions for such terms.
....

Original issue reported on code.google.com by alanruttenberg@gmail.com on 22 May 2012 at 4:26

[GoogleCodeExporter]

I would suggest option #1. 
An editor should be able go give an elucidation when no adequate NL def is 
available or multiple (possibly) inconsistent definitions exist that the editor 
does not want to chose between. An elucidation can also serve to point to a 
larger theory surrounding the term that currently is not expressed in the OWL 
or FOL rendering. This also serves as an important warning for users of the 
term.

Original comment by albertgo...@gmail.com on 22 May 2012 at 1:47

[GoogleCodeExporter]

option #1 would be adding a new annotation (not object) property right?

Could we provide a definition for elucidation and definition that clearly state 
of they are distinct, and then decide how they relate to each other?

Current definition for "definition" reads "The official definition, explaining 
the meaning of a class or property. Shall be Aristotelian, formalized and 
normalized. Can be augmented with colloquial definitions."

A definition for elucidation I found on wiktionary is "A making clear; the act 
of elucidating or that which elucidates, as an explanation, an exposition, an 
illustration; as, one example may serve for further elucidation of the subject."

Original comment by mcour...@gmail.com on 22 May 2012 at 3:54

[GoogleCodeExporter]

I'd be happy with a new annotation property 

Original comment by dosu...@gmail.com on 22 May 2012 at 4:03

[GoogleCodeExporter]

Original comment by alanruttenberg@gmail.com on 23 May 2012 at 4:11

• Changed state: Accepted

[GoogleCodeExporter]

I vote for #1.   The definition annotation property already has a good, and a 
precise, "definition".  Changing it to elucidation would unnecessarily demote 
numerous, perfectly good definitions to "elucidation" status, which I don't 
even know why one would propose it.

Original comment by hoga...@gmail.com on 23 May 2012 at 5:54

[GoogleCodeExporter]

Resolved that we will do this, with the definition (or elucidation ;-) of 
elucidation taken from the bfo2 reference.

Original comment by alanruttenberg@gmail.com on 25 May 2012 at 5:36

• Changed state: Started

[GoogleCodeExporter]

Original comment by alanruttenberg@gmail.com on 15 Jun 2012 at 4:53

• Changed state: Done

[GoogleCodeExporter]

Current elucidation for IAO_0000600:elucidation reads more like an example of 
usage than a real definition: "Primitive terms in a highest-level ontology such 
as BFO are terms which are so basic to our understanding of reality that there 
is no way of defining them in a non-circular fashion. For these, therefore, we 
can provide only elucidations, supplemented by examples and by axioms"
This doesn't indicate what an elucidation is, nor how it relates to definition 
(if it does; is definition a subtype of elucidation?)
Definition is currently defined as "The official definition, explaining the 
meaning of a class or property. Shall be Aristotelian, formalized and 
normalized. Can be augmented with colloquial definitions."

Could we work on this? 

Original comment by mcour...@gmail.com on 18 Jun 2012 at 4:17

• Changed state: Started