FrontPage - Integrated Collaboration Object Model for Interoperable Collaboration Services (ICOM) TC Wiki
Integrated Collaboration Object Model for Interoperable Collaboration Services (ICOM) TC Wiki
FrontPage
FrontPage
RecentChanges
FindPage
HelpContents
Immutable Page
Comments
Info
NOTE: This wiki is provided by the
OASIS
standards consortium as a collaborative tool for members of the
OASIS Integrated Collaboration Object Model (ICOM) Technical Committee
, who are permited to post to these pages. As this is an official workspace of the TC, the
OASIS IPR Policy
and
other OASIS rules
apply to its use. To learn more about the work of the TC, send a comment, or join this effort, visit the
OASIS ICOM TC
homepage.
Wiki pages are transient documents, so intermediate edits may not be saved. TC members should move all permanent work and stable artifacts to the TC's
document repository
, where the archival work product of the TC also can be viewed by the public.
OASIS Integrated Collaboration Object Model (ICOM) for Interoperable Collaboration Services
OASIS Integrated Collaboration Object Model (ICOM) Technical Committee was chartered on March 3, 2009 to specify the normative standards for collaboration objects, along with the classes, attributes, relationships, constraints, and behavior, for a broad range of collaboration activities in an integrated and interoperable collaboration environment. Cisco Systems, DERI, ESoCE-NET, Ontolog-CIM3, and Oracle Corporation are OASIS members who have representatives serving on this TC.
The ICOM specifications will encompass and improve on a range of models which are part of existing standards and technologies. The existing standards and technologies were developed independently and had created the impedances between the components across standard and technology boundaries. The ICOM TC envisages that the new solutions based on ICOM specifications will offer seamless transitions between different functional components to enable the applications that mash up the model of different component areas from different interoperable service providers.
More details ...
The Model
The model is modular to allow extensibility. The core concepts, meta-concepts and their relations are included in the
Core Model
, while the specific concepts and relations for each area of interest are defined in separate
extension models
Representations of the Model
As part of ICOM we define two separate representations of the model (core and extensions).
UML/OO Representation
RDF Representation
Because of the differences between the two representation languages, some aspects will naturally be distinct between the two representations. However, a direct transformation between the two is a requirement in the modelling process.
Discussion ...
Use Cases and Examples
Use case for core concepts
Use case for metadata concepts
Ontolog forum data
Mapping between ICOM Forum Model and Jive Forum package
Prototyping
The ICOM TC will provide several prototypes for using the defined model.
JPA prototyping
Meetings
28-29 June 2010
- F2F meeting at Oracle
Dissemination
Standard presentation
Slides from Semantic Technology presentation
Posters from Semantic Technology conference
Public Page Summary
Public Page Summary
This wiki is powered by
MoinMoin
CategoryHomepage
FrontPage (last edited 2010-09-01 13:58:32 by
Chancellor.Pascale
Immutable Page
Comments
Info
MoinMoin Powered
Python Powered
GPL licensed
Valid HTML 4.01