Working Group meeting

Date: 10/10/2024  
Participants: Eugen Costetchi, Achilles Dougalis, Ioannis Fountoukidis, Grzegorz Kostkowski, Natalie Muric, Cristian Vasquez
Model editor:  Achilles Dougalis
Note editor: Eugen Costetchi, Grzegorz Kostkowski

Agenda

  • Discuss about Enterprise Architect Modifications

    • Notes

    • Schedule

    • Explain the GIT branches in epo-conceptual-model (for the month of Oct), any changes from the WG will have to be done in the sandbox and then merged into the dev, after the 4.2.0 release

  • Clean up collaboration notebook

  • Clarify where to post the agenda for the WGM

    • The channel posts do not seem to work well

Discussions

  • It was decided that the agenda for the WGM will be still posted in the channel. In addition, it can also be sent to participants by email.

  • The way of working in GIT branches in the repository hosting CM file was recapped.

    • In one branch, 4.2.0 work will be done

    • In another branch, the other work such as mapping issues, eEvaluation and Preaward can happen in parallel.

    • For EA files, the development is like a trunk-based approach.

    • The possibility of introducing another auxiliary branch to facilitate parallel work was discussed.

    • It has been agreed that work done for other modules will need to be copied to a version on the develop branch.

  • A proposal of EA modifications was presented.

    • The presentation was organized in the following way:

      • The proposed solution was compared with the current state,

      • The envisioned changes were explained by presenting examples (screenshots, parts of generated artefacts) **

      • As seen below, the following perspectives were presented: EA, TTL and HTML.

UFERN8bv0sfIiIiIiIiIiL6z8PSh4iIiIiIiIhIh1j6EBERERERERHpEEsfIiIiIiIiIiIdYulDRERERERERKRDLH2IiIiIiIiIiHSIpQ8RERERERERkQ6x9CEiIiIiIiIi0iGWPkREREREREREOsTSh4iIiIiIiIhIh1j6EBERERERERHpEEsfIiIiIiIiIiIdYulDRERERERERKRDLH2IiIiIiIiIiHSIpQ8RERERERERkQ79PzR22pn0wu7sAAAAAElFTkSuQmCC
8nzOvAQCA1hCeAwAAAAAAAABgITwHAAAAAAAAAMBCeA4AAAAAAAAAgIXwHAAAAAAAAAAAC+E5AAAAAAAAAAAWwnMAAAAAAAAAACyE5wAAAAAAAAAAWAjPAQAAAAAAAACwEJ4DAAAAAAAAAGAhPAcAAAAAAAAAwEJ4DgAAAAAAAACAhfAcAAAAAAAAAAAL4TkAAAAAAAAAABbCcwAAAAAAAAAALITnAAAAAAAAAABYCM8BAAAAAAAAALAQngMAAAAAAAAAYCE8BwAAAAAAAADAQngOAAAAAAAAAICF8BwAAAAAAAAAAAvhOQAAAAAAAAAAFsJzAAAAAAAAAAAshOcAAAAAAAAAAFgIzwEAAAAAAAAAsBCeAwAAAAAAAABgITwHAAAAAAAAAMBCeA4AAAAAAAAAgIXwHAAAAAAAAAAAC+E5AAAAAAAAAAAWwnMAAAAAAAAAACyE5wAAAAAAAAAAWAjPAQAAAAAAAACwEJ4DAAAAAAAAAGAhPAcAAAAAAAAAwEJ4DgAAAAAAAACAhfAcAAAAAAAAAAAL4TkAAAAAAAAAABbCcwAAAAAAAAAALITnAAAAAAAAAABYCM8BAAAAAAAAALAQngMAAAAAAAAAYCE8BwAAAAAAAADAQngOAAAAAAAAAICF8BwAAAAAAAAAAAvhOQAAAAAAAAAAFsJzAAAAAAAAAAAshOcAAAAAAAAAAFgIzwEAAAAAAAAAsBCeAwAAAAAAAABgITwHAAAAAAAAAMBCeA4AAAAAAAAAgIXwHAAAAAAAAAAAC+E5AAAAAAAAAAAWwnMAAAAAAAAAACyE5wAAAAAAAAAAWAjPAQAAAAAAAACwEJ4DAAAAAAAAAGAhPAcAAAAAAAAAwEJ4DgAAAAAAAACAhfAcAAAAAAAAAAAL4TkAAAAAAAAAABbCcwAAAAAAAAAALITnAAAAAAAAAABYCM8BAAAAAAAAALAQngMAAAAAAAAAYCE8BwAAAAAAAADAQngOAAAAAAAAAICF8BwAAAAAAAAAAAvhOQAAAAAAAAAAFsJzAAAAAAAAAAAshOcAAAAAAAAAAFgIzwEAAAAAAAAAsBCeAwAAAAAAAABg+f8BWtl3JrCzoJMAAAAASUVORK5CYII=
B0XAmSyi8nkoAAAAAElFTkSuQmCC
  • Two cases of core and external concepts were covered. The above pictures depict the core concept of epo:CatalogueProvider. **

    • EA and TTL perspectives, core concepts

  • It was proposed to keep additional information in a floating note attached to a class.

    • It was explained why the proposition is to use a floating note: A regular property cannot be used due to a length limitation (max 250 characters).

Ppf8PAlY7hsza9ZEAAAAASUVORK5CYII=
  • A concern that this may not be an optimal way of visualizing additional information was raised (from the user perspective), but the proposal was accepted.

    • A proposal to use skos:historyNote property to keep WG approval DD/MM/YYY text formerly stored as a part of a definition was accepted. At the same time it was decided the alternative properties initially considered for this purpose, that is: _dct:date, dct:issued, dct:modified _will not be used.

    • It was clarified that the WG approval DD/MM/YYY text will be used to record the last modified date. It was agreed not to keep track of historical WG approval DD/MM/YYY entries as the past changes can be checked by inspecting the previous versions of the model.

    • It was agreed that BT in skos:editorialNote won’t be represented as a concept (RDF resource), having it as a tag in EA and in the HTML is enough.

      • HTML perspective, core and external concepts

    • Additional information (in the floating notes in EA) will not appear in the HTML.

AbMfKz4Maa76AAAAAElFTkSuQmCC
  • EA and HTML perspective, external concepts

    • _WG approval DD/MM/YYY _will be handled in the same way as in case of core concepts.

    • The decision about what a definition should look like for an external concept was made.

      • The proposal was to include both a link to the original concept and text of the definition.

      • It was decided not to include the part about reusing a concept with lexical adaptation. The decision was to keep only the link to the original definition of the concept.

Jydo0LUWxXgAAAAASUVORK5CYII=
  • However, the need to have such a link that would direct to a human-readable definition was stated.

  • It was agreed that further effort will be done in order to verify that such a link points to a human-readable version when it can be provided (best-effort), for every external vocabulary.

    • Results of this verification (for example concepts coming from every used external vocabulary) will be presented during the next WG meeting.

      • It was discussed that during the next WG meeting, the working group will resolve 4.2.0 issues.

Action Points

  • Demonstrate that it’s feasible to provide human-readable links to an original definition of a concept for all external vocabularies that are used.