jseguraf
commented
4 years ago Date: 20/02/2020
The discussion started with a context explanation of meetings that took place during this week in Brussels regarding the Core Vocabularies.
One of the points of the discussion was that the Corge Agent Vocabulary (CAGV) does not exist at the moment, ePO cannot reuse classes from a Vocabulary that does not exist. Here, the agreement was to move the classes from CAGV to ePO, and when the CAGV will be mature the classes will be moved again to the CAGV.
Concerning this movement, the questions as to whether the class Agent should be renamed this name is used in several classes (e.g. FOAF, ePO, CAGV, etc.). The WG agreed that that the term Agent was needed, however it was decided all those properties and classes that are not needed and not used explicitly in ePO should be removed.
The WG started with an analysis of those classes and properties that came from other vocabularies in order to see whether they are used or not in ePO. In order to start this analysis, the WG took as an example of the Organization class. In this case, the only class needed is the org:Organization class and therefore there is no need to mention that it is an equivalent of the class foaf:Organization. Subclasses of the org:Organization were analysed. In the case of the org:OrganizationalCollaboration, the WG decided when this class should be used:
- For Joint Procurement: several Buyers get together and buy together.
- For Consortia that are not legal entities, e.g. two companies that have agreed to work together but have not registered a new Legal Entity. This is often the case for tenderers, however, under certain national legislations, this collaboration has to be formalised after award, in which case the new entity will be treated as an organization (an Economic Operator) and not as a collaboration of organizations.
In addition to this decision, the following comment was added to the class Economic Operator:
- The org:OrganizationalCollaboration class is used for Consortia, see the Agent diagram to understand that this collaboration is a group of other Agents or type Organization or Persons.
Date: 11/02/2020
Everis explained that SEMIC is still evolving the Core Agent Vocabulary (CAGV), which is the one reused in ePO, and they discovered some findings that need to be discussed with the WG. Everis presented to the WG the working version of the CAGV. The first point discussed in the meeting during the analysis of the CAGV that everis presented was related to the class “Contact Point”. The WG discussed the difference between the class Contact Point and the class Channel. The difference explained was that the Contact Point is just the single contact point of an Organization, Person or System, while the Channel is the element where the service is performed. Analyzing the Contact Point term defined in eForms, the WG arrived at the conclusion that the Contact Point in eForms was thought in case that for whatever reason somebody needs to contact somebody else.
The second point discussed was about how to know if the Organization is public or not. Everis proposed to consider the Public Organization as a role. The WG said that Public Organization is not a role because it is a legal status. It is needed a mix between a Public Organisation and Organisation, and to specify whether the organization is public or not. For that purpose was created a class named "Public Organisation" which inherits from Formal Organization. The Agent package will be updated according to the latest version of the CAGV. Moreover, OP proposed to have the Contact Point as Role in order to have all the granularity.
The third and last point discussed in the context of the Agent discussion was about how and whether ePO should use the Electronic Means of Communication class. According to the discussion, the Electronic Means of Communication class should be renamed as Channel like in the CPSV-AP. In addition, the Contact Point will be also linked to Channel.