OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

icom message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Draft Minutes of ICOM TC Meeting, April 14, 2010


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

 

Agenda

 

1. Roll Call

2. Approve draft minutes from March 31 TC Meeting

3. Status of RDF ontology in Drupal Neologism

4. Demo of JPA programming examples for ICOM

5. AOB

 

1. The following eligible members were present

 

Laura Dragan

Deirdre Lee

Patrick Durusau

Eric Chan

 

2. Approve draft minutes from March 31 TC Meeting

 

Draft Meeting minutes approved.

 

3. Status of RDF ontology in Drupal Neologism

 

Eric indicated that the RDF model in Figure 8 of http://wiki.oasis-open.org/icom needs to be updated. Deirdre and Laura mentioned about the upcoming workshop at DERI to review the ICOM TC’s RDF methodologies. They suggested to generate the RDF diagrams after the feedbacks from the review.

 

4. Demo of JPA programming examples for ICOM

 

Eric explained that he was recently busy with touching up the JPA prototype framework. Eric gave a demo of JPA programming examples running against the Beehive server.

 

Eric will request for approval to share the codes with ICOM TC members for joint development efforts. The prototype comes with a connector for Beehive server. For joint development, the TC will have to share a hosted Beehive server. The TC members can contribute the connectors for other collaboration servers.

 

5. AOB

 

Eric mentioned that he will give an overview of ICOM at the next CMIS TC meeting (tentatively scheduled for Monday, May 3rd). He would be updating the ICOM wiki page with UML model of a few artifact modules, including the UnifiedMessage model which had been reviewed by ICOM TC.

 

The following issues were raised (to be discussed in the next TC meeting):

 

a.       add “description” property for all entities.

b.      Group has “subGroups” property, which is analogous to Community’s subCommunities property; we need to rename “communities” to “subCommunities” in the model.

c.       Group has “groups” property representing the superGroups.

 

Note: One proposal to be discussed in the next TC meeting is to rename super “groups” to “assignedGroups” and “subgroups” to “memberGroups”.  The “assignedGroups” property is analogous to “assignedRoles” property, both of which can be properties of Actor and Group.  Roles can also have “memberGroups” property. Both Role and Group can have “memberActors” property.

 

The TC Meeting was adjourned.

 

 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]