There is a GSIM annex on Statistical Classification, which provides additional information on implementing the GSIM classification objects. For example, the attribute lists includes attributes that are inherited.
At the moment, all this detail is also included in GSIM.
(NB: separate issue for whether these attributes should be on Node Set or Statistical Classification, and Node vs Classification Item)
The work below tries to detail where changes should be made to GSIM attributes so to keep the modelling correct and consistent, but also to make it still useable to non-modellers. Note the additional detail/specification will be kept in the classification annex.
Summary
| Current | Proposal | Affects |
|---|---|---|
| Owner | Base Group: Role | Classification Series, Correspondence Table |
| Release date | Administrative Details: attribute -> Created Date | Classification Index |
| Termination date | Administrative Details: attribute -> Valid Until | Statistical Classification |
| Maintenance unit | Base Group: Role | Statistical Classification, Classification Index, Correspondence Table |
| Contact persons | Base Group: Agent in Role | Statistical Classification, Classification Index, Correspondence Table |
| Publications | Administrative Details: attribute -> Documentation | Statistical Classification, Classification Index, Correspondence Table |
| Changes from previous version or update | Base Group: Change Event or Change Event Tuple | Statistical Classification |
| Changes from base Statistical Classification | Base Group: Change Event or Change Event Tuple | Statistical Classification |
| Changes from previous version of the Statistical Classification | Base Group: Change Event or Change Event Tuple | Classification Item |
Identifier | Identifiable Artefact: : attribute -> Id | Correspondence Table |
| Alternative names | Administrative Details: attribute -> Alias | Classification Item |
| Explanatory notes | Concept Group: Explanatory notes | Statistical Classification |
| Valid from | Administrative Details: attribute -> Valid From | Classification Item, Map, Classification Index Entry |
| Valid to | Administrative Details: attribute -> Valid Until | Classification Item, Map, Classification Index Entry |
| Current GSIM attributes | Description | Proposed |
|---|---|---|
| Name | These are the two attributes that every object inherits from Identifiable artefact Update description to use standard text | |
| Description |
| Current GSIM attributes | Description | Proposed |
|---|---|---|
| Name | These are the two attributes that every object inherits from Identifiable artefact Update description to use standard text | |
| Description | ||
| Context | No change | |
| Objects/units classified | No change | |
| Subject areas | No change | |
| Owners | There is an object in the Base Group called "role": The responsible function involved in the statistical Business Process. | |
| Keywords | No change |
Statistical Classification (NB: separate issue for whether these attributes should be on Node Set or Statistical Classification)
| Current GSIM attributes | Description | Proposed |
|---|---|---|
| Name | These are the two attributes that every object inherits from Identifiable artefact Update description to use standard text | |
| Description | ||
| Introduction | The introduction provides a detailed description of the Statistical Classification, the background for its creation, the classification variable and objects/units classified, classification rules etc. | Change Statistical Classification to NodeSet |
| Release date | Date on which the Statistical Classification was released. | This is an attribute that can be inherited from Administrative Details: Created Date: The date on which the information object was created Update description to use standard text - Make a note of inheritance |
| Termination date | Date on which the Statistical Classification was superseded by a successor version or otherwise ceased to be valid. | This is an attribute that can be inherited from Administrative Details: Valid Until - "The date on which the information object is no longer effective or valid." Update description to use standard text - Make a note of inheritance |
| Current | Indicates whether or not the Statistical Classification is currently valid. | Change Statistical Classification to NodeSet |
| Maintenance unit | The unit or group of persons within the organisation who are responsible for the Statistical Classification (i.e, for maintaining, updating and changing it). | There is an object in the Base Group called "role": The responsible function involved in the statistical Business Process. |
| Contact persons | Person(s) who may be contacted for additional information about the Statistical Classification. | There is an object in Base Group call "Agent In Role" Definition: Reflects an agent acting in a specific role. Explanatory Text: An Agent In Role may apply to either type of Agent - an Organization or Individual. The object is intended to reflect a single Agent acting in a single Role and as such is a very unambiguous representation. A common example would be to identify which Individuals or departments within an Organization provide administrative data. |
| Legal base | Indicates that the Statistical Classification is covered by a legal act or by some other formal agreement. | Change Statistical Classification to NodeSet |
| Publications | A list of the publications, including print, PDF, HTML and other electronic formats, in which the Statistical Classification has been published. | This is an attribute that can be inherited from Administrative Details: Documentation - "An official document or paper that has been published by an organization. " Update description to use standard text - Make a note of inheritance |
| Name types | A list of the defined types of alternative item names available for the Statistical Classification. Each name type refers to a list of alternative item names. | Change Statistical Classification to NodeSet |
| Languages available | A Statistical Classification can exist in one or several languages. Indicates the languages available, whether the version is completely or partially translated, and which part is available in which language. | Change Statistical Classification to NodeSet |
| Copyright | Statistical Classifications may have restricted copyrights. Such Statistical Classifications might be excluded from downloading. Notes the copyright statement that should be displayed in official publications to indicate the copyright owner. | Change Statistical Classification to NodeSet |
| Dissemination allowed | Indicates whether or not the Statistical Classification may be published or otherwise disseminated (e.g. electronic dissemination). | Change Statistical Classification to NodeSet |
| Version | Indicates if the Statistical Classification is a version. | Change Statistical Classification to NodeSet |
| Update | Indicates if the Statistical Classification is an update. | Change Statistical Classification to NodeSet |
| Floating | Indicates if the Statistical Classification is a floating classification. In a floating statistical classification, a validity period should be defined for all Classification Items which will allow the display of the item structure and content at different points of time. | Change Statistical Classification to NodeSet, Classification Item to Node. |
| Predecessor | For those Statistical Classifications that are versions or updates, notes the preceding Statistical Classification of which the actual Statistical Classification is the successor. | Change Statistical Classification to NodeSet |
| Successor | Notes the Statistical Classification that superceded the actual Statistical Classification. | Change Statistical Classification to NodeSet |
| Changes from previous version or update | A summary description of the nature and content of changes from the preceding version or update. Specific changes are recorded in the Classification Item object under the “Changes from previous version and updates” attribute. | There is an object in the Base Group called "Change Event": A change event captures that a change has occurred. It identifies the information objects that have been affected, and the new information objects that have been created due to the change. "Change Event Tuple": A Change Event Tuple records which Identifiable Artefacts were changed by a Change Event. It keeps track of the source Identifiable Artefact(s) to which the Change Event was applied and the resulting target Identifiable Artefact(s). |
| Derived from | A Statistical Classification can be derived from one of the classification versions of another Classification Series. The derived Statistical Classification can either inherit the structure of the classification version from which it is derived, usually adding more detail, or use a large part of its Classification Items, rearranging them in a different structure. Indicates the classification version from which the actual Statistical Classification is derived. | Change Statistical Classification to NodeSet, Classification Item to Node. Not sure about series reference |
| Updates possible | Indicates whether or not updates are allowed within the classification version i.e. without leading to a new version. Indicate here what structural changes, if any, are permissable within a version. Note whether Classification Items can be added to the structure and whether they can be revalidated or invalidated. Such changes are more likely to be permissable in floating classifications. Also indicate whether changes to such things as Classification Item names and explanatory notes that do not involve structural changes are permissible within a version. | Change Statistical Classification to NodeSet, Classification Item to Node |
| Updates | Summary description of changes which have occurred since the most recent classification version or classificationupdate came into force. | Remove classification |
| Variants available | Identifies any variants associated with this version. | No change |
| Variant | For those Statistical Classifications that are variants, notes the Statistical Classification on which it is based and any subsequent versions of that Statistical Classification to which it is also applicable. | Change Statistical Classification to NodeSet |
| Changes from base Statistical Classification | Describes the relationship between the variant and its base Statistical Classification, including regroupings, aggregations added and extensions. | There is an object in the Base Group called "Change Event": A change event captures that a change has occurred. It identifies the information objects that have been affected, and the new information objects that have been created due to the change. "Change Event Tuple": A Change Event Tuple records which Identifiable Artefacts were changed by a Change Event. It keeps track of the source Identifiable Artefact(s) to which the Change Event was applied and the resulting target Identifiable Artefact(s). |
| Purpose of variant | If the Statistical Classification is a variant, notes the specific purpose for which it was developed. | Change Statistical Classification to NodeSet |
| Current GSIM attributes | Description | Proposed |
|---|---|---|
| Name | These are the two attributes that every object inherits from Identifiable artefact Update description to use standard text | |
| Description | ||
| Level number | The number associated with the Level. Levels are numbered consecutively starting with level 1 at the highest (most aggregated) Level. | No change |
| Level name | The name given to the Level. | No change |
| Issue #90: Attributes of Classification objects agrees to remove this attribute | ||
| Code type | Indicates whether the item code at the Level is alphabetical, numerical or alphanumerical. | No change |
| Code structure | Indicates how the code is constructed of numbers, letters and separators. | No change |
| Dummy code | Rule for the construction of dummy codes from the codes of the next higher level (used when one or several categories are the same in two consecutive levels). | No change |
| Items | An ordered list of the Categories (Classification Items) that constitute the Level. | Change Classification Item to Node |
| Current GSIM attributes | Description | Proposed |
|---|---|---|
| Name | These are the two attributes that every object inherits from Identifiable artefact Update description to use standard text | |
| Description | ||
| Identifier | A Correspondence Table is identified by a unique identifier, which may typically include the identifiers of the versions or variants involved. | This is an attribute that can be inherited from Identifiable Artefact: Id: The unique identifier of the information object; assigned by the owner agency.. Update description to use standard text - Make a note of inheritance |
| Owners | The statistical office, other authority or section that created and maintains the Correspondence Table. A Correspondence Table may have several owners. | There is an object in the Base Group called "role": The responsible function involved in the statistical Business Process. |
| Maintenance unit | The unit or group of persons who are responsible for the Correspondence Table, i.e. for maintaining and updating it. | There is an object in the Base Group called "role": The responsible function involved in the statistical Business Process. |
| Contact persons | The person(s) who may be contacted for additional information about the Correspondence Table. | There is an object in Base Group call "Agent In Role" Definition: Reflects an agent acting in a specific role. Explanatory Text: An Agent In Role may apply to either type of Agent - an Organization or Individual. The object is intended to reflect a single Agent acting in a single Role and as such is a very unambiguous representation. A common example would be to identify which Individuals or departments within an Organization provide administrative data. |
| Publications | A list of the publications in which the Correspondence Table has been published. | This is an attribute that can be inherited from Administrative Details: Documentation - "An official document or paper that has been published by an organization. " Update description to use standard text - Make a note of inheritance |
| Source | The Statistical Classification from which the correspondence is made. | Change Statistical Classification to NodeSet |
| Target | The Statistical Classification(s) to which the correspondence is directed. There may be multiple Target Statistical Classifications associated with the Correspondence Table. | Change Statistical Classification to NodeSet |
| Source level | The correspondence is normally restricted to a certain Level in the source Statistical Classification. In this case, target items are assigned only to source items on the given level. If no level is indicated, target items can be assigned to any level of the source Statistical Classification. | Change Statistical Classification to NodeSet |
| Target level | The correspondence is normally restricted to a certain Level in the target Statistical Classification. In this case, source items are assigned only to target items on the given level. If no level is indicated, source items can be assigned to any level of the target Statistical Classification. | Change Statistical Classification to NodeSet |
| Relationship type | A correspondence can define a 1:1, 1:N, N:1 or M:N relationship between source and target items. | |
| Floating | If the source and/or target Statistical Classifications of a correspondence table are floating classifications, the date of the correspondence table must be noted. The correspondence table expresses the relationships between the two Statistical Classifications as they existed on the date specified in the table. | Change Statistical Classification to NodeSet |
| Current GSIM attributes | Description | Proposed |
|---|---|---|
| Name | These are the two attributes that every object inherits from Identifiable artefact Update description to use standard text | |
| Description | ||
| Release date | Date when the current version of the Classification Index was released. | This is an attribute that can be inherited from Administrative Details: Created Date: The date on which the information object was created Update description to use standard text - Make a note of inheritance |
| Maintenance unit | The unit or group of persons within the organisation responsible for the Classification Index, i.e. for adding, changing or deleting Classification Index Entries. | There is an object in the Base Group called "role": The responsible function involved in the statistical Business Process. |
| Contact persons | Person(s) who may be contacted for additional information about the Classification Index. | There is an object in Base Group call "Agent In Role" Definition: Reflects an agent acting in a specific role. Explanatory Text: An Agent In Role may apply to either type of Agent - an Organization or Individual. The object is intended to reflect a single Agent acting in a single Role and as such is a very unambiguous representation. A common example would be to identify which Individuals or departments within an Organization provide administrative data. |
| Publications | A list of the publications in which the Classification Index has been published. | This is an attribute that can be inherited from Administrative Details: Documentation - "An official document or paper that has been published by an organization. " Update description to use standard text - Make a note of inheritance |
| Languages | A Classification Index can exist in several languages. Indicates the languages available. If a Classification Index exists in several languages, the number of entries in each language may be different, as the number of terms describing the same phenomenon can change from one language to another. However, the same phenomena should be described in each language. | |
| Corrections | ||
| Coding Instructions | Additional information which drives the coding process for all entries in a Classification Index. |
Classification Item (NB: separate issue for whether these attributes should be on Node or Classification Item)
| Current GSIM attributes | Description | Proposed |
|---|---|---|
| Name | These are the two attributes that every object inherits from Identifiable artefact Update description to use standard text | |
| Description | ||
| Code | A Classification Item is identified by an alphabetical, numerical or alphanumerical code, which is in line with the code structure of the classification Level. The code is unique within the Statistical Classification to which the item belongs. | Change Statistical Classification to NodeSet, Classification Item to Node |
| Official name | A Classification Item has a name as provided by the owner or maintenance unit. The name describes the content of the category. The name is unique within the Statistical Classification to which the item belongs, except for categories that are identical at more than one level in a hierarchical classification. | Change Statistical Classification to NodeSet, Classification Item to Node |
| Alternative names | A Classification Item can be expressed in terms of one or several alternative names. Each alternative name is associated with a name type. | This is an attribute that can be inherited from Administrative Details: Alias: The alias or alia associated with the information object. Update description to use standard text - Make a note of inheritance |
| Explanatory notes | A Classification Item may be associated with explanatory notes, which further describe and clarify the contents of the Category. Explanatory notes consist of: General note: Contains either additional information about the Category, or a general description of the Category, which is not structured according to the "includes", "includes also", "excludes" pattern. Includes: Specifies the contents of the Category. Includes also: A list of borderline cases, which belong to the described Category. Excludes: A list of borderline cases, which do not belong to the described Category. Excluded cases may contain a reference to the Classification Items to which the excluded cases belong. | LIM proposed this to be a separate object with attributes of:
|
| Level number | The number of the Level to which the item belongs. | |
| Generated | Indicates whether or not the item has been generated to make the level to which it belongs complete. | |
| Currently valid | If updates are allowed in the Statistical Classification, an item may be restricted in its validity, i.e. it may become valid or invalid after the Statistical Classification has been released. Indicates whether or not the item is currently valid. | Change Statistical Classification to NodeSet |
| Valid from | Date from which the item became valid. The date must be defined if the item belongs to a floating Statistical classification. | This is an attribute that can be inherited from Administrative Details: Valid From- "The date on which the information object is effective or valid." Update description to use standard text - Make a note of inheritance |
| Valid to | Date at which the item became invalid. The date must be defined if the item belongs to a floating Statistical classification and is no longer valid. | This is an attribute that can be inherited from Administrative Details: Valid Until - "The date on which the information object is no longer effective or valid." Update description to use standard text - Make a note of inheritance |
| Future events | The future events describe a change (or a number of changes) related to an invalid item. These changes may e.g. have turned the now invalid item into one or several successor items. This allows the possibility to follow successors of the item in the future. | |
| Changes from previous version of the Statistical Classification | Describes the changes, which the item has been subject to from the previous version to the actual Statistical Classification. | There is an object in the Base Group called "Change Event": A change event captures that a change has occurred. It identifies the information objects that have been affected, and the new information objects that have been created due to the change. "Change Event Tuple": A Change Event Tuple records which Identifiable Artefacts were changed by a Change Event. It keeps track of the source Identifiable Artefact(s) to which the Change Event was applied and the resulting target Identifiable Artefact(s). |
| Updates | Describes the changes, which the item has been subject to during the life time of the actual Statistical Classification. | Change Statistical Classification to NodeSet |
| Parent item | The item at the next higher level of the classification Statistical Classification of which the actual item is a sub item. | Change Statistical Classification to NodeSet |
| Sub items | Each item, which is not at the lowest level of the Statistical Classification, might contain one or a number of sub items, i.e. items at the next lower level of the Statistical Classification. | Change Statistical Classification to NodeSet |
| Linked items | Items of other classification versions or variants with which the item is linked, either as source or target, through Correspondence Tables. | |
| Case laws | Refers to identifiers of one or more case law rulings related to the Classification Item. | Change Classification Item to Node |
| Case law descriptions | Refers to descriptions of the above case laws | |
| Case law dates | Refers to date of above case laws |
| Current GSIM attributes | Description | Proposed |
|---|---|---|
| Name | These are the two attributes that every object inherits from Identifiable artefact Update description to use standard text | |
| Description | ||
| Valid from | Date from which the Map became valid. The date must be defined if the Map belongs to a floating correspondence table. | This is an attribute that can be inherited from Administrative Details: Valid From- "The date on which the information object is effective or valid." Update description to use standard text - Make a note of inheritance |
| Valid to | Date at which the Map became invalid. The date must be defined if the Map belongs to a floating correspondence table and is no longer valid. | This is an attribute that can be inherited from Administrative Details: Valid Until - "The date on which the information object is no longer effective or valid." Update description to use standard text - Make a note of inheritance |
| Current GSIM attributes | Description | Proposed |
|---|---|---|
| Name | These are the two attributes that every object inherits from Identifiable artefact Update description to use standard text | |
| Description | ||
| Text | Text describing the type of object/unit or object property. | |
| Valid from | Date from which the Classification Index Entry became valid. The date must be defined if the Classification Index Entry belongs to a floating Classification Index. | This is an attribute that can be inherited from Administrative Details: Valid From- "The date on which the information object is effective or valid." Update description to use standard text - Make a note of inheritance |
| Valid to | Date at which the Classification Index Entry became invalid. The date must be defined if the Classification Index Entry belongs to a floating Classification Index and is no longer valid. | This is an attribute that can be inherited from Administrative Details: Valid Until - "The date on which the information object is no longer effective or valid." Update description to use standard text - Make a note of inheritance |
| Coding Instructions | Additional information which drives the coding process. Required when coding is dependent upon one or many other factors. |
- No labels
1 Comment
user-8e470
Meeting 15/5
Following changes agreed
Identifier
Identifiable Artefact: : attribute -> Id
Change Administrative Details attribute to Valid To as it is more inclusive.