ISSUE-189: Clarify validation report trigger in section 3
Clarify validation report trigger in section 3
- Raised by:
- Karen Coyle
- Opened on:
- The section on the validation report implies that it is the validation process itself that triggers a validation report. However, there has been discussion that a validation report is only created when the validation process concludes that the focus node does NOT obey the defined constraints. This is not clear in the section, which says only: "The validation report is the result of the validation process and includes a set of zero or more validation results." It isn't clear that "validation results" means reporting on focus nodes that do not obey the constraints (if that is what is intended).
Also, in the terminology entry on constraints, it says: "Constraints can also have non-validating properties (such as names and default values) that do not lead to validation results." This again implies that all validating properties result in a validation report, without mention of the results of the comparison between the constraints and the focus node.
- Related Actions Items:
- No related actions
- Related emails:
- Proposal to close ISSUE-189 (from firstname.lastname@example.org on 2016-11-13)
- shapes-ISSUE-189 (validation trigger): Clarify validation report trigger in section 3 (from email@example.com on 2016-10-09)
I'd like to add to this issue the question of clarifying what happens with multiple validation actions that result in non-conformance to report. Does each validation action result in a separate validation report, or is the one report for each constraint, or one report for each shape graph/data graph comparison?Karen Coyle, 11 Oct 2016, 12:49:22
RESOLUTION: Close ISSUE-189, adopting Dimitris and Karen's proposal: https://lists.w3.org/Archives/Public/public-data-shapes-wg/2016Nov/0051.html
Display change log