Skip to Content

Changes for page 4 Specific Item Schemes

Last modified by Artur on 2025/09/10 11:19
From version 15.5
edited by Helena
on 2025/05/16 13:43
Change comment: There is no comment for this version
To version 15.10
edited by Helena
on 2025/05/16 13:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -174,7 +174,16 @@
174 174  
175 175  A ValueList inherits from //EnumeratedList// (and hence the //MaintenableArtefact//) and thus has the following attributes:
176 176  
177 -id// //uri// //urn// //version// //validFrom// //validTo// //isExternalReference registryURL structureURL repositoryURL
177 +id
178 +uri
179 +urn
180 +version
181 +validFrom
182 +validTo
183 +isExternalReference
184 +registryURL
185 +structureURL
186 +repositoryURL
178 178  
179 179  ValueItem inherits from //EnumeratedItem//, which adds an id, with relaxed constraints, to the former.
180 180  
... ... @@ -207,10 +207,26 @@
207 207  
208 208  === 4.5.2 Explanation of the Diagram ===
209 209  
210 -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:
219 +The ConceptScheme inherits from the //ItemScheme //and therefore has the following attributes:
211 211  
212 -id uri urn
221 +id
222 +uri
223 +urn
224 +version
225 +validFrom
226 +validTo
227 +isExternalReference
228 +registryURL
229 +structureURL
230 +repositoryURL
231 +isPartial
213 213  
233 +Concept inherits from Item and has the following attributes:
234 +
235 +id
236 +uri
237 +urn
238 +
214 214  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).
215 215  
216 216  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.
... ... @@ -241,12 +241,10 @@
241 241  |(% style="width:204px" %)**Class**|(% style="width:222px" %)**Feature**|(% style="width:337px" %)**Description**
242 242  |(% style="width:204px" %)ConceptScheme|(% style="width:222px" %)(((
243 243  Inherits from
244 -
245 245  //ItemScheme//
246 246  )))|(% style="width:337px" %)The descriptive information for an arrangement or division of concepts into groups based on characteristics, which the objects have in common.
247 247  |(% style="width:204px" %)Concept|(% style="width:222px" %)(((
248 248  Inherits from
249 -
250 250  //Item//
251 251  )))|(% style="width:337px" %)A concept is a unit of knowledge created by a unique combination of characteristics.
252 252  |(% style="width:204px" %) |(% style="width:222px" %)/hierarchy|(% style="width:337px" %)Associates the parent and the child concept.
... ... @@ -275,11 +275,22 @@
275 275  
276 276  The categories are modelled as a hierarchical //ItemScheme//. The CategoryScheme inherits from the //ItemScheme// and has the following attributes:
277 277  
278 -id uri urn version validFrom validTo isExternalReference structureURL serviceURL isPartial
301 +id
302 +uri
303 +urn
304 +version
305 +validFrom
306 +validTo
307 +isExternalReference
308 +structureURL
309 +serviceURL
310 +isPartial
279 279  
280 280  Category inherits from //Item// and has the following attributes:
281 281  
282 -id uri urn
314 +id
315 +uri
316 +urn
283 283  
284 284  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).
285 285  
... ... @@ -301,19 +301,16 @@
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.
... ... @@ -351,17 +351,12 @@
351 351  |**Class**|(% style="width:246px" %)**Feature**|(% style="width:336px" %)**Description**
352 352  |//OrganisationScheme//|(% style="width:246px" %)(((
353 353  Abstract Class Inherits from
354 -
355 355  //ItemScheme//
356 356  
357 357  Sub classes are:
358 -
359 359  AgencyScheme
360 -
361 361  DataProviderScheme
362 -
363 363  MetadataProviderScheme DataConsumerScheme
364 -
365 365  OrganisationUnitScheme
366 366  )))|(% style="width:336px" %)A maintained collection of Organisations.
367 367  | |(% style="width:246px" %)/items|(% style="width:336px" %)(((
... ... @@ -371,19 +371,12 @@
371 371  )))
372 372  |//Organisation//|(% style="width:246px" %)(((
373 373  Abstract Class
400 +Inherits from //Item//
374 374  
375 -Inherits from
376 -
377 -//Item//
378 -
379 379  Sub classes are:
380 -
381 381  Agency
382 -
383 383  DataProvider
384 -
385 385  MetadataProvider DataConsumer
386 -
387 387  OrganisationUnit
388 388  )))|(% 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.
389 389  | |(% style="width:246px" %)+contact|(% style="width:336px" %)Association to the Contact information.
... ... @@ -409,27 +409,22 @@
409 409  | |(% style="width:246px" %)/items|(% style="width:336px" %)Association to the Organisation Units in the scheme.
410 410  |Agency|(% style="width:246px" %)(((
411 411  Inherits from
412 -
413 413  //Organisation//
414 414  )))|(% 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.
415 415  |DataProvider|(% style="width:246px" %)(((
416 416  Inherits from
417 -
418 418  //Organisation//
419 419  )))|(% style="width:336px" %)An organisation that produces data.
420 420  |MetadataProvider|(% style="width:246px" %)(((
421 421  Inherits from
422 -
423 423  //Organisation//
424 424  )))|(% style="width:336px" %)An organisation that produces reference metadata.
425 425  |DataConsumer|(% style="width:246px" %)(((
426 426  Inherits from
427 -
428 428  //Organisation//
429 429  )))|(% style="width:336px" %)An organisation using data as input for further processing.
430 430  |OrganisationUnit|(% style="width:246px" %)(((
431 431  Inherits from
432 -
433 433  //Organisation//
434 434  )))|(% style="width:336px" %)A designation in the organisational structure.
435 435  | |(% style="width:246px" %)/hierarchy|(% style="width:336px" %)Association to child Organisation Units