Changes for page 4 Specific Item Schemes

Last modified by Artur on 2025/09/10 11:19

From version 13.2
edited by Helena
on 2025/05/15 10:31
Change comment: There is no comment for this version
To version 16.2
edited by Helena
on 2025/05/16 22:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -4,33 +4,21 @@
4 4  
5 5  == 4.1 Introduction ==
6 6  
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:
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:
8 8  
9 9  Codelist
10 -
11 11  ConceptScheme
12 -
13 13  CategoryScheme
14 -
15 -AgencyScheme, DataProviderScheme, MetadataProviderScheme,
16 -
17 -DataConsumerScheme, OrganisationUnitScheme, which all inherit from the abstract class //OrganisationScheme//
18 -
12 +AgencyScheme, DataProviderScheme, MetadataProviderScheme, DataConsumerScheme, OrganisationUnitScheme, which all inherit from the abstract class //OrganisationScheme//
19 19  ReportingTaxonomy
20 -
21 21  TransformationScheme
22 -
23 23  RulesetScheme
24 -
25 25  UserDefinedOperatorScheme
26 -
27 27  NamePersonalisationScheme
28 -
29 29  CustomTypeScheme
30 -
31 31  VtlMappingScheme
32 32  
33 -Note that the VTL related schemes (the last 6 of the above list) are detailed in a dedicated section below (section 15).
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).
34 34  
35 35  == 4.2 Inheritance View ==
36 36  
... ... @@ -48,19 +48,30 @@
48 48  
49 49  ==== 4.3.2.1 Narrative ====
50 50  
51 -The Codelist inherits from the //ItemScheme// and therefore has the following attributes: id uri urn version validFrom validTo isExternalReference serviceURL structureURL isPartial
39 +The Codelist inherits from the //ItemScheme// and therefore has the following [[attributes>>doc:xwiki:Glossary.Attribute.WebHome]]:
52 52  
53 -The Code inherits from //Item// and has the following attributes:
41 +id
42 +uri
43 +urn
44 +version
45 +validFrom
46 +validTo
47 +isExternalReference
48 +serviceURL
49 +structureURL
50 +isPartial
54 54  
55 -id uri urn
52 +The [[Code>>doc:xwiki:Glossary.Code.WebHome]] inherits from //Item// and has the following [[attributes>>doc:xwiki:Glossary.Attribute.WebHome]]:
56 56  
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).
54 +id
55 +uri
56 +urn
58 58  
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.
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).
60 60  
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
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.
62 62  
63 -//ItemScheme//.
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//.
64 64  
65 65  ==== 4.3.2.2 Definitions ====
66 66  
... ... @@ -87,33 +87,32 @@
87 87  
88 88  ==== 4.3.3.1 Narrative ====
89 89  
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.
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.
91 91  
92 92  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.
93 93  
94 94  ==== 4.3.3.2 Definitions ====
95 95  
96 -:
97 -
98 98  (((
99 -|**Class**|**Feature**|**Description**
100 -|CodelistExtension| |The association between Codelists that may extend other Codelists.
101 -| |prefix|A prefix to be used for a Codelist used in a extension, in order to avoid Code Conflicts.
102 -| |sequence|The order that will be used when extending a Codelist, for resolving Code conflicts. The latest Codelist used overrides any previous Codelist.
103 -|InclusiveCodeSelection| |The subset of Codes to be included when extending a Codelist.
104 -|ExclusiveCodeSelection| |The subset of Codes to be excluded when extending a Codelist.
105 -|MemberValue|(((
96 +(% style="width:753.039px" %)
97 +|(% style="width:184px" %)**Class**|(% style="width:145px" %)**Feature**|(% style="width:421px" %)**Description**
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 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 +|(% style="width:184px" %)MemberValue|(% style="width:145px" %)(((
106 106  Inherits from:
107 107  
108 108  //SelectionValue//
109 -)))|A collection of values based on Codes and their children.
110 -| |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.
111 -| |value|The value of the Code 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.
112 112  )))
113 113  
114 114  === 4.3.4 Class Diagram – Geospatial Codelist ===
115 115  
116 -The geospatial support is implemented via an extension of the normal ,,Codelist,,. This is illustrated in the following diagrams.
114 +The geospatial support is implemented via an extension of the normal //Codelist//. This is illustrated in the following diagrams.
117 117  
118 118  [[image:SDMX 3-0-0 SECTION 2 FINAL-1.0 (1)_en_472b895.jpg||height="863" width="466"]]
119 119  
... ... @@ -128,7 +128,6 @@
128 128  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:
129 129  
130 130  GeographicCodelist
131 -
132 132  GeoGridCodelist
133 133  
134 134  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.
... ... @@ -137,6 +137,7 @@
137 137  
138 138  ==== 4.3.4.2 Definitions ====
139 139  
137 +(% style="width:760.039px" %)
140 140  |(% colspan="2" %)**Class**|(% colspan="4" %)**Feature**|**Description**
141 141  |(% colspan="2" %)//GeoCodelist//|(% colspan="4" %)(((
142 142  Abstract Class Sub Classes:
... ... @@ -149,19 +149,16 @@
149 149  )))
150 150  |(% colspan="2" %)//GeoRefCode//|(% colspan="4" %)(((
151 151  Abstract Class Sub Classes:
152 -
153 153  GeoFeatureSet
154 -
155 155  GeoGridCode
156 156  )))|The abstract class that represents a special type of Code, which includes geospatial information.
157 -|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.
158 -|GeoGridCodelist|(% colspan="3" %) | |(% colspan="2" %)A code list that has defined a geographical grid composed of cells representing regular squared portions of the Earth.
159 -|(% 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.
160 -|
161 -|GeoFeatureSetCode|(% colspan="4" %) |(% colspan="2" %)A Code that has a geo feature set.
162 -| |(% 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).
163 -|GeoGridCode|(% colspan="4" %) |(% colspan="2" %)A Code that represents a Geo Grid Cell belonging in a specific grid definition.
164 -| |(% colspan="4" %)geoCell|(% colspan="2" %)The value used to assign the Code to one cell in the grid.
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.
154 +|(% colspan="2" %)GeoGridCodelist|(% colspan="4" %) |A code list that has defined a geographical grid composed of cells representing regular squared portions of the Earth.
155 +|(% colspan="2" %) |(% colspan="4" %)gridDefinition|Contains a regular expression string corresponding to the grid definition for the GeoGrid Codelist.
156 +|(% colspan="2" %)GeoFeatureSetCode|(% colspan="4" %) |A Code that has a geo feature set.
157 +|(% colspan="2" %) |(% colspan="4" %)value|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).
158 +|(% colspan="2" %)GeoGridCode|(% colspan="4" %) |A Code that represents a Geo Grid Cell belonging in a specific grid definition.
159 +|(% colspan="2" %) |(% colspan="4" %)geoCell|The value used to assign the Code to one cell in the grid.
165 165  
166 166  == 4.4 ValueList ==
167 167  
... ... @@ -177,7 +177,16 @@
177 177  
178 178  A ValueList inherits from //EnumeratedList// (and hence the //MaintenableArtefact//) and thus has the following attributes:
179 179  
180 -id// //uri// //urn// //version// //validFrom// //validTo// //isExternalReference registryURL structureURL repositoryURL
175 +id
176 +uri
177 +urn
178 +version
179 +validFrom
180 +validTo
181 +isExternalReference
182 +registryURL
183 +structureURL
184 +repositoryURL
181 181  
182 182  ValueItem inherits from //EnumeratedItem//, which adds an id, with relaxed constraints, to the former.
183 183  
... ... @@ -187,17 +187,18 @@
187 187  
188 188  ==== 4.4.2.2 Definitions ====
189 189  
190 -|**Class**|**Feature**|**Description**
194 +(% style="width:749.039px" %)
195 +|**Class**|**Feature**|(% style="width:421px" %)**Description**
191 191  |ValueList|(((
192 192  Inherits from
193 193  
194 194  //EnumeratedList//
195 -)))|A list from which some statistical concepts (enumerated concepts) take their values.
200 +)))|(% style="width:421px" %)A list from which some statistical concepts (enumerated concepts) take their values.
196 196  |ValueItem|(((
197 197  Inherits from
198 198  
199 199  //EnumeratedItem//
200 -)))|A language independent set of letters, numbers or symbols that represent a concept whose meaning is described in a natural language.
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 201  
202 202  == 4.5 Concept Scheme and Concepts ==
203 203  
... ... @@ -209,10 +209,26 @@
209 209  
210 210  === 4.5.2 Explanation of the Diagram ===
211 211  
212 -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:
217 +The ConceptScheme inherits from the //ItemScheme //and therefore has the following attributes:
213 213  
214 -id uri urn
219 +id
220 +uri
221 +urn
222 +version
223 +validFrom
224 +validTo
225 +isExternalReference
226 +registryURL
227 +structureURL
228 +repositoryURL
229 +isPartial
215 215  
231 +Concept inherits from Item and has the following attributes:
232 +
233 +id
234 +uri
235 +urn
236 +
216 216  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).
217 217  
218 218  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.
... ... @@ -239,24 +239,23 @@
239 239  
240 240  ==== 4.5.4.2 Definitions ====
241 241  
242 -|**Class**|**Feature**|**Description**
243 -|ConceptScheme|(((
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" %)(((
244 244  Inherits from
245 -
246 246  //ItemScheme//
247 -)))|The descriptive information for an arrangement or division of concepts into groups based on characteristics, which the objects have in common.
248 -|Concept|(((
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" %)(((
249 249  Inherits from
250 -
251 251  //Item//
252 -)))|A concept is a unit of knowledge created by a unique combination of characteristics.
253 -| |/hierarchy|Associates the parent and the child concept.
254 -| |coreRepresentation|Associates a Representation.
255 -| |+ISOConcept|Association to an ISO concept reference.
256 -|ISOConceptReference| |The identity of an ISO concept definition.
257 -| |conceptAgency|The maintenance agency of the concept scheme containing the concept.
258 -| |conceptSchemeID|The identifier of the concept scheme.
259 -| |conceptID|The identifier of the concept.
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.
260 260  
261 261  == 4.6 Category Scheme ==
262 262  
... ... @@ -276,11 +276,22 @@
276 276  
277 277  The categories are modelled as a hierarchical //ItemScheme//. The CategoryScheme inherits from the //ItemScheme// and has the following attributes:
278 278  
279 -id uri urn version validFrom validTo isExternalReference structureURL serviceURL isPartial
299 +id
300 +uri
301 +urn
302 +version
303 +validFrom
304 +validTo
305 +isExternalReference
306 +structureURL
307 +serviceURL
308 +isPartial
280 280  
281 281  Category inherits from //Item// and has the following attributes:
282 282  
283 -id uri urn
312 +id
313 +uri
314 +urn
284 284  
285 285  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).
286 286  
... ... @@ -298,22 +298,20 @@
298 298  
299 299  ==== 4.6.4.1 Definitions ====
300 300  
332 +(% style="width:753.039px" %)
301 301  |**Class**|(% colspan="2" %)**Feature**|**Description**
302 302  |CategoryScheme|(% colspan="2" %)(((
303 303  Inherits from
304 -
305 305  //ItemScheme//
306 306  )))|The descriptive information for an arrangement or division of categories into groups based on characteristics, which the objects have in common.
307 307  | |(% colspan="2" %)/items|Associates the categories.
308 308  |Category|(((
309 309  Inherits from
310 -
311 311  //Item//
312 312  )))|(% colspan="2" %)An item at any level within a classification, typically tabulation categories, sections, subsections, divisions, subdivisions, groups, subgroups, classes and subclasses.
313 313  | |/hierarchy|(% colspan="2" %)Associates the parent and the child Category.
314 314  |Categorisation|(((
315 315  Inherits from
316 -
317 317  //MaintainableArtefact//
318 318  )))|(% colspan="2" %)Associates an Identifable Artefact with a Category.
319 319  | |+categorisedArtefact|(% colspan="2" %)Associates the Identifable Artefact.
... ... @@ -347,91 +347,75 @@
347 347  
348 348  ==== 4.7.2.2 Definitions ====
349 349  
350 -|**Class**|**Feature**|**Description**
351 -|//OrganisationScheme//|(((
379 +(% style="width:763.039px" %)
380 +|**Class**|(% style="width:246px" %)**Feature**|(% style="width:336px" %)**Description**
381 +|//OrganisationScheme//|(% style="width:246px" %)(((
352 352  Abstract Class Inherits from
353 -
354 354  //ItemScheme//
355 355  
356 356  Sub classes are:
357 -
358 358  AgencyScheme
359 -
360 360  DataProviderScheme
361 -
362 362  MetadataProviderScheme DataConsumerScheme
363 -
364 364  OrganisationUnitScheme
365 -)))|A maintained collection of Organisations.
366 -| |/items|(((
390 +)))|(% style="width:336px" %)A maintained collection of Organisations.
391 +| |(% style="width:246px" %)/items|(% style="width:336px" %)(((
367 367  Association to the
368 368  
369 369  Organisations in the scheme.
370 370  )))
371 -|//Organisation//|(((
396 +|//Organisation//|(% style="width:246px" %)(((
372 372  Abstract Class
398 +Inherits from //Item//
373 373  
374 -Inherits from
375 -
376 -//Item//
377 -
378 378  Sub classes are:
379 -
380 380  Agency
381 -
382 382  DataProvider
383 -
384 384  MetadataProvider DataConsumer
385 -
386 386  OrganisationUnit
387 -)))|An organisation is a unique framework of authority within which a person or persons act, or are designated to act, towards some purpose.
388 -| |+contact|Association to the Contact information.
389 -| |/hierarchy|Association to child Organisations.
390 -|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.
391 -| |name|The designation of the Contact person by a linguistic expression.
392 -| |organisationUnit|The designation of the organisational structure by a linguistic expression, within which Contact person works.
393 -| |responsibility|The function of the contact person with respect to the organisation role for which this person is the Contact.
394 -| |telephone|The telephone number of the Contact.
395 -| |fax|The fax number of the Contact.
396 -| |email|The Internet e-mail address of the Contact.
397 -| |X400|The X400 address of the Contact.
398 -| |uri|The URL address of the Contact.
399 -|AgencyScheme| |A maintained collection of Maintenance Agencies.
400 -| |/items|Association to the Maintenance Agency in the scheme.
401 -|DataProviderScheme| |A maintained collection of Data Providers.
402 -| |/items|Association to the Data Providers in the scheme.
403 -|MetadataProviderScheme| |A maintained collection of Metadata Providers.
404 -| |/items|Association to the Metadata Providers in the scheme.
405 -|DataConsumerScheme| |A maintained collection of Data Consumers.
406 -| |/items|Association to the Data Consumers in the scheme.
407 -|OrganisationUnitScheme| |A maintained collection of Organisation Units.
408 -| |/items|Association to the Organisation Units in the scheme.
409 -|Agency|(((
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" %)(((
410 410  Inherits from
411 -
412 412  //Organisation//
413 -)))|Responsible agency for maintaining artefacts such as statistical classifications, glossaries, structural metadata such as Data and Metadata Structure Definitions, Concepts and Code lists.
414 -|DataProvider|(((
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" %)(((
415 415  Inherits from
416 -
417 417  //Organisation//
418 -)))|An organisation that produces data.
419 -|MetadataProvider|(((
434 +)))|(% style="width:336px" %)An organisation that produces data.
435 +|MetadataProvider|(% style="width:246px" %)(((
420 420  Inherits from
421 -
422 422  //Organisation//
423 -)))|An organisation that produces reference metadata.
424 -|DataConsumer|(((
438 +)))|(% style="width:336px" %)An organisation that produces reference metadata.
439 +|DataConsumer|(% style="width:246px" %)(((
425 425  Inherits from
426 -
427 427  //Organisation//
428 -)))|An organisation using data as input for further processing.
429 -|OrganisationUnit|(((
442 +)))|(% style="width:336px" %)An organisation using data as input for further processing.
443 +|OrganisationUnit|(% style="width:246px" %)(((
430 430  Inherits from
431 -
432 432  //Organisation//
433 -)))|A designation in the organisational structure.
434 -| |/hierarchy|Association to child Organisation Units
446 +)))|(% style="width:336px" %)A designation in the organisational structure.
447 +| |(% style="width:246px" %)/hierarchy|(% style="width:336px" %)Association to child Organisation Units
435 435  
436 436  == 4.8 Reporting Taxonomy ==
437 437  
... ... @@ -465,22 +465,21 @@
465 465  
466 466  ==== 4.8.2.2 Definitions ====
467 467  
468 -|**Class**|**Feature**|**Description**
469 -|ReportingTaxonomy|(((
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" %)(((
470 470  Inherits from
471 -
472 472  //ItemScheme//
473 -)))|A scheme which defines the composition structure of a data report where each component can be described by an independent Dataflow or Metadataflow.
474 -| |/items|Associates the Reporting Category
475 -|ReportingCategory|(((
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" %)(((
476 476  Inherits from
477 -
478 478  //Item//
479 -)))|A component that gives structure to the report and links to data and metadata.
480 -| |/hierarchy|Associates child Reporting Category.
481 -| |+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.
482 -| |+structure|(((
483 -Association to the Data Structure
484 -
485 -Definition and Metadata Structure Definitions which define the structural metadata describing the data and metadata that are contained at this part of the report.
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.
486 486  )))
497 +
498 +{{putFootnotes/}}