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:

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.

Restricting cardinalities for epo:hasNoticeType

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.

If it is a D24, then it is a Prior Information Notice.

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