Skip to Content
Last modified by Helena on 2025/09/10 11:19
From version 6.4
edited by Elena
on 2025/06/16 17:38
Change comment: There is no comment for this version
To version 7.1
edited by Elena
on 2025/06/16 17:44
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -186,7 +186,7 @@
186 186  
187 187  ===== //4.4.1.1.4 Constraint Content Target// =====
188 188  
189 -The (% style="color:#e74c3c" %)constraint(%%) content target is used to attach metadata to data by referencing an attachment (% style="color:#e74c3c" %)constraint(%%). This attachment (% style="color:#e74c3c" %)constraint(%%) in turn defines the [[data set>>doc:sdmx:Glossary.Data set.WebHome]](s) and keys to which the metadata applies. This is equivalent to using the [[data set>>doc:sdmx:Glossary.Data set.WebHome]] or identifiable object target along with the key descriptor values target. The difference is that the attachment (% style="color:#e74c3c" %)constraint(%%) allows the target set to be defined once, and be reused by multiple reports, whereas the former method would require that the [[data set>>doc:sdmx:Glossary.Data set.WebHome]] (or equivalent data structure, [[dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]], or [[provision agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]]) reference and key descriptor value set be repeated for each report. Only one (% style="color:#e74c3c" %)constraint(%%) content target can occur within a metadata target.
189 +The [[constraint>>doc:Glossary.Constraint.WebHome]] content target is used to attach metadata to data by referencing an attachment [[constraint>>doc:Glossary.Constraint.WebHome]]. This attachment [[constraint>>doc:Glossary.Constraint.WebHome]] turn defines the [[data set>>doc:sdmx:Glossary.Data set.WebHome]](s) and keys to which the metadata applies. This is equivalent to using the [[data set>>doc:sdmx:Glossary.Data set.WebHome]] or identifiable object target along with the key descriptor values target. The difference is that the attachment [[constraint>>doc:Glossary.Constraint.WebHome]] allows the target set to be defined once, and be reused by multiple reports, whereas the former method would require that the [[data set>>doc:sdmx:Glossary.Data set.WebHome]] (or equivalent data structure, [[dataflow>>doc:sdmx:Glossary.Dataflow.WebHome]], or [[provision agreement>>doc:sdmx:Glossary.Provision agreement.WebHome]]) reference and key descriptor value set be repeated for each report. Only one [[constraint>>doc:Glossary.Constraint.WebHome]] content target can occur within a metadata target.
190 190  
191 191  ===== //4.4.1.1.5 Report Period Target// =====
192 192  
... ... @@ -207,11 +207,11 @@
207 207  
208 208  ===== //4.4.1.2.1 Metadata Attribute// =====
209 209  
210 -A metadata [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] is [[component>>doc:sdmx:Glossary.Component.WebHome]] of the content of a metadata report. Similar to a data [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] in a data structure, the metadata [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] takes its semantic from a (% style="color:#e74c3c" %)concept(%%). This (% style="color:#e74c3c" %)concept(%%) serves to define the meaning of the information contained in the report. As with data structure [[components>>doc:sdmx:Glossary.Component.WebHome]], it is important to make use of common (% style="color:#e74c3c" %)concepts(%%) whenever possible, as this makes the metadata relatable to other metadata reports.
210 +A metadata [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] is [[component>>doc:sdmx:Glossary.Component.WebHome]] of the content of a metadata report. Similar to a data [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] in a data structure, the metadata [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] takes its semantic from a (% style="color:#e74c3c" %)[[concept>>doc:sdmx:Glossary.Concept.WebHome]](%%). This [[concept>>doc:sdmx:Glossary.Concept.WebHome]] serves to define the meaning of the information contained in the report. As with data structure [[components>>doc:sdmx:Glossary.Component.WebHome]], it is important to make use of common (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%) whenever possible, as this makes the metadata relatable to other metadata reports.
211 211  
212 -The content of a metadata [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] can be a value and/or other metadata [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]]. The value of a metadata [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] can serve a number of purposes. First, as with a data [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] it can be an enumerated value from a [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[code list>>doc:sdmx:Glossary.Code list.WebHome]]. It can also be a noncoded value of any given data type. Where the metadata [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] value differs from that of a data [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] is that if the value is textual, it can be represented in parallel language values, and if necessary be structured using XHTML. It is not necessary that a metadata [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] has a value, as it might only serve to contain other metadata [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] for the purpose of organising metadata reports (in which case the metadata [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] is designated as “isPresentational” indicating that no value is expected to be reported for the metadata [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] in a report).l.
212 +The content of a metadata [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] can be a value and/or other metadata [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]]. The value of a metadata [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] can serve a number of purposes. First, as with a data [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] it can be an enumerated value from a [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] [[code list>>doc:sdmx:Glossary.Code list.WebHome]]. It can also be a noncoded value of any given data type. Where the metadata [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] value differs from that of a data [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] is that if the value is textual, it can be represented in parallel language values, and if necessary be structured using XHTML. It is not necessary that a metadata [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] has a value, as it might only serve to contain other metadata [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] for the purpose of organising metadata reports (in which case the metadata [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] is designated as “isPresentational” indicating that no value is expected to be reported for the metadata [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] in a report).
213 213  
214 -Metadata [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] are not reusable across various (% style="color:#e74c3c" %)levels(%%) of a report structure. If an [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] is intended to occur at multiple (% style="color:#e74c3c" %)levels(%%), it must be redefined at each (% style="color:#e74c3c" %)level(%%). However, the identification of a metadata [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] is only required to be unique within the scope within which it is defined. Therefore, if the intention is to reuse a metadata [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] at different (% style="color:#e74c3c" %)levels(%%), it is recommended that the same identification be used to convey this intention. It should also be noted that within a scope, a metadata [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] can have cardinality (minimum and maximum number of occurrences). This allows metadata [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] to be repeated at various (% style="color:#e74c3c" %)levels(%%), as well as giving the report structure the ability to enforce content requirements.
214 +Metadata [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] are not reusable across various levels of a report structure. If an [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] is intended to occur at multiple levels, it must be redefined at each level. However, the identification of a metadata [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] is only required to be unique within the scope within which it is defined. Therefore, if the intention is to reuse a metadata [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] at different levels, it is recommended that the same identification be used to convey this intention. It should also be noted that within a scope, a metadata [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] can have cardinality (minimum and maximum number of occurrences). This allows metadata [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] to be repeated at various levels, as well as giving the report structure the ability to enforce content requirements.
215 215  
216 216  === 4.4.2 Metadata Sets ===
217 217  
... ... @@ -219,7 +219,7 @@
219 219  
220 220  The manner in which a metadata report is related to an object is through the specification of its target. The metadata structure defines the possible types of targets for a given report structure, and an instance of a report uses one of these target types to identify the actual target of the metadata. The target is essentially a collection of references to data or [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] and possibly a period to which the report applies. It is assumed that any system processing metadata reports will be able to resolve these references, or perhaps more appropriately, any system working with data or [[structural metadata>>doc:sdmx:Glossary.Structural metadata.WebHome]] will be able to process the related metadata reports.
221 221  
222 -The actual content of the report is always contained in an [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] set. This [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] set is the collection of metadata [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] for which values are provided. As with data, the key to a useful metadata report is understanding what is being reported. This comes down to effective (% style="color:#e74c3c" %)concept(%%) usage. The content of any report is essentially made up of values reported against (% style="color:#e74c3c" %)concepts(%%). In order for systems to understand the meaning of the metadata, they must understand the (% style="color:#e74c3c" %)concepts(%%).
222 +The actual content of the report is always contained in an [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] set. This [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] set is the collection of metadata [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] for which values are provided. As with data, the key to a useful metadata report is understanding what is being reported. This comes down to effective (% style="color:#e74c3c" %)[[concept>>doc:sdmx:Glossary.Concept.WebHome]](%%) usage. The content of any report is essentially made up of values reported against (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%). In order for systems to understand the meaning of the metadata, they must understand the (% style="color:#e74c3c" %)[[concepts>>doc:sdmx:Glossary.Concept.WebHome]](%%).
223 223  
224 224  With the [[metadata structure definition>>doc:sdmx:Glossary.Metadata structure definition.WebHome]], the content of any report can be evaluated for completeness and validity. From the metadata structure, one can determine if all necessary metadata [[attributes>>doc:sdmx:Glossary.Attribute.WebHome]] are present for a given report structure and if the values assigned to them are allowable based on the [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] definition.
225 225