Changes for page 4 Specific Item Schemes

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

From 15.4 to 15.5 From 16.1 to 16.2

From version 15.5

edited by Helena
on 2025/05/16 13:43

Change comment: There is no comment for this version

To version 16.1

edited by Helena
on 2025/05/16 13:48

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

@@ -174,7 +174,16 @@
  A ValueList inherits from //EnumeratedList// (and hence the //MaintenableArtefact//) and thus has the following attributes:
--id// //uri// //urn// //version// //validFrom// //validTo// //isExternalReference registryURL structureURL repositoryURL
++id
++uri
++urn
++version
++validFrom
++validTo
++isExternalReference
++registryURL
++structureURL
++repositoryURL
  ValueItem inherits from //EnumeratedItem//, which adds an id, with relaxed constraints, to the former.
@@ -207,10 +207,26 @@
  === 4.5.2 Explanation of the Diagram ===
--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:
++The ConceptScheme inherits from the //ItemScheme //and therefore has the following attributes:
--id uri urn
++id
++uri
++urn
++version
++validFrom
++validTo
++isExternalReference
++registryURL
++structureURL
++repositoryURL
++isPartial
++Concept inherits from Item and has the following attributes:
++
++id
++uri
++urn
++
  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).
  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 @@
  |(% style="width:204px" %)**Class**|(% style="width:222px" %)**Feature**|(% style="width:337px" %)**Description**
  |(% style="width:204px" %)ConceptScheme|(% style="width:222px" %)(((
  Inherits from
--
  //ItemScheme//
  )))|(% style="width:337px" %)The descriptive information for an arrangement or division of concepts into groups based on characteristics, which the objects have in common.
  |(% style="width:204px" %)Concept|(% style="width:222px" %)(((
  Inherits from
--
  //Item//
  )))|(% style="width:337px" %)A concept is a unit of knowledge created by a unique combination of characteristics.
  |(% style="width:204px" %) |(% style="width:222px" %)/hierarchy|(% style="width:337px" %)Associates the parent and the child concept.
@@ -275,11 +275,22 @@
  The categories are modelled as a hierarchical //ItemScheme//. The CategoryScheme inherits from the //ItemScheme// and has the following attributes:
--id uri urn version validFrom validTo isExternalReference structureURL serviceURL isPartial
++id
++uri
++urn
++version
++validFrom
++validTo
++isExternalReference
++structureURL
++serviceURL
++isPartial
  Category inherits from //Item// and has the following attributes:
--id uri urn
++id
++uri
++urn
  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).
@@ -301,19 +301,16 @@
  |**Class**|(% colspan="2" %)**Feature**|**Description**
  |CategoryScheme|(% colspan="2" %)(((
  Inherits from
--
  //ItemScheme//
  )))|The descriptive information for an arrangement or division of categories into groups based on characteristics, which the objects have in common.
  | |(% colspan="2" %)/items|Associates the categories.
  |Category|(((
  Inherits from
--
  //Item//
  )))|(% colspan="2" %)An item at any level within a classification, typically tabulation categories, sections, subsections, divisions, subdivisions, groups, subgroups, classes and subclasses.
  | |/hierarchy|(% colspan="2" %)Associates the parent and the child Category.
  |Categorisation|(((
  Inherits from
--
  //MaintainableArtefact//
  )))|(% colspan="2" %)Associates an Identifable Artefact with a Category.
  | |+categorisedArtefact|(% colspan="2" %)Associates the Identifable Artefact.
@@ -351,17 +351,12 @@
  |**Class**|(% style="width:246px" %)**Feature**|(% style="width:336px" %)**Description**
  |//OrganisationScheme//|(% style="width:246px" %)(((
  Abstract Class Inherits from
--
  //ItemScheme//
  Sub classes are:
--
  AgencyScheme
--
  DataProviderScheme
--
  MetadataProviderScheme DataConsumerScheme
--
  OrganisationUnitScheme
  )))|(% style="width:336px" %)A maintained collection of Organisations.
  | |(% style="width:246px" %)/items|(% style="width:336px" %)(((
@@ -371,19 +371,12 @@
  )))
  |//Organisation//|(% style="width:246px" %)(((
  Abstract Class
++Inherits from //Item//
--Inherits from
--
--//Item//
--
  Sub classes are:
--
  Agency
--
  DataProvider
--
  MetadataProvider DataConsumer
--
  OrganisationUnit
  )))|(% 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.
  | |(% style="width:246px" %)+contact|(% style="width:336px" %)Association to the Contact information.
@@ -409,27 +409,22 @@
  | |(% style="width:246px" %)/items|(% style="width:336px" %)Association to the Organisation Units in the scheme.
  |Agency|(% style="width:246px" %)(((
  Inherits from
--
  //Organisation//
  )))|(% 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.
  |DataProvider|(% style="width:246px" %)(((
  Inherits from
--
  //Organisation//
  )))|(% style="width:336px" %)An organisation that produces data.
  |MetadataProvider|(% style="width:246px" %)(((
  Inherits from
--
  //Organisation//
  )))|(% style="width:336px" %)An organisation that produces reference metadata.
  |DataConsumer|(% style="width:246px" %)(((
  Inherits from
--
  //Organisation//
  )))|(% style="width:336px" %)An organisation using data as input for further processing.
  |OrganisationUnit|(% style="width:246px" %)(((
  Inherits from
--
  //Organisation//
  )))|(% style="width:336px" %)A designation in the organisational structure.
  | |(% style="width:246px" %)/hierarchy|(% style="width:336px" %)Association to child Organisation Units
@@ -470,13 +470,11 @@
  |(% style="width:177px" %)**Class**|(% style="width:152px" %)**Feature**|(% style="width:428px" %)**Description**
  |(% style="width:177px" %)ReportingTaxonomy|(% style="width:152px" %)(((
  Inherits from
--
  //ItemScheme//
  )))|(% 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.
  |(% style="width:177px" %) |(% style="width:152px" %)/items|(% style="width:428px" %)Associates the Reporting Category
  |(% style="width:177px" %)ReportingCategory|(% style="width:152px" %)(((
  Inherits from
--
  //Item//
  )))|(% style="width:428px" %)A component that gives structure to the report and links to data and metadata.
  |(% style="width:177px" %) |(% style="width:152px" %)/hierarchy|(% style="width:428px" %)Associates child Reporting Category.