LEAP person

Belongs to LEAP 2.0 > classes

Working definition
Information about the portfolio holder, or referring to another individual person of relevance to the portfolio holder.

Explanation
Other people didn't really get a look-in in IMS LIP. Yet they are clearly very important in a portfolio context. The most we can represent about a person is some information about them. But if there is a good source of information about that person, perhaps through which contact details can be obtained, then a reference to that source is all that is needed. If there is no known authoritative source, a LEAP person structure can hold identifying details. Primary identifying details will be what identifies that person to the portfolio holder; secondary details will be what enables that person to be identified by others, which should be subject to the person's permission.

Examples
You or me.

Alternative terms, with nuances of meaning

 * Person
 * Individual
 * Identity
 * Persona

What it is not
A LEAP person is not normally an authoritative primary source of information about that person.

Predicates
See the notes on LEAP triples for an explanation of what forms of triples there are, and how they are represented here.
 * "Direct" predicates are those where this class is in the domain of the predicate (but its superclass is not).
 * "Inverse" predicates, if given for reference, are those where the class is in the range, but not the domain, of the predicate.
 * "=" means the predicate expects a literal object: the type of literal may be specified here.
 * "&rarr;" means the predicate expects an object URL referring to an instance of the given class(es).
 * "&larr;" is used for inverse predicates, and means that triples may exist with instances of the given class(es) as subject and this class as object.

Inherited
from agent; in particular
 * certifies &rarr; LEAP item
 * manages &rarr; LEAP activity (not LEAP agent: that is a different relationship)
 * owns &rarr; LEAP resource; or more generally the LEAP item record
 * publishes &rarr; LEAP item
 * related &rarr; any URI identifying the person; any URL giving more information about them; any LEAP pattern related to them
 * sponsors &rarr; LEAP activity

Direct

 * attends &rarr; LEAP meeting
 * known as = the name of that person as known to the portfolio holder
 * more to come related to LEAP2A personal data

Inverse

 * attended by &larr; LEAP meeting

Personal Information
An Atom version of this is being tested by PIOP partners for LEAP2A. See LEAP2A personal data

Existing places information held
See LEAP2A person and LEAP2A literals

Any more? Add them like this
(and if you can, add a link to more information about how information can be obtained from it, and in what format)

Issues
Contact details are a tricky issue. Discuss under the discussion tab

See also, a separate discussion of LEAP person identity.

A note can go here of any other issues that are not represented above, which can then be discussed on the list or under the discussion tab.