- All Known Subinterfaces:
ConformanceResult
,CoverageResult
,DescriptiveResult
,QuantitativeResult
Base interface of more specific result classes.
At least one data quality result shall be provided for each data quality element.
Different types of results can be provided for the same data quality elements. This could be
a quantitative result,
a conformance result,
a descriptive result or
a coverage result.
- Since:
- 2.0
- See Also:
- TODO:
- Renamed in 19157:2022:
QualityResult
.
-
Method Details
-
getResultScope
@UML(identifier="resultScope", obligation=OPTIONAL, specification=ISO_19157) default Scope getResultScope()Scope of the result. Quality frequently differs between various parts of the data set for which quality is evaluated. Therefore several evaluations may be applied for the same data quality element. To avoid repeating the measure and evaluation procedure descriptions in several instances ofElement
, several results with individual result scopes can be used.- Returns:
- scope of the result, or
null
if unspecified. - Since:
- 3.1
- See Also:
-
getDateTime
@UML(identifier="dateTime", obligation=OPTIONAL, specification=ISO_19157) default Temporal getDateTime()Date when the result was generated. The returned value should be an instance ofLocalDate
,LocalDateTime
,OffsetDateTime
orZonedDateTime
, depending whether hours are defined and how the timezone (if any) is defined. But other types are also allowed.- Returns:
- date of the result, or
null
if none. - Since:
- 3.1
-