Skip to Content

Wiki source code of 4 Specific Item Schemes

Version 3.1 by Helena on 2025/05/15 09:59
Show last authors
1 = 4 Specific Item Schemes =
2
3 == 4.1 Introduction ==
4
5 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:
6
7 Codelist
8
9 ConceptScheme
10
11 CategoryScheme
12
13 AgencyScheme, DataProviderScheme, MetadataProviderScheme,
14
15 DataConsumerScheme, OrganisationUnitScheme, which all inherit from the abstract class //OrganisationScheme//
16
17 ReportingTaxonomy
18
19 TransformationScheme
20
21 RulesetScheme
22
23 UserDefinedOperatorScheme
24
25 NamePersonalisationScheme
26
27 CustomTypeScheme
28
29 VtlMappingScheme
30
31 Note that the VTL related schemes (the last 6 of the above list) are detailed in a dedicated section below (section 15).
32
33 == 4.2 Inheritance View ==
34
35 The inheritance and relationship views are shown together in each of the diagrams in the specific sections below.
36
37 == 4.3 Codelist ==
38
39 === 4.3.1 Class Diagram ===
40
41 [[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_98388f74.jpg||height="674" width="433"]]
42
43 **Figure 16: Class diagram of the Codelist**
44
45 === 4.3.2 Explanation of the Diagram ===
46
47 ==== 4.3.2.1 Narrative ====
48
49 The Codelist inherits from the //ItemScheme// and therefore has the following attributes: id uri urn version validFrom validTo isExternalReference serviceURL structureURL isPartial
50
51 The Code inherits from //Item// and has the following attributes:
52
53 id uri urn
54
55 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).
56
57 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.
58
59 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
60
61 //ItemScheme//.
62
63 ==== 4.3.2.2 Definitions ====
64
65 |**Class**|**Feature**|**Description**
66 |Codelist|(((
67 Inherits from
68
69 //ItemScheme//
70 )))|A list from which some statistical concepts (coded concepts) take their values.
71 |Code|(((
72 Inherits from
73
74 Item
75 )))|A language independent set of letters, numbers or symbols that represent a concept whose meaning is described in a natural language.
76 ||hierarchy|Associates the parent and the child codes.
77 ||extends|Associates a Codelist with any Codelists that it may extend.
78
79 === 4.3.3 Class Diagram – Codelist Extension ===
80
81 [[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_e758cbcf.jpg||height="546" width="559"]]
82
83 **Figure 17: Class diagram for Codelist Extension**
84
85 ==== 4.3.3.1 Narrative ====
86
87 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^^[[^^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.
88
89 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.
90
91 ==== 4.3.3.2 Definitions ====
92
93 :
94
95 (((
96 |**Class**|**Feature**|**Description**
97 |CodelistExtension||The association between Codelists that may extend other Codelists.
98 ||prefix|A prefix to be used for a Codelist used in a extension, in order to avoid Code Conflicts.
99 ||sequence|The order that will be used when extending a Codelist, for resolving Code conflicts. The latest Codelist used overrides any previous Codelist.
100 |InclusiveCodeSelection||The subset of Codes to be included when extending a Codelist.
101 |ExclusiveCodeSelection||The subset of Codes to be excluded when extending a Codelist.
102 |MemberValue|(((
103 Inherits from:
104
105 //SelectionValue//
106 )))|A collection of values based on Codes and their children.
107 ||cascadeValues|A property to indicate if the child Codes of the selected Code shall be included in the selection. It is also possible to include children and exclude the Code by using the 'excluderoot' value.
108 ||value|The value of the Code to include in the selection. It may include the ‘%’ character as a wildcard.
109 )))
110
111 === 4.3.4 Class Diagram – Geospatial Codelist ===
112
113 The geospatial support is implemented via an extension of the normal ,,Codelist,,. This is illustrated in the following diagrams.
114
115 [[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_472b895.jpg||height="863" width="466"]]
116
117 **Figure 18: Inheritance for the GeoCodelist**
118
119 [[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_410255be.jpg||height="405" width="559"]]
120
121 **Figure 19: Class diagram for Geospatial Codelist**
122
123 ==== 4.3.4.1 Narrative ====
124
125 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:
126
127 GeographicCodelist
128
129 GeoGridCodelist
130
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.
132
133 The latter, i.e., GeoGridCodelist, comprises a set of GridCodes, which are related to the gridDefinition specified in the GeoGridCodelist.
134
135 ==== 4.3.4.2 Definitions ====
136
137 |(% colspan="2" %)**Class**|(% colspan="4" %)**Feature**|**Description**
138 |(% colspan="2" %)//GeoCodelist//|(% colspan="4" %)(((
139 Abstract Class Sub Classes:
140
141 GeographicCodelist GeoGridCodelist geoType
142 )))|(((
143 The abstract class that represents a special type of Codelist, which includes geospatial information.
144
145 The type of Geo Codelist that the Codelist will become.
146 )))
147 |(% colspan="2" %)//GeoRefCode//|(% colspan="4" %)(((
148 Abstract Class Sub Classes:
149
150 GeoFeatureSet
151
152 GeoGridCode
153 )))|The abstract class that represents a special type of Code, which includes geospatial information.
154 |GeographicCodelist|(% colspan="4" %)|(% colspan="2" %)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.
155 |GeoGridCodelist//     //|(% colspan="3" %)||(% colspan="2" %)A code list that has defined a geographical grid composed of cells representing regular squared portions of the Earth.
156 |(% rowspan="2" %)|(% colspan="2" rowspan="2" %)|gridDefinition|(% rowspan="2" %)|(% colspan="2" rowspan="2" %)Contains a regular expression string corresponding to the grid definition for the GeoGrid Codelist.
157 |
158 |GeoFeatureSetCode|(% colspan="4" %)|(% colspan="2" %)A Code that has a geo feature set.
159 ||(% colspan="4" %)value|(% colspan="2" %)The geo feature set of the Code, which represents a set of points defining a feature in a format defined a predefined pattern (see section 6).
160 |GeoGridCode|(% colspan="4" %)|(% colspan="2" %)A Code that represents a Geo Grid Cell belonging in a specific grid definition.
161 ||(% colspan="4" %)geoCell|(% colspan="2" %)The value used to assign the Code to one cell in the grid.
162
163 == 4.4 ValueList ==
164
165 === 4.4.1 Class Diagram ===
166
167 [[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_4d9e301b.jpg||height="695" width="526"]]
168
169 **Figure 20: Class diagram of the ValueList**
170
171 === 4.4.2 Explanation of the Diagram ===
172
173 ==== 4.4.2.1 Narrative ====
174
175 A ValueList inherits from //EnumeratedList// (and hence the //MaintenableArtefact//) and thus has the following attributes:
176
177 id// //uri// //urn// //version// //validFrom// //validTo// //isExternalReference registryURL structureURL repositoryURL
178
179 ValueItem inherits from //EnumeratedItem//, which adds an id, with relaxed constraints, to the former.
180
181 Through the inheritance from //NameableArtefact// the ValueList has 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). Similarly, the ValueItem, inherits the association to InternationalString and to the Annotation from the //EnumeratedItem//.
182
183 The ValueList can have one or more ValueItems.
184
185 ==== 4.4.2.2 Definitions ====
186
187 |**Class**|**Feature**|**Description**
188 |ValueList|(((
189 Inherits from
190
191 //EnumeratedList//
192 )))|A list from which some statistical concepts (enumerated concepts) take their values.
193 |ValueItem|(((
194 Inherits from
195
196 //EnumeratedItem//
197 )))|A language independent set of letters, numbers or symbols that represent a concept whose meaning is described in a natural language.
198
199 == 4.5 Concept Scheme and Concepts ==
200
201 === 4.5.1 Class Diagram - Inheritance ===
202
203 [[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_e6942837.jpg||height="717" width="457"]]
204
205 **Figure 21 Class diagram of the Concept Scheme**
206
207 === 4.5.2 Explanation of the Diagram ===
208
209 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:
210
211 id uri urn
212
213 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).
214
215 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.
216
217 A partial ConceptScheme (where isPartial is set to “true”) is identical to a ConceptScheme and contains the Concept and associated names and descriptions, just as in a normal ConceptScheme. However, its content is a subset of the full ConceptScheme. The way this works is described in section 3.5.3.1 on ItemScheme.
218
219 === 4.5.3 Class Diagram Relationship ===
220
221 [[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_d9b0bdf4.jpg||height="450" width="461"]]
222
223 **Figure 22: Relationship class diagram of the Concept Scheme**
224
225 === 4.5.4 Explanation of the diagram ===
226
227 ==== 4.5.4.1 Narrative ====
228
229 The ConceptScheme can have one or more Concepts. A Concept can have zero or more child Concepts, thus supporting a hierarchy of Concepts. Note that a child Concept can have only one parent Concept in this association. The purpose of the hierarchy is to relate concepts that have a semantic relationship: for example, a Reporting_Country and Vis_a_Vis_Country may both have Country as a parent concept, or a CONTACT may have a PRIMARY_CONTACT as a child concept. It is not the purpose of such schemes to define reporting structures: these reporting structures are defined in the MetadataStructureDefinition.
230
231 The Concept can be associated with a coreRepresentation. The coreRepresentation is the specification of the format and value domain of the Concept when used on a structure like a DataStructureDefinition or a MetadataStructureDefinition, unless the specification of the Representation is overridden in the relevant structure definition. In a hierarchical ConceptScheme the Representation is inherited from the parent Concept unless overridden at the level of the child Concept.
232
233 The Representation is documented in more detail in the section on the SDMX Base.
234
235 The Concept may be related to a concept described in terms of the ISO/IEC 11179 standard. The ISOConceptReference identifies this concept and concept scheme in which it is contained.
236
237 ==== 4.5.4.2 Definitions ====
238
239 |**Class**|**Feature**|**Description**
240 |ConceptScheme|(((
241 Inherits from
242
243 //ItemScheme//
244 )))|The descriptive information for an arrangement or division of concepts into groups based on characteristics, which the objects have in common.
245 |Concept|(((
246 Inherits from
247
248 //Item//
249 )))|A concept is a unit of knowledge created by a unique combination of characteristics.
250 ||/hierarchy|Associates the parent and the child concept.
251 ||coreRepresentation|Associates a Representation.
252 ||+ISOConcept|Association to an ISO concept reference.
253 |ISOConceptReference||The identity of an ISO concept definition.
254 ||conceptAgency|The maintenance agency of the concept scheme containing the concept.
255 ||conceptSchemeID|The identifier of the concept scheme.
256 ||conceptID|The identifier of the concept.
257
258 == 4.6 Category Scheme ==
259
260 === 4.6.1 Context ===
261
262 This package defines the structure that supports the definition of and relationships between categories in a category scheme. It is similar to the package for concept scheme. An example of a category scheme is one which categorises data – sometimes known as a subject matter domain scheme or a data category scheme. Importantly, as will be seen later, the individual nodes in the scheme (the “categories”) can be associated to any set of IdentiableArtefacts in a Categorisation.
263
264 === 4.6.2 Class diagram Inheritance ===
265
266 [[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_3a450acd.jpg||height="776" width="452"]]
267
268 **Figure 23 Inheritance Class diagram of the Category Scheme**
269
270 === 4.6.3 Explanation of the Diagram ===
271
272 ==== 4.6.3.1 Narrative ====
273
274 The categories are modelled as a hierarchical //ItemScheme//. The CategoryScheme inherits from the //ItemScheme// and has the following attributes:
275
276 id uri urn version validFrom validTo isExternalReference structureURL serviceURL isPartial
277
278 Category inherits from //Item// and has the following attributes:
279
280 id uri urn
281
282 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).
283
284 Through the inheritance the CategoryScheme comprise one or more Categorys, and the Category itself can have one or more child Category in the (inherited) hierarchy association. Note that a child Category can have only one parent Category in this association.
285
286 A partial CategoryScheme (where isPartial is set to “true”) is identical to a CategoryScheme and contains the Category and associated names and descriptions, just as in a normal CategoryScheme. However, its content is a subset of the full CategoryScheme. The way this works is described in section 3.5.3.1 on ItemScheme.
287
288 === 4.6.4 Class diagram Relationship ===
289
290 [[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_3696e610.jpg||height="407" width="525"]]
291
292 **Figure 24: Relationship Class diagram of the Category Scheme**
293
294 The CategoryScheme can have one or more Categorys. The Category is Identifiable and has identity information. A Category can have zero or more child Categorys, thus supporting a hierarchy of Categorys. Any IdentifiableArtefact can be +categorisedBy a Category. This is achieved by means of a Categorisation. Each Categorisation can associate one IdentifiableArtefact with one Category. Multiple Categorisations can be used to build a set of IdentifiableArtefacts that are +categorisedBy the same Category. Note that there is no navigation (i.e. no embedded reference) to the Categorisation from the Category. From an implementation perspective this is necessary as Categorisation has no affect on the versioning of either the Category or the IdentifiableArtefact.
295
296 ==== 4.6.4.1 Definitions ====
297
298 |**Class**|(% colspan="2" %)**Feature**|**Description**
299 |CategoryScheme|(% colspan="2" %)(((
300 Inherits from
301
302 //ItemScheme//
303 )))|The descriptive information for an arrangement or division of categories into groups based on characteristics, which the objects have in common.
304 ||(% colspan="2" %)/items|Associates the categories.
305 |Category|(((
306 Inherits from
307
308 //Item//
309 )))|(% colspan="2" %)An item at any level within a classification, typically tabulation categories, sections, subsections, divisions, subdivisions, groups, subgroups, classes and subclasses.
310 ||/hierarchy|(% colspan="2" %)Associates the parent and the child Category.
311 |Categorisation|(((
312 Inherits from
313
314 //MaintainableArtefact//
315 )))|(% colspan="2" %)Associates an Identifable Artefact with a Category.
316 ||+categorisedArtefact|(% colspan="2" %)Associates the Identifable Artefact.
317 ||+categorisedBy|(% colspan="2" %)Associates the Category.
318
319 == 4.7 Organisation Scheme ==
320
321 === 4.7.1 Class Diagram ===
322
323 [[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_e9f53aa7.jpg||height="470" width="588"]]
324
325 **Figure 25 The Organisation Scheme class diagram**
326
327 === 4.7.2 Explanation of the Diagram ===
328
329 ==== 4.7.2.1 Narrative ====
330
331 The //OrganisationScheme// is abstract. It contains //Organisation// which is also abstract. The //Organisation// can have child //Organisation//.
332
333 The //OrganisationScheme// can be one of five types:
334
335 1. AgencyScheme – contains Agency which is restricted to a flat list of agencies (i.e., there is no hierarchy). Note that the SDMX system of (Maintenance) Agency can be hierarchic and this is explained in more detail in the SDMX Standards Section 6 “Technical Notes”.
336 1. DataProviderScheme – contains DataProvider which is restricted to a flat list of agencies (i.e., there is no hierarchy).
337 1. MetadataProviderScheme – contains MetadataProvider which is restricted to a flat list of agencies (i.e., there is no hierarchy).
338 1. DataConsumerScheme – contains DataConsumer which is restricted to a flat list of agencies (i.e., there is no hierarchy).
339 1. OrganisationUnitScheme – contains OrganisationUnit which does inherit the /hierarchy association from Organisation.
340
341 Reference metadata can be attached to the //Organisation// by means of the metadata attachment mechanism. This mechanism is explained in the Reference Metadata section of this document (see section 7). This means that the model does not specify the specific reference metadata that can be attached to a DataProvider, MetadataProvider, DataConsumer, OrganisationUnit or Agency, except for limited Contact information.
342
343 A partial //OrganisationScheme// (where isPartial is set to “true”) is identical to an //OrganisationScheme// and contains the //Organisation// and associated names and descriptions, just as in a normal //OrganisationScheme//. However, its content is a subset of the full //OrganisationScheme//. The way this works is described in section 3.5.3.1 on //ItemScheme//.
344
345 ==== 4.7.2.2 Definitions ====
346
347 |**Class**|**Feature**|**Description**
348 |//OrganisationScheme//|(((
349 Abstract Class Inherits from
350
351 //ItemScheme//
352
353 Sub classes are:
354
355 AgencyScheme
356
357 DataProviderScheme
358
359 MetadataProviderScheme DataConsumerScheme
360
361 OrganisationUnitScheme
362 )))|A maintained collection of Organisations.
363 ||/items|(((
364 Association to the
365
366 Organisations in the scheme.
367 )))
368 |//Organisation//|(((
369 Abstract Class
370
371 Inherits from
372
373 //Item//
374
375 Sub classes are:
376
377 Agency
378
379 DataProvider
380
381 MetadataProvider DataConsumer
382
383 OrganisationUnit
384 )))|An organisation is a unique framework of authority within which a person or persons act, or are designated to act, towards some purpose.
385 ||+contact|Association to the Contact information.
386 ||/hierarchy|Association to child Organisations.
387 |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.
388 ||name|The designation of the Contact person by a linguistic expression.
389 ||organisationUnit|The designation of the organisational structure by a linguistic expression, within which Contact person works.
390 ||responsibility|The function of the contact person with respect to the organisation role for which this person is the Contact.
391 ||telephone|The telephone number of the Contact.
392 ||fax|The fax number of the Contact.
393 ||email|The Internet e-mail address of the Contact.
394 ||X400|The X400 address of the Contact.
395 ||uri|The URL address of the Contact.
396 |AgencyScheme||A maintained collection of Maintenance Agencies.
397 ||/items|Association to the Maintenance Agency in the scheme.
398 |DataProviderScheme||A maintained collection of Data Providers.
399 ||/items|Association to the Data Providers in the scheme.
400 |MetadataProviderScheme||A maintained collection of Metadata Providers.
401 ||/items|Association to the Metadata Providers in the scheme.
402 |DataConsumerScheme||A maintained collection of Data Consumers.
403 ||/items|Association to the Data Consumers in the scheme.
404 |OrganisationUnitScheme||A maintained collection of Organisation Units.
405 ||/items|Association to the Organisation Units in the scheme.
406 |Agency|(((
407 Inherits from
408
409 //Organisation//
410 )))|Responsible agency for maintaining artefacts such as statistical classifications, glossaries, structural metadata such as Data and Metadata Structure Definitions, Concepts and Code lists.
411 |DataProvider|(((
412 Inherits from
413
414 //Organisation//
415 )))|An organisation that produces data.
416 |MetadataProvider|(((
417 Inherits from
418
419 //Organisation//
420 )))|An organisation that produces reference metadata.
421 |DataConsumer|(((
422 Inherits from
423
424 //Organisation//
425 )))|An organisation using data as input for further processing.
426 |OrganisationUnit|(((
427 Inherits from
428
429 //Organisation //
430 )))|A designation in the organisational structure.
431 ||/hierarchy|Association to child Organisation Units
432
433 == 4.8 Reporting Taxonomy ==
434
435 === 4.8.1 Class Diagram ===
436
437 [[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_b041cf76.jpg||height="763" width="533"]]
438
439 **Figure 26: Class diagram of the Reporting Taxonomy**
440
441 === 4.8.2 Explanation of the Diagram ===
442
443 ==== 4.8.2.1 Narrative ====
444
445 In some data reporting environments, and in particular those in primary reporting, a report may comprise a variety of heterogeneous data, each described by a different //Structure//. Equally, a specific disseminated or published report may also comprise a variety of heterogeneous data. The definition of the set of linked sub reports is supported by the ReportingTaxonomy.
446
447 The ReportingTaxonomy is a specialised form of //ItemScheme//. Each ReportingCategory of the ReportingTaxonomy can link to one or more //StructureUsage// which itself can be one of Dataflow, or Metadataflow, and one or more //Structure//, which itself can be one of DataStructureDefinition or MetadataStructureDefinition. It is expected that within a specific ReportingTaxonomy each Category that is linked in this way will be linked to the same class (e.g. all Category in the scheme will link to a Dataflow). Note that a ReportingCategory can have child ReportingCategory and in this way it is possible to define a hierarchical ReportingTaxonomy. It is possible in this taxonomy that some ReportingCategory are defined just to give a reporting structure. For instance:
448
449 Section 1
450
451 1. linked to Datafow_1
452 1. linked to Datafow_2
453
454 Section 2
455
456 1. linked to Datafow_3
457 1. linked to Datafow_4
458
459 Here, the nodes of Section 1 and Section 2 would not be linked to Dataflow but the other would be linked to a Dataflow (and hence the DataStructureDefinition).
460
461 A partial ReportingTaxonomy (where isPartial is set to “true”) is identical to a ReportingTaxonomy and contains the ReportingCategory and associated names and descriptions, just as in a normal ReportingTaxonomy. However, its content is a sub set of the full ReportingTaxonomy The way this works is described in section 3.5.3.1 on //ItemScheme//.
462
463 ==== 4.8.2.2 Definitions ====
464
465 |**Class**|**Feature**|**Description**
466 |ReportingTaxonomy|(((
467 Inherits from
468
469 //ItemScheme //
470 )))|A scheme which defines the composition structure of a data report where each component can be described by an independent Dataflow or Metadataflow.
471 ||/items|Associates the Reporting Category
472 |ReportingCategory|(((
473 Inherits from
474
475 //Item//
476 )))|A component that gives structure to the report and links to data and metadata.
477 ||/hierarchy|Associates child Reporting Category.
478 ||+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.
479 ||+structure|(((
480 Association to the Data Structure
481
482 Definition and Metadata Structure Definitions which define the structural metadata describing the data and metadata that are contained at this part of the report.
483 )))