Bug #27
PERIODICITY and Observed TimePeriod conflicts in samples.
| Status: | New | Start date: | 11/25/2009 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | % Done: | 0% |
||
| Category: | Data Structure Definition | |||
| Target version: | v.Next (Postponed) | |||
| Origin: | Origin Reference: |
Description
28. Sample error PERIODICITY=4,Yet OBS_VALUE TIME_PERIOD=FY10 and FY10-Q1. SDMX-HD Library should validate this.
Suggest PERIODICITY (The actual Frequency of observations) is deleted as it can always be derived from the Observation Time Period.
History
Updated by Philippe Boucher over 3 years ago
- Category set to Connectathon
Updated by Bob Jolliffe over 3 years ago
- Category changed from Connectathon to DataSet messages
Updated by Bob Jolliffe over 3 years ago
- Category changed from DataSet messages to Data Structure Definition
Updated by Philippe Boucher about 3 years ago
- Target version set to v1.0
Updated by Gary Patchen about 3 years ago
- Status changed from New to Closed
We had FREQ and PERIODICITY the wrong way around.
As FREQ is obligator we therefore can't delete it. However if FREQ is reported as QUARTERLY yet the observations are YEARLY this rule should generate a warning.
Updated by Gary Patchen over 2 years ago
- Status changed from Closed to New
- Target version changed from v1.0 to v.Next (Postponed)
Still need to generate a warning via a schematron rule or simple validation