OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

cmis-comment message

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


Subject: Re: [cmis-comment] Bringing semantic capabilities to CMIS compliant content repositories


Dear Suat,

Thank you for your post. We appreciate your CMS Adapter work.


To all CMIS TC members, especially those who are interested in ontology or RDF:

The Apache Stanbol project provides semantic capabilities to CMIS repositories. I encourage you to take a look at Suat's blog on model mapping (see link below) and inject your thoughts on the proposed approach.


Best regards,

David


On Tue, Mar 20, 2012 at 4:13 AM, Suat Gonul <suatgonul@gmail.com> wrote:
Dear CMIS community,

I would like to inform you about the study related with the CMIS
specification, that we did in the scope of Apache Stanbol project [1].
As a brief introduction, Stanbol is a software aiming to bring semantic
capabilities to existing content management systems. One of the
subcomponents of Stanbol is CMS Adapter[2].

In the scope of CMS Adapter, in the first step, we tried to transform
structure of a CMIS repository into an OWL model based ontology. In this
method, all object types registered with the repository are transformed
to classes. Folders and documents can be transformed into either classes
or individuals. When content repository objects are transformed into
individuals, they are created as instances of classes which correspond
to their object types. Furthermore, relationships are transformed into
object properties and corresponding assertion is set between the source
and target individuals. The aim in extracting such kind of an OWL model
based ontology, is to enable reasoning on it (which cannot be done on
content repository itself in our opinion). I have written a blog post
about this feature at [3]. We have also a paper regarding this feature.
It can be downloaded from [4].

The second approach is a bidirectional mapping approach between RDF data
and content repositories. It basically provides populating content
repository with RDF data in one way and transforming content repository
structure into RDF in the other way. The mapping process is done
according to a handful of configurations parameters. For instance one
indicates the resources to be mapped to the content repository, one
indicates parents of selected resources, etc. There is also another blog
post including details about this feature at [5].

I would be glad if you have a look at the blog post and could share your
opinions about our approaches, further ideas to improve the existing
design.

Best regards,
Suat

[1] http://incubator.apache.org/stanbol/
[2] http://incubator.apache.org/stanbol/docs/trunk/cmsadapter/
[3]
http://blog.iks-project.eu/stanbol-cms-adaptor-allows-you-to-transform-jcrcmis-nodes-into-semantic-web-schemas/
[4]
http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.188.7723&rep=rep1&type=pdf
[5]
http://blog.iks-project.eu/adding-knowledge-to-jcrcmis-content-repositories/


--
This publicly archived list offers a means to provide input to the
OASIS Content Management Interoperability Services (CMIS) TC.

In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.

Subscribe: cmis-comment-subscribe@lists.oasis-open.org
Unsubscribe: cmis-comment-unsubscribe@lists.oasis-open.org
List help: cmis-comment-help@lists.oasis-open.org
List archive: http://lists.oasis-open.org/archives/cmis-comment/
Feedback License: http://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
Committee: http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=cmis
Join OASIS: http://www.oasis-open.org/join/




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