Augment CONSERT Pipeline with conflict detection and resolution steps
- Lenguaje dominante
- HTML
- Estrellas
- 2
- Forks
- 0
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
### Why
The CONSERT Engine processing pipeline defines steps for conflict/constraint detection and resolution between two ContextAssertions prior to insertion in the DROOLS knowledge base.
These steps are currently missing from the implementation
### What
- the AtomicAction for `insertAtomicEvent` and `insertDerivedEvent` are updated to a flow including conflict detection and resolution steps, prior to deleting old event with its extension/derivation
- Conflict detection is enabled via a DROOLS query that identifies the _type_ of the conflict and the FactHandles of the conflicting assertions.
- Conflict resolution is implemented by default via specific rules for each conflict _type_
### Notes
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Evaluación
Este issue todavía no se ha evaluado.