Wiki source code of 4 Specific Item Schemes

Version 36.4 by Helena K. on 2026/06/08 16:24

version	line-number	content
3.2	1	{{box title="Contents"}}
	2	{{toc/}}
	3	{{/box}}
1.1	4
3.2	5	== 4.1 Introduction ==
	6
36.2	7	The structures that are an arrangement of objects into [[hierarchies>>doc:sdmx:Glossary 2\.1.Hierarchy.WebHome]] or lists based on characteristics, and which are maintained as a group inherit from //ItemScheme//. These concrete classes are:
1.1	8
32.2	9	[[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]]
36.2	10	ConceptScheme
	11	CategoryScheme
	12	AgencyScheme, DataProviderScheme, MetadataProviderScheme, DataConsumerScheme, OrganisationUnitScheme, which all inherit from the abstract class //OrganisationScheme//
	13	ReportingTaxonomy
1.1	14	TransformationScheme
	15	RulesetScheme
	16	UserDefinedOperatorScheme
	17	NamePersonalisationScheme
	18	CustomTypeScheme
	19	VtlMappingScheme
	20
32.2	21	Note that the [[VTL>>doc:sdmx:Glossary 2\.1.Validation and transformation language.WebHome]] related schemes (the last 6 of the above list) are detailed in a dedicated section below ([[section 15>>doc:Methodology.SDMX 3\.1 Standards\. Section 2\. Information model.15 Validation and Transformation Language.WebHome]]).
1.1	22
3.3	23	== 4.2 Inheritance View ==
1.1	24
	25	The inheritance and relationship views are shown together in each of the diagrams in the specific sections below.
	26
3.3	27	== 4.3 Codelist ==
1.1	28
5.1	29	=== 4.3.1 Class Diagram ===
1.1	30
18.2	31	[[image:image42.png]]
	32
1.1	33	Figure 16: Class diagram of the Codelist
	34
