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, October 13, 2010


Minutes of ICOM TC Meeting, October 13, taken by Eric S. Chan

 

Agenda

 

1. Roll Call

2. Review the updated draft.

See: http://www.oasis-open.org/apps/org/workgroup/icom/download.php/39751/icom-spec-draft-01a.doc

3. AOB

 

1. The following eligible members were present

 

Deirdre Lee

Peter Yim

Eric Chan

 

2. Review the updated draft.

 

Issue 1:

Patrick Durusau, in the week before, suggested an update to ICOM draft specification to position it as a framework for a broad range of domain models.

 

“The Integrated Collaboration Object Model (ICOM) for Interoperable Collaboration Services standard defines a framework for a broad range of domain models for collaboration activities in an integrated and interoperable collaboration environment.”

 

Issue 2:

A new concept of RoleDefinition was added to the draft. RoleDefinition contains a set of privileges. A Role assigns the set of privileges in a role definition to a set of accessors for an assigned scope. Eric explained that RoleDefinition improves the versatility of the Role-based access control (RBAC) model. An implementation can potentially introduce a large number of privileges to support fine-grained access control. To  adhere to the principle of least privileges,  applications need to carefully design minimal sets of privileges needed for any role to perform a task. It may involve simulations to determine the privileges needed for a sequence of operations. RoleDefinition is used to represented named sets of privileges. The same role definition for a space participants coordinator role can be used in multiple team or project spaces.

 

Issue 3:

Previously, the Privilege and AccessType classes are defined as enum classes in the draft. They were redefined as mixin classes so the implementations can define their own enumerations for privileges and access types. Peter suggested that ICOM provides "examples", "defaults" or "non-normative references" for privileges and access types that may be used in implementations.

 

3. AOB

 

Peter Yim briefed the participants regarding his interaction with kmgov and kmwg (Federal KM Working Group) in the message http://www.oasis-open.org/apps/org/workgroup/icom/email/archives/201010/msg00003.html. Kmgov is starting a discussion thread on “Subject Matter Expertise identification system,” which is related to the ICOM+Tacit+RDF demo we presented to Ontolog.

 

Peter also called for ICOM TC members to get involved in the OOR Architecture and API discussions and to explore synergies between ICOM work and OOR. (look for Open Ontology Repository working group meetings http://ontolog.cim3.net/cgi-bin/wiki.pl?OOR/ConferenceCall_2010_10_15).  Please also refer to OOR homepage at: http://OpenOntologyRepository.org.

 

Deirdre to convey the call for participation in OOR to DERI.

The TC Meeting was adjourned.



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