Skip to Content
Last modified by Artur K. on 2026/05/29 14:29
From version 19.1
edited by Artur K.
on 2026/05/29 14:29
Change comment: Copied from sdmxsrlocalization:Methodology.SDMX 3\.0 Standards\. Section 6\. Technical Notes.4 General Notes for Implementers.WebHome
To version 15.1
edited by Elena Yasinovskaya
on 2025/06/17 19:00
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.arturkryazhev
1 +xwiki:XWiki.elenasemanticproorg
Tags
... ... @@ -1,0 +1,1 @@
1 +Artefact|Attribute|Category|Category scheme|Code|Code list|Component|Concept scheme|Data consumer|Data consumer scheme|Data provider|Data set|Data structure definition|Dataflow|Decimals|Dimension|Facet|Hierarchy|Identifiable artefact|Maintenance agency|Metadataflow|Reference metadata|Reporting taxonomy|Representation|SDMX Information Model|SDMX-JSON|SDMX-ML|Statistical data and metadata exchange|Structural metadata|Structure set|Time format|Time period|isExternalReference
Content
... ... @@ -250,7 +250,7 @@
250 250  
251 251  A specialized [[attribute>>doc:Glossary.Attribute.WebHome]] (reporting year start day) exists for the purpose of communicating the reporting year start day. This [[attribute>>doc:Glossary.Attribute.WebHome]] has a fixed identifier
252 252  
253 -(REPORTING_YEAR_START_DAY) and a fixed [[representation>>doc:Glossary.Representation.WebHome]] (xs:gMonthDay) so that it can always be easily identified and processed in a data message. Although this [[attribute>>doc:Glossary.Attribute.WebHome]] exists in specialized sub-class, it functions the same as any other [[attribute>>doc:Glossary.Attribute.WebHome]] outside of its identification and [[representation>>doc:Glossary.Representation.WebHome]]. It must takes its identity from a (% style="color:#e74c3c" %)[[concept>>doc:Glossary.Concept.WebHome]](%%) and state its relationship with other [[components>>doc:Glossary.Component.WebHome]] of the [[data structure definition>>doc:Glossary.Data structure definition.WebHome]]. The ability to state this relationship allows this reporting year start day [[attribute>>doc:Glossary.Attribute.WebHome]] to exist at the appropriate levels of a data message. In the absence of this [[attribute>>doc:Glossary.Attribute.WebHome]], the reporting year start date is assumed to be January 1; therefore if the reporting year coincides with the calendar year, this [[Attribute>>doc:Glossary.Attribute.WebHome]] is not necessary.
253 +(REPORTING_YEAR_START_DAY) and a fixed [[representation>>doc:Glossary.Representation.WebHome]] (xs:gMonthDay) so that it can always be easily identified and processed in a data message. Although this [[attribute>>doc:Glossary.Attribute.WebHome]] exists in specialized sub-class, it functions the same as any other [[attribute>>doc:Glossary.Attribute.WebHome]] outside of its identification and [[representation>>doc:Glossary.Representation.WebHome]]. It must takes its identity from a (% style="color:#e74c3c" %)[[concept>>doc:sdmx:Glossary.Concept.WebHome]](%%) and state its relationship with other [[components>>doc:Glossary.Component.WebHome]] of the [[data structure definition>>doc:Glossary.Data structure definition.WebHome]]. The ability to state this relationship allows this reporting year start day [[attribute>>doc:Glossary.Attribute.WebHome]] to exist at the appropriate levels of a data message. In the absence of this [[attribute>>doc:Glossary.Attribute.WebHome]], the reporting year start date is assumed to be January 1; therefore if the reporting year coincides with the calendar year, this [[Attribute>>doc:Glossary.Attribute.WebHome]] is not necessary.
254 254  
255 255  Since the duration and the reporting year start day are known for any reporting period, it is possible to relate any reporting period to a distinct calendar period. The actual Gregorian calendar period covered by the reporting period can be computed as follows (based on the standard format of [REPROTING_YEAR]-[PERIOD_INDICATOR][PERIOD_VALUE] and the reporting year start day as [REPORTING_YEAR_START_DAY]):
256 256  
... ... @@ -371,7 +371,7 @@
371 371  * Reporting Day: 2006-D156**-05:00**
372 372  * Reporting Year Start Day: 07-01**-05:00**
373 373  
374 -According to ISO 8601, a date without a time-zone is considered "local time". [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] assumes that local time is that of the sender of the message. In this version of [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]], an optional field is added to the sender definition in the header for specifying a time zone. This field has a default value of 'Z' (UTC). This determination of local time applies for all dates in a message.
374 +According to ISO 8601, a date without a time-zone is considered "local time". [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] assumes that local time is that of the sender of the message. In this (% style="color:#e74c3c" %)version(%%) of [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]], an optional field is added to the sender definition in the header for specifying a time zone. This field has a default value of 'Z' (UTC). This determination of local time applies for all dates in a message.
375 375  
376 376  === 4.2.10 Representing Time Spans Elsewhere ===
377 377  
... ... @@ -485,7 +485,7 @@
485 485  
486 486  === 4.3.3 Legacy-versioned artefacts ===
487 487  
488 -Organisations wishing to keep a maximum of backwards compatibility with existing implementations can continue using the previous 2-digit convention for [[version>>doc:Glossary.Version.WebHome]] numbers (MAJOR.MINOR) as in the past, such as '2.3', but without the ‘isFinal’ property. The new [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] 3.0 standard does not add any strict rules or guarantees about changes in those [[artefacts>>doc:Glossary.Artefact.WebHome]], since the legacy versioning rules were rather loose and non-binding, including the meaning of the ‘isFinal’ property, and their implementations were varying.
488 +Organisations wishing to keep a maximum of backwards compatibility with existing implementations can continue using the previous 2-digit convention for (% style="color:#e74c3c" %)version(%%) numbers (MAJOR.MINOR) as in the past, such as '2.3', but without the ‘isFinal’ property. The new [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] 3.0 standard does not add any strict rules or guarantees about changes in those [[artefacts>>doc:Glossary.Artefact.WebHome]], since the legacy versioning rules were rather loose and non-binding, including the meaning of the ‘isFinal’ property, and their implementations were varying.
489 489  
490 490  In order to make [[artefacts>>doc:Glossary.Artefact.WebHome]] immutable or changes truly predictable, a move to the new semantic versioning syntax is required.
491 491  
... ... @@ -507,7 +507,7 @@
507 507  
508 508  The detailed rules for dependency management and references are listed in chapter 14 in the annex for “Semantic Versioning”.
509 509  
510 -In order to allow resolving the described new forms of dependencies, the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] 3.0 Rest API supports retrievals legacy-versioned, wildcarded and extended [[artefact>>doc:Glossary.Artefact.WebHome]] [[versions>>doc:Glossary.Version.WebHome]]:
510 +In order to allow resolving the described new forms of dependencies, the [[SDMX>>doc:Glossary.Statistical data and metadata exchange.WebHome]] 3.0 Rest API supports retrievals legacy-versioned, wildcarded and extended [[artefact>>doc:Glossary.Artefact.WebHome]] (% style="color:#e74c3c" %)versions(%%):
511 511  
512 512  * [[Artefact>>doc:Glossary.Artefact.WebHome]] queries for a **specific** [[version>>doc:Glossary.Version.WebHome]] (X.Y, X.Y.Z or X.Y.Z-EXT).
513 513  * [[Artefact>>doc:Glossary.Artefact.WebHome]] queries for **latest available** semantic [[versions>>doc:Glossary.Version.WebHome]] within the wildcard scope (X+.Y.Z, X.Y+.Z or X.Y.Z+).
SKMS.Methodology.Code.MethodologyClass[0]
Index
... ... @@ -1,1 +1,0 @@
1 -4
SUZ.Methodology.Code.MethodologyClass[0]
index
... ... @@ -1,0 +1,1 @@
1 +4
© Semantic R&D Group, 2026