Issue 17 in bfo: Preferred label policy

1 view
Skip to first unread message

b...@googlecode.com

unread,
Jan 13, 2012, 2:08:23 PM1/13/12
to bfo-d...@googlegroups.com
Status: Accepted
Owner: alanrut...@gmail.com
Labels: Type-Defect Priority-Medium

New issue 17 by alanrut...@gmail.com: Preferred label policy
http://code.google.com/p/bfo/issues/detail?id=17

See discussion in

http://groups.google.com/group/bfo-owl-devel/browse_thread/thread/9527351b8a7e2d58/0b7617e1221c9a66

Proposal: The principle is that when reading a r b, we get an english
sentence, which is what motivates the verb "is". Include alternative
terms, with the verb, and without verb but with underscores instead of
spaces.


b...@googlecode.com

unread,
Jan 13, 2012, 2:20:36 PM1/13/12
to bfo-d...@googlegroups.com
Updates:
Labels: -Type-Defect Type-BFO2-design

Comment #1 on issue 17 by alanrut...@gmail.com: Preferred label policy
http://code.google.com/p/bfo/issues/detail?id=17

(No comment was entered for this change.)

b...@googlecode.com

unread,
Apr 29, 2012, 5:19:23 AM4/29/12
to bfo-d...@googlegroups.com
Updates:
Status: Started

Comment #2 on issue 17 by janna.ha...@gmail.com: Preferred label policy
http://code.google.com/p/bfo/issues/detail?id=17

This is now resolved, using the label form that includes the verb as the
preferred label, in the latest working group version of BFO 2 in OWL.

Is there any further action needed on this tracker?

b...@googlecode.com

unread,
Apr 29, 2012, 6:11:06 PM4/29/12
to bfo-d...@googlegroups.com

Comment #3 on issue 17 by alanrut...@gmail.com: Preferred label policy
http://code.google.com/p/bfo/issues/detail?id=17

Resolution is something that happens when the group makes a decision, not
when an individual edits a particular version of a document. As much as I
like the proposal and this way of handling it, having proposed it, a review
of the email trail shows there is not yet consensus about the matter. I
suggest the issue be brought up at our upcoming meeting or subsequent one.

It is also misleading to suggest that there is a latest working group
version of BFO2 in OWL. That is another unresolved issue, and the hope is
that at our upcoming call we can work towards remedying that.

Reply all
Reply to author
Forward
0 new messages