3.3	35	=== 4.3.2 Explanation of the Diagram ===
1.1	36
3.3	37	==== 4.3.2.1 Narrative ====
1.1	38
36.3	39	The [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] inherits from the //ItemScheme// and therefore has the following [[attributes>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]]: id uri urn [[version>>doc:sdmx:Glossary 2\.1.Version.WebHome]] validFrom validTo [[isExternalReference>>doc:sdmx:Glossary 2\.1.isExternalReference.WebHome]] serviceURL structureURL isPartial
1.1	40
36.3	41	The [[Code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] inherits from //Item// and has the following [[attributes>>doc:sdmx:Glossary 2\.1.Attribute.WebHome]]:
1.1	42
36.2	43	id
	44	uri
	45	urn
1.1	46
36.3	47	Both [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] and [[Code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] have the association to InternationalString to support a multilingual name, an optional multi-lingual description, and an association to [[Annotation>>doc:sdmx:Glossary 2\.1.Annotation.WebHome]] to support notes (not shown).
1.1	48
36.3	49	Through the inheritance the [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] comprise one or more [[Codes>>doc:sdmx:Glossary 2\.1.Code.WebHome]], and the [[Code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] itself can have one or more child [[Codes>>doc:sdmx:Glossary 2\.1.Code.WebHome]] in the (inherited) [[hierarchy>>doc:sdmx:Glossary 2\.1.Hierarchy.WebHome]] association. Note that a child [[Code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] can have only one parent [[Code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] in this association. A more complex Hierarhcy, which allows multiple parents is described later.
1.1	50
36.3	51	A partial [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] (where isPartial is set to 'true') is identical to a [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] and contains the [[Code>>doc:sdmx:Glossary 2\.1.Code.WebHome]] and associated names and descriptions, just as in a normal [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]]. However, its content is a subset of the full [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]]. 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//.
1.1	52
3.3	53	==== 4.3.2.2 Definitions ====
1.1	54
5.2	55	(% style="width:912.835px" %)
	56	\|Class\|Feature\|(% style="width:656px" %)Description
36.4	57	\|(%%)(% style="background-color:#d35400" %)[[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]]\|(((
1.1	58	Inherits from
36.2	59	//ItemScheme//
36.4	60	)))\|(% style="width:656px" %)A list from which some statistical [[concepts>>doc:sdmx:Glossary 2\.1.Concept.WebHome]] (coded [[concepts>>doc:sdmx:Glossary 2\.1.Concept.WebHome]]) take their values.
	61	\|[[Code>>doc:Glossary 2\.1.Code.WebHome]]\|(((
1.1	62	Inherits from
36.2	63	Item
36.4	64	)))\|(% style="width:656px" %)A [[language>>doc:sdmx:Glossary 2\.1.Language.WebHome]] independent set of letters, numbers or symbols that represent a [[concept>>doc:sdmx:Glossary 2\.1.Concept.WebHome]] whose meaning is described in a natural [[language>>doc:sdmx:Glossary 2\.1.Language.WebHome]].
	65	\| \|[[hierarchy>>doc:sdmx:Glossary 2\.1.Hierarchy.WebHome]]\|(% style="width:656px" %)Associates the parent and the child [[codes>>doc:sdmx:Glossary 2\.1.Code.WebHome]].
	66	\| \|extends\|(% style="width:656px" %)Associates a [[Codelist>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] with any [[Codelists>>doc:sdmx:Glossary 2\.1.Code list.WebHome]] that it may extend.
1.1	67
	68	==== 4.3.3 Class Diagram – Codelist Extension ====
	69
18.3	70	[[image:image43.png]]
	71
1.1	72	Figure 17: Class diagram for Codelist Extension
	73
3.3	74	==== 4.3.3.1 Narrative ====
1.1	75
36.2	76	A Codelist may extend other Codelists via the CodelistExtension class. The latter, via the sequence, indicates the order of precedence of the extended Codelists for conflict resolution of Codes. Besides that, the prefix property is used to ensure uniqueness of inherited Codes in the extending{{footnote}}The Codelist that extends 0..* Codelists is the 'extending' Codelist, while the Codelist(s) that are inherited is/are the 'extended' Codelist(s).{{/footnote}} Codelist in case conflicting Codes must be included in the latter. Each CodelistExtension association may include one InclusiveCodeSelection or one ExclusiveCodeSelection; those allow including or excluding a specific selection of Codes from the extended Codelists.
1.1	77
36.2	78	The code selection classes may have MemberValues in order to specify the subset of the Codes that should be included or excluded from the extended Codelist. A MemberValue may have a value that corresponds to a Code, including its children Codes (via the cascadeValues property), or even include instances of the wildcard character ‘%’ in order to point to a set of Codes with common parts in their identifiers.
1.1	79
33.1	80	==== 4.3.3.2 Definitions ====
1.1	81
5.2	82	(% style="width:970.835px" %)
	83	\|Class\|Feature\|(% style="width:655px" %)Description
36.2	84	\|CodelistExtension\| \|(% style="width:655px" %)The association between Codelists that may extend other Codelists.
	85	\| \|prefix\|(% style="width:655px" %)A prefix to be used for a Codelist used in a extension, in order to avoid Code Conflicts.
	86	\| \|sequence\|(% style="width:655px" %)(((
	87	The order that will be used when extending a Codelist, for resolving Code conflicts. The latest Codelist used overrides any previous Codelist.
1.1	88	)))
36.2	89	\|InclusiveCodeSelection\| \|(% style="width:655px" %)The subset of Codes to be included when extending a Codelist.
	90	\|ExclusiveCodeSelection\| \|(% style="width:655px" %)The subset of Codes to be excluded when extending a Codelist.
	91	\|MemberValue\|(((
1.1	92	Inherits from:
36.2	93	//SelectionValue//
31.4	94	)))\|(% style="width:655px" %)A collection of values based on Codes and their children.
36.2	95	\| \|cascadeValues\|(% style="width:655px" %)A property to indicate if the child Codes of the selected Code shall be included in the selection. It is also possible to include children and exclude the Code by using the 'excluderoot' value.
	96	\| \|value\|(% style="width:655px" %)The value of the Code to include in the selection. It may include the ‘%’ character as a wildcard.
1.1	97
3.3	98	=== 4.3.4 Class Diagram – Geospatial Codelist ===
1.1	99
36.2	100	The geospatial support is implemented via an extension of the normal Codelist. This is illustrated in the following diagrams.
1.1	101
18.3	102	[[image:image44.png]]
	103
1.1	104	Figure 18: Inheritance for the GeoCodelist
	105
18.4	106	[[image:image45.png]]
	107
1.1	108	Figure 19: Class diagram for Geospatial Codelist
	109
3.3	110	==== 4.3.4.1 Narrative ====
1.1	111
36.2	112	A //GeoCodelist// is a specialisation of Codelist that includes geospatial information, by comprising a set of special Codes, i.e., //GeoRefCode//s. A //GeoCodelist// may be implemented by any of the two following classes, via the geoType property:
1.1	113
36.2	114	GeographicCodelist
1.1	115
36.2	116	GeoGridCodelist
1.1	117
36.2	118	The former, i.e., GeographicCodelist, comprises a set of GeoFeatureSetCodes, by adding a value in the Code that follows a pattern to represent a geo feature set.
1.1	119
36.2	120	The latter, i.e., GeoGridCodelist, comprises a set of GridCodes, which are related to the gridDefinition specified in the GeoGridCodelist.
1.1	121
33.1	122	==== 4.3.4.2 Definitions ====
1.1	123
5.2	124	(% style="width:960.835px" %)
	125	\|Class\|Feature\|(% style="width:559px" %)Description
36.2	126	\|//GeoCodelist//\|(((
1.1	127	Abstract Class Sub Classes:
36.2	128	GeographicCodelist
	129	GeoGridCodelist
	130	)))\|(% style="width:559px" %)The abstract class that represents a special type of Codelist, which includes geospatial information.
	131	\| \|geoType\|(% style="width:559px" %)The type of Geo Codelist that the Codelist will become.
	132	\|//GeoRefCode//\|(((
1.1	133	Abstract Class
	134	Sub Classes:
36.2	135	GeoFeatureSetCode
	136	GeoGridCode
31.4	137	)))\|(% style="width:559px" %)The abstract class that represents a special type of Code, which includes geospatial information.
36.2	138	\|GeographicCodelist\| \|(% style="width:559px" %)A special Codelist that has been extended to add a geographical feature set to each of its items, typically, this would include all types of administrative geographies.
	139	\|GeoGridCodelist\| \|(% style="width:559px" %)A code list that has defined a geographical grid composed of cells representing regular squared portions of the Earth.
	140	\| \|gridDefinition\|(% style="width:559px" %)Contains a regular expression string corresponding to the grid definition for the GeoGridCodelist.
	141	\|GeoFeatureSetCode\| \|(% style="width:559px" %)A Code that has a geo feature set.
	142	\| \|value\|(% style="width:559px" %)The geo feature set of the Code, which represents a set of points defining a feature in a format defined a predefined pattern (see section 6).
	143	\|GeoGridCode\| \|(% style="width:559px" %)A Code that represents a Geo Grid Cell belonging in a specific grid definition.
	144	\| \|geoCell\|(% style="width:559px" %)The value used to assign the Code to one cell in the grid.
