Skip to Content

Changes for page 4 Specific Item Schemes

Last modified by Artur on 2025/09/10 11:19
From version 16.2
edited by Helena
on 2025/05/16 22:48
Change comment: There is no comment for this version
To version 13.3
edited by Helena
on 2025/05/15 10:34
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -4,21 +4,33 @@
4 4  
5 5  == 4.1 Introduction ==
6 6  
7 -The structures that are an arrangement of objects into [[hierarchies>>doc:xwiki:Glossary.Hierarchy.WebHome]] or lists based on characteristics, and which are maintained as a group inherit from //ItemScheme//. These concrete classes are:
7 +The structures that are an arrangement of objects into hierarchies or lists based on characteristics, and which are maintained as a group inherit from //ItemScheme//. These concrete classes are:
8 8  
9 9  Codelist
10 +
10 10  ConceptScheme
12 +
11 11  CategoryScheme
12 -AgencyScheme, DataProviderScheme, MetadataProviderScheme, DataConsumerScheme, OrganisationUnitScheme, which all inherit from the abstract class //OrganisationScheme//
14 +
15 +AgencyScheme, DataProviderScheme, MetadataProviderScheme,
16 +
17 +DataConsumerScheme, OrganisationUnitScheme, which all inherit from the abstract class //OrganisationScheme//
18 +
13 13  ReportingTaxonomy
20 +
14 14  TransformationScheme
22 +
15 15  RulesetScheme
24 +
16 16  UserDefinedOperatorScheme
26 +
17 17  NamePersonalisationScheme
28 +
18 18  CustomTypeScheme
30 +
19 19  VtlMappingScheme
20 20  
21 -Note that the [[VTL>>doc:xwiki:Glossary.Validation and transformation language.WebHome]] related schemes (the last 6 of the above list) are detailed in a dedicated section below (section 15).
33 +Note that the VTL related schemes (the last 6 of the above list) are detailed in a dedicated section below (section 15).
22 22  
23 23  == 4.2 Inheritance View ==
24 24  
... ... @@ -36,30 +36,19 @@
36 36  
37 37  ==== 4.3.2.1 Narrative ====
38 38  
39 -The Codelist inherits from the //ItemScheme// and therefore has the following [[attributes>>doc:xwiki:Glossary.Attribute.WebHome]]:
51 +The Codelist inherits from the //ItemScheme// and therefore has the following attributes: id uri urn version validFrom validTo isExternalReference serviceURL structureURL isPartial
40 40  
41 -id
42 -uri
43 -urn
44 -version
45 -validFrom
46 -validTo
47 -isExternalReference
48 -serviceURL
49 -structureURL
50 -isPartial
53 +The Code inherits from //Item// and has the following attributes:
51 51  
52 -The [[Code>>doc:xwiki:Glossary.Code.WebHome]] inherits from //Item// and has the following [[attributes>>doc:xwiki:Glossary.Attribute.WebHome]]:
55 +id uri urn
53 53  
54 -id
55 -uri
56 -urn
57 +Both Codelist and Code have the association to InternationalString to support a multilingual name, an optional multi-lingual description, and an association to Annotation to support notes (not shown).
57 57  
58 -Both Codelist and [[Code>>doc:xwiki:Glossary.Code.WebHome]] have the association to InternationalString to support a multilingual name, an optional multi-lingual description, and an association to [[Annotation>>doc:xwiki:Glossary.Annotation.WebHome]] to support notes (not shown).
59 +Through the inheritance the Codelist comprise one or more Codes, and the Code itself can have one or more child Codes in the (inherited) hierarchy association. Note that a child Code can have only one parent Code in this association. A more complex Hierarhcy, which allows multiple parents is described later.
59 59  
60 -Through the inheritance the Codelist comprise one or more [[Codes>>doc:xwiki:Glossary.Code.WebHome]], and the [[Code>>doc:xwiki:Glossary.Code.WebHome]] itself can have one or more child [[Codes>>doc:xwiki:Glossary.Code.WebHome]] in the (inherited) [[hierarchy>>doc:xwiki:Glossary.Hierarchy.WebHome]] association. Note that a child [[Code>>doc:xwiki:Glossary.Code.WebHome]] can have only one parent [[Code>>doc:xwiki:Glossary.Code.WebHome]] in this association. A more complex Hierarhcy, which allows multiple parents is described later.
61 +A partial Codelist (where isPartial is set to 'true') is identical to a Codelist and contains the Code and associated names and descriptions, just as in a normal Codelist. However, its content is a subset of the full Codelist. The way this works is described in section 3.5.3.1 on
61 61  
62 -A partial Codelist (where isPartial is set to 'true') is identical to a Codelist and contains the [[Code>>doc:xwiki:Glossary.Code.WebHome]] and associated names and descriptions, just as in a normal Codelist. However, its content is a subset of the full Codelist. The way this works is described in section 3.5.3.1 on //ItemScheme//.
63 +//ItemScheme//.
63 63  
64 64  ==== 4.3.2.2 Definitions ====
65 65  
... ... @@ -86,12 +86,14 @@
86 86  
87 87  ==== 4.3.3.1 Narrative ====
88 88  
89 -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.
90 +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^^[[(% class="wikiinternallink wikiinternallink" %)^^2^^>>path:#sdfootnote2sym||name="sdfootnote2anc"]](%%)^^ 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.
90 90  
91 91  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 ,,Code,,s (via the ,,cascadeValues,, property), or even include instances of the wildcard character ‘%’ in order to point to a set of ,,Code,,s with common parts in their identifiers.
92 92  
93 93  ==== 4.3.3.2 Definitions ====
94 94  
96 +:
97 +
95 95  (((
96 96  (% style="width:753.039px" %)
97 97  |(% style="width:184px" %)**Class**|(% style="width:145px" %)**Feature**|(% style="width:421px" %)**Description**
... ... @@ -111,7 +111,7 @@
111 111  
112 112  === 4.3.4 Class Diagram – Geospatial Codelist ===
113 113  
114 -The geospatial support is implemented via an extension of the normal //Codelist//. This is illustrated in the following diagrams.
117 +The geospatial support is implemented via an extension of the normal ,,Codelist,,. This is illustrated in the following diagrams.
115 115  
116 116  [[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_472b895.jpg||height="863" width="466"]]
117 117  
... ... @@ -126,6 +126,7 @@
126 126  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:
127 127  
128 128  GeographicCodelist
132 +
129 129  GeoGridCodelist
130 130  
131 131  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.
... ... @@ -147,7 +147,9 @@
147 147  )))
148 148  |(% colspan="2" %)//GeoRefCode//|(% colspan="4" %)(((
149 149  Abstract Class Sub Classes:
154 +
150 150  GeoFeatureSet
156 +
151 151  GeoGridCode
152 152  )))|The abstract class that represents a special type of Code, which includes geospatial information.
153 153  |(% colspan="2" %)GeographicCodelist|(% colspan="4" %) |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.
... ... @@ -172,16 +172,7 @@
172 172  
173 173  A ValueList inherits from //EnumeratedList// (and hence the //MaintenableArtefact//) and thus has the following attributes:
174 174  
175 -id
176 -uri
177 -urn
178 -version
179 -validFrom
180 -validTo
181 -isExternalReference
182 -registryURL
183 -structureURL
184 -repositoryURL
181 +id// //uri// //urn// //version// //validFrom// //validTo// //isExternalReference registryURL structureURL repositoryURL
185 185  
186 186  ValueItem inherits from //EnumeratedItem//, which adds an id, with relaxed constraints, to the former.
187 187  
... ... @@ -191,18 +191,17 @@
191 191  
192 192  ==== 4.4.2.2 Definitions ====
193 193  
194 -(% style="width:749.039px" %)
195 -|**Class**|**Feature**|(% style="width:421px" %)**Description**
191 +|**Class**|**Feature**|**Description**
196 196  |ValueList|(((
197 197  Inherits from
198 198  
199 199  //EnumeratedList//
200 -)))|(% style="width:421px" %)A list from which some statistical concepts (enumerated concepts) take their values.
196 +)))|A list from which some statistical concepts (enumerated concepts) take their values.
201 201  |ValueItem|(((
202 202  Inherits from
203 203  
204 204  //EnumeratedItem//
205 -)))|(% style="width:421px" %)A language independent set of letters, numbers or symbols that represent a concept whose meaning is described in a natural language.
201 +)))|A language independent set of letters, numbers or symbols that represent a concept whose meaning is described in a natural language.
206 206  
207 207  == 4.5 Concept Scheme and Concepts ==
208 208  
... ... @@ -214,26 +214,10 @@
214 214  
215 215  === 4.5.2 Explanation of the Diagram ===
216 216  
217 -The ConceptScheme inherits from the //ItemScheme //and therefore has the following attributes:
213 +The ConceptScheme inherits from the //ItemScheme //and therefore has the following attributes: id uri urn version validFrom validTo isExternalReference registryURL structureURL repositoryURL isPartial Concept inherits from Item and has the following attributes:
218 218  
219 -id
220 -uri
221 -urn
222 -version
223 -validFrom
224 -validTo
225 -isExternalReference
226 -registryURL
227 -structureURL
228 -repositoryURL
229 -isPartial
215 +id uri urn
230 230  
231 -Concept inherits from Item and has the following attributes:
232 -
233 -id
234 -uri
235 -urn
236 -
237 237  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).
238 238  
239 239  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.
... ... @@ -260,23 +260,24 @@
260 260  
261 261  ==== 4.5.4.2 Definitions ====
262 262  
263 -(% style="width:765.039px" %)
264 -|(% style="width:204px" %)**Class**|(% style="width:222px" %)**Feature**|(% style="width:337px" %)**Description**
265 -|(% style="width:204px" %)ConceptScheme|(% style="width:222px" %)(((
243 +|**Class**|**Feature**|**Description**
244 +|ConceptScheme|(((
266 266  Inherits from
246 +
267 267  //ItemScheme//
268 -)))|(% style="width:337px" %)The descriptive information for an arrangement or division of concepts into groups based on characteristics, which the objects have in common.
269 -|(% style="width:204px" %)Concept|(% style="width:222px" %)(((
248 +)))|The descriptive information for an arrangement or division of concepts into groups based on characteristics, which the objects have in common.
249 +|Concept|(((
270 270  Inherits from
251 +
271 271  //Item//
272 -)))|(% style="width:337px" %)A concept is a unit of knowledge created by a unique combination of characteristics.
273 -|(% style="width:204px" %) |(% style="width:222px" %)/hierarchy|(% style="width:337px" %)Associates the parent and the child concept.
274 -|(% style="width:204px" %) |(% style="width:222px" %)coreRepresentation|(% style="width:337px" %)Associates a Representation.
275 -|(% style="width:204px" %) |(% style="width:222px" %)+ISOConcept|(% style="width:337px" %)Association to an ISO concept reference.
276 -|(% style="width:204px" %)ISOConceptReference|(% style="width:222px" %) |(% style="width:337px" %)The identity of an ISO concept definition.
277 -|(% style="width:204px" %) |(% style="width:222px" %)conceptAgency|(% style="width:337px" %)The maintenance agency of the concept scheme containing the concept.
278 -|(% style="width:204px" %) |(% style="width:222px" %)conceptSchemeID|(% style="width:337px" %)The identifier of the concept scheme.
279 -|(% style="width:204px" %) |(% style="width:222px" %)conceptID|(% style="width:337px" %)The identifier of the concept.
253 +)))|A concept is a unit of knowledge created by a unique combination of characteristics.
254 +| |/hierarchy|Associates the parent and the child concept.
255 +| |coreRepresentation|Associates a Representation.
256 +| |+ISOConcept|Association to an ISO concept reference.
257 +|ISOConceptReference| |The identity of an ISO concept definition.
258 +| |conceptAgency|The maintenance agency of the concept scheme containing the concept.
259 +| |conceptSchemeID|The identifier of the concept scheme.
260 +| |conceptID|The identifier of the concept.
280 280  
281 281  == 4.6 Category Scheme ==
282 282  
... ... @@ -296,22 +296,11 @@
296 296  
297 297  The categories are modelled as a hierarchical //ItemScheme//. The CategoryScheme inherits from the //ItemScheme// and has the following attributes:
298 298  
299 -id
300 -uri
301 -urn
302 -version
303 -validFrom
304 -validTo
305 -isExternalReference
306 -structureURL
307 -serviceURL
308 -isPartial
280 +id uri urn version validFrom validTo isExternalReference structureURL serviceURL isPartial
309 309  
310 310  Category inherits from //Item// and has the following attributes:
311 311  
312 -id
313 -uri
314 -urn
284 +id uri urn
315 315  
316 316  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).
317 317  
... ... @@ -329,20 +329,22 @@
329 329  
330 330  ==== 4.6.4.1 Definitions ====
331 331  
332 -(% style="width:753.039px" %)
333 333  |**Class**|(% colspan="2" %)**Feature**|**Description**
334 334  |CategoryScheme|(% colspan="2" %)(((
335 335  Inherits from
305 +
336 336  //ItemScheme//
337 337  )))|The descriptive information for an arrangement or division of categories into groups based on characteristics, which the objects have in common.
338 338  | |(% colspan="2" %)/items|Associates the categories.
339 339  |Category|(((
340 340  Inherits from
311 +
341 341  //Item//
342 342  )))|(% colspan="2" %)An item at any level within a classification, typically tabulation categories, sections, subsections, divisions, subdivisions, groups, subgroups, classes and subclasses.
343 343  | |/hierarchy|(% colspan="2" %)Associates the parent and the child Category.
344 344  |Categorisation|(((
345 345  Inherits from
317 +
346 346  //MaintainableArtefact//
347 347  )))|(% colspan="2" %)Associates an Identifable Artefact with a Category.
348 348  | |+categorisedArtefact|(% colspan="2" %)Associates the Identifable Artefact.
... ... @@ -376,75 +376,91 @@
376 376  
377 377  ==== 4.7.2.2 Definitions ====
378 378  
379 -(% style="width:763.039px" %)
380 -|**Class**|(% style="width:246px" %)**Feature**|(% style="width:336px" %)**Description**
381 -|//OrganisationScheme//|(% style="width:246px" %)(((
351 +|**Class**|**Feature**|**Description**
352 +|//OrganisationScheme//|(((
382 382  Abstract Class Inherits from
354 +
383 383  //ItemScheme//
384 384  
385 385  Sub classes are:
358 +
386 386  AgencyScheme
360 +
387 387  DataProviderScheme
362 +
388 388  MetadataProviderScheme DataConsumerScheme
364 +
389 389  OrganisationUnitScheme
390 -)))|(% style="width:336px" %)A maintained collection of Organisations.
391 -| |(% style="width:246px" %)/items|(% style="width:336px" %)(((
366 +)))|A maintained collection of Organisations.
367 +| |/items|(((
392 392  Association to the
393 393  
394 394  Organisations in the scheme.
395 395  )))
396 -|//Organisation//|(% style="width:246px" %)(((
372 +|//Organisation//|(((
397 397  Abstract Class
398 -Inherits from //Item//
399 399  
375 +Inherits from
376 +
377 +//Item//
378 +
400 400  Sub classes are:
380 +
401 401  Agency
382 +
402 402  DataProvider
384 +
403 403  MetadataProvider DataConsumer
386 +
404 404  OrganisationUnit
405 -)))|(% style="width:336px" %)An organisation is a unique framework of authority within which a person or persons act, or are designated to act, towards some purpose.
406 -| |(% style="width:246px" %)+contact|(% style="width:336px" %)Association to the Contact information.
407 -| |(% style="width:246px" %)/hierarchy|(% style="width:336px" %)Association to child Organisations.
408 -|Contact|(% style="width:246px" %) |(% style="width:336px" %)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.
409 -| |(% style="width:246px" %)name|(% style="width:336px" %)The designation of the Contact person by a linguistic expression.
410 -| |(% style="width:246px" %)organisationUnit|(% style="width:336px" %)The designation of the organisational structure by a linguistic expression, within which Contact person works.
411 -| |(% style="width:246px" %)responsibility|(% style="width:336px" %)The function of the contact person with respect to the organisation role for which this person is the Contact.
412 -| |(% style="width:246px" %)telephone|(% style="width:336px" %)The telephone number of the Contact.
413 -| |(% style="width:246px" %)fax|(% style="width:336px" %)The fax number of the Contact.
414 -| |(% style="width:246px" %)email|(% style="width:336px" %)The Internet e-mail address of the Contact.
415 -| |(% style="width:246px" %)X400|(% style="width:336px" %)The X400 address of the Contact.
416 -| |(% style="width:246px" %)uri|(% style="width:336px" %)The URL address of the Contact.
417 -|AgencyScheme|(% style="width:246px" %) |(% style="width:336px" %)A maintained collection of Maintenance Agencies.
418 -| |(% style="width:246px" %)/items|(% style="width:336px" %)Association to the Maintenance Agency in the scheme.
419 -|DataProviderScheme|(% style="width:246px" %) |(% style="width:336px" %)A maintained collection of Data Providers.
420 -| |(% style="width:246px" %)/items|(% style="width:336px" %)Association to the Data Providers in the scheme.
421 -|MetadataProviderScheme|(% style="width:246px" %) |(% style="width:336px" %)A maintained collection of Metadata Providers.
422 -| |(% style="width:246px" %)/items|(% style="width:336px" %)Association to the Metadata Providers in the scheme.
423 -|DataConsumerScheme|(% style="width:246px" %) |(% style="width:336px" %)A maintained collection of Data Consumers.
424 -| |(% style="width:246px" %)/items|(% style="width:336px" %)Association to the Data Consumers in the scheme.
425 -|OrganisationUnitScheme|(% style="width:246px" %) |(% style="width:336px" %)A maintained collection of Organisation Units.
426 -| |(% style="width:246px" %)/items|(% style="width:336px" %)Association to the Organisation Units in the scheme.
427 -|Agency|(% style="width:246px" %)(((
388 +)))|An organisation is a unique framework of authority within which a person or persons act, or are designated to act, towards some purpose.
389 +| |+contact|Association to the Contact information.
390 +| |/hierarchy|Association to child Organisations.
391 +|Contact| |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.
392 +| |name|The designation of the Contact person by a linguistic expression.
393 +| |organisationUnit|The designation of the organisational structure by a linguistic expression, within which Contact person works.
394 +| |responsibility|The function of the contact person with respect to the organisation role for which this person is the Contact.
395 +| |telephone|The telephone number of the Contact.
396 +| |fax|The fax number of the Contact.
397 +| |email|The Internet e-mail address of the Contact.
398 +| |X400|The X400 address of the Contact.
399 +| |uri|The URL address of the Contact.
400 +|AgencyScheme| |A maintained collection of Maintenance Agencies.
401 +| |/items|Association to the Maintenance Agency in the scheme.
402 +|DataProviderScheme| |A maintained collection of Data Providers.
403 +| |/items|Association to the Data Providers in the scheme.
404 +|MetadataProviderScheme| |A maintained collection of Metadata Providers.
405 +| |/items|Association to the Metadata Providers in the scheme.
406 +|DataConsumerScheme| |A maintained collection of Data Consumers.
407 +| |/items|Association to the Data Consumers in the scheme.
408 +|OrganisationUnitScheme| |A maintained collection of Organisation Units.
409 +| |/items|Association to the Organisation Units in the scheme.
410 +|Agency|(((
428 428  Inherits from
412 +
429 429  //Organisation//
430 -)))|(% style="width:336px" %)Responsible agency for maintaining artefacts such as statistical classifications, glossaries, structural metadata such as Data and Metadata Structure Definitions, Concepts and Code lists.
431 -|DataProvider|(% style="width:246px" %)(((
414 +)))|Responsible agency for maintaining artefacts such as statistical classifications, glossaries, structural metadata such as Data and Metadata Structure Definitions, Concepts and Code lists.
415 +|DataProvider|(((
432 432  Inherits from
417 +
433 433  //Organisation//
434 -)))|(% style="width:336px" %)An organisation that produces data.
435 -|MetadataProvider|(% style="width:246px" %)(((
419 +)))|An organisation that produces data.
420 +|MetadataProvider|(((
436 436  Inherits from
422 +
437 437  //Organisation//
438 -)))|(% style="width:336px" %)An organisation that produces reference metadata.
439 -|DataConsumer|(% style="width:246px" %)(((
424 +)))|An organisation that produces reference metadata.
425 +|DataConsumer|(((
440 440  Inherits from
427 +
441 441  //Organisation//
442 -)))|(% style="width:336px" %)An organisation using data as input for further processing.
443 -|OrganisationUnit|(% style="width:246px" %)(((
429 +)))|An organisation using data as input for further processing.
430 +|OrganisationUnit|(((
444 444  Inherits from
432 +
445 445  //Organisation//
446 -)))|(% style="width:336px" %)A designation in the organisational structure.
447 -| |(% style="width:246px" %)/hierarchy|(% style="width:336px" %)Association to child Organisation Units
434 +)))|A designation in the organisational structure.
435 +| |/hierarchy|Association to child Organisation Units
448 448  
449 449  == 4.8 Reporting Taxonomy ==
450 450  
... ... @@ -478,21 +478,22 @@
478 478  
479 479  ==== 4.8.2.2 Definitions ====
480 480  
481 -(% style="width:759.039px" %)
482 -|(% style="width:177px" %)**Class**|(% style="width:152px" %)**Feature**|(% style="width:428px" %)**Description**
483 -|(% style="width:177px" %)ReportingTaxonomy|(% style="width:152px" %)(((
469 +|**Class**|**Feature**|**Description**
470 +|ReportingTaxonomy|(((
484 484  Inherits from
472 +
485 485  //ItemScheme//
486 -)))|(% style="width:428px" %)A scheme which defines the composition structure of a data report where each component can be described by an independent Dataflow or Metadataflow.
487 -|(% style="width:177px" %) |(% style="width:152px" %)/items|(% style="width:428px" %)Associates the Reporting Category
488 -|(% style="width:177px" %)ReportingCategory|(% style="width:152px" %)(((
474 +)))|A scheme which defines the composition structure of a data report where each component can be described by an independent Dataflow or Metadataflow.
475 +| |/items|Associates the Reporting Category
476 +|ReportingCategory|(((
489 489  Inherits from
478 +
490 490  //Item//
491 -)))|(% style="width:428px" %)A component that gives structure to the report and links to data and metadata.
492 -|(% style="width:177px" %) |(% style="width:152px" %)/hierarchy|(% style="width:428px" %)Associates child Reporting Category.
493 -|(% style="width:177px" %) |(% style="width:152px" %)+flow|(% style="width:428px" %)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.
494 -|(% style="width:177px" %) |(% style="width:152px" %)+structure|(% style="width:428px" %)(((
495 -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.
496 -)))
480 +)))|A component that gives structure to the report and links to data and metadata.
481 +| |/hierarchy|Associates child Reporting Category.
482 +| |+flow|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.
483 +| |+structure|(((
484 +Association to the Data Structure
497 497  
498 -{{putFootnotes/}}
486 +Definition and Metadata Structure Definitions which define the structural metadata describing the data and metadata that are contained at this part of the report.
487 +)))