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)
Details
- Page properties
-
- Content
-
... ... @@ -69,12 +69,12 @@ 69 69 Inherits from 70 70 71 71 //ItemScheme// 72 -)))|(% style="width:465px" %)A list from which some statistical (% style="color:#2ecc71" %)concepts(%%)(coded(% style="color:#2ecc71" %)concepts(%%))take their values.72 +)))|(% style="width:465px" %)A list from which some statistical concepts (coded concepts) take their values. 73 73 |Code|((( 74 74 Inherits from 75 75 76 76 Item 77 -)))|(% style="width:465px" %)A language independent set of letters, numbers or symbols that represent a (% style="color:#2ecc71" %)concept(%%)whose meaning is described in a natural language.77 +)))|(% style="width:465px" %)A language independent set of letters, numbers or symbols that represent a concept whose meaning is described in a natural language. 78 78 | |hierarchy|(% style="width:465px" %)Associates the parent and the child codes. 79 79 | |extends|(% style="width:465px" %)Associates a Codelist with any Codelists that it may extend. 80 80 ... ... @@ -96,17 +96,17 @@ 96 96 (% style="width:753.039px" %) 97 97 |(% style="width:184px" %)**Class**|(% style="width:145px" %)**Feature**|(% style="width:421px" %)**Description** 98 98 |(% style="width:184px" %)CodelistExtension|(% style="width:145px" %) |(% style="width:421px" %)The association between Codelists that may extend other Codelists. 99 -|(% style="width:184px" %) |(% style="width:145px" %)prefix|(% style="width:421px" %)A prefix to be used for a Codelist used in a extension, in order to avoid [[Code>>doc:xwiki:Glossary.Code.WebHome]]Conflicts.100 -|(% style="width:184px" %) |(% style="width:145px" %)sequence|(% style="width:421px" %)The order that will be used when extending a Codelist, for resolving [[Code>>doc:xwiki:Glossary.Code.WebHome]]conflicts. The latest Codelist used overrides any previous Codelist.101 -|(% style="width:184px" %)InclusiveCodeSelection|(% style="width:145px" %) |(% style="width:421px" %)The subset of [[Codes>>doc:xwiki:Glossary.Code.WebHome]]to be included when extending a Codelist.102 -|(% style="width:184px" %)ExclusiveCodeSelection|(% style="width:145px" %) |(% style="width:421px" %)The subset of [[Codes>>doc:xwiki:Glossary.Code.WebHome]]to be excluded when extending a Codelist.99 +|(% style="width:184px" %) |(% style="width:145px" %)prefix|(% style="width:421px" %)A prefix to be used for a Codelist used in a extension, in order to avoid Code Conflicts. 100 +|(% style="width:184px" %) |(% style="width:145px" %)sequence|(% style="width:421px" %)The order that will be used when extending a Codelist, for resolving Code conflicts. The latest Codelist used overrides any previous Codelist. 101 +|(% style="width:184px" %)InclusiveCodeSelection|(% style="width:145px" %) |(% style="width:421px" %)The subset of Codes to be included when extending a Codelist. 102 +|(% style="width:184px" %)ExclusiveCodeSelection|(% style="width:145px" %) |(% style="width:421px" %)The subset of Codes to be excluded when extending a Codelist. 103 103 |(% style="width:184px" %)MemberValue|(% style="width:145px" %)((( 104 104 Inherits from: 105 105 106 106 //SelectionValue// 107 -)))|(% style="width:421px" %)A collection of values based on [[Codes>>doc:xwiki:Glossary.Code.WebHome]]and their children.108 -|(% style="width:184px" %) |(% style="width:145px" %)cascadeValues|(% style="width:421px" %)A property to indicate if the child [[Codes>>doc:xwiki:Glossary.Code.WebHome]]of the selected[[Code>>doc:xwiki:Glossary.Code.WebHome]]shall be included in the selection. It is also possible to include children and exclude the[[Code>>doc:xwiki:Glossary.Code.WebHome]]by using the 'excluderoot' value.109 -|(% style="width:184px" %) |(% style="width:145px" %)value|(% style="width:421px" %)The value of the [[Code>>doc:xwiki:Glossary.Code.WebHome]]to include in the selection. It may include the ‘%’ character as a wildcard.107 +)))|(% style="width:421px" %)A collection of values based on Codes and their children. 108 +|(% style="width:184px" %) |(% style="width:145px" %)cascadeValues|(% style="width:421px" %)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. 109 +|(% style="width:184px" %) |(% style="width:145px" %)value|(% style="width:421px" %)The value of the Code to include in the selection. It may include the ‘%’ character as a wildcard. 110 110 ))) 111 111 112 112 === 4.3.4 Class Diagram – Geospatial Codelist === ... ... @@ -389,7 +389,9 @@ 389 389 OrganisationUnitScheme 390 390 )))|(% style="width:336px" %)A maintained collection of Organisations. 391 391 | |(% style="width:246px" %)/items|(% style="width:336px" %)((( 392 -Association to the Organisations in the scheme. 392 +Association to the 393 + 394 +Organisations in the scheme. 393 393 ))) 394 394 |//Organisation//|(% style="width:246px" %)((( 395 395 Abstract Class ... ... @@ -458,7 +458,7 @@ 458 458 459 459 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. 460 460 461 -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>>doc:xwiki:Glossary.Dataflow.WebHome]], or[[Metadataflow>>doc:xwiki:Glossary.Metadataflow.WebHome]], and one or more //Structure//, which itself can be one of DataStructureDefinition or MetadataStructureDefinition. It is expected that within a specific ReportingTaxonomy each[[Category>>doc:xwiki:Glossary.Category.WebHome]]that is linked in this way will be linked to the same class (e.g. all[[Category>>doc:xwiki:Glossary.Category.WebHome]]in the scheme will link to a[[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]]). 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:463 +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: 462 462 463 463 Section 1 464 464 ... ... @@ -470,12 +470,10 @@ 470 470 1. linked to Datafow_3 471 471 1. linked to Datafow_4 472 472 473 -Here, the nodes of Section 1 and Section 2 would not be linked to [[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]]but the other would be linked to a[[Dataflow>>doc:xwiki:Glossary.Dataflow.WebHome]](and hence the DataStructureDefinition).475 +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). 474 474 475 -A partial ReportingTaxonomy (where isPartial is set to “true”) is identical to a ReportingTaxonomy and contains the ReportingCategory and associated 477 +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//. 476 476 477 -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//. 478 - 479 479 ==== 4.8.2.2 Definitions ==== 480 480 481 481 (% style="width:759.039px" %)