Draft Minutes of ICOM TC Meeting, June 10, 2009

Minutes of ICOM TC Meeting, June 10, taken by Eric S. Chan

Agenda:

1. Roll Call

2. Approve draft minutes from May 13 and 27 TC Meetings

3. Reconcile Beehive object model and SIOC ontology

4. Feasibility of JPA and Jenabean prototypes for ICOM

5. AOB

1. The following eligible members were present

Philip Arkcoll

Stefan Decker

Deidre Lee

Patrick Durusau

Rafiul Ahad

Eric Chan

2. The draft minutes from May 13 and 27 Meetings were approved.

3. In reconciling Beehive model and SIOC ontology, Eric pointed out the close correspondences of concepts between the Beehive Object Model and SIOC ontology.

Beehive community corresponds to SIOC community. In both formalisms, community consists of people and spaces. Beehive community is modeled after enterprise and organizational hierarchies. SIOC community is modeled after online communities. Eric indicated that organizational hierarchies may be constrained by single containment, i.e. a sub-organization may belong to only one parent organization. Stefan commented that if communities are hierarchical, they should not be constrained by single containment, i.e. a sub-community may be contained by more than one super-community. Rafiul commented that single containment constraint, if needed, can be defined as extension/specialization of core ICOM. Eric concurred with Stefan and Rafiul to avoid over specification by constraints.

Beehive workspace corresponds to SIOC space. SIOC site is a specialization of SIOC space. A workspace may also be contained by more than one community.

Beehive folder corresponds to SIOC container. Deidre indicated that SIOC container hierarchy is a graph rather than a tree. Rafiul commented that containment hierarchy may be a directed acyclic graph.

Eric will open the issues to investigate multi-containment of community, workspace/space, and folder/container, the implications of multi-containment on access control and policies enforcement, and graph vs. DAG.

Eric indicated that role-based participation is essential for ICOM workspace. Deidre commented that SIOC ontology also defines the role concept and function-of property, however ICOM may provide more use cases for SIOC.

Eric emphasized that the TC will reconcile the concepts from existing systems into a new, contiguous, and coherent set of concepts for ICOM. The ICOM concepts can be mapped to Beehive Object Model, SIOC ontology, and other ontologies such as FOAF, iCalendar, Nepomuk, etc.

4. Eric indicated that an open source foundation is interested in ICOM provided there is an open source implementation to leverage. Java persistence API may be an example API for ICOM objects. Jenabean is an example tool that converts JPA objects to/from RDF triples. Eric requested TC members to review the feasibility of JPA.

The meeting was adjourned.

Regards,

Eric

icom message