1.1	145
3.3	146	== 4.4 ValueList ==
1.1	147
3.3	148	=== 4.4.1 Class Diagram ===
1.1	149
18.5	150	[[image:image46.png]]
	151
1.1	152	Figure 20: Class diagram of the ValueList
	153
3.3	154	=== 4.4.2 Explanation of the Diagram ===
1.1	155
3.3	156	==== 4.4.2.1 Narrative ====
1.1	157
36.2	158	A ValueList inherits from //EnumeratedList// (and hence the //MaintenableArtefact//) and thus has the following attributes:
1.1	159
36.2	160	id
	161	uri
	162	urn
	163	version
	164	validFrom
	165	validTo
	166	isExternalReference
5.3	167	registryURL
36.2	168	structureURL
5.3	169	repositoryURL
1.1	170
36.2	171	ValueItem inherits from //EnumeratedItem//, which adds an id, with relaxed constraints, to the former.
1.1	172
36.2	173	Through the inheritance from //NameableArtefact// the ValueList has the association to InternationalString to support a multi-lingual name, an optional multi-lingual description, and an association to Annotation to support notes (not shown). Similarly, the ValueItem, inherits the association to InternationalString and to the Annotation from the //EnumeratedItem//.
1.1	174
36.2	175	The ValueList can have one or more ValueItems.
1.1	176
3.3	177	==== 4.4.2.2 Definitions ====
1.1	178
5.2	179	(% style="width:929.835px" %)
	180	\|Class\|(% style="width:175px" %)Feature\|(% style="width:632px" %)Description
