Hello
IKS team and Apache Stanbol mailing list,


we have recently submitted an early adoption proposal for Apache Stanbol
and we’d like to post a brief summary of our proposal and a brief profile
of our company for presenting us to the community.

The complete version of the proposal is available on the IKS blog (
http://wiki.iks-project.eu/index.php/Etcware_Proposal).



*Company Profile*

Etcware s.r.l. is a SME (Small Medium Enterprise) based in Rome, Italy, and
founded in 2007 by highly skilled ITC professionals. We develop web portals
and content management solutions for the Public Administration and private
customers, by using the Liferay, OpenCMS and Drupal platforms.We are
focused in productizing and reusing implemented solutions and in performing
feasibility studies for complex scenarios.

Our company has also acquired significant competences in the usage of
semantic technologies and standards. After the experience in an Italian
research project, we have developed a product for SKOS thesaurus publishing
and management, named SKOSware (http://www.skosware.it).

* *

*Early adoption proposal*

Recently we have developed a Liferay based solution for a Public
Administration institution (Garante per la Protezione dei Dati Personali,
Italian Data Protection Authority), in which we have deployed an innovative
semantic search solution based on SKOSware. In this architecture we updated
the Liferay core to allow manual metadata enrichment for contents and
documents, through concepts included in one or more SKOS thesaurus. This
allows us to perform searches and refinements based on dynamic facets,
hierarchically organized. The facet structure is compliant with the SKOS
thesaurus organization. Metadata enrichments are published inside the HTML
pages as RDFa snippets, while geo-localization and chrono-references are
used to place contents on a map and on a timeline.

Our vision is to integrate Stanbol in place of our manual metadata
enrichment for the CMS contents. This will allow us to add additional
content enrichment through Stanbol engines. Moreover, content enrichment
and tagging will become mostly automatic in this way. Stanbol integration
in our Liferay solution will be “loosely coupled” to allow an easy porting
in the next version of the CMS, and to enable a maximum degree of reuse of
our semantic customization.

*The solution will be integrated in the Italian data protection Authority
portal as a demo*, running Stanbol enhancement engines on their document
corpus composed by 12.000 items, 2.000 of which already manually enriched
with metadata.

Our plan to integrate Stanbol is based on the following steps:

   1. Thesauri selected from SKOSware are imported into Stanbol to create a
   base custom knowledge domain.
   2. The Content editor creates or updates contents and documents on
   Liferay. These contents are enriched through Stanbol enhancement engines,
   on editing post-process event.
   3. The Liferay administrator launches Stanbol automatic metadata
   enrichment for all contents and documents (batch enrichment process).
   4. The End-user searches contents and documents by using full-text
   search or tag-cloud-based search and refines the results or expands the
   search scope on similar or related contents (under the scenes SKOS
   thesaurus concepts and semantic relations are used to define the related
   contents).
   5. As the end-user views portal contents, terms similar to SKOS concepts
   (skos:prefLabel or skos:altLabel are used for entity highlighting) are
   automatically decorated and their description is shown on some specific GUI
   event (like mouseover).
   6. Inference rules and semantic reasoning will be used to complete and
   enrich the domain knowledge base, thus suggesting additional concepts and
   OWL relations.
   7. Optional use of some IKS VIE widgets on the frontend presentation
   layer.



Best regards.


     -Andrea

------------------------------------------------
Andrea Ciapetti
Etcware srl
mail: [email protected]
mail: [email protected]
mobile: +39 320 6197534
------------------------------------------------

Reply via email to