[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Draft Minutes of ICOM TC Meeting, March 3, 2010
|
Minutes of ICOM TC Meeting, March 3, taken by Eric S. Chan Agenda 1. Roll Call 2. Approve draft minutes from Feb 3 and 17 TC
Meetings 3. Propose metadata model for ICOM draft 4. Drafting ICOM specification according to
OASIS Template 5. Review Message artifact 6. AOB 1. The following eligible members were present Laura Dragan Deirdre Lee Patrick Durusau Marc Pallot Eric Chan 2. Approve draft minutes from Feb 3 and 17 TC
Meetings Draft minutes approved. 3. Propose metadata model for ICOM draft We worked on this metadata model for several weeks. We
have a draft model to be documented in the ICOM wiki page http://wiki.oasis-open.org/icom. TC members
will continue to review and critique the metadata model. We observed that almost all types of entities are bondable
except Bond, which is not bondable. Eric to correct the earlier UML diagrams by
removing the dashed arrow from Entity to Bondable. Each subclass of Entity may
realize Bondable. This restriction avoids recursive structures of bonds. In UML model, CategoryApplication, TagApplication, and
BondEntityRelation are not entities. Category application and bond are two ways
to add properties to entities. Category application aggregates the properties
on an entity such that the domain of the properties is represented by the
category. Bond aggregates the properties in a n-ary relation. Eric to distill the metadata model and include it in the ICOM
draft model at http://wiki.oasis-open.org/icom/DraftModel.
So far the TC has developed the core and metadata models.
Additional models will be defined as modules. The TC will continue to define
the modules, such as Calendar, TaskList, AddressBook, Forum, Conference, etc.,
which are among Oracle’s contributions to ICOM TC. Other members may contribute
new modules, such as Google Wave, Blogs, etc. 4. Drafting ICOM specification according to OASIS
Template Patrick explained the template for OASIS Draft
Specification. It is important to distinguish normative and non-normative,
mandatory and optional parts of the specification. If we refer to other
specifications, we need to designate whether the references are normative or
not. The template may not reflect this, but there is an expectation for the
conformance clause has to be in the last numbered section before any appendices
in the document. There are expectations and requirements by OASIS, other than
that the specification document can be organized in the way that makes sense,
for example organizing by core, metadata, and modules. Patrick’s preference is
to include use cases in the non-normative appendix of the specification.
Patrick is currently occupied with ODF 1.2 specification, afterwards he can
contribute to polishing the ICOM specification after the material is already
written down. As part of the ICOM specification, the RDF ontology (XML
src) and UML model (Java src) will be the sources of truth. The specification
document (based on OASIS template) will disambiguate the concepts and
explicitly define the vocabularies in the model. The TC will be ramping up with
the draft specification document over the next two months. Currently, the TC is
using the wiki pages for primer and draft model to document the progress. 5. Review Message Artifact Before the meeting, Eric sent out the UML model of
UnifiedMessage and Content. In this model, the message senders and receivers are
participants of the messaging activity. Participants are referenced by object
id of any addressable entity, not just by email addresses. In the UML model
Addressable is an auxiliary concept represented by UML interface, which
includes Actor, Group, and Space. The concept of participant can be seen in other contexts,
such as participants in calendar scheduling, task assignments, forums,
conferences, etc., in addition to messaging activities. The participants can
also be represented by email addresses only (where addressable object id is
null) for compatibility with IMAP, SMTP protocols and to include participants
who are external to the system. Addressable can have multiple addresses with different
address schemes, such as mailto, im, tel, fax, etc., and one primary address. Space is addressable so when you include a space in the
messaging activity, the message is delivered to the inbox of the space. The
space can maintain a complete thread of conversation so that any new
participants of the message thread can see the complete thread of messages in
the space, as long as they are members of the space. Eric mentioned that the bcc of the unified message is
readable by the sender of the message. The bcc can be updated in the draft
message. Bcc is not readable in the received message. Therefore, we need to
model the three modes of the message. In the diagram, the
DraftUnifiedMessage is a subclass but may be changed. Eric also briefly explained several operational semantics of
the UnifiedMessage to be elaborated, using the return receipt, delivered time,
switching the mode of the message from received to draft, etc., in the model. Content model is an abstraction of MIME. There is a concept
of MimeConvertible which can be parts of a MultiContent. Message contains a
Content, which may be a MultiContent to represent attachments, forwarded to,
and replied to message threads, in nested content hierarchy. The Message and
Document are MimeConvertible so they can be encapsulated inside the
MultiContent. OnlineContent and SimpleContent are leaf nodes of the hierarchy.
The OnlineContent can be rendered in line to the message body, but it usually
represent something online or life, such as a web conference or a chat room.
The content disposition type is a directive to render the content inline or as
attachments for download. Eric to reorganize the ICOM TC
workspace using folders for figures, webcasts, src, etc. Some URL (in
wiki pages) may be broken after this reorganization. Eric to update the wiki
pages. In overtime, Deirdre, Laura, Marc, and Eric discussed the
lightning presentation and poster session of ICOM at the Semantic Technology
2010 conference in San Francisco. They also discussed scheduling the ICOM F2F
Meeting around the time of the conference in June. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]