I can understand why Identifiable Artefact and Administrative Details belong to the Base Group.

Most other information objects are identifiable and can be administered, but I do not understand the reason for putting Agent, Agent Role, Individual and Organisation in the Base Group.

In discussions with others in my organisation these would seem to be better placed in the Business Group. The only relations shown in the UML are within the Base Group and to 2 information objects in the Exchange Group.

Is it intended that all information objects can use these through some relationship and/or via the Adminstrative Details information Object e.g. Owner Agency in B. Administrative Attributes

of Annex D:  Extending the model?

Some more examples of use and a better reason behind the grouping in the Base Group than that currently provided in GSIM Specification IV Technical Information paragraphs 109, 110, 121, 113

would be appreciated.

  • No labels

6 Comments

  1. user-8e470

    06 Apr, 2018

    Jenny Linnerud -

    I think there are two issues - what group objects are in, and more explanation of the Base group. 

    After the LIM work, the base group expanded to include a number of extra objects. Was this comment resolved in the LIM group?

  2. Jenny Linnerud

    06 Apr, 2018

    No, we didn't discuss it there. I created the issue based on my own experience in trying to implement GSIM, including LIM, in our own organisation.

  3. user-8e470

    06 Apr, 2018

    Thanks! I have been trying to make sure we are not duplicating conversation (smile)

  4. user-8e470

    12 Apr, 2018

    ModernStats World discussion 12/4: All objects should be kept in base. In a number of countries these objects are used to connect other information which is outside the scope of GSIM. 

     

     

  5. Jenny Linnerud

    19 Apr, 2018

    Interesting - In LIM we introduced AgentInRole to replace AgentRole because an Agent can have many Roles and a Role can be carried out by many Agents.

    Does this mean we will have to keep both AgentRole and AgentInRole? This goes against the principle of Model Coherence.

  6. user-8e470

    19 Apr, 2018

    Hi Jenny, Agent Role is removed in the new version.