Changes for page 4 Data and Metadata Creation and Reporting

Summary

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

Details

Page properties

Content

...	...	@@ -14,24 +14,24 @@
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. 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 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 to first consider 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 when an existing concept will suffice. By reusing an existing 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 are to be defined, the first step is to determine an appropriate grouping for concepts. In [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]], all concepts are defined in schemes. These schemes serve to group similar concepts into groups which can be useful for maintenance purposes. One possible distinction to be used to determine the grouping of concepts is their intended usage. If concepts are only to be used for metadata, it may be best to group these into a single scheme. Similarly, if concepts are only to be used for data, these too may be grouped into a single scheme. It is important to consider that concepts themselves are not versioned, rather the schemes in which they are defined are versioned. This means that if any property of a 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 defined in that scheme. Therefore, when grouping concepts into schemes it is important to consider the stability of the 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 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. When you consider that these 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, a concept can reference another 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:#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(%%).
35	35
36	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.>
37	37