Working Group meeting

Date: 02/08/2022
Participants: Natalie Muric, Csongor Nyulas
Model editor: Eugeniu Costetchi
Note editor: Andreea Pas─âre

Agenda

  • eNotice development

Discussion

eNotice

  • Separate the Notice systematisation (Notice module) from the Notice content (NoticeContent module)

  • In the Notice module we have instances created from the values of CV like in the example below:

G9PAQS464orgAAAAAElFTkSuQmCC
  • We are constraining a class to a specific value of a property (Directive 23 in the image above)

  • There is a controlled list for all notice subtypes in eForms.

F8XjPjj8G9ynwAAAABJRU5ErkJggg==
  • Restricting cardinalities for epo:hasNoticeType

e5Ll7vPwf32F5ULAmvPsAAAAASUVORK5CYII=
  • The namespace prefix to be used should be epo-not:

  • The notice package from ePO core should be moved to the Notice module.

  • Check all attributes from epo:Document and decide what namespace should be used (epo:hasPublicationDate) and if they should be moved at the Notice level.

  • For the moment what is in the Document class should stay there and decide what can be moved in the future.

  • The package notice classes seem ok. Check and validate this package.

  • Creating pmc:at-voc:notice-type with a comment that this value is not part of the notice type controlled vocabulary yet.

sE9jxUktsDMAAAAASUVORK5CYII=
  • If it is a D24, then it is a Prior Information Notice.

  • If it is a D25, then it is a Periodic Indicative Notice.