designated action (1) It is critical that these classes not be mistaken for processes themselves. If you intend to build logical axioms within the BFO framework it will be necessary to create realtions between instances of 'designated actions' and 'processes.' We leave this mapping undone in order to accomodate various non-BFO process value sets. (2) We believe it is important to separate 'processes' from their inputs, outputs, or participants in action designatation. For example: instead of a 'designated process of blood extraction' we would advocate for creation of a designated action such as 'designated process of extraction' so that this class may also be used with different objects, like teeth. This is of course, application dependent. This is only a guide. (3) It is our intent that all instances of 'designated actions' that are related to instances of 'permission directive' be processes or events in which deontic roles of some kind may be realized. Stated another way, a 'designated action' should be an action that is not allowable unless a process makes it so: for example, a 'process of informed consent' with a subprocess 'act of permitting.' A 'Directive Information Content Entity' that designates a process as permissable. Cooper Stansbury, Elizabeth Umberfield, Kathleen Ford, Marcy Harris Designative Information Content Entity