Changes for page 5 Data Structure Definition and Dataset

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -13,9 +13,13 @@
13	13	The actual SDMX Base construct from which the concrete classes inherit depends upon the requirements of the class for:
14	14
15	15	Annotation – //AnnotableArtefact//
	16	+
16	16	Identification – //IdentifiableArtefact//
	18	+
17	17	Naming – //NameableArtefact//
	20	+
18	18	Versioning – //VersionableArtefact//
	22	+
19	19	Maintenance – //MaintainableArtefact//
20	20
21	21	== 5.2 Inheritance View ==
...	...	@@ -32,22 +32,28 @@
32	32
33	33	Those classes in the SDMX metamodel which require annotations inherit from //AnnotableArtefact//. These are:
34	34
35		-//IdentifiableArtefact
36		-DataSet
37		-Key// (and therefore //SeriesKey// and //GroupKey//)
	39	+//IdentifiableArtefact//
	40	+
	41	+//DataSet//
	42	+
	43	+//Key// (and therefore //SeriesKey// and //GroupKey//)
	44	+
38	38	//Observation//
39	39
40	40	Those classes in the SDMX metamodel which require annotations and global identity are derived from //IdentifiableArtefact//. These are:
41	41
42		-//NameableArtefact
43		-ComponentList
44		-Component//
	49	+//NameableArtefact//
45	45
	51	+//ComponentList//
	52	+
	53	+//Component//
	54	+
46	46	Those classes in the SDMX metamodel which require annotations, global identity, multilingual name and multilingual description are derived from //NameableArtefact//. These are:
47	47
48		-//VersionableArtefact
49		-Item//
	57	+//VersionableArtefact//
50	50
	59	+//Item//
	60	+
51	51	The classes in the SDMX metamodel which require annotations, global identity, multilingual name and multilingual description, and versioning are derived from //VersionableArtefact//. These are:
52	52
53	53	//MaintainableArtefact//
...	...	@@ -54,15 +54,18 @@
54	54
55	55	Abstract classes which represent information that is maintained by Maintenance Agencies all inherit from //MaintainableArtefact//, they also inherit all the features of a //VersionableArtefact//, and are:
56	56
57		-//StructureUsage
58		-Structure
59		-ItemScheme//
	67	+//StructureUsage//
60	60
	69	+//Structure//
	70	+
	71	+//ItemScheme//
	72	+
61	61	All the above classes are abstract. The key to understanding the class diagrams presented in this section are the concrete classes that inherit from these abstract classes.
62	62
63	63	Those concrete classes in the SDMX Data Structure Definition and Dataset packages of the metamodel which require to be maintained by Agencies all inherit (via other abstract classes) from //MaintainableArtefact//, these are:
64	64
65	65	Dataflow
	78	+
66	66	DataStructureDefinition
67	67
68	68	The component structures that are lists of lists, inherit directly from //Structure//. A //Structure// contains several lists of components. The concrete class that inherits from //Structure// is:
...	...	@@ -74,8 +74,11 @@
74	74	The concrete classes which inherit from //ComponentList// and are subcomponents of the DataStructureDefinition are:
75	75
76	76	DimensionDescriptor – content is Dimension and TimeDimension
	90	+
77	77	DimensionGroupDescriptor – content is an association to Dimension, TimeDimension
	92	+
78	78	MeasureDescriptor – content is Measure
	94	+
79	79	AttributeDescriptor – content is DataAttribute and an association to MetadataAttribute
80	80
81	81	The classes that inherit from //Component// are:
...	...	@@ -83,6 +83,7 @@
83	83	Measure
84	84
85	85	//DimensionComponent// and thereby its sub classes of Dimension and TimeDimension
	102	+
86	86	//Attribute// and thereby its sub classes of DataAttribute and MetadataAttribute
87	87
88	88	The concrete classes identified above are the majority of the classes required to define the metamodel for the DataStructureDefinition. The diagrams and explanations in the rest of this section show how these concrete classes are related in order to support the functionality required.
...	...	@@ -153,8 +153,10 @@
153	153
154	154	**Figure 30: Representation of DSD Components**
155	155
156		-Each of Dimension, TimeDimension, Measure, DataAttribute and MetadataAttribute can have a Representation specified (using the localRepresentation association). If this is not specified in the DataStructureDefinition then the representation specified for Concept (coreRepresentation) is used. Measure, and DataAttribute may be also represented by multilingual text (as seen in the DataSet diagram further down). An exception is the MetadataAttribute, where its Representation is specified in the MetadataStructureDefinition.
	173	+Each of Dimension, TimeDimension, Measure, DataAttribute and MetadataAttribute can have a Representation specified (using the localRepresentation association). If this is not specified in the DataStructureDefinition then the representation specified for Concept
157	157
	175	+(coreRepresentation) is used. Measure, and DataAttribute may be also represented by multilingual text (as seen in the DataSet diagram further down). An exception is the MetadataAttribute, where its Representation is specified in the MetadataStructureDefinition.
	176	+
158	158	A DataStructureDefinition can be extended to form a derived DataStructureDefinition. This is supported in the StructureMap.
159	159
160	160	==== 5.3.2.2 Definitions ====
...	...	@@ -499,4 +499,6 @@
499	499	)))|(% style="width:437px" %)An attribute that takes it value from a Code in Code list.
500	500	|(% style="width:147px" %) |(% style="width:222px" %)+valueOf|(% style="width:437px" %)Association to the Code that is the value of the Attribute Value. Note that this is a conceptual association showing that the Code must exist in the Code list associated with the Data Attribute in the Data Structure Definition. In the actual Data Set the value of the Code is placed in the Attribute Value.
501	501
	521	+
	522	+
502	502