36.2	181	\|ValueList\|(% style="width:175px" %)(((
1.1	182	Inherits from
36.2	183	//EnumeratedList//
31.4	184	)))\|(% style="width:632px" %)A list from which some statistical concepts (enumerated concepts) take their values.
36.2	185	\|ValueItem\|(% style="width:175px" %)(((
1.1	186	Inherits from
36.2	187	//EnumeratedItem//
	188	)))\|(% style="width:632px" %)A language independent set of letters, numbers or symbols that represent a concept whose meaning is described in a natural language.
1.1	189
3.3	190	== 4.5 Concept Scheme and Concepts ==
1.1	191
3.3	192	=== 4.5.1 Class Diagram - Inheritance ===
1.1	193
18.6	194	[[image:image47.png]]
	195
5.4	196	Figure 21 Class diagram of the Concept Scheme
1.1	197
3.3	198	=== 4.5.2 Explanation of the Diagram ===
1.1	199
36.2	200	The ConceptScheme inherits from the //ItemScheme //and therefore has the following attributes:
1.1	201
36.2	202	id
	203	uri
	204	urn
	205	version validFrom validTo
	206	isExternalReference
5.5	207	registryURL
36.2	208	structureURL
5.5	209	repositoryURL
36.2	210	isPartial
1.1	211
36.2	212	Concept inherits from Item and has the following attributes:
5.5	213
36.2	214	id
	215	uri
	216	urn
5.5	217
36.2	218	Through the inheritance from //NameableArtefact// both ConceptScheme and Concept have the association to InternationalString to support a multi-lingual name, an optional multilingual description, and an association to Annotation to support notes (not shown).
1.1	219
36.2	220	Through the inheritance from //ItemScheme// the ConceptScheme comprise one or more Concepts, and the Concept itself can have one or more child Concepts in the (inherited) hierarchy association. Note that a child Concept can have only one parent Concept in this association.
1.1	221
36.2	222	A partial ConceptScheme (where isPartial is set to “true”) is identical to a ConceptScheme and contains the Concept and associated names and descriptions, just as in a normal ConceptScheme. However, its content is a subset of the full ConceptScheme. 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.
1.1	223
3.3	224	=== 4.5.3 Class Diagram Relationship ===
1.1	225
18.6	226	[[image:image48.png]]
	227
1.1	228	Figure 22: Relationship class diagram of the Concept Scheme
	229
