Draft Minutes of ICOM TC Meeting, April 28, 2010

[Eric Chan <eric.s.chan@oracle.com>]

Minutes of ICOM TC Meeting, April 28, taken by Eric S. Chan

 

Agenda

 

1.   Roll Call

2.   Approve draft minutes from April 14 TC Meeting

3.   Status of RDF ontology

4.   Review the artifact modules

5.   Discuss the open issues from previous TC Meeting

6.   AOB

 

1. The following eligible members were present

 

Laura Dragan

Deirdre Lee

Patrick Durusau

Marc Pallot

Eric Chan

 

2.   Approve draft minutes from April 14 TC Meeting

 

Draft Meeting minutes approved.

 

3.   Status of RDF ontology

 

Deirdre and Laura reported the feedbacks for ICOM RDF model from the workshop at DERI. The main feedbacks are

·         keep the ICOM RDF model as simple and generic as possible, so as to achieve wider adoption.

o   For example when defining interfaces and abstract classes, use comments to describe how the interface should be interpreted (such as saying its instances must be also instances of some concrete class). Don’t use constraints to enforce the semantics of interface or abstract class.

·         focus on the correctness of the data rather than the model

o   Use OWL domain restriction to customize the range per the domain. Describe the restriction by comments/documentations. Focus on having the data to conform to the restrictions. Don’t need to define the “distinguished” properties, such as elementOfFolder, elementOfWorkspace, parentOfEntity, parentOfArtifact, etc., to strictly enforce the domain and range.

o   important to work with the real data when developing the transformation rules to maintain the correctness of data. To get the real data, Eric suggested to install Beehive to generate the data in the ICOM schema and transform the data to RDF.

 

Deirdre and Laura also presented ICOM overview to a general audience at DERI. Deirdre sent out the slides used for the presentation. The key points are

·         define mapping of SIOC and Nepomuk to ICOM.

·         FOAF person and SIOC User Account represents different aspects of an Actor but do not exactly map to Actor.

·         try to adopt the solutions already established by ontologies such as FOAF, SIOC, etc.

 

Eric mentioned the concepts similar to FOAF person and SIOC User Account were also introduced in Beehive Object Model. For example, there is an auxiliary concept called Person (Actor is a Person) although BOM concept of Person may or may not exactly match the FOAF person. Actor also has member Principals to represent the different credentials of the Actor, which may or may not exactly match the multiple SIOC:UserAccount for a single FOAF:Person.  We need to carefully analyze these concepts case by case. These concepts are to be incorporated into ICOM through a refinement process.

 

4.   Review the artifact modules

 

Eric would incorporate the UML model of a few the artifact modules in Section 11 of ICOM wiki page. Deirdre and Laura would supply the RDF models for the core concepts and artifact modules to be added to the wiki page. The diagrams were to be updated in time for the presentation of ICOM overview to the CMIS TC on May 3^rd.

 

Detail review of the artifact modules was deferred to a subsequent meeting.

 

5.   Discuss the open issues from previous TC Meeting

 

Discussion of open issues from the previous TC meeting was deferred to a subsequent meeting.

 

6.   AOB

 

The participants discussed the schedule, format, agenda, and external participants for the June 28 and 29 meeting. The June 28 and 29 meeting would be organized as a workshop. The participants shall propose the tutorials, use case exercises, etc., for the workshop. Shall identify use cases that highlight the benefits/advantages of ICOM (such as universal inbox with social networking features).

 

Participants considered the following topics:

·         build use case scenarios with UML model within the UML design tools (to analyze the application of ICOM).

·         programming tutorials with ICOM-JPA binding.

·         tutorial for developing the connectors in JPA runtime to connect to service providers.

 

Eric would reach out to CMIS TC and other communities to invite the external participants to the workshop.

 

The TC Meeting was adjourned.