Data or Metadata Structure Definition - Revision history

Vmurrell: /* Data Structure Definitions with Multiple Measures */

2023-08-08T10:05:06Z

‎Data Structure Definitions with Multiple Measures

2022-09-05T08:32:03Z

‎Structure Properties

2022-08-31T15:57:33Z

‎Data Structure Components

2022-08-31T15:56:33Z

‎Structure Properties

2022-08-23T08:05:29Z

‎Data Structure Components

2022-08-23T08:04:31Z

‎Data Structure Components

2022-08-23T08:04:01Z

‎Data Structure Components

2022-08-23T07:59:03Z

‎Usage

2022-08-22T09:39:46Z

‎Context within the SDMX 2.1 Information Model

2022-08-22T09:38:41Z

← Older revision		Revision as of 10:05, 8 August 2023
Line 168:		Line 168:

	=Data Structure Definitions with Multiple Measures=		=Data Structure Definitions with Multiple Measures=
−	Data Structures can be created in the Registry containing multiple measures, however the generate data set option does not support multiple measures ~~and the load/validation process will reject~~ datasets ~~containing~~ multiple measures.	+	Data Structures can be created in the Registry containing multiple measures, however the generate data set option does not support multiple measures. FXL does not support Creating datasets with multiple measures.

@@ Line 15: / Line 15: @@
 |-
 ! scope=row style="text-align: left;"  | Item Scheme
-| [[Item_Scheme|No]]
+| [[Item_Scheme V11|No]]
 |-
 ! scope=row style="text-align: left;"  | SDMX Information Model Versions

@@ Line 74: / Line 74: @@
 <p>
 <strong>The role of Concepts In defining a DSD's Components</strong><br>
-Every Dimension, Attribute and Measure is described by a predefined [[Concepts V11]]. Concepts have their own default [[Representation]] which can be overridden by defining a Local Representation for the Component in the DSD. That's particularly helpful when using some standard Concepts like the [https://registry.sdmx.org/ws/public/sdmxapi/rest/conceptscheme/SDMX/CROSS_DOMAIN_CONCEPTS/2.0 SDMX Cross Domain Concepts] where the default Representation is 'String', but the Component needs to be Enumerated or have some use case specific restriction on what values are allowable.
+Every Dimension, Attribute and Measure is described by a predefined [[Concepts V11|Concept]]. Concepts have their own default [[Representation]] which can be overridden by defining a Local Representation for the Component in the DSD. That's particularly helpful when using some standard Concepts like the [https://registry.sdmx.org/ws/public/sdmxapi/rest/conceptscheme/SDMX/CROSS_DOMAIN_CONCEPTS/2.0 SDMX Cross Domain Concepts] where the default Representation is 'String', but the Component needs to be Enumerated or have some use case specific restriction on what values are allowable.
 </p>

@@ Line 9: / Line 9: @@
 |-
 ! scope=row style="text-align: left;"  | Maintainable
-| [[Maintainable|Yes]]
+| [[Maintainable V11|Yes]]
 |-
 ! scope=row style="text-align: left;"  | Identifiable
-| [[Identifiable|Yes]]
+| [[Identifiable V11|Yes]]
 |-
 ! scope=row style="text-align: left;"  | Item Scheme

@@ Line 74: / Line 74: @@
 <p>
 <strong>The role of Concepts In defining a DSD's Components</strong><br>
-Every Dimension, Attribute and Measure is described by a predefined [[Concepts V10]]. Concepts have their own default [[Representation]] which can be overridden by defining a Local Representation for the Component in the DSD. That's particularly helpful when using some standard Concepts like the [https://registry.sdmx.org/ws/public/sdmxapi/rest/conceptscheme/SDMX/CROSS_DOMAIN_CONCEPTS/2.0 SDMX Cross Domain Concepts] where the default Representation is 'String', but the Component needs to be Enumerated or have some use case specific restriction on what values are allowable.
+Every Dimension, Attribute and Measure is described by a predefined [[Concepts V11]]. Concepts have their own default [[Representation]] which can be overridden by defining a Local Representation for the Component in the DSD. That's particularly helpful when using some standard Concepts like the [https://registry.sdmx.org/ws/public/sdmxapi/rest/conceptscheme/SDMX/CROSS_DOMAIN_CONCEPTS/2.0 SDMX Cross Domain Concepts] where the default Representation is 'String', but the Component needs to be Enumerated or have some use case specific restriction on what values are allowable.
 </p>

@@ Line 48: / Line 48: @@
 and optionally the [[Representation]] for each Component.</p>
-<p>Each [[Dataflow|Dataflow]] references a single DSD which describes the structure of the dataset that the Dataflow represents.</p>
+<p>Each [[Data_or_Metadataflow|Dataflow]] references a single DSD which describes the structure of the dataset that the Dataflow represents.</p>
 =Conventions=

@@ Line 37: / Line 37: @@
 |}
-==Context within the SDMX 2.1 Information Model==
+==Context within the SDMX 3.0 Information Model==
-[[File:L_DSD1.png|Data Structure Definition|600px]]
+[[File:SDMX3 Data-or-MetadataStructureDefinition.png|Data or Metadata Structure Definition|600px]]
 ==Usage==

← Older revision	Revision as of 09:38, 22 August 2022
(No difference)