Changes for page 4 Specific Item Schemes

Last modified by Helena K. on 2026/06/08 16:44

From version 36.12
edited by Helena K.
on 2026/06/08 16:43
Change comment: There is no comment for this version
To version 37.1
edited by Helena K.
on 2026/06/08 16:44
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -442,7 +442,7 @@
442 442  
443 443  In some data reporting environments, and in particular those in primary reporting, a report may comprise a variety of heterogeneous data, each described by a different //Structure//. Equally, a specific disseminated or published report may also comprise a variety of heterogeneous data. The definition of the set of linked sub reports is supported by the ReportingTaxonomy.
444 444  
445 -The ReportingTaxonomy is a specialised form of //ItemScheme//. Each ReportingCategory of the ReportingTaxonomy can link to one or more //StructureUsage// which itself can be one of Dataflow, or Metadataflow, and one or more //Structure//, which itself can be one of DataStructureDefinition or MetadataStructureDefinition. It is expected that within a specific ReportingTaxonomy each Category that is linked in this way will be linked to the same class (e.g. all Category in the scheme will link to a Dataflow). Note that a ReportingCategory can have child ReportingCategory and in this way it is possible to define a hierarchical ReportingTaxonomy. It is possible in this taxonomy that some ReportingCategory are defined just to give a reporting structure. For instance:
445 +The ReportingTaxonomy is a specialised form of //ItemScheme//. Each ReportingCategory of the ReportingTaxonomy can link to one or more //StructureUsage// which itself can be one of [[Dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]], or [[Metadataflow>>doc:sdmx:Glossary 2\.1.Metadataflow.WebHome]], and one or more //Structure//, which itself can be one of DataStructureDefinition or MetadataStructureDefinition. It is expected that within a specific ReportingTaxonomy each [[Category>>doc:sdmx:Glossary 2\.1.Category.WebHome]] that is linked in this way will be linked to the same class (e.g. all [[Category>>doc:sdmx:Glossary 2\.1.Category.WebHome]] in the scheme will link to a [[Dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]]). Note that a ReportingCategory can have child ReportingCategory and in this way it is possible to define a hierarchical ReportingTaxonomy. It is possible in this taxonomy that some ReportingCategory are defined just to give a reporting structure. For instance:
446 446  
447 447  Section 1
448 448  
... ... @@ -454,7 +454,7 @@
454 454  1. linked to Datafow_3
455 455  1. linked to Datafow_4
456 456  
457 -Here, the nodes of Section 1 and Section 2 would not be linked to Dataflow but the other would be linked to a Dataflow (and hence the DataStructureDefinition).
457 +Here, the nodes of Section 1 and Section 2 would not be linked to [[Dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]] but the other would be linked to a [[Dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]] (and hence the DataStructureDefinition).
458 458  
459 459  A partial ReportingTaxonomy (where isPartial is set to “true”) is identical to a ReportingTaxonomy and contains the ReportingCategory and associated names and descriptions, just as in a normal ReportingTaxonomy. However, its content is a sub set of the full ReportingTaxonomy The way this works is described in section [[3.5.3.1>>doc:Methodology.SDMX 3\.1 Standards\. Section 2\. Information model.3 SDMX Base Package.WebHome||anchor="H3.5.3.1Narrative"]] on //ItemScheme//.
460 460  
... ... @@ -465,12 +465,12 @@
465 465  |ReportingTaxonomy|(((
466 466  Inherits from
467 467  //ItemScheme//
468 -)))|(% style="width:668px" %)A scheme which defines the composition structure of a data report where each component can be described by an independent Dataflow or Metadataflow.
469 -| |/items|(% style="width:668px" %)Associates the Reporting Category
470 -|ReportingCategory|Inherits from //Item//|(% style="width:668px" %)A component that gives structure to the report and links to data and metadata.
471 -| |/hierarchy|(% style="width:668px" %)Associates child Reporting Category.
472 -| |+flow|(% style="width:668px" %)Association to the data and metadata flows that link to metadata about the provisioning and related data and metadata sets, and the structures that define them.
473 -| |+structure|(% style="width:668px" %)Association to the Data Structure Definition and Metadata Structure Definitions which define the structural metadata describing the data and metadata that are contained at this part of the report.
468 +)))|(% style="width:668px" %)A scheme which defines the composition structure of a data report where each [[component>>doc:sdmx:Glossary 2\.1.Component.WebHome]] can be described by an independent [[Dataflow>>doc:sdmx:Glossary 2\.1.Dataflow.WebHome]] or [[Metadataflow>>doc:sdmx:Glossary 2\.1.Metadataflow.WebHome]].
469 +| |/items|(% style="width:668px" %)Associates the [[Reporting Category>>doc:sdmx:Glossary 2\.1.Reporting category.WebHome]]
470 +|ReportingCategory|Inherits from //Item//|(% style="width:668px" %)A [[component>>doc:sdmx:Glossary 2\.1.Component.WebHome]] that gives structure to the report and links to data and metadata.
471 +| |/hierarchy|(% style="width:668px" %)Associates child [[Reporting Category>>doc:sdmx:Glossary 2\.1.Reporting category.WebHome]].
472 +| |+flow|(% style="width:668px" %)Association to the data and [[metadata flows>>doc:sdmx:Glossary 2\.1.Metadataflow.WebHome]] that link to metadata about the provisioning and related data and [[metadata sets>>doc:sdmx:Glossary 2\.1.Metadata set.WebHome]], and the structures that define them.
473 +| |+structure|(% style="width:668px" %)Association to the [[Data Structure Definition>>doc:sdmx:Glossary 2\.1.Data structure definition.WebHome]] and [[Metadata Structure Definitions>>doc:sdmx:Glossary 2\.1.Metadata structure definition.WebHome]] which define the [[structural metadata>>doc:sdmx:Glossary 2\.1.Structural metadata.WebHome]] describing the data and metadata that are contained at this part of the report.
474 474  
475 475  ----
476 476  
© Semantic R&D Group, 2026