[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Draft Minutes of ICOM TC Meeting, January 6, 2010
Minutes of ICOM TC Meeting, January 6, taken by Eric S. Chan Agenda 1 Roll Call 2 Review and feedback for draft model 3 AOB 1. The following eligible members were present Deirdre Lee Laura Dragan Patrick Durusau Marc Pallot Eric Chan 2. Review and feedback for draft model Marc Pallot provided a use case for groups and membership
(see Figure 1 below), which was the main agenda of this TC Meeting. Marc
described a hierarchy of projects, subprojects, work packages, and tasks. At
the top level are projects, which are divided into subprojects. Each subproject
can be divided into work packages, which in turn can be divided into tasks. Each
of these project units is supported by an ICOM space containing several folders.
Project tasks are assignable to groups. Conceptually, the smallest unit of participation
in the project units are groups of individuals rather than individuals who may
be supplied by multiple organizations. The organizational hierarchies are determined
independently of the project unit hierarchies. Each organization can independently
assign individuals to the groups that it contributes to the project units. We discussed how to represent this use case in ICOM. First
we observed that ICOM communities are hierarchical although spaces themselves
are not hierarchical. Since each community can contain a set of spaces, spaces
can belong in different levels of hierarchy. We considered using bonds to
represent the division of a project unit into subunits. Bond represents n-ary relationships
among a set of n entities. Note that Bond has an attribute called “root”
to distinguish one of the n entities and an n-tuple attribute that holds one BondEntityRelation
per entity. To represent the division of a project unit into subunits, the “root”
attribute of Bond can distinguish the “parent” project unit that is
being divided, while the n-tuple of BondEntityRelation’s can represent
the subunits of the project unit (see Figure 2 below). Users can add annotations
in the BondEntityRelation objects. Figure 3 depicts how one bond is used to divide
Project into two subprojects (SP1, SP2) and another bond is used to subdivide
SP1 into three work packages (WP1, WP2, WP3). Figure 1 Groups and Membership Use Case Figure 2 UML Composite Diagram for Project Unit Division Figure 3 UML Composite Diagram for Division of Project into Subprojects and Work Packages 3 AOB The TC Meeting was adjourned. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]