Resolve confusion related to assignment predicates

[rjyounes]

isAssignmentOf and isAssignmentTo cause confusion because you can go in different directions: a person is assigned to a project, or a project is assigned to a person. We've discussed various options but never settled on any.

One proposal: use just one predicate, say, assigns, to both participants in the Assignment. The person is the assignee, the other thing is what's assigned.

But: sometimes there are two people, such as in a supervisor assignment. There could also be causes where neither is a person.

The best idea might be to just rename the predicates for clarity; e.g., hasAssignee vs hasAssigned or assigns.

[rjyounes]

My suggestion above (hasAssignee and hasAssigned) helps in the case of project and person (we wouldn't say the project is the "assignee") but not in the supervisor case. The case of 2 people generally is more difficult.

For supervisor assignment specifically, it goes through a labor agreement so you only need one person, the supervisor, attached to the assignment - the direct report is derived from the agreement.

[rjyounes]

Using a single predicate, assigns, for both objects makes it impossible if both are people (supervisor, guardian, etc.).

Proposal:

• Use hasAssignee for the assignee
  • Note: hasRecipient doesn't work because it's disjoint with hasGiver, but I can assign something to myself, violating disjointness.
• Use hasGiver for the thing that does the assigning
• Keep isAssignmentOf for the thing being assigned

DECISION:

• Change isAssignmentTo to hasAssignee.
• Add scope notes about difficult cases, like 2 people.

[dbsemantic]

@rjyounes I believe the decision here should be switched, where we:

• Keep isAssignmentTo for the thing being assigned (i.e., the project in a project assignment)
• Update isAssignmentOf to hasAssignee, referring to the person assigned to the project in a projectAssignment.

This maintains the semantics already in place in the scope notes, where isAssignmentTo is used for the inanimate item. Every other aspect of the issue remains the same.

[rjyounes]

It seems we still have not made these predicates sufficiently clear. Note your comment:

Update isAssignment_Of_ to hasAssignee, referring to the person assigned to the project in a projectAssignment.

Can you please think through this and come up with some completely unambiguous predicates?