...
Notes
- Collection and Curation ProcessProc
- why planned process? might not be helpful
- Looks okay otherwise
- Can we restrict the use of the process to particular roles? We might not be able to name the roles
- Will add a note that there might be class restrictions added regarding roles – the roles that inhere in a Collection Process must come from a particular set, for example. Might we be role restrictionsable to add a class restriction that the bearer of the role that inheres in a Collection Process must be from a particular set – a person, an organization.
- Positions
- As a process, a relationship
- A pattern: person bearer_of role realized_in position realizes role inheres_in organization. The person has a role in the position. The organization has a role in the organizationposition.
- But the position held by someone else? The position is "filled". Position as described above is a performance. What are they performing? Is it like the performance of a symphony? An elected office? Formal/informal? Like "goalie" in soccer? There may be two uses of the term position. One is as a relationship. The other is as an entity that can be filled and exists whether or not it is filled. Such an entity can be counted – "how many faculty positions does the department have" "how many positions are filled?"