Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 4.2
edited by Elena
on 2025/06/16 16:22
Change comment: There is no comment for this version
To version 4.1
edited by Artur
on 2025/05/27 15:51
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.elenasemanticproorg
1 +xwiki:XWiki.arturkryazhev
Tags
... ... @@ -1,1 +1,0 @@
1 -Annotation|Artefact|Attribute|Attribute relationship|Code|Code list|Comparability|Component|Concept|Concept scheme|Confidentiality|Confidentiality - status|Contact phone number|Data provider|Data set|Data structure definition|Dataflow|Decimals|Dimension|Facet|Hierarchy|Item scheme|Measure|Metadata set|Metadata structure definition|Provision agreement|Reference area|Reference metadata|Representation|SDMX Information Model|SDMX-ML|Statistical data and metadata exchange|Structural metadata|Title|Unit of measure
Content
... ... @@ -10,20 +10,20 @@
10 10  
11 11  == 4.2 Basics ==
12 12  
13 -Fundamental to defining a structure definition is defining the [[concepts>>doc:Glossary.Concept.WebHome]] which describe the information contained in the data or metadata and the [[code lists>>doc:sdmx:Glossary.Code list.WebHome]] which provide specific values for these [[concepts>>doc:Glossary.Concept.WebHome]].
13 +Fundamental to defining a structure definition is defining the (% style="color:#e74c3c" %)concepts(%%) which describe the information contained in the data or metadata and the [[code lists>>doc:sdmx:Glossary.Code list.WebHome]] which provide specific values for these (% style="color:#e74c3c" %)concepts(%%).
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:#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 (% 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.