3.3	230	=== 4.5.4 Explanation of the diagram ===
1.1	231
3.3	232	==== 4.5.4.1 Narrative ====
1.1	233
36.2	234	The ConceptScheme can have one or more Concepts. A Concept can have zero or more child Concepts, thus supporting a hierarchy of Concepts. Note that a child Concept can have only one parent Concept in this association. The purpose of the hierarchy is to relate concepts that have a semantic relationship: for example, a Reporting_Country and Vis_a_Vis_Country may both have Country as a parent concept, or a CONTACT may have a PRIMARY_CONTACT as a child concept. It is not the purpose of such schemes to define reporting structures: these reporting structures are defined in the MetadataStructureDefinition.
1.1	235
36.2	236	The Concept can be associated with a coreRepresentation. The coreRepresentation is the specification of the format and value domain of the Concept when used on a structure like a DataStructureDefinition or a MetadataStructureDefinition, unless the specification of the Representation is overridden in the relevant structure definition. In a hierarchical ConceptScheme the Representation is inherited from the parent Concept unless overridden at the level of the child Concept.
1.1	237
36.2	238	The Representation is documented in more detail in the section on the SDMX Base.
1.1	239
36.2	240	The Concept may be related to a concept described in terms of the ISO/IEC 11179 standard. The ISOConceptReference identifies this concept and concept scheme in which it is contained.
1.1	241
3.3	242	==== 4.5.4.2 Definitions ====
1.1	243
5.2	244	(% style="width:912.835px" %)
	245	\|(% style="width:170px" %)Class\|(% style="width:184px" %)Feature\|(% style="width:548px" %)Description
	246	\|(% style="width:170px" %)(((
36.2	247	ConceptScheme
5.2	248	)))\|(% style="width:184px" %)(((
1.1	249	Inherits from
36.2	250	//ItemScheme//
31.4	251	)))\|(% style="width:548px" %)The descriptive information for an arrangement or division of concepts into groups based on characteristics, which the objects have in common.
36.2	252	\|(% style="width:170px" %)Concept\|(% style="width:184px" %)(((
1.1	253	Inherits from
36.2	254	//Item//
	255	)))\|(% style="width:548px" %)A concept is a unit of knowledge created by a unique combination of characteristics.
31.4	256	\|(% style="width:170px" %) \|(% style="width:184px" %)/hierarchy\|(% style="width:548px" %)Associates the parent and the child concept.
36.2	257	\|(% style="width:170px" %) \|(% style="width:184px" %)coreRepresentation\|(% style="width:548px" %)Associates a Representation.
	258	\|(% style="width:170px" %) \|(% style="width:184px" %)+ISOConcept\|(% style="width:548px" %)Association to an ISO concept reference.
	259	\|(% style="width:170px" %)ISOConceptReference\|(% style="width:184px" %) \|(% style="width:548px" %)The identity of an ISO concept definition.
	260	\|(% style="width:170px" %) \|(% style="width:184px" %)conceptAgency\|(% style="width:548px" %)The maintenance agency of the concept scheme containing the concept.
	261	\|(% style="width:170px" %) \|(% style="width:184px" %)conceptSchemeID\|(% style="width:548px" %)The identifier of the concept scheme.
	262	\|(% style="width:170px" %) \|(% style="width:184px" %)conceptID\|(% style="width:548px" %)The identifier of the concept.
1.1	263
3.3	264	== 4.6 Category Scheme ==
1.1	265
3.3	266	=== 4.6.1 Context ===
1.1	267
36.2	268	This package defines the structure that supports the definition of and relationships between categories in a category scheme. It is similar to the package for concept scheme. An example of a category scheme is one which categorises data – sometimes known as a subject matter domain scheme or a data category scheme. Importantly, as will be seen later, the individual nodes in the scheme (the “categories”) can be associated to any set of IdentiableArtefacts in a Categorisation.
1.1	269
3.3	270	=== 4.6.2 Class diagram Inheritance ===
1.1	271
18.6	272	[[image:image49.png]]
	273
31.5	274	Figure 23 Inheritance Class diagram of the Category Scheme
1.1	275
3.3	276	=== 4.6.3 Explanation of the Diagram ===
1.1	277
3.3	278	==== 4.6.3.1 Narrative ====
1.1	279
36.2	280	The categories are modelled as a hierarchical //ItemScheme//. The CategoryScheme inherits from the //ItemScheme// and has the following attributes:
1.1	281
36.2	282	id
	283	uri
	284	urn
	285	version
	286	validFrom
	287	validTo
	288	isExternalReference
	289	structureURL
	290	serviceURL
	291	isPartial
