RE: [icom] Draft Minutes of ICOM TC Meeting, March 18th, 2009

["Martin Chapman" <martin.chapman@oracle.com>]

Just a minor nit, but the role call after the first meeting is not to establish voting members, but to record who on the roster is
attending. The initial voting list was established on the first call. An individual will lose voting rights by not turning up to two
meetings in a row. An individual will (re)-gain voting rights by attending two meetings in a row.

Martin.

> -----Original Message-----
> From: Eric S. Chan [mailto:eric-s.chan@oracle.com]
> Sent: 18 March 2009 22:53
> To: icom@lists.oasis-open.org
> Subject: [icom] Draft Minutes of ICOM TC Meeting, March 18th, 2009
> 
> Minutes of ICOM TC Meeting, March 18^th , taken by Eric S. Chan
> 
> Agenda:
> 
>     * 1. Roll call to establish voting members
>     * 2. Review the TC Issue Recording and Resolution Process
>     * 3. Discuss UML and RDF Modeling Tools and OASIS Specification Formats
>     * 4. Discuss Liaison with CMIS
>     * 5. AOB
> 
> 
> 
> 1. Roll call to establish voting members
> 
> Eligible Persons present in the call were:
> 
>    1. Siegfried Handschuh
>    2. Marc Pallot
>    3. Philip Arkcoll
>    4. Rafiul Ahad
>    5. Eric Chan
>    6. Martin Chapman
>    7. Ramesh Vasudevan
> 
> OASIS Staff Present:
> 
>    1. Robin Cover
> 
> Eric noted Rajani Sadasivam from UAB as an observer at the TC meeting.
> 
> 
> 2. Review the TC Issue Recording and Resolution Process
> 
> Martin Chapman supplied the issue process slides
> http://www.oasis-open.org/apps/org/workgroup/icom/email/archives/200903/ppt00000.ppt
> and discussed the issue recording and resolution process commonly used
> by OASIS TCs.
> 
> Martin summarized that the TC meetings decide to open, close, defer, or
> resolve the issues. New issues are raised by TC Members at and in
> between meetings. Issues are raised by email to the TC mailing list with
> subject line beginning with “NEW ISSUE: [title]”. An issue number will
> be assigned to any issue raised even though the issue may not be
> accepted as an issue. The TC page should record the issue resolution
> once the resolution is marked as resolved. Use JIRA to record open and
> closed issues. Martin emphasized the need for majority vote to reopen
> any issues. This rule helped the TCs prevent churning of issues by small
> minority.
> 
> Action item: confirm with Mary about setting up JIRA for the ICOM TC.
> 
> Eric Chan motioned and Martin seconded the motion to allow the TC
> members to work on technical issues outside of the regular biweekly TC
> meetings. The regular TC meetings will be reserved for tracking,
> approving, recording, and formal resolution of issues. Rafiul Ahad
> requested an amendment to the motion for members to communicate the
> details of the technical discussions and issues to the ICOM TC mailing
> list. The motion was approved.
> 
> 
> 3. Discuss UML and RDF Modeling Tools and OASIS Specification Formats
> 
> Eric proposed to review the modeling tools to enable interchangeable
> model source files.
> 
> Eric has been using Borland Together Architect 2007 for Eclipse to
> define the UML model for Beehive Object Model. The model (including
> diagram elements such as associations and strong or weak aggregations)
> for this tool is represented in Java with annotations. Any TC member can
> edit the Java classes and annotations using any IDE. Eric can generate
> the UML diagrams from the Java classes.
> 
> Siegfried Handschuh suggested the open source UML modeling tool from
> ArgoUML http://argouml.tigris.org/. For RDF modeling tool, Siegfried
> suggested Protégé from Stanford University http://protege.stanford.edu/.
> 
> Action items:
> · Raise an issue for adopting a UML modeling tool, e.g. using Java and
> annotations
> · Raise an issue for adopting an RDF modeling tool, e.g. Protégé
> 
> Eric proposed to use XHTML format from the OASIS specification templates
> at http://docs.oasis-open.org/templates/index.html for the ICOM
> specification working draft.
> Marc Pallot proposed to publish the working draft in wiki
> http://wiki.oasis-open.org/icom. Eric commented that the XHTML working
> draft simplifies importing into Wiki, and the draft can be maintained
> using the XHTML editor http://www.nvu.com/.
> 
> Action Item:
> · Raise an issue for draft specification format, e.g. XHTML
> 
> 
> 4. Discuss Liaison with CMIS
> 
> Eric reported the status of ICOM liaison with the CMIS TC. Eric expects
> to be called to present the ICOM to the CMIS TC during a CMIS TC
> meeting. Eric sent the presentation slides
> http://lists.oasis-open.org/archives/icom/200903/ppt00001.ppt to the
> CMIS mailing list. Eric and Siegfried discussed to add a few slides
> presenting DERI’s experience with Drupal content management platform
> http://drupal.org/. Siegfried indicated that Drupal is incorporating
> SIOC http://rdfs.org/sioc/spec/.
> 
> 
> 5. AOB
> 
> Eric will track an action item to upload the input documents from
> members to the OASIS repository.
> 
> Eric will propose a meeting (outside of regular TC meeting) to present
> the Beehive Object Model in Oracle's input document to the TC and call
> for presentations by other members.
> 
> Philip Arkcoll asked how members may suggest agenda for the TC meeting.
> Members can propose amendment to the proposed agenda at and in between
> meetings. After the roll call in each meeting, the members shall motion
> amendments to the agenda for the meeting.
> 
> Meeting adjourned.
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php