Changes for page 4 Specific Item Schemes
Last modified by Artur on 2025/09/10 11:19
Summary
-
Page properties (3 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 6 removed)
-
Objects (0 modified, 0 added, 1 removed)
Details
- Page properties
-
- Parent
-
... ... @@ -1,1 +1,0 @@ 1 -Methodology.SDMX 2\.1 Standards\. Section 2\. Information model\: UML conceptual design.WebHome - Content
-
... ... @@ -1,16 +1,14 @@ 1 -{{box title="**Contents**"}} 2 -{{toc/}} 3 -{{/box}} 1 += {{id name="_Toc370986"/}}4 Specific Item Schemes = 4 4 5 5 == {{id name="_Toc370987"/}}4.1 Introduction == 6 6 7 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 -* Codelist 10 -* ConceptScheme 11 -* CategoryScheme 7 +* Codelist// // 8 +* ConceptScheme// // 9 +* CategoryScheme// // 12 12 * AgencyScheme, DataProviderScheme, DataConsumerScheme, OrganisationUnitScheme which all inherit from the abstract class //OrganisationScheme// 13 -* Reporting Taxonomy 11 +* Reporting Taxonomy// // 14 14 15 15 == {{id name="_Toc370988"/}}4.2 Inheritance View == 16 16 ... ... @@ -20,8 +20,6 @@ 20 20 21 21 === {{id name="_Toc370990"/}}4.3.1 Class Diagram === 22 22 23 -[[image:1747732337979-971.png]] 24 - 25 25 **Figure 15 Class diagram of the Codelist** 26 26 27 27 === {{id name="_Toc370991"/}}4.3.2 Explanation of the Diagram === ... ... @@ -34,8 +34,8 @@ 34 34 * uri 35 35 * urn 36 36 * version 37 -* validFrom 38 -* validTo 33 +* validFrom// // 34 +* validTo// // 39 39 * isExternalReference 40 40 * serviceURL 41 41 * structureURL ... ... @@ -56,18 +56,21 @@ 56 56 57 57 ==== 4.3.2.2 Definitions ==== 58 58 55 +: 56 + 59 59 ((( 60 -(% style="width:905.294px" %) 61 -|(% style="width:132px" %)**Class**|(% style="width:172px" %)**Feature**|(% style="width:598px" %)**Description** 62 -|(% style="width:132px" %)Codelist|(% style="width:172px" %)((( 58 +|**Class**|**Feature**|**Description** 59 +|Codelist|((( 63 63 Inherits from 61 + 64 64 //ItemScheme// 65 -)))| (% style="width:598px" %)A list from which some statistical concepts (coded concepts) take their values.66 -| (% style="width:132px" %)Code|(% style="width:172px" %)(((63 +)))|A list from which some statistical concepts (coded concepts) take their values. 64 +|Code|((( 67 67 Inherits from 66 + 68 68 //Item// 69 -)))| (% style="width:598px" %)A language independent set of letters, numbers or symbols that represent a concept whose meaning is described in a natural language.70 -| (% style="width:132px" %)|(% style="width:172px" %)/hierarchy|(% style="width:598px" %)Associates the parent and the child codes.68 +)))|A language independent set of letters, numbers or symbols that represent a concept whose meaning is described in a natural language. 69 +||/hierarchy|Associates the parent and the child codes. 71 71 ))) 72 72 73 73 == {{id name="_Toc370992"/}}4.4 Concept Scheme and Concepts == ... ... @@ -74,8 +74,6 @@ 74 74 75 75 === {{id name="_Toc370993"/}}4.4.1 Class Diagram - Inheritance === 76 76 77 -[[image:1747732287949-594.png]] 78 - 79 79 **Figure 16 Class diagram of the Concept Scheme** 80 80 81 81 === {{id name="_Toc370994"/}}4.4.2 Explanation of the Diagram === ... ... @@ -82,18 +82,18 @@ 82 82 83 83 The ConceptScheme inherits from the //ItemScheme //and therefore has the following attributes: 84 84 85 -* id 86 -* uri 87 -* urn 88 -* version 89 -* validFrom 90 -* validTo 82 +* id// // 83 +* uri// // 84 +* urn// // 85 +* version// // 86 +* validFrom// // 87 +* validTo// // 91 91 * isExternalReference 92 92 * registryURL 93 93 * structureURL 94 94 * repositoryURL 95 -* final 96 -* isPartial 92 +* final// // 93 +* isPartial// // 97 97 98 98 Concept inherits from Item and has the following attributes: 99 99 ... ... @@ -111,8 +111,6 @@ 111 111 112 112 === {{id name="_Toc370995"/}}4.4.3 Class Diagram - Relationship === 113 113 114 -[[image:1747732242162-856.png]] 115 - 116 116 **Figure 17: Relationship class diagram of the Concept Scheme** 117 117 118 118 === {{id name="_Toc370996"/}}4.4.4 Explanation of the diagram === ... ... @@ -119,10 +119,14 @@ 119 119 120 120 ==== 4.4.4.1 Narrative ==== 121 121 122 -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.117 +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 123 123 124 - The Concept can be associated with a coreRepresentation. The coreRepresentation isthe specification of the format and value domain of the Concept when used on a structure like a DataStructureDefinition or aMetadataStructureDefinition, 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.119 +MetadataStructureDefinition. 125 125 121 +The Concept can be associated with a coreRepresentation. The coreRepresentation isthe specification of the format and value domain of the Concept when used on a structure like a DataStructureDefinition or a 122 + 123 +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. 124 + 126 126 Note that the ConceptScheme is used as the Representation of the MeasureDimension in a DataStructureDefinition (see 5.3.2). Each Concept in this ConceptScheme is a specific measure, each of which can be given a coreRepresentation. Thus the valid format of the observation for each measure when reported in a data set for the MeasureDimension is specified in the Concept. This allows a different format for each measure. This is covered in more detail in 5.3. 127 127 128 128 The Representation is documented in more detail in the section on the SDMX Base. ... ... @@ -131,26 +131,27 @@ 131 131 132 132 ==== 4.4.4.2 Definitions ==== 133 133 133 +: 134 + 134 134 ((( 135 -(% style="width:931.294px" %) 136 -|(% style="width:195px" %)**Class**|(% style="width:210px" %)**Feature**|(% style="width:522px" %)**Description** 137 -|(% style="width:195px" %)ConceptScheme|(% style="width:210px" %)((( 136 +|**Class**|**Feature**|**Description** 137 +|ConceptScheme|((( 138 138 Inherits from 139 139 140 140 //ItemScheme// 141 -)))| (% style="width:522px" %)The descriptive information for an arrangement or division of concepts into groups based on characteristics, which the objects have in common.142 -| (% style="width:195px" %)Concept|(% style="width:210px" %)(((141 +)))|The descriptive information for an arrangement or division of concepts into groups based on characteristics, which the objects have in common. 142 +|Concept|((( 143 143 Inherits from 144 144 145 145 //Item// 146 -)))| (% style="width:522px" %)A concept is a unit of knowledge created by a unique combination of characteristics.147 -| (% style="width:195px" %)|(% style="width:210px" %)/hierarchy|(% style="width:522px" %)Associates the parent and the child concept.148 -| (% style="width:195px" %)|(% style="width:210px" %)coreRepresentation|(% style="width:522px" %)Associates a Representation.149 -| (% style="width:195px" %)|(% style="width:210px" %)+ISOConcept|(% style="width:522px" %)Association to an ISO concept reference.150 -| (% style="width:195px" %)ISOConceptReference|(% style="width:210px" %)|(% style="width:522px" %)The identity of an ISO concept definition.151 -| (% style="width:195px" %)|(% style="width:210px" %)conceptAgency|(% style="width:522px" %)The maintenance agency of the concept scheme containing the concept.152 -| (% style="width:195px" %)|(% style="width:210px" %)conceptSchemeID|(% style="width:522px" %)The identifier of the concept scheme.153 -| (% style="width:195px" %)|(% style="width:210px" %)conceptID|(% style="width:522px" %)The identifier of the concept.146 +)))|A concept is a unit of knowledge created by a unique combination of characteristics. 147 +||/hierarchy|Associates the parent and the child concept. 148 +||coreRepresentation|Associates a Representation. 149 +||+ISOConcept|Association to an ISO concept reference. 150 +|ISOConceptReference||The identity of an ISO concept definition. 151 +||conceptAgency|The maintenance agency of the concept scheme containing the concept. 152 +||conceptSchemeID|The identifier of the concept scheme. 153 +||conceptID|The identifier of the concept. 154 154 ))) 155 155 156 156 == {{id name="_Toc370997"/}}4.5 Category Scheme == ... ... @@ -161,12 +161,8 @@ 161 161 162 162 === {{id name="_Toc370999"/}}4.5.2 Class diagram - Inheritance === 163 163 164 -(% class="wikigeneratedid" id="H" %) 165 -[[image:1747732448450-721.png]] 164 +====== Figure 18 Inheritance Class diagram of the Category Scheme ====== 166 166 167 -(% class="wikigeneratedid" id="HFigure18InheritanceClassdiagramoftheCategoryScheme" %) 168 -**Figure 18 Inheritance Class diagram of the Category Scheme** 169 - 170 170 === {{id name="_Toc371000"/}}4.5.3 Explanation of the Diagram === 171 171 172 172 ==== 4.5.3.1 Narrative ==== ... ... @@ -173,7 +173,7 @@ 173 173 174 174 The categories are modelled as a hierarchical //ItemScheme//. The CategoryScheme inherits from the //ItemScheme// and has the following attributes: 175 175 176 -* id 172 +* id// // 177 177 * uri 178 178 * urn 179 179 * version ... ... @@ -183,7 +183,7 @@ 183 183 * structureURL 184 184 * serviceURL 185 185 * final 186 -* isPartial 182 +* isPartial// // 187 187 188 188 Category inherits from //Item// and has the following attributes: 189 189 ... ... @@ -199,33 +199,37 @@ 199 199 200 200 === {{id name="_Toc371001"/}}4.5.4 Class diagram - Relationship === 201 201 202 -[[image:1747732486733-495.png]] 203 - 204 204 **Figure 19: Relationship Class diagram of the Category Scheme** 205 205 206 -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.200 +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 207 207 202 +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. 203 + 208 208 ==== 4.5.4.1 Definitions ==== 209 209 206 +: 207 + 210 210 ((( 211 -(% style="width:965.294px" %) 212 -|(% style="width:171px" %)**Class**|(% style="width:213px" %)**Feature**|(% style="width:577px" %)**Description** 213 -|(% style="width:171px" %)CategoryScheme|(% style="width:213px" %)((( 209 +|**Class**|**Feature**|**Description** 210 +|CategoryScheme|((( 214 214 Inherits from 212 + 215 215 //ItemScheme// 216 -)))| (% style="width:577px" %)The descriptive information for an arrangement or division of categories into groups based on characteristics, which the objects have in common.217 -| (% style="width:171px" %)|(% style="width:213px" %)/items|(% style="width:577px" %)Associates the categories.218 -| (% style="width:171px" %)Category|(% style="width:213px" %)(((214 +)))|The descriptive information for an arrangement or division of categories into groups based on characteristics, which the objects have in common. 215 +||/items|Associates the categories. 216 +|Category|((( 219 219 Inherits from 218 + 220 220 //Item// 221 -)))| (% style="width:577px" %)An item at any level within a classification, typically tabulation categories, sections, subsections, divisions, subdivisions, groups, subgroups, classes and subclasses.222 -| (% style="width:171px" %)|(% style="width:213px" %)/hierarchy|(% style="width:577px" %)Associates the parent and the child Category.223 -| (% style="width:171px" %)Categorisation|(% style="width:213px" %)(((220 +)))|An item at any level within a classification, typically tabulation categories, sections, subsections, divisions, subdivisions, groups, subgroups, classes and subclasses. 221 +||/hierarchy|Associates the parent and the child Category. 222 +|Categorisation|((( 224 224 Inherits from 224 + 225 225 MaintainableArtefact 226 -)))| (% style="width:577px" %)Associates anIdentifableArtefact with a Category.227 -| (% style="width:171px" %)|(% style="width:213px" %)+categorisedArtefact|(% style="width:577px" %)Associates the IdentifableArtefact.228 -| (% style="width:171px" %)|(% style="width:213px" %)+categorisedBy|(% style="width:577px" %)Associates the Category.226 +)))|Associates anIdentifableArtefact with a Category. 227 +||+categorisedArtefact|Associates the IdentifableArtefact. 228 +||+categorisedBy|Associates the Category. 229 229 ))) 230 230 231 231 == {{id name="_Toc371002"/}}4.6 Organisation Scheme == ... ... @@ -234,8 +234,7 @@ 234 234 235 235 [[image:SDMX_2-1_SECTION_2_InformationModel_2020-07_dcd0149.png||height="456" width="580"]] 236 236 237 -(% class="wikigeneratedid" id="HFigure20TheOrganisationSchemeclassdiagram" %) 238 -**Figure 20 The Organisation Scheme class diagram** 237 +====== Figure 20 The Organisation Scheme class diagram ====== 239 239 240 240 === {{id name="_Toc371004"/}}4.6.2 Explanation of the Diagram === 241 241 ... ... @@ -256,70 +256,83 @@ 256 256 257 257 ==== 4.6.2.2 Definitions ==== 258 258 259 -(% style="width:845.294px" %) 260 -|(% style="width:181px" %)**Class**|(% style="width:217px" %)**Feature**|(% style="width:429px" %)**Description** 261 -|(% style="width:181px" %)//OrganisationScheme//|(% style="width:217px" %)((( 258 +|**Class**|**Feature**|**Description** 259 +|//OrganisationScheme//|((( 262 262 Abstract Class Inherits from 261 + 263 263 //ItemScheme// 263 + 264 264 Sub classes are: 265 + 265 265 AgencyScheme 267 + 266 266 DataProviderScheme 269 + 267 267 DataConsumerScheme 271 + 268 268 OrganisationUnitScheme 269 -)))| (% style="width:429px" %)A maintained collection of Organisations.270 -| (% style="width:181px" %)|(% style="width:217px" %)/items|(% style="width:429px" %)Association to the Organisations in the scheme.271 -| (% style="width:181px" %)//Organisation//|(% style="width:217px" %)(((273 +)))|A maintained collection of Organisations. 274 +||/items|Association to the Organisations in the scheme. 275 +|//Organisation//|((( 272 272 Inherits from 277 + 273 273 //Item// 279 + 274 274 Sub classes are: 281 + 275 275 Agency 283 + 276 276 DataProvider 285 + 277 277 DataConsumer 287 + 278 278 OrganisationUnit 279 -)))| (% style="width:429px" %)An organisation is a unique framework of authority within which a person or persons act, or are designated to act, towards some purpose.280 -| (% style="width:181px" %)|(% style="width:217px" %)+contact|(% style="width:429px" %)Association to the Contact information.281 -| (% style="width:181px" %)|(% style="width:217px" %)/hierarchy|(% style="width:429px" %)Association to child Organisations.282 -| (% style="width:181px" %)Contact|(% style="width:217px" %)|(% style="width:429px" %)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.283 -| (% style="width:181px" %)|(% style="width:217px" %)name|(% style="width:429px" %)The designation of the Contact person by a linguistic expression.284 -| (% style="width:181px" %)|(% style="width:217px" %)organisationUnit|(% style="width:429px" %)The designation of the organisational structure by a linguistic expression, within which Contact person works.285 -| (% style="width:181px" %)|(% style="width:217px" %)responsibility|(% style="width:429px" %)The function of the contact person with respect to the organisation role for which this person is the Contact.286 -| (% style="width:181px" %)|(% style="width:217px" %)telephone|(% style="width:429px" %)The telephone number of the Contact.287 -| (% style="width:181px" %)|(% style="width:217px" %)fax|(% style="width:429px" %)The fax number of the Contact.288 -| (% style="width:181px" %)|(% style="width:217px" %)email|(% style="width:429px" %)The Internet e-mail address of the Contact.289 -| (% style="width:181px" %)|(% style="width:217px" %)X400|(% style="width:429px" %)The X400 address of the Contact.290 -| (% style="width:181px" %)|(% style="width:217px" %)uri|(% style="width:429px" %)The URL address of the Contact.291 -| (% style="width:181px" %)AgencyScheme|(% style="width:217px" %)|(% style="width:429px" %)A maintained collection of Maintenace Agencies.292 -| (% style="width:181px" %)|(% style="width:217px" %)/items|(% style="width:429px" %)Association to the Maintenance Agency in the scheme.293 -| (% style="width:181px" %)DataProviderScheme|(% style="width:217px" %)|(% style="width:429px" %)A maintained collection of Data Providers.294 -| (% style="width:181px" %)|(% style="width:217px" %)/items|(% style="width:429px" %)Association to the Data Providers in the scheme.295 -| (% style="width:181px" %)DataConsumerScheme|(% style="width:217px" %)|(% style="width:429px" %)A maintained collection of Data Consumers.296 -| (% style="width:181px" %)|(% style="width:217px" %)/items|(% style="width:429px" %)Association to the Data Consumers in the scheme.297 -| (% style="width:181px" %)OrganisationUnitScheme|(% style="width:217px" %)|(% style="width:429px" %)A maintained collection of Organisation Units.298 -| (% style="width:181px" %)|(% style="width:217px" %)/items|(% style="width:429px" %)Association to the Organisation Units in the scheme.299 -| (% style="width:181px" %)Agency|(% style="width:217px" %)(((289 +)))|An organisation is a unique framework of authority within which a person or persons act, or are designated to act, towards some purpose. 290 +||+contact|Association to the Contact information. 291 +||/hierarchy|Association to child Organisations. 292 +|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. 293 +||name|The designation of the Contact person by a linguistic expression. 294 +||organisationUnit|The designation of the organisational structure by a linguistic expression, within which Contact person works. 295 +||responsibility|The function of the contact person with respect to the organisation role for which this person is the Contact. 296 +||telephone|The telephone number of the Contact. 297 +||fax|The fax number of the Contact. 298 +||email|The Internet e-mail address of the Contact. 299 +||X400|The X400 address of the Contact. 300 +||uri|The URL address of the Contact. 301 +|AgencyScheme||A maintained collection of Maintenace Agencies. 302 +||/items|Association to the Maintenance Agency in the scheme. 303 +|DataProviderScheme||A maintained collection of Data Providers. 304 +||/items|Association to the Data Providers in the scheme. 305 +|DataConsumerScheme||A maintained collection of Data Consumers. 306 +||/items|Association to the Data Consumers in the scheme. 307 +|OrganisationUnitScheme||A maintained collection of Organisation Units. 308 +||/items|Association to the Organisation Units in the scheme. 309 +|Agency|((( 300 300 Inherits from 311 + 301 301 //Organisation// 302 -)))| (% style="width:429px" %)Responsible agency for maintaining artefacts such as statistical classifications, glossaries, structural metadata such as Data and Metadata Structure Definitions, Concepts and Code lists.303 -| (% style="width:181px" %)DataProvider|(% style="width:217px" %)(((313 +)))|Responsible agency for maintaining artefacts such as statistical classifications, glossaries, structural metadata such as Data and Metadata Structure Definitions, Concepts and Code lists. 314 +|DataProvider|((( 304 304 Inherits from 316 + 305 305 //Organisation// 306 -)))| (% style="width:429px" %)An organisation that produces data or reference metadata.307 -| (% style="width:181px" %)DataConsumer|(% style="width:217px" %)(((318 +)))|An organisation that produces data or reference metadata. 319 +|DataConsumer|((( 308 308 Inherits from 321 + 309 309 //Organisation// 310 -)))| (% style="width:429px" %)An organisation using data as input for further processing.311 -| (% style="width:181px" %)OrganisationUnit|(% style="width:217px" %)(((323 +)))|An organisation using data as input for further processing. 324 +|OrganisationUnit|((( 312 312 Inherits from 313 -//Organisation// 314 -)))|(% style="width:429px" %)A designation in the organisational structure. 315 -|(% style="width:181px" %) |(% style="width:217px" %)/hierarchy|(% style="width:429px" %)Association to child Organisation Units 316 316 327 +//Organisation // 328 +)))|A designation in the organisational structure. 329 +||/hierarchy|Association to child Organisation Units 330 + 317 317 == {{id name="_Toc371005"/}}4.7 Reporting Taxonomy == 318 318 319 319 === {{id name="_Toc371006"/}}4.7.1 Class Diagram === 320 320 321 -[[image:1747732548003-370.png]] 322 - 323 323 **Figure 21: Class diagram of the Reporting Taxonomy** 324 324 325 325 === {{id name="_Toc371007"/}}4.7.2 Explanation of the Diagram === ... ... @@ -332,9 +332,10 @@ 332 332 333 333 Section 1 334 334 335 -1. linked to DatafowDefinition_1 336 -1. linked to DatafowDefinition_2 347 +~1. linked to DatafowDefinition_1 337 337 349 +2 linked to DatafowDefinition_2 350 + 338 338 Section 2 339 339 340 340 1. linked toDatafowDefinition_3 ... ... @@ -346,19 +346,22 @@ 346 346 347 347 ==== 4.7.2.2 Definitions ==== 348 348 349 -(% style="width:1033.29px" %) 350 -|**Class**|**Feature**|(% style="width:687px" %)**Description** 362 +|**Class**|**Feature**|**Description** 351 351 |ReportingTaxonomy|((( 352 352 Inherits from 353 -//ItemScheme// 354 -)))|(% style="width:687px" %)A scheme which defines the composition structure of a data report where each component can be described by an independent Dataflow Definition or Metdataflow Definition. 355 -| |items|(% style="width:687px" %)Associates the Reporting Category 365 + 366 +//ItemScheme // 367 +)))|A scheme which defines the composition structure of a data report where each component can be described by an independent Dataflow Definition or Metdataflow Definition. 368 +||items|Associates the Reporting Category 356 356 |ReportingCategory|((( 357 357 Inherits from 371 + 358 358 //Item// 359 -)))|(% style="width:687px" %)A component that gives structure to the report and links to data and metadata. 360 -| |hierarchy|(% style="width:687px" %)Associates child Reporting Category. 361 -| |+flow|(% style="width:687px" %)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. 362 -| |+structure|(% style="width:687px" %)((( 363 -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. 373 +)))|A component that gives structure to the report and links to data and metadata. 374 +||hierarchy|Associates child Reporting Category. 375 +||+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. 376 +||+structure|((( 377 +Association to the Data Structure Definition and Metadata Structure 378 + 379 +Definitions which define the structural metadata describing the data and metadata that are contained at this part of the report. 364 364 )))
- 1747732242162-856.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.helena - Size
-
... ... @@ -1,1 +1,0 @@ 1 -21.8 KB - Content
- 1747732287949-594.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.helena - Size
-
... ... @@ -1,1 +1,0 @@ 1 -42.4 KB - Content
- 1747732337979-971.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.helena - Size
-
... ... @@ -1,1 +1,0 @@ 1 -39.3 KB - Content
- 1747732448450-721.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.helena - Size
-
... ... @@ -1,1 +1,0 @@ 1 -34.0 KB - Content
- 1747732486733-495.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.helena - Size
-
... ... @@ -1,1 +1,0 @@ 1 -18.6 KB - Content
- 1747732548003-370.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.helena - Size
-
... ... @@ -1,1 +1,0 @@ 1 -48.9 KB - Content
- SUZ.Methodology.Code.MethodologyClass[0]
-
- index
-
... ... @@ -1,1 +1,0 @@ 1 -5