1.1	292
36.2	293	Category inherits from //Item// and has the following attributes:
1.1	294
36.2	295	id
	296	uri
	297	urn
1.1	298
36.2	299	Both CategoryScheme and Category have the association to InternationalString to support a multi-lingual name, an optional multi-lingual description, and an association to Annotation to support notes (not shown on the model).
1.1	300
36.2	301	Through the inheritance the CategoryScheme comprise one or more Categorys, and the Category itself can have one or more child Category in the (inherited) hierarchy association. Note that a child Category can have only one parent Category in this association.
1.1	302
36.2	303	A partial CategoryScheme (where isPartial is set to “true”) is identical to a CategoryScheme and contains the Category and associated names and descriptions, just as in a normal CategoryScheme. However, its content is a subset of the full CategoryScheme. 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.
1.1	304
3.3	305	=== 4.6.4 Class diagram Relationship ===
1.1	306
18.7	307	[[image:image50.png]]
	308
31.6	309	Figure 24: Relationship Class diagram of the Category Scheme
1.1	310
36.2	311	The CategoryScheme can have one or more Categorys. The Category is Identifiable and has identity information. A Category can have zero or more child Categorys, thus supporting a hierarchy of Categorys. Any IdentifiableArtefact can be +categorisedBy a Category. This is achieved by means of a Categorisation. Each Categorisation can associate one IdentifiableArtefact with one Category. Multiple Categorisations can be used to build a set of IdentifiableArtefacts that are +categorisedBy the same Category. Note that there is no navigation (i.e. no embedded reference) to the Categorisation from the Category. From an implementation perspective this is necessary as Categorisation has no effect on the versioning of either the CategoryScheme or the IdentifiableArtefact.
1.1	312
3.3	313	==== 4.6.4.1 Definitions ====
1.1	314
5.2	315	(% style="width:935.835px" %)
	316	\|Class\|Feature\|(% style="width:601px" %)Description
36.2	317	\|CategoryScheme\|(((
1.1	318	Inherits from
36.2	319	//ItemScheme//
31.4	320	)))\|(% style="width:601px" %)The descriptive information for an arrangement or division of categories into groups based on characteristics, which the objects have in common.
	321	\| \|/items\|(% style="width:601px" %)Associates the categories.
36.2	322	\|Category\|(((
1.1	323	Inherits from
36.2	324	//Item//
	325	)))\|(% style="width:601px" %)An item at any level within a classification, typically tabulation categories, sections, subsections, divisions, subdivisions, groups, subgroups, classes and subclasses.
31.4	326	\| \|/hierarchy\|(% style="width:601px" %)Associates the parent and the child Category.
36.2	327	\|Categorisation\|(((
1.1	328	Inherits from
36.2	329	//MaintainableArtefact//
	330	)))\|(% style="width:601px" %)Associates an Identifable Artefact with a Category.
	331	\| \|+categorisedArtefact\|(% style="width:601px" %)Associates the Identifable Artefact.
	332	\| \|+categorisedBy\|(% style="width:601px" %)Associates the Category.
1.1	333
3.3	334	== 4.7 Organisation Scheme ==
1.1	335
3.4	336	=== 4.7.1 Class Diagram ===
1.1	337
18.7	338	[[image:image51.png]]
	339
