Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 5.1
edited by Elena
on 2025/06/16 16:27
Change comment: There is no comment for this version
To version 5.4
edited by Elena
on 2025/06/16 16:33
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -14,30 +14,30 @@
14 14  
15 15  === 4.2.1 Defining Concepts ===
16 16  
17 -Any [[component>>doc:sdmx:Glossary.Component.WebHome]] of a data or [[metadata structure definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]] must take its semantic from a [[concept>>xwiki:Main.concept]]. This concept is important in that it:
17 +Any [[component>>doc:sdmx:Glossary.Component.WebHome]] of a data or [[metadata structure definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]] must take its semantic from a (% style="color:#e74c3c" %)concept(%%). This (% style="color:#e74c3c" %)concept(%%) is important in that it:
18 18  
19 19  1. Provides a detailed definition of the [[component>>doc:sdmx:Glossary.Component.WebHome]] which describes the structure of the data or metadata.
20 -1. Can allow data and metadata for different structures to be comparable when [[concepts>>xwiki:Main.concepts]] are reused.
20 +1. Can allow data and metadata for different structures to be comparable when (% style="color:#e74c3c" %)concepts(%%) are reused.
21 21  
22 -It is important when defining [[concepts>>xwiki:Main.concepts]] to first consider [[concepts>>xwiki:Main.concepts]] which are already defined within a given community, whether it be the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] community as a whole or a smaller community of users in a particular sector. As general rule, one should not define a new [[concept>>xwiki:Main.concept]] when an existing [[concept>>xwiki:Main.concept]] will suffice. By reusing an existing [[concept>>xwiki:Main.concept]], data and metadata are more easily understood in a wider range of applications. This leads to greater interoperability and [[comparability>>doc:sdmx:Glossary.Comparability.WebHome]] of data/metadata.
22 +It is important when defining (% style="color:#e74c3c" %)concepts(%%) to first consider (% style="color:#e74c3c" %)concepts(%%) which are already defined within a given community, whether it be the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] community as a whole or a smaller community of users in a particular sector. As general rule, one should not define a new (% style="color:#e74c3c" %)concept(%%) when an existing (% style="color:#e74c3c" %)concept(%%) will suffice. By reusing an existing (% style="color:#e74c3c" %)concept(%%), data and metadata are more easily understood in a wider range of applications. This leads to greater interoperability and [[comparability>>doc:sdmx:Glossary.Comparability.WebHome]] of data/metadata.
23 23  
24 -Assuming new [[concepts>>xwiki:Main.concepts]] are to be defined, the first step is to determine an appropriate grouping for [[concepts>>xwiki:Main.concepts]]. In [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]], all [[concepts>>xwiki:Main.concepts]] are defined in schemes. These schemes serve to group similar [[concepts>>xwiki:Main.concepts]] into groups which can be useful for maintenance purposes. One possible distinction to be used to determine the grouping of [[concepts>>xwiki:Main.concepts]] is their intended usage. If [[concepts>>xwiki:Main.concepts]] are only to be used for metadata, it may be best to group these into a single scheme. Similarly, if [[concepts >>xwiki:Main.concepts]]are only to be used for data, these too may be grouped into a single scheme. It is important to consider that [[concepts >>xwiki:Main.concepts]]themselves are not versioned, rather the schemes in which they are defined are versioned. This means that if any property of a[[ concept >>xwiki:Main.concept]]is to change, the (% style="color:#e74c3c" %)version(%%) of the scheme in which it is defined must change if the scheme is marked as “final”. This in effect (% style="color:#e74c3c" %)versions(%%) all [[concepts>>xwiki:Main.concepts]] defined in that scheme. Therefore, when grouping [[concepts>>xwiki:Main.concepts]] into schemes it is important to consider the stability of the [[concept >>xwiki:Main.concept]]definitions.
24 +Assuming new (% style="color:#e74c3c" %)concepts(%%) are to be defined, the first step is to determine an appropriate grouping for (% style="color:#e74c3c" %)concepts(%%). In [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]], all (% style="color:#e74c3c" %)concepts(%%) are defined in schemes. These schemes serve to group similar (% style="color:#e74c3c" %)concepts(%%) into groups which can be useful for maintenance purposes. One possible distinction to be used to determine the grouping of (% style="color:#e74c3c" %)concepts(%%) is their intended usage. If (% style="color:#e74c3c" %)concepts(%%) are only to be used for metadata, it may be best to group these into a single scheme. Similarly, if (% style="color:#e74c3c" %)concepts(%%) are only to be used for data, these too may be grouped into a single scheme. It is important to consider that (% style="color:#e74c3c" %)concepts(%%) themselves are not versioned, rather the schemes in which they are defined are versioned. This means that if any property of a (% style="color:#e74c3c" %)concept(%%) is to change, the (% style="color: rgb(231, 76, 60); color: rgb(231, 76, 60)" %)version(%%) of the scheme in which it is defined must change if the scheme is marked as “final”. This in effect (% style="color: rgb(231, 76, 60); color: rgb(231, 76, 60)" %)versions(%%) all (% style="color:#e74c3c" %)concepts(%%) defined in that scheme. Therefore, when grouping (% style="color:#e74c3c" %)concepts(%%) into schemes it is important to consider the stability of the (% style="color:#e74c3c" %)concept(%%) definitions.
25 25  
26 -A [[concept>>xwiki:Main.concept]] itself consists of three main [[components>>doc:sdmx:Glossary.Component.WebHome]]:
26 +A (% style="color:#e74c3c" %)concept(%%) itself consists of three main [[components>>doc:sdmx:Glossary.Component.WebHome]]:
27 27  
28 28  1. Its identification, which must be unique within the scheme.
29 29  1. Its name.
30 30  1. Its description.
31 31  
32 -Note that the description is not mandatory, but is highly recommended in order to provide a more complete definition of a [[concept>>xwiki:Main.concept]]. When you consider that these [[concepts>>xwiki:Main.concepts]] are the building blocks which are constructed to define the structure of all data and metadata in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]], it should be apparent why complete definitions are important.
32 +Note that the description is not mandatory, but is highly recommended in order to provide a more complete definition of a (% style="color:#e74c3c" %)concept(%%). When you consider that these (% style="color:#e74c3c" %)concepts(%%) are the building blocks which are constructed to define the structure of all data and metadata in [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]], it should be apparent why complete definitions are important.
33 33  
34 -In addition to the basic definition properties of the [[concept>>xwiki:Main.concept]], a [[concept>>xwiki:Main.concept]] can reference another [[concept>>xwiki:Main.concept]] from within the same scheme as its parent (% style="color:#e74c3c" %)concept(%%). The exact nature of this parent child relationship is not strictly enforced by the standard, but it is typically used to denote the child (% style="color:#e74c3c" %)concept(%%) is a specialization of the parent. For example, one may have a (% style="color:#e74c3c" %)concept(%%) which defines a [[reference area>>doc:sdmx:Glossary.Reference area.WebHome]] (% style="color:#e74c3c" %)concept(%%) as a "geographic area to which a measured statistical phenomenon relates". In order to allow for more specific types of [[references areas>>doc:sdmx:Glossary.Reference area.WebHome]], one might define (% style="color:#e74c3c" %)concepts(%%) for countries as well as groups of geographically similar countries (e.g. continents) and political countries (e.g. military or economic alliances). These child (% style="color:#e74c3c" %)concepts(%%) could reference the [[reference area>>doc:sdmx:Glossary.Reference area.WebHome]] (% style="color:#e74c3c" %)concept(%%) as a parent in order to note that they are specializations of a [[reference area>>doc:sdmx:Glossary.Reference area.WebHome]]". An example of this can be seen in the Common Structures sample set. In this sample the [[confidentiality status>>doc:sdmx:Glossary.Confidentiality - status.WebHome]] references the [[confidentiality>>doc:sdmx:Glossary.Confidentiality.WebHome]] (% style="color:#e74c3c" %)concept(%%) as a parent. The status is a specialization of a general [[confidentiality>>doc:sdmx:Glossary.Confidentiality.WebHome]] (% style="color:#e74c3c" %)concept(%%).
34 +In addition to the basic definition properties of the (% style="color:#e74c3c" %)concept(%%), a (% style="color:#e74c3c" %)concept(%%) can reference another (% style="color:#e74c3c" %)concept(%%) from within the same scheme as its parent (% style="color: rgb(231, 76, 60); color: rgb(231, 76, 60)" %)concept(%%). The exact nature of this parent child relationship is not strictly enforced by the standard, but it is typically used to denote the child (% style="color: rgb(231, 76, 60); color: rgb(231, 76, 60)" %)concept(%%) is a specialization of the parent. For example, one may have a (% style="color: rgb(231, 76, 60); color: rgb(231, 76, 60)" %)concept(%%) which defines a [[reference area>>doc:sdmx:Glossary.Reference area.WebHome]] (% style="color: rgb(231, 76, 60); color: rgb(231, 76, 60)" %)concept(%%) as a "geographic area to which a measured statistical phenomenon relates". In order to allow for more specific types of [[references areas>>doc:sdmx:Glossary.Reference area.WebHome]], one might define (% style="color: rgb(231, 76, 60); color: rgb(231, 76, 60)" %)concepts(%%) for countries as well as groups of geographically similar countries (e.g. continents) and political countries (e.g. military or economic alliances). These child (% style="color: rgb(231, 76, 60); color: rgb(231, 76, 60)" %)concepts(%%) could reference the [[reference area>>doc:sdmx:Glossary.Reference area.WebHome]] (% style="color: rgb(231, 76, 60); color: rgb(231, 76, 60)" %)concept(%%) as a parent in order to note that they are specializations of a [[reference area>>doc:sdmx:Glossary.Reference area.WebHome]]". An example of this can be seen in the Common Structures sample set. In this sample the [[confidentiality status>>doc:sdmx:Glossary.Confidentiality - status.WebHome]] references the [[confidentiality>>doc:sdmx:Glossary.Confidentiality.WebHome]] (% style="color: rgb(231, 76, 60); color: rgb(231, 76, 60)" %)concept(%%) as a parent. The status is a specialization of a general [[confidentiality>>doc:sdmx:Glossary.Confidentiality.WebHome]] (% style="color: rgb(231, 76, 60); color: rgb(231, 76, 60)" %)concept(%%).
35 35  
36 -< note the test for whether something is a specialization is to ask the question “is xxx a type of yyy” In the Cross Domain (% style="color:#e74c3c" %)Concepts(%%) the question would be “Is [[confidentiality status>>doc:sdmx:Glossary.Confidentiality - status.WebHome]] a type of [[confidentiality>>doc:sdmx:Glossary.Confidentiality.WebHome]]”. The answer is “no”. The problem here is that the cross domain (% style="color:#e74c3c" %)concepts(%%) are grouped, often in a structural and not semantic sense. This, unfortunately, is carried over in the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] and needs to be rectified.>
36 +< note the test for whether something is a specialization is to ask the question “is xxx a type of yyy” In the Cross Domain (% style="color: rgb(231, 76, 60); color: rgb(231, 76, 60)" %)Concepts(%%) the question would be “Is [[confidentiality status>>doc:sdmx:Glossary.Confidentiality - status.WebHome]] a type of [[confidentiality>>doc:sdmx:Glossary.Confidentiality.WebHome]]”. The answer is “no”. The problem here is that the cross domain (% style="color: rgb(231, 76, 60); color: rgb(231, 76, 60)" %)concepts(%%) are grouped, often in a structural and not semantic sense. This, unfortunately, is carried over in the [[SDMX-ML>>doc:sdmx:Glossary.SDMX-ML.WebHome]] and needs to be rectified.>
37 37  
38 -When a [[component>>doc:sdmx:Glossary.Component.WebHome]] in a structure definition takes its semantic from a (% style="color:#e74c3c" %)concept(%%), it always is provided a value in the data or metadata reported against the structure. A (% style="color:#e74c3c" %)concept(%%) can define the default nature of these values. This is done with a definition of a //core [[representation>>doc:sdmx:Glossary.Representation.WebHome]]//. The core [[representation>>doc:sdmx:Glossary.Representation.WebHome]] can either be a un-coded text format, in which a data type is defined along with [[facets>>doc:sdmx:Glossary.Facet.WebHome]] which serve to further restrict that data type, or a coded enumeration in which a [[code list>>doc:sdmx:Glossary.Code list.WebHome]] can be referenced. In the case where an enumerated core [[representation>>doc:sdmx:Glossary.Representation.WebHome]] is defined, the nature of the enumeration values can be described in the same manner that the un-coded text format could be. Note that if a (% style="color:#e74c3c" %)concept(%%) is not provided a core [[representation>>doc:sdmx:Glossary.Representation.WebHome]], it is assumed to have an unbounded value set (i.e. it could be represented by a variety of [[code lists>>doc:sdmx:Glossary.Code list.WebHome]] or un-enumerated formats when used in a [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] or [[MSD>>doc:sdmx:Glossary.Metadata structure definition.WebHome]]). However, as with any core [[representation>>doc:sdmx:Glossary.Representation.WebHome]], a usage of the (% style="color:#e74c3c" %)concept(%%) in a structure definition can always provide a local [[representation>>doc:sdmx:Glossary.Representation.WebHome]] which overrides the core [[representation>>doc:sdmx:Glossary.Representation.WebHome]] of the (% style="color:#e74c3c" %)concept(%%).
38 +When a [[component>>doc:sdmx:Glossary.Component.WebHome]] in a structure definition takes its semantic from a (% style="color: rgb(231, 76, 60); color: rgb(231, 76, 60)" %)concept(%%), it always is provided a value in the data or metadata reported against the structure. A (% style="color: rgb(231, 76, 60); color: rgb(231, 76, 60)" %)concept(%%) can define the default nature of these values. This is done with a definition of a //core [[representation>>doc:sdmx:Glossary.Representation.WebHome]]//. The core [[representation>>doc:sdmx:Glossary.Representation.WebHome]] can either be a un-coded text format, in which a data type is defined along with [[facets>>doc:sdmx:Glossary.Facet.WebHome]] which serve to further restrict that data type, or a coded enumeration in which a [[code list>>doc:sdmx:Glossary.Code list.WebHome]] can be referenced. In the case where an enumerated core [[representation>>doc:sdmx:Glossary.Representation.WebHome]] is defined, the nature of the enumeration values can be described in the same manner that the un-coded text format could be. Note that if a (% style="color: rgb(231, 76, 60); color: rgb(231, 76, 60)" %)concept(%%) is not provided a core [[representation>>doc:sdmx:Glossary.Representation.WebHome]], it is assumed to have an unbounded value set (i.e. it could be represented by a variety of [[code lists>>doc:sdmx:Glossary.Code list.WebHome]] or un-enumerated formats when used in a [[DSD>>doc:sdmx:Glossary.Data structure definition.WebHome]] or [[MSD>>doc:sdmx:Glossary.Metadata structure definition.WebHome]]). However, as with any core [[representation>>doc:sdmx:Glossary.Representation.WebHome]], a usage of the (% style="color: rgb(231, 76, 60); color: rgb(231, 76, 60)" %)concept(%%) in a structure definition can always provide a local [[representation>>doc:sdmx:Glossary.Representation.WebHome]] which overrides the core [[representation>>doc:sdmx:Glossary.Representation.WebHome]] of the (% style="color: rgb(231, 76, 60); color: rgb(231, 76, 60)" %)concept(%%).
39 39  
40 -Finally, in order to provide a more complete conceptual definition, the (% style="color:#e74c3c" %)concept(%%) can reference an ISO 11179 (% style="color:#e74c3c" %)concept(%%). The intention of this reference is to reference the ISO 11179 (% style="color:#e74c3c" %)concept(%%) definition from which this [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] (% style="color:#e74c3c" %)concept(%%) definition is derived.
40 +Finally, in order to provide a more complete conceptual definition, the (% style="color: rgb(231, 76, 60); color: rgb(231, 76, 60)" %)concept(%%) can reference an ISO 11179 (% style="color: rgb(231, 76, 60); color: rgb(231, 76, 60)" %)concept(%%). The intention of this reference is to reference the ISO 11179 (% style="color: rgb(231, 76, 60); color: rgb(231, 76, 60)" %)concept(%%) definition from which this [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] (% style="color: rgb(231, 76, 60); color: rgb(231, 76, 60)" %)concept(%%) definition is derived.
41 41  
42 42  === 4.2.2 Defining Code Lists ===
43 43