Roles are AIAO roles
Status: proposed
A role states what the standard requires of an agent’s relation to an activity: its scope and the conditions it must meet. That is what AIAO means by aiao:Role, a control that governs an aiao:AgentActivityRelation. So every NWSS role is an aiao:Role. It is also a skos:Concept in one roles scheme, so that instruments can offer it and the site can list it.
An agent holds a role through an aiao:AgentActivityRelation, with aiao:hasAgent, aiao:hasActivity and aiao:isGovernedBy the role. A project design names its parties the same way. A record’s nwss:observerRole is a shortcut for the role governing the observer’s relation to the recording activity. A role’s requirements are stated on the role, and the workflow test that enforces each one is linked from it. For example, a collector must be enrolled at the facility it delivers to, and an evaluator never evaluates a round they collected.
Each role exists once. The collector and the facility operator are not repeated as observer roles; the observer roles are a collection within the one scheme. Relationships to a place (occupant, owner, responsible party) and classifications of an agent (collector kind) are not roles. They stay concepts, carried on the relation.
This replaces the AgentRole and observer-role concepts that NWSS took from ncgs.