31.6	340	Figure 25 The Organisation Scheme class diagram
1.1	341
3.4	342	=== 4.7.2 Explanation of the Diagram ===
1.1	343
3.4	344	==== 4.7.2.1 Narrative ====
1.1	345
36.2	346	The //OrganisationScheme// is abstract. It contains //Organisation// which is also abstract. The //Organisation// can have child //Organisation//.
1.1	347
36.2	348	The //OrganisationScheme// can be one of five types:
1.1	349
36.2	350	1. AgencyScheme – contains Agency which is restricted to a flat list of agencies (i.e., there is no hierarchy). Note that the SDMX system of (Maintenance) Agency can be hierarchic and this is explained in more detail in the SDMX Standards Section 6 “Technical Notes”.
	351	1. DataProviderScheme – contains DataProvider which is restricted to a flat list of agencies (i.e., there is no hierarchy).
	352	1. MetadataProviderScheme – contains MetadataProvider which is restricted to a flat list of agencies (i.e., there is no hierarchy).
	353	1. DataConsumerScheme – contains DataConsumer which is restricted to a flat list of agencies (i.e., there is no hierarchy).
	354	1. (% style="background-color:#d35400" %)OrganisationUnitScheme(%%) – contains OrganisationUnit which does inherit the /hierarchy association from Organisation.
1.1	355
36.2	356	Reference metadata can be attached to the //Organisation// by means of the metadata attachment mechanism. This mechanism is explained in the Reference Metadata section of this document (see section 7). This means that the model does not specify the specific reference metadata that can be attached to a DataProvider, MetadataProvider, DataConsumer, OrganisationUnit or Agency, except for limited Contact information.
1.1	357
36.2	358	A partial //OrganisationScheme// (where isPartial is set to “true”) is identical to an //OrganisationScheme// and contains the //Organisation// and associated names and descriptions, just as in a normal //OrganisationScheme//. However, its content is a subset of the full //OrganisationScheme//. 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//.
1.1	359
35.1	360	==== 4.7.2.2 Definitions ====
1.1	361
5.2	362	(% style="width:946.835px" %)
	363	\|Class\|Feature\|(% style="width:540px" %)Description
36.2	364	\|//OrganisationScheme//\|(((
1.1	365	Abstract Class
	366	Inherits from
36.2	367	//ItemScheme//
1.1	368	Sub classes are:
36.2	369	AgencyScheme
	370	DataProviderScheme
	371	MetadataProviderScheme
	372	DataConsumerScheme
	373	OrganisationUnitScheme
5.2	374	)))\|(% style="width:540px" %)A maintained collection of Organisations.
	375	\| \|/items\|(% style="width:540px" %)Association to the Organisations in the scheme.
36.2	376	\|//Organisation//\|(((
1.1	377	Abstract Class
	378	Inherits from
36.2	379	//Item//
1.1	380	Sub classes are:
36.2	381	Agency
	382	DataProvider
	383	MetadataProvider
	384	DataConsumer
	385	OrganisationUnit
5.2	386	)))\|(% style="width:540px" %)An organisation is a unique framework of authority within which a person or persons act, or are designated to act, towards some purpose.
36.2	387	\| \|+contact\|(% style="width:540px" %)Association to the Contact information.
5.2	388	\| \|/hierarchy\|(% style="width:540px" %)Association to child Organisations.
36.2	389	\|Contact\| \|(% style="width:540px" %)An instance of a role of an individual or an organization (or organization part or organization person) to whom an information item(s), a material object(s) and/or person(s) can be sent to or from in a specified context.
	390	\| \|name\|(% style="width:540px" %)The designation of the Contact person by a linguistic expression.
11.2	391	\| \|organisationUnit\|(% style="width:540px" %)The designation of the organisational structure by a linguistic expression, within which Contact person works.
36.2	392	\| \|responsibility\|(% style="width:540px" %)The function of the contact person with respect to the organisation role for which this person is the Contact.
	393	\| \|telephone\|(% style="width:540px" %)The telephone number of the Contact.
	394	\| \|fax\|(% style="width:540px" %)The fax number of the Contact.
	395	\| \|email\|(% style="width:540px" %)The Internet e-mail address of the Contact.
	396	\| \|X400\|(% style="width:540px" %)The X400 address of the Contact.
	397	\| \|uri\|(% style="width:540px" %)The URL address of the Contact.
	398	\|AgencyScheme\| \|(% style="width:540px" %)A maintained collection of Maintenance Agencies.
	399	\| \|/items\|(% style="width:540px" %)Association to the Maintenance Agency in the scheme.
	400	\|DataProviderScheme\| \|(% style="width:540px" %)A maintained collection of Data Providers.
	401	\| \|/items\|(% style="width:540px" %)Association to the Data Providers in the scheme.
	402	\|MetadataProviderScheme\| \|(% style="width:540px" %)A maintained collection of Metadata Providers.
