Changes for page 4 Specific Item Schemes
Last modified by Artur on 2025/09/10 11:19
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 3 removed)
Details
- Page properties
-
- Content
-
... ... @@ -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 === ... ... @@ -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 === ... ... @@ -111,7 +111,6 @@ 111 111 112 112 === {{id name="_Toc370995"/}}4.4.3 Class Diagram - Relationship === 113 113 114 -[[image:1747732242162-856.png]] 115 115 116 116 **Figure 17: Relationship class diagram of the Concept Scheme** 117 117 ... ... @@ -119,8 +119,10 @@ 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 119 +MetadataStructureDefinition. 120 + 124 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 a 125 125 126 126 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. ... ... @@ -254,69 +254,83 @@ 254 254 255 255 ==== 4.6.2.2 Definitions ==== 256 256 257 -(% style="width:845.294px" %) 258 -|(% style="width:181px" %)**Class**|(% style="width:217px" %)**Feature**|(% style="width:429px" %)**Description** 259 -|(% style="width:181px" %)//OrganisationScheme//|(% style="width:217px" %)((( 254 +|**Class**|**Feature**|**Description** 255 +|//OrganisationScheme//|((( 260 260 Abstract Class Inherits from 257 + 261 261 //ItemScheme// 259 + 262 262 Sub classes are: 261 + 263 263 AgencyScheme 263 + 264 264 DataProviderScheme 265 + 265 265 DataConsumerScheme 267 + 266 266 OrganisationUnitScheme 267 -)))| (% style="width:429px" %)A maintained collection of Organisations.268 -| (%style="width:181px" %)|(% style="width:217px" %)/items|(% style="width:429px" %)Association to the Organisations in the scheme.269 -| (% style="width:181px" %)//Organisation//|(% style="width:217px" %)(((269 +)))|A maintained collection of Organisations. 270 +| |/items|Association to the Organisations in the scheme. 271 +|//Organisation//|((( 270 270 Inherits from 273 + 271 271 //Item// 275 + 272 272 Sub classes are: 277 + 273 273 Agency 279 + 274 274 DataProvider 281 + 275 275 DataConsumer 283 + 276 276 OrganisationUnit 277 -)))| (% 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.278 -| (%style="width:181px" %)|(% style="width:217px" %)+contact|(% style="width:429px" %)Association to the Contact information.279 -| (%style="width:181px" %)|(% style="width:217px" %)/hierarchy|(% style="width:429px" %)Association to child Organisations.280 -| (% 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.281 -| (%style="width:181px" %)|(% style="width:217px" %)name|(% style="width:429px" %)The designation of the Contact person by a linguistic expression.282 -| (%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.283 -| (%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.284 -| (%style="width:181px" %)|(% style="width:217px" %)telephone|(% style="width:429px" %)The telephone number of the Contact.285 -| (%style="width:181px" %)|(% style="width:217px" %)fax|(% style="width:429px" %)The fax number of the Contact.286 -| (%style="width:181px" %)|(% style="width:217px" %)email|(% style="width:429px" %)The Internet e-mail address of the Contact.287 -| (%style="width:181px" %)|(% style="width:217px" %)X400|(% style="width:429px" %)The X400 address of the Contact.288 -| (%style="width:181px" %)|(% style="width:217px" %)uri|(% style="width:429px" %)The URL address of the Contact.289 -| (% style="width:181px" %)AgencyScheme|(%style="width:217px" %)|(% style="width:429px" %)A maintained collection of Maintenace Agencies.290 -| (%style="width:181px" %)|(% style="width:217px" %)/items|(% style="width:429px" %)Association to the Maintenance Agency in the scheme.291 -| (% style="width:181px" %)DataProviderScheme|(%style="width:217px" %)|(% style="width:429px" %)A maintained collection of Data Providers.292 -| (%style="width:181px" %)|(% style="width:217px" %)/items|(% style="width:429px" %)Association to the Data Providers in the scheme.293 -| (% style="width:181px" %)DataConsumerScheme|(%style="width:217px" %)|(% style="width:429px" %)A maintained collection of Data Consumers.294 -| (%style="width:181px" %)|(% style="width:217px" %)/items|(% style="width:429px" %)Association to the Data Consumers in the scheme.295 -| (% style="width:181px" %)OrganisationUnitScheme|(%style="width:217px" %)|(% style="width:429px" %)A maintained collection of Organisation Units.296 -| (%style="width:181px" %)|(% style="width:217px" %)/items|(% style="width:429px" %)Association to the Organisation Units in the scheme.297 -| (% style="width:181px" %)Agency|(% style="width:217px" %)(((285 +)))|An organisation is a unique framework of authority within which a person or persons act, or are designated to act, towards some purpose. 286 +| |+contact|Association to the Contact information. 287 +| |/hierarchy|Association to child Organisations. 288 +|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. 289 +| |name|The designation of the Contact person by a linguistic expression. 290 +| |organisationUnit|The designation of the organisational structure by a linguistic expression, within which Contact person works. 291 +| |responsibility|The function of the contact person with respect to the organisation role for which this person is the Contact. 292 +| |telephone|The telephone number of the Contact. 293 +| |fax|The fax number of the Contact. 294 +| |email|The Internet e-mail address of the Contact. 295 +| |X400|The X400 address of the Contact. 296 +| |uri|The URL address of the Contact. 297 +|AgencyScheme| |A maintained collection of Maintenace Agencies. 298 +| |/items|Association to the Maintenance Agency in the scheme. 299 +|DataProviderScheme| |A maintained collection of Data Providers. 300 +| |/items|Association to the Data Providers in the scheme. 301 +|DataConsumerScheme| |A maintained collection of Data Consumers. 302 +| |/items|Association to the Data Consumers in the scheme. 303 +|OrganisationUnitScheme| |A maintained collection of Organisation Units. 304 +| |/items|Association to the Organisation Units in the scheme. 305 +|Agency|((( 298 298 Inherits from 307 + 299 299 //Organisation// 300 -)))| (% 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.301 -| (% style="width:181px" %)DataProvider|(% style="width:217px" %)(((309 +)))|Responsible agency for maintaining artefacts such as statistical classifications, glossaries, structural metadata such as Data and Metadata Structure Definitions, Concepts and Code lists. 310 +|DataProvider|((( 302 302 Inherits from 312 + 303 303 //Organisation// 304 -)))| (% style="width:429px" %)An organisation that produces data or reference metadata.305 -| (% style="width:181px" %)DataConsumer|(% style="width:217px" %)(((314 +)))|An organisation that produces data or reference metadata. 315 +|DataConsumer|((( 306 306 Inherits from 317 + 307 307 //Organisation// 308 -)))| (% style="width:429px" %)An organisation using data as input for further processing.309 -| (% style="width:181px" %)OrganisationUnit|(% style="width:217px" %)(((319 +)))|An organisation using data as input for further processing. 320 +|OrganisationUnit|((( 310 310 Inherits from 311 -//Organisation// 312 -)))|(% style="width:429px" %)A designation in the organisational structure. 313 -|(% style="width:181px" %) |(% style="width:217px" %)/hierarchy|(% style="width:429px" %)Association to child Organisation Units 314 314 323 +//Organisation // 324 +)))|A designation in the organisational structure. 325 +| |/hierarchy|Association to child Organisation Units 326 + 315 315 == {{id name="_Toc371005"/}}4.7 Reporting Taxonomy == 316 316 317 317 === {{id name="_Toc371006"/}}4.7.1 Class Diagram === 318 318 319 - 320 320 **Figure 21: Class diagram of the Reporting Taxonomy** 321 321 322 322 === {{id name="_Toc371007"/}}4.7.2 Explanation of the Diagram === ... ... @@ -344,19 +344,22 @@ 344 344 345 345 ==== 4.7.2.2 Definitions ==== 346 346 347 -(% style="width:1033.29px" %) 348 -|**Class**|**Feature**|(% style="width:687px" %)**Description** 358 +|**Class**|**Feature**|**Description** 349 349 |ReportingTaxonomy|((( 350 350 Inherits from 351 -//ItemScheme// 352 -)))|(% 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. 353 -| |items|(% style="width:687px" %)Associates the Reporting Category 361 + 362 +//ItemScheme // 363 +)))|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. 364 +| |items|Associates the Reporting Category 354 354 |ReportingCategory|((( 355 355 Inherits from 367 + 356 356 //Item// 357 -)))|(% style="width:687px" %)A component that gives structure to the report and links to data and metadata. 358 -| |hierarchy|(% style="width:687px" %)Associates child Reporting Category. 359 -| |+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. 360 -| |+structure|(% style="width:687px" %)((( 361 -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. 369 +)))|A component that gives structure to the report and links to data and metadata. 370 +| |hierarchy|Associates child Reporting Category. 371 +| |+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. 372 +| |+structure|((( 373 +Association to the Data Structure Definition and Metadata Structure 374 + 375 +Definitions which define the structural metadata describing the data and metadata that are contained at this part of the report. 362 362 )))
- 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