Draft Minutes of ICOM TC Meeting, November 11, 2009

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

Minutes of ICOM TC Meeting, November 11, taken by Eric S. Chan

 

Agenda

 

1. Roll Call

2. Approve draft minutes from October 28 TC Meeting

3. Review the ICOM draft model on http://wiki.oasis-open.org/icom/DraftModel

4. AOB

 

1. The following eligible members were present

 

Deirdre Lee

Patrick Durusau

Eric Chan

 

2. Approve draft minutes from October 28 TC Meeting

 

Approval deferred.

 

3. Review the ICOM draft model

 

Eric created the wiki page for the ICOM draft model in http://wiki.oasis-open.org/icom/DraftModel. The ICOM draft model in this page will be distilled from various proposals in http://wiki.oasis-open.org/icom/Categorisation where TC participants may contribute new concepts and to mix and match the concepts from different contributions.

 

So far the ICOM draft model captures the high-level concepts. It organizes the concepts into the Scope, Subject, and Artifact branches. The draft model can be extended in two general tracks. One track is to define the specialized classes of artifacts, such as message, document, blog, wiki page, etc. Another track is to specify the metadata for the top-level classes, for example at the Entity class level, to constitute the metadata framework for all entities in the Scope, Subject, and Artifact branches. Any new class of artifacts will have to conform to the metadata framework defined on the Entity or Artifact class.

 

4. AOB

 

Eric posted a UML diagram of the entity metadata model in Figure 11 on http://wiki.oasis-open.org/icom/Categorisation. The metadata for Entity includes Category, Tag, Bond, Subscription, Reminder, and access control policy.

 

The model describes how one category or tag can be applied to multiple entities. When the same metadata is applied to multiple entities, each instance of association between the metadata and an entity would need to be represented by a “link” object that can hold the attributions for the specific instance of metadata application. In order to represent the instances of associations, Beehive object model introduced CategoryApplication, TagApplication, and BondEntityRelation to represent, respectively, the application or association of a Category, Tag, and Bond with an entity. Eric would update the UML diagram in Figure 11 to reflect the CategoryApplication, TagApplication, and BondEntityRelation for the associations between a Category, Tag, and Bond with an Entity. Eric explained that a TagApplication can be used to hold the “offset” of a text in a document or a “path identifier” for a specific attachment in a message. This way a tag can be applied to a part of an artifact using a part identifier relative to the parent’s URI. Similarly, a CategoryApplication or BondEntityRelation can hold the attributions for a specific entity.

 

Subscription is an Event-Condition-Action (ECA) rule that the users can attach to the entities to subscribe to events on the entity and to perform the actions when the ECA conditions are met. Reminder is a special type of Subscription that employs a time window relative to an event, for examples to send a notification 24 hours before the due date of an assignment. Reminder also detects non-occurrence of events, such as to send an alert to the user if he/she has not read a high priority message within 12 hours of receiving the message.

 

Patrick suggested that a Subscription and Reminder should be applicable to multiple entities, and furthermore, for a stream of events on an entity. Beehive model currently creates a separate subscription or reminder for each entity. The TC can evaluate whether to employ SubscriptionApplication and ReminderApplication to represent the separate associations between a subscription or reminder with multiple entities. In Beehive object model, a subscription on a container applies to a stream of events in the container, for example a subscription to filter each new message delivered into the inbox.

 

Eric and Deirdre discussed how the metadata model can be represented in RDF. Deirdre alluded that Category, which supports hierarchy classification or taxonomy, may be represented as instances of rdfs:Class in RDF ICOM.

 

 

The meeting was adjourned.