Talk:LEAP predicates

first
Not for pattern, as patterns are not of themselves intentional. Though patterns may have a most important part?

Identity details
People have names and/or IDs with organizations they are involved with. There needs to be some way of recording this. Maybe we need an identity class, which doesn't have content as such (like a personality) but which does have
 * the individual identified (defaults to the portfolio holder)
 * a related personality
 * the organization identified with
 * the name used
 * any number etc. used
 * the intent of the relationship

required by
Perhaps like iCalendar resources, have a predicate sub to "supported_by" which means requires. Inverse would be sub to "supports", required by.

reasons for
looks like a good idea might be
 * is reason for
 * sub-relation of is supported by
 * has reason
 * sub-relation of supports