Annotations need to be altered to support provenance-based distribution of errors and warnings. When upstream annotations are activated (first time), new linked errors/warnings are created for each direct child. These new annotations are in open state and can be changed to another type, comments added, and/or activated. This process continues downstream as each propagated annotation is activated.
If upstream annotations is deactivated or closed, this will cause all downstream annotations to also deactivate or close (implies upstream party made a mistake). If upstream is reactivated (possibly after re-evaluation/edits), existing linked downstream annotations remain in current state (open) until responsible parties reassess impact.
dvstans
commented
4 years ago
Annotations need to be altered to support provenance-based distribution of errors and warnings. When upstream annotations are activated (first time), new linked errors/warnings are created for each direct child. These new annotations are in open state and can be changed to another type, comments added, and/or activated. This process continues downstream as each propagated annotation is activated.
If upstream annotations is deactivated or closed, this will cause all downstream annotations to also deactivate or close (implies upstream party made a mistake). If upstream is reactivated (possibly after re-evaluation/edits), existing linked downstream annotations remain in current state (open) until responsible parties reassess impact.