search

sdmx-twg / sdmx-im

SDMX Information Model - UML model and functional description, definition of classes, associations and attributes
6 stars 3 forks source link

Allow "H" code in time period for half-yearly/semi-annual data #19

Open trainot opened 2 years ago

trainot commented 2 years ago

Allow "H" code in time period for half-yearly/semi-annual data. This would require a change in the common schema to permit flexibility on being able to specify either "S" or "H" for half-yearly data in time period.

egreising commented 2 years ago

May I ask whether there is a consensus in making this change? We have traditionaly avoided having "synonyms" for standard codes, and for this particular case, we already have the YYYY-S{1-2} notation and the Extended ISO 8601-2:2019 (which I understand is supported as part of the Gregorian Time Period specification) that established the special months "40" and "41" to represent semester 1 and 2, respectively. So YYYY-H{1-2} would be a third way of coding the same time period. That means that all the systems should check for the three possible coding schemes when receiving data. Besides, I understand that this kind of modifications would require the agreement of the SWG. Any other points of view?

dbarr99 commented 2 years ago

Hello, I agree with Edgardo that if YYYY-H is a synonym for the existing YYYY-S then the costs of allowing it seem to outweigh the benefits - every existing system that checks for YYYY-S would have to change to check for YYYY-H.

It seems more cost-efficient that either the current system(s) that support YYYY-H interpret it as YYYY-S and/or the reporters change to report YYYY-S. Best, David

stratosn commented 6 months ago

@agent96 do we need to agree within the TWG on how to move forward with this issue?