These are logged in different issues, but compiled here to ensure we have consistent approach.


Attributes inheritance Issue

Issue #

Object with “Date” issue

Can be covered by

GSIM Sprint (23 Jan)

Comment #2 from Issue #2-22

Assessment – Date Assessed (1..*)

AD – Created Date (0..1), IA – Version Date (0..1) or AD – Last Updated Date (0..1)

  • To remove Date Assessed from Assessment
  • To add attribute Date Assessed to Administrative Details

Comment #3 from Issue #2-22

Business Case – Date Initiated (0..1)

Business Process - Date Initiated (0..1)

Business Process – Date Ended (0..1)

Business Statistical Program - Date Initiated (0..1)

Business Statistical Program - Date Ended (0..1)

AD - Valid From (0..1)

AD - Valid From (0..1)

AD – Valid To (0..1)

AD - Valid From (0..1)

AD – Valid To (0..1)

If we are going to use those often maybe we would want to add Date Initiated and Date Ended to AD

  • To remove above two from business group
  • To add above two with text stating that they are appropriate for business group


Comment #11 from Issue #2-22

Statistical Program Cycle – Reference Period End (1..1)

Statistical Program Cycle – Reference Period Start (1..1)

AD – Valid To (0..1)

AD – Valid From (0..1)

There is semantic difference. So no.

Comment #12 from Issue #2-22

Statistical Program Design – Date Ended (0..1)

Statistical Program Design – Date Initiated (0..1)

Statistical Support Program – Date Ended (0..1)

Statistical Support Program – Date Initiated (0..1)

AD - Valid From (0..1)

AD – Valid To (0..1)

AD - Valid From (0..1)

AD – Valid To (0..1)

Same for the second row.

Comment #2-c from Issue #2-23

Classification Index – Release Date (0..1)

AD – Valid From (0..1) or IA – Version Date (0..1)

  • To remove Release Date from Classification Index
  • To add above attribute to AD

Comment #2 from Issue #2-24

Questionnaire – Date Replacement (1..1)

AD – Valid To (0..1)

To remove Date Replacement from Questionnaire

Comment #2 from Issue #2-25

Dimensional Data Set - Data Extraction Date (0..1, value type-DateTime)


AD – Created Date (0..1, value type-Date)

To remove Date Extraction Date from Dimensional Data Set

Comment #3 from Issue #2-25

Information Resource – Location (1..*)

AD – Url (0..*)

To remove Location (already can inherit id from IA)


Agent In Role Issue

Issue #

Attributes that can be covered with Agent In Role

GSIM Sprint (23 Jan)

Comment #2 from Issue #2-23

Classification Index – Maintenance Unit (0..*)

Decision: To remove Maintenance Unit from Classification Index and to add note that maintenance unit can be derived from Agent In Role

Discussion

  • If we remove these attributes, how would people know they can be derived through Agent In Role?
  • But it would be difficult to understand this. Having an example of how to use Agent In Role to cover these attributes can be helpful Francine Kalonji - to provide an example
  • We should promote use of Agent In Role more, the objects that can be re-used

Comment #5 from Issue #2-23

Classification Series – Owners (0..1)

The same for the first row

Comment #7 from Issue #2-23

Correspondence Table – Contact Persons (0..*)

Correspondence Table – Maintenance Unit (1..*)

Correspondence Table – Owners (0..*)

The same for the first row

Comment #10 from Issue #2-23

Statistical Classification – Contact Person (0..*)

Statistical Classification – Contact Person (1..*)

The same for the first row

Comment #3 from Issue #2-25

Information Resource – Owner (0..1)

The same for the first row



  • No labels

7 Comments

  1. InKyung Choi

    24 Jan, 2019

    GSIM Sprint (24 Jan.)

    Regarding Agent In Role: to add new sub-types Owner, Contact Person and Maintainer (or Maintenance Unit) Francine Kalonji for proposals. 

  2. Francine Kalonji

    29 Jan, 2019

    Owner: The statistical office or other authority responsible for defining, specifying, creating and making decisions about the maintenance of an information object and/or its metadata. Some information objects may have several owners.

    Maintainer: The unit or group of persons within the organisation responsible for managing an information object and its metadata e.g. adding, modifying or deleting metadata about an information object.

    Explanatory Text: The maintainer is responsible for all administrative and operational issues relating to one or a set of an information objects. It is answerable to all stakeholders for all issues related to the information object(s) under its responsibility. The maintainer is not a decision-making body. Decisions are made collaboratively among the owners of the artefact.

    Contact: Person(s) responsible for providing additional information about an information object and/or its metadata, either directly or indirectly by linking to its source.

  3. Francine Kalonji

    29 Jan, 2019

  4. Francine Kalonji

    29 Jan, 2019

    An example:

    Two Sub-Organizations (SO1, SO2) play the role of Owner (O) for a Statistical Classification (SC21), one other Sub-Organization (SO3) plays the role of Maintainer (M), and one Individual  (I1) is the Contact (C) for that Statistical Classification.  Here are the instances of the Object AgentInRole :

    1. {O},{SO1}, {SC21}
    2. {O},{SO2}, {SC21}
    3. {M},{SO3},{SC21}
    4. {C},{I1}, {SC21}

    Let's say that (SO3) is also the Maintainer for a Variable (V3), we will have another instance:

    1. {M},{SO3},{V3}

  5. Jenny Linnerud

    20 Feb, 2019

    I suggest:

    Owner: The statistical office or other authority responsible for defining, specifying, creating and making decisions about the maintenance of an information object and/or its metadata. Some information objects may have several owners.

    Maintainer: The unit or group of persons within the organisation responsible for maintaining an information object and it's metadata e.g. creating, updating or deleting metadata about an information object.

    or

    Manager: The unit or group of persons within the organisation responsible for managing an information object and it's metadata e.g. creating, updating or deleting metadata about an information object.

    Explanatory Text: The maintainer is responsible for all administrative and operational issues relating to one or a set of an information objects. It is answerable to all stakeholders for all issues related to the information object(s) under its responsibility. The maintainer is not a decision-making body. Decisions are made collaboratively among by the owner(s) of the information Object

    Contact: Person(s) responsible for providing user support and/or additional information about an information object. and/or its metadata, either directly or indirectly by linking to its source..

    I am a little uncomfortable with 'metadata' about an information object. Metadata is mostly interpreted as data about data. Metainformation would be information about information. Do we actually mean attributes here?

  6. Jenny Linnerud

    20 Feb, 2019

    If the association 'has sub-agents' only refers to Organization why not put the association from Organization to Organization with text 'has sub-organizations'?

  7. Jenny Linnerud

    20 Feb, 2019

    I suggest:

    Two Sub-Organizations (SO1, SO2) play the role of Owner (O) for a Statistical Classification (SC21), one other Sub-Organization (SO3) plays the role of Maintainer (M), and one Individual  (I1) is the Contact (C) for that Statistical Classification.  Here are the instances of the information object AgentInRole for Statistical Classification (SC21) :

    1. {SO1}, {O},{SC21}
    2. {SO2},{O} {SC21}
    3. {SO3},{M}, {SC21}
    4. {I1}, {C}, {SC21}

      Let's say that (SO3) is also the Maintainer for a Variable (V3), we will have another instance:

    1. {SO3},{M}, {V3}
      Note that I have deliberately swapped the order above so that the Agent comes first and the Role second as it does when reading AgentInRole.