Agenda
1. Roll Call
2. Approve draft minutes from April 14 TC
Meeting
http://www.oasis-open.org/apps/org/workgroup/icom/email/archives/201004/msg00001.html
3. Status of RDF ontology
4. Review the artifact modules (see texts below,
part 1)
5. Discuss the open issues from previous TC Meeting
(see texts below, part 2)
6. AOB
Please sign on to ICOM TC chat room
http://webconf.soaphub.org/conf/room/ICOM-TC
Biweekly ICOM TC Meeting Conference Call
Date: Wednesday, 28 April, 2010
Time: 09:00am - 10:00am PDT
InterCall Conference id: 9128348
InterCall Password: ICOMTC (426682)
From the AMER region dial:
+1 866-682-4770
+1 408-774-4073
From the EMEA region dial:
+44 (0) 2081181001 (UK)
+44 (0) 8444936817 (UK)
+353 (0) 1 247 5650 (Dublin)
+33 (0) 176728936 (Paris)
From the APAC region dial:
+61 2 8064 0613 (Australia)
For your local numbers, please check additional global
access numbers listed at http://www.intercall.com/oracle/access_numbers.htm
Part 1. (for section 11.0 of ICOM wiki front page)
Figure 15 in http://wiki.oasis-open.org/icom
shows a variety of containers in the ICOM space to support various
collaboration activities. The heterogeneous folder stands out as a high-level
concept of ICOM space to serve as the "universal" inbox, outbox,
trash, and public/published container for any types of artifacts in the space.
Several types of artifacts, including Documents and Messages, do not need
specialized containers. However, specialized types of artifacts such as
Occurrences, Tasks, Contacts, Topics, Discussion Messages, and Conference Transcripts
need specialized containers to provide additional structures for the artifacts.
ICOM includes Calendar, TaskList, AddressBook, Forum, and Conference containers
that provide the structures and also designate the collaboration activities.
These artifacts can be mixed with Documents and Messages in the heterogeneous
folders. The specialized containers and artifacts are defined as modules in
ICOM. In this section we describe the most common container modules.
Figure 29. Document Model
Figure 30. Content Model
Figure 31. Unified Message Model
Figure 32. Discussion Forum Model
Figure 33. Address Book Model
TODO:
Figure 34. Calendar Model
Figure 35. TaskList Model
Part 2. (Open Issues)
The following issues were raised
in the last 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.
Figure x Group, Role, Actor Model