Notice refersToProcedure to be removed

[muricna]

The Notice refersToProcedure is a duplicate of ResultNotice refersToProcedure and creates confusion as it could be used for CompetitionNotice which announcesProcedure. Specific predicates should be used for each type of Notice to ease querying.

[cristianvasquez]

This point is open to debate, as it depends on the types of queries being executed.

For instance, in a query like "Retrieve all notices associated with a specific procedure", using different predicates for each notice type complicates the query. It would require handling multiple predicates through unions or relying on inference.

From a simplicity standpoint, I believe a single predicate should be used. The relationship with the procedure can already be inferred from the notice type. For example, a ResultNotice conveys the results of a procedure. Notices are already distinguishable by their class (ResultNotice, CompetitionNotice) and the value of epo:hasNoticeType.

I suggest moving this discussion and analysing a couple of queries, to understand the tradeoffs

[muricna]

Notice refersToProcedure is wrong because it has a cardinality of 1. A planning notice does not refer to a Procedure. Even if the cardinality is relaxed I do not think it should have the same relation as the result notice. It could be something like isAbout but this would not enable the querying of all notices since as previously stated the planning notices would be excluded.