5.2	403	\| \|/items\|(% style="width:540px" %)Association to the Metadata Providers in the scheme.
36.2	404	\|DataConsumerScheme\| \|(% style="width:540px" %)A maintained collection of Data Consumers.
	405	\| \|/items\|(% style="width:540px" %)Association to the Data Consumers in the scheme.
	406	\|(%%)(% style="background-color:#d35400" %)OrganisationUnitScheme\| \|(% style="width:540px" %)A maintained collection of Organisation Units.
	407	\| \|/items\|(% style="width:540px" %)Association to the Organisation Units in the scheme.
	408	\|Agency\|(((
1.1	409	Inherits from
36.2	410	//Organisation//
	411	)))\|(% style="width:540px" %)Responsible agency for maintaining artefacts such as statistical classifications, glossaries, structural metadata such as Data and Metadata Structure Definitions, Concepts and Code lists.
	412	\|DataProvider\|(((
1.1	413	Inherits from
36.2	414	//Organisation//
5.2	415	)))\|(% style="width:540px" %)An organisation that produces data.
36.2	416	\|MetadataProvider\|(((
1.1	417	Inherits from
36.2	418	//Organisation//
	419	)))\|(% style="width:540px" %)An organisation that produces reference metadata.
	420	\|DataConsumer\|(((
1.1	421	Inherits from
36.2	422	//Organisation//
5.2	423	)))\|(% style="width:540px" %)An organisation using data as input for further processing.
36.2	424	\|OrganisationUnit\|(((
1.1	425	Inherits from
36.2	426	//Organisation//
5.2	427	)))\|(% style="width:540px" %)A designation in the organisational structure.
36.2	428	\| \|/hierarchy\|(% style="width:540px" %)Association to child Organisation Units
1.1	429
35.1	430	(% style="width:946.835px" %)
	431	\|(% style="width:540px" %)
	432
3.4	433	== 4.8 Reporting Taxonomy ==
1.1	434
3.4	435	=== 4.8.1 Class Diagram ===
1.1	436
18.7	437	[[image:image52.png]]
	438
1.1	439	Figure 26: Class diagram of the Reporting Taxonomy
	440
4.1	441	=== 4.8.2 Explanation of the Diagram ===
1.1	442
4.1	443	==== 4.8.2.1 Narrative ====
1.1	444
36.2	445	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.
1.1	446
36.2	447	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:
1.1	448
	449	Section 1
	450
	451	1. linked to Datafow_1
	452	1. linked to Datafow_2
	453
	454	Section 2
	455
	456	1. linked to Datafow_3
	457	1. linked to Datafow_4
	458
36.2	459	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).
1.1	460
36.2	461	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//.
1.1	462
33.1	463	==== 4.8.2.2 Definitions ====
1.1	464
5.2	465	(% style="width:969.835px" %)
	466	\|Class\|Feature\|(% style="width:668px" %)Description
36.2	467	\|ReportingTaxonomy\|(((
1.1	468	Inherits from
36.2	469	//ItemScheme//
31.4	470	)))\|(% 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.
36.2	471	\| \|/items\|(% style="width:668px" %)Associates the Reporting Category
	472	\|ReportingCategory\|Inherits from //Item//\|(% style="width:668px" %)A component that gives structure to the report and links to data and metadata.
	473	\| \|/hierarchy\|(% style="width:668px" %)Associates child Reporting Category.
	474	\| \|+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.
	475	\| \|+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.
1.1	476
	477	----
	478
36.1	479	{{putFootnotes/}}