Glossary - Revision history

Vmurrell: /* Time Dimension */

2025-11-03T12:59:50Z

‎Time Dimension

2025-11-03T12:59:06Z

‎Time Dimension

2025-11-03T12:58:00Z

‎Representation

2025-11-03T12:56:16Z

‎Maintainable artefact

2025-11-03T12:56:04Z

‎Maintainable artefact

2025-11-03T12:53:53Z

‎Maintainable artefact

2025-11-03T12:52:50Z

‎Attribute

2025-11-03T12:52:31Z

2025-11-03T12:48:54Z

‎Representation

2025-11-03T12:45:00Z

‎Examples

@@ Line 135: / Line 135: @@
 =Time Dimension=
-The Component in a [[Glossary#Time Series]] [[Data Structure Definition]] that holds the observation time.
+The Component in a [[Glossary#Time Series|Time Series]] [[Data Structure Definition]] that holds the observation time.
 For Time Series, an observation is uniquely identified by the combination of the series dimensions and the time dimension.

@@ Line 135: / Line 135: @@
 =Time Dimension=
-The [[Component]] in a [[Time Series]] [[Data Structure Definition]] that holds the observation time.
+The Component in a [[Glossary#Time Series]] [[Data Structure Definition]] that holds the observation time.
 For Time Series, an observation is uniquely identified by the combination of the series dimensions and the time dimension.

@@ Line 72: / Line 72: @@
 =Representation=
-The representation of a [[Concept]] or [[Component]] defines the set of legal values.
+The representation of a [[Concepts]] or Component defines the set of legal values.
 There are two different representation types:

@@ Line 28: / Line 28: @@
 * Annotations (optional)
-Item| such as Codes and Concepts, are not maintainable artefacts because they can only exist within their containers, in this case Codelists and Concept Schemes respectively.
+Item such as Codes and Concepts, are not maintainable artefacts because they can only exist within their containers, in this case Codelists and Concept Schemes respectively.
 =URN=

@@ Line 28: / Line 28: @@
 * Annotations (optional)
 Item| such as Codes and Concepts, are not maintainable artefacts because they can only exist within their containers, in this case Codelists and Concept Schemes respectively.
 =URN=

@@ Line 20: / Line 20: @@
 =Maintainable artefact=
-An SDMX maintainable artefact is one that can be independently created and maintained by a [[maintenance agency]].<br><br>
+An SDMX maintainable artefact is one that can be independently created and maintained by an [[agency]].<br><br>
 Maintainable artefacts have:
 * ID

@@ Line 3: / Line 3: @@
 Statistical concept providing qualitative information about a specific statistical object.
-In practice, Attributes are [[/Glossary#Component|Components]] used in [[Data Structure Definition|Data Structure Definitions]] to add additional information which is not required to uniquely identify series or observations. Attributes can be attached at different levels in the dataset:
+In practice, Attributes are [[Glossary#Component|Components]] used in [[Data Structure Definition|Data Structure Definitions]] to add additional information which is not required to uniquely identify series or observations. Attributes can be attached at different levels in the dataset:
 * Dataset
 * Group

@@ Line 3: / Line 3: @@
 Statistical concept providing qualitative information about a specific statistical object.
-In practice, Attributes are [[Component|Components]] used in [[Data Structure Definition|Data Structure Definitions]] to add additional information which is not required to uniquely identify series or observations. Attributes can be attached at different levels in the dataset:
+In practice, Attributes are [[/Glossary#Component|Components]] used in [[Data Structure Definition|Data Structure Definitions]] to add additional information which is not required to uniquely identify series or observations. Attributes can be attached at different levels in the dataset:
 * Dataset
 * Group
@@ Line 12: / Line 12: @@
 Structural artefact used to define the structure of a Data or Metadata Set.
-In a [[Data Structure Definition]], the [[Dimension|Dimensions]] and [[Attribute|Attributes]] are its components.
+In a [[Data Structure Definition]], the [[Glossary#Dimension|Dimensions]] and [[[Glossary#Attribute|Attributes]] are its components.
 =Dimension=

← Older revision		Revision as of 12:48, 3 November 2025
Line 131:		Line 131:
	* TimeRange (common:TimeRangeType, startDateTime + Duration)		* TimeRange (common:TimeRangeType, startDateTime + Duration)
	* XHTML (common:StructuredText, allows for multi-lingual text content that has XHTML markup)		* XHTML (common:StructuredText, allows for multi-lingual text content that has XHTML markup)
		+
		+	=SDMX Metadata Registry=
		+	The central repository and maintenance tool for all of the SQL structural metadata including Codelists, Concepts and Data Structure Definitions.
		+
		+	=Time Dimension=
		+	The [[Component]] in a [[Time Series]] [[Data Structure Definition]] that holds the observation time.
		+
		+	For Time Series, an observation is uniquely identified by the combination of the series dimensions and the time dimension.
		+
		+	=Time Series=
		+	Series of observations (data points) in time order.
		+
		+	In many SDMX use cases, time series have a defined frequency which is either explicitly defined using a 'FREQ' or similar dimension, or implicitly derived from the observation timestamps. For instance, observations with timestamps of '2015, 2016 and 2017' imply the frequency is annual. Whereas observations with timestamps '2015-Q1, 2015-Q2 and 2015-Q3' imply quarterly.

@@ Line 47: / Line 47: @@
 |}
-===Examples===
+'''Examples'''
 The following SDMX structures are maintainable artefacts:
 * Agency Schemes