Working Group meeting

Date: 06/09/2022
Participants: Cecile Guasch, Natalie Muric, Csongor Nyulas, Giovanni Paolo Sellito
Model editor: Eugeniu Costetchi
Note editor: Andreea Pasăre

Agenda

  • Notice metadata overview

Discuss notice metadata

  • Plan to generate a new version with notice metadate included.

  • Publish the normalisation scheme for standard form mappings.

  • Diagram containing notice metadata:

D1fI1ydocJ9pAAAAAElFTkSuQmCC
FsKXApoX9yHAI0WU2KICOfokCNmDgXb+sg0SFk4YnsMUZwjOEbajWdMGmNhMSUGOncbBuZEP5DSCRAGCL5k2F+RqaAlEiSNxG8BediyLswiZIqpd87dKWTIf8PPQQysCbo4MIAAAAASUVORK5CYII=

At-voc:implementation-regulation

  • This needs to be changed.

  • The relation for regulation implementation should go from epo:Notice to at-voc:legal-basis.

  • If we include the regulations, we have to change the name “legal-basis” of the controlled vocabulary.

  • Changed epo:hasImplementationRegulation to epo:isBasedOnImplementationRegulation wit the following definition: “Indicates under which regulation a notice is created.
    WG Acceptance 06/09/2022”

  • How to signal the difference between SF notices and eForms notices?

    • The implementation regulation should help in this, but might not be enough.

Notice predicates

  • epo:Notice is part of ePO core.

  • Keeping all predicates that go from epo:Notice in the Notice module with the prefix epo-not.

  • The RDF for PPDS should contain all these predicates from the notice module.