One of the Leap2A item types
<rdf:type rdf:resource="leap2:affiliation" /> or <rdf:type rdf:resource="http://terms.leapspecs.org/affiliation" />
|Definition:||An affiliation describes the association with some specific organization, where the holder holds any role within that organization or any enduring relationship with it. The concept as in Leap2A includes relationships like membership, that are normally considered to be affiliations, but can extend beyond that to any state-like relationship that is not being exercised as an ongoing activity.|
|Can degrade to:
/ inherits from:
(Example based on one supplied by PebblePad.) New elements record the id for the portfolio holder's affiliation. Each affiliation must be supported by exactly one Leap2A/organization. If the role changes within an affiliation, a number of shorter affiliation items, each with a different given role, may occur as parts of a longer overall affiliation item where the role is not given. In this case, the shorter affiliation items may be regarded as inheriting the organization details from the longer overall one. People are associated with organizations over considerable periods of time, and within that time they may have various roles, each of which may last for a particular time. For instance, one may start as a student member, and progress to being an associate member, fellow, etc.
The history of this concept in e-portfolio use goes back at least to IMS LIP, which has an "affiliation" element that in its own way provides for this (information model; binding; best practice guide).