Improve textual definitions and examples of use for some of the directive information entity terms.

• IAO_0000033 directive information entity

  • add editor note: Philly2013 - AR: What differentiates a directive information entity from an information concretization is that it can have concretizations that are either qualities or realizable entities. The concretizations that are realizable entities are created when an individual chooses to take up the direction, i.e. has the intention to (try to) realize it.
  • change status: ready for release

• IAO_0000104 plan specification

  • change textual definition: A directive information entity that, when concretized, is realized in a process in which the bearer tries to achieve the objectives, in part by taking the actions specified.
  • change example of use: To lose weight, go running daily for at least 30 minutes. To isolate plasma from blood, centrifuge tubes at 1100-1300 rpm for 15 minutes.
  • change status: ready for release

• IAO_0000007 action specification

  • change status: ready for release

• IAO_0000064 algorithm

  • change status: ready for release

See OBI Core review notes for discussion: https://docs.google.com/document/d/1J3VjL6pbMY3q6GYZqsqqs4CbgEgIxnivMXcj_qcyznc/edit?usp=sharing

Decisions on OBI/IAO call 2014-03-31. James will implement.

• IAO_0000104 plan specification
  • Revised textual definition: "A directive information entity with action specifications and objective specifications as parts that, when concretized, is realized in a process in which the bearer tries to achieve the objectives by taking the actions specified."
  • add editor note: "A plan specification can have other parts, such as conditional specifications."

Will be closed through commit (following call on April 7th, 2014

Fixed by commit 668. Note that I did not mark "algorithm" as "ready for release" because of the outstanding issue 167. Instead I made a note in that tracker item.