Working Group meeting

Date: 05/10/2021
Participants: Cecille Guasch, Giorgia Lodi, Natalie Muric, Giovanni Paolo Sellitto
Model editor: Eugeniu Costetchi
Note editor: Andreea Pasăre

Agenda:

  • presented social role by hoekstra

  • and a student example

  • if we adopt this model, check instance of a student model

  • presented loted2-original → roles

Discussion:

Social Role by Hoekstra was presented during this session. This model is similar to what we had in v2.0.1.

The difference is that Agent Role Reification has owl:Thing → Context.
It was discussed that it might be better to have roles as controlled vocabulary as well.
At the moment, we don’t have roles as a controlled vocabulary, we have them as classes.

A person does not stop to be a person when it becomes a student.

A person is rigid, but a role is not rigid.

In the data we have the same person repeated many times according to the role.

This is not the correct approach and should be fixed.

Proposing to try a student example as a buyer for “signing of the contract” situation.

We have to take the Buyer, the Agent, the relationship between them and the Lot.

wfsMpvywYdjAwAAAABJRU5ErkJggg==

Buyer example diagram:

If Buyer is not in a procedure, he is not a Buyer anymore, but an Organisation.

If we adopt a hierarchy of roles it becomes useful to constraint what subclasses from the hierarchy can adopt that role.

4ftm1sWUJWY6YAAAAASUVORK5CYII=
Q1w0AACCAjAAAAILICAAAIIiMAAAAgsgIAAAgiIwAAACCyAgAACCIjAAAAILICAAAIIiMAAAAgv4ftDLNImJandcAAAAASUVORK5CYII=

Buyer example 1 diagram:

There’s an association between organisation and procurement in the example Buyer.

Discussed the Turtle example from the last meeting. The role can be instantiated only once.

Should draw the diagram for this example offline and come back with an analysis/comparison for the next time.

Note: take care of the cardinalities between Agent - Roles - Procedure - Lot. (AgentRole Reification)