D.7.4 Early Adopter Report 2012

D.7.4 Early Adopter Report
2012
Deliverable:
8.7.4 – Early Adopters Report 2012
Delivery Date:
Author(s):
13th February 2013
John Pereira, Salzburg Research
Filename:
IKS_D874_early_adopters_report_20130129_final.docx
Publication Level: Restricted
2 / 232
Del ive ra bl e 8.7 .4 Ea rly Ad opt er s Re port 2 01 2 – 13 Fe br ua ry 20 13
Table of contents
Table of contents ..................................................................................................................................................... 2 History ..................................................................................................................................................................... 5 Copyright Notice..................................................................................................................................................... 5 IKS in a Nutshell..................................................................................................................................................... 5 1 Executive Summary ......................................................................................................................................... 6 2 Early Adopters Programme Objectives ........................................................................................................ 7 2.1 Summary of Evaluation Contract ...................................................................................................... 7 2.2 Evaluation Phases of the IKS Stack................................................................................................... 7 3 Identifying and Selecting Early Adopters ..................................................................................................... 8 4 3.1 Communication Approach ................................................................................................................. 9 3.2 Issues to Consider for Contacting CMS Providers ............................................................................ 9 3.3 Types of Early Adopters .................................................................................................................. 10 Early Adopters Status Reports ..................................................................................................................... 11 4.1 4.2 4.3 4.4 5 Early Adopter Summary 2012 ......................................................................................................... 11 Early Adopter Summary 2011 ......................................................................................................... 12 Early Adopter Summary 2010 ......................................................................................................... 13 Summary of Signed Contracts ......................................................................................................... 14 4.4.1 CMS Vendors .................................................................................................................... 14 4.4.2 CMS Integrators ................................................................................................................ 14 4.4.3 CMS Tool Providers .......................................................................................................... 14 4.4.4 CMS End-Users ................................................................................................................. 15 4.5 Proposals Under Discussion but not Awarded ................................................................................ 15 4.6 IKS UX Winners.............................................................................................................................. 16 Early Adopter Proposals ............................................................................................................................... 17 5.1 CMS Vendors .................................................................................................................................. 17 5.1.1 QuinScape.......................................................................................................................... 17 5.1.2 Gentics ............................................................................................................................... 19 5.1.3 GOSS Interactive ............................................................................................................... 20 5.1.4 Netzmuehle Internet .......................................................................................................... 21 5.1.5 eZsystems .......................................................................................................................... 23 5.1.6 Jadu .................................................................................................................................... 24 5.1.7 Liip .................................................................................................................................... 26 5.1.8 Ximdex .............................................................................................................................. 28 5.1.9 Typo3 ................................................................................................................................. 29 5.1.10 MakoLab............................................................................................................................ 30 5.1.11 ShqiperiaCom .................................................................................................................... 31 5.2 CMS Integrators............................................................................................................................... 32 5.2.1 Klein & Partner KG ........................................................................................................... 32 5.2.2 Zaizi Ltd ............................................................................................................................ 33 5.2.3 SourceSense ....................................................................................................................... 33 5.2.4 Punkt.netServices GmbH .................................................................................................. 35 5.2.5 Evo42 Communications Ltd .............................................................................................. 36 5.2.6 Beorn Technologies ........................................................................................................... 37 5.2.7 Lunaria ............................................................................................................................... 39 5.2.8 Acuity Unlimited ............................................................................................................... 41 5.2.9 Interact ............................................................................................................................... 45 5.2.10 Drunomics ......................................................................................................................... 48 5.2.11 Logicells ............................................................................................................................ 49 5.3 CMS Tool Providers ........................................................................................................................ 50 © IKS Cons ort ium
20 13
3 / 232
Del ive ra bl e 8.7 .4 Ea rly Ad opt er s Re port 2 01 2 – 13 Fe br ua ry 20 13
6 5.3.1 SalsaDev ............................................................................................................................ 50 5.3.2 Object’Ive .......................................................................................................................... 52 5.3.3 PAUX Technologies .......................................................................................................... 54 5.3.4 Intt...................................................................................................................................... 56 5.3.5 Apache Lenya .................................................................................................................... 57 5.3.6 Ectware s.r ......................................................................................................................... 59 5.3.7 CELI France SAS .............................................................................................................. 61 5.3.8 Content Control ................................................................................................................. 64 5.3.9 Formcept ............................................................................................................................ 65 5.3.10 Sztakipedia ........................................................................................................................ 67 5.3.11 Netlabs.org......................................................................................................................... 68 5.3.12 MarkTheGlobe .................................................................................................................. 71 5.3.13 Compusic/buddycloud ....................................................................................................... 73 5.3.14 Gnowsis ............................................................................................................................. 75 5.3.15 Conatix .............................................................................................................................. 76 5.3.16 Fluid Operations ................................................................................................................ 78 5.3.17 Manafactory ....................................................................................................................... 80 5.4 CMS End-Users ............................................................................................................................... 82 5.4.1 SEWEBAR ........................................................................................................................ 82 5.4.2 Cytogenetics Labs ............................................................................................................. 83 5.4.3 World Heritage Organisation ............................................................................................ 85 5.4.4 SIMsKultur ........................................................................................................................ 87 5.4.5 Software AG ...................................................................................................................... 88 Summary of Evaluations ............................................................................................................................... 89 6.1 6.2 6.3 CMS Vendors .................................................................................................................................. 89 6.1.1 QuinScape.......................................................................................................................... 89 6.1.2 GOSS Interactive ............................................................................................................... 91 6.1.3 Gentics ............................................................................................................................. 111 6.1.4 Ximdex ............................................................................................................................ 114 6.1.5 MakoLab.......................................................................................................................... 115 6.1.6 Typo3 ............................................................................................................................... 117 6.1.7 Netzmuehle ...................................................................................................................... 117 CMS Integrators............................................................................................................................. 118 6.2.1 Klein & Partner KG ......................................................................................................... 118 6.2.2 Zaizi Ltd .......................................................................................................................... 119 6.2.3 SourceSense ..................................................................................................................... 121 6.2.4 Punkt.netservices ............................................................................................................. 122 6.2.5 Evo43 Communications .................................................................................................. 131 6.2.6 Interact ............................................................................................................................. 132 6.2.7 Acuity Limited................................................................................................................. 133 6.2.8 Lunaria ............................................................................................................................. 135 6.2.9 Drunomics ....................................................................................................................... 135 6.2.10 Logicells .......................................................................................................................... 136 6.2.11 Content Control ............................................................................................................... 137 6.2.12 Object’Ive ........................................................................................................................ 138 6.2.13 Ooffee .............................................................................................................................. 140 CMS Tool Providers ...................................................................................................................... 141 6.3.1 SalsaDev .......................................................................................................................... 141 6.3.2 Ectware s.r.l ..................................................................................................................... 142 6.3.3 CELI France SAS ............................................................................................................ 143 6.3.4 FORMCEPT .................................................................................................................... 144 6.3.5 Netlabs.org....................................................................................................................... 145 6.3.6 Sztakipedia ...................................................................................................................... 146 6.3.7 MarkTheGlobe ................................................................................................................ 149 6.3.8 Compusic/buddycloud ..................................................................................................... 150 6.3.9 Conatix ............................................................................................................................ 153 6.3.10 Gnowsis ........................................................................................................................... 155 6.3.11 Fluid Operations .............................................................................................................. 156 © IKS Cons ort ium
20 13
4 / 232
Del ive ra bl e 8.7 .4 Ea rly Ad opt er s Re port 2 01 2 – 13 Fe br ua ry 20 13
6.3.12 Manafactory ..................................................................................................................... 158 CMS End-Users ............................................................................................................................. 160 6.4.1 Cytogenetics Lab ............................................................................................................. 160 6.4.2 GzEvD ............................................................................................................................. 161 6.4.3 SIMsKULTUR ................................................................................................................ 162 6.4.4 Software AG .................................................................................................................... 163 Contact Database ......................................................................................................................................... 164 6.4 7 7.1 7.2 7.3 7.4 7.5 Contacts Summary ......................................................................................................................... 165 Active Members............................................................................................................................. 168 Wait and See .................................................................................................................................. 174 No Response .................................................................................................................................. 176 No Contact ..................................................................................................................................... 201 © IKS Cons ort ium
20 13
5 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
History
Version
Name
Date
Remark
V0.1
V1.0
John Pereira
Wernher Behrendt
21 February 2013
18 Feb. 13
First version
Quality Control
Copyright Notice
This document contains material, which is the copyright of certain IKS consortium parties, and may not be reproduced or copied without permission. The commercial use of any information contained in this document may
require a license from the proprietor of that information. Neither the IKS consortium as a whole, nor a certain
party of the IKS consortium warrant that the information contained in this document is capable of use, nor that
use of the information is free from risk, and accepts no liability for loss or damage suffered by any person using
this information.
Neither the European Commission, nor any person acting on behalf of the Commission, is responsible for any
use, which might be made of the information in this document.
The views expressed in this document are those of the authors and do not necessarily reflect the policies of the
European Commission.
IKS in a Nutshell
Interactive Knowledge (IKS) is an integrating project targeting small to medium CMS providers in Europe
providing technology platforms for content and knowledge management to thousands of end user organisations.
Current CMS technology platforms lack the capability for semantic web enabled, intelligent content, and therefore lack the capacity for users to interact with the content at the user’s knowledge level. The objective of IKS
therefore, is to bring semantic capabilities to current CMS frameworks. IKS puts forward the “Semantic CMS
Technology Stack” which merges the advances in semantic web infrastructure and services with CMS industry
needs of coherent architectures that fit into existing technology landscapes. IKS will provide the specifications
and at least one Open Source Reference Implementation of the full IKS Stack. To validate the IKS Stack prototype solutions for industrial use cases ranging from ambient intelligence infotainment, project management and
controlling to an online holiday booking system will be developed.
© IKS Consortium
2013
6 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
1 Executive Summary
In the final year of IKS report there were a total of 16 new early adopter contracts signed. The total number of
early adopter contracts signed as part of the IKS Early Adopters Programme amounts to 36 plus the 5 from the
UI/X Challenge - this represents a total of 41 IKS early adopters. Of the 16 new early adopter contracts signed in
2012 a great majority of them completed their validation work in the second half of the year. Despite the maturing nature of the IKS technology the challenge for the early adopters of validating a “moving target” continued
throughout 2012. The great work of the IKS development teams helped to overcome this to a certain extent with
individual support and consultation. Most of this support took place directly on the development mailing lists i.e.
Apache Stanbol Development Mailing list and the VIE/IKS Google Groups mailing list. Of the 41 early
adopters: 7 were CMS Vendors, 13 CMS integrators, 12 Tool Providers, 4 End-users and 5 as part of the UI/X
Challenge. The loose term CMS is applied here simply for ease of use. This term however extends to include
document management systems, web content management systems, groupware, and more process oriented content management systems.
Type
CMS Vendors
CMS Integrators
CMS Tool Providers
CMS End-User Organisations
IKS UI/X Challenge Adopters
Total
Signed on
7
13
12
4
5
41
As part of the validation work all early adopters were asked to complete a simple questionnaire consisting of 19
questions. All questionnaires are available on the public wiki: http://wiki.iks-project.eu/index.php/Validation
The 19 questions can be grouped into the 7 main themes:
1.
2.
3.
4.
5.
6.
7.
Do I understand the IKS technology?
Does the IKS technology add value to my technology stack?
Is the IKS technology robust for implementation?
Is the License acceptable?
Can I get involved? Level of community support
Am I confident about the sustainability of IKS technology?
Does IKS technology add direct value to my clients?
The results of the questionnaire grouped according to the 7 themes above are provided in the chart below. A
majority of the IKS early adopters (73%) indicated that they were confident about their understanding of the IKS
technology. They also felt confident about the level of community support and ability to participate in the community development process (65%). There was also strong support for the permissive software license chosen
(62%). 64% agreed that the IKS technology added to their own technology stack. There was however concern
about the maturity of the technology for immediate application (50%), and only 42% were confident about the
long-term sustainability of the technology. These figures improved, especially in terms of sustainability with the
graduation of the Apache Stanbol project and rapid take-up of Create.js in major open source content management systems such as Typo3 and Drupal.
The early adopters were less confident about the immediate value of IKS technology to their current client base.
Although it must be said that most of the adopters listed the questions of whether the technology improves customer retention (loyalty) or help manage business processes as not applicable for their adoption use case. Most
of the adoption use cases were motivated by a need to expose themselves to semantic technologies rather than
develop new down-stream applications. So it can be said that the adoption helped the companies bring incremental improvements to their current products rather than launch new downstream semantically enabled products.
© IKS Consortium
2013
7 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
2 Early Adopters Programme Objectives
From the DoW: “Throughout the project, we will recruit up to 40 typically small CMS suppliers and provide
training as well as small validation case development grants which should enable them to participate in the
external validation of the IKS. There is a budget allocation of € 260.000 for these external activities, amounting
to an average cost of 6500 € per external validation case, including initial training in the use of the Stack components. The training given will offset some of their initial investment needed to adopt the technology. The validation will be by questionnaire and by interviews with selected developers from this group of users.”
2.1 Summary of Evaluation Contract
The framework for the early adopters activities is formulated in a general contract that applies to all participants.
The contract has the following elements;
(the complete version is available online evaluation contract)
1)
one of your (early adopters) technical staff
will be attending a dedicated workshop (the first
Early-adopters workshop will take place in Salzburg, Austria in the second half of June 2010)
where the concepts and workings of the stack will
be explained - you receive a travel and subsistence
grant for this. Workshops will be held at different
locations in Europe so that it will be easy for participants to attend one of them.
2)
you will be using specific IKS components
of your choice (depending on where your firm's
technology needs are) and you will integrate them
in your current CMS technology. You will receive a
development grant for the integration effort and IKS will link to your site if you can show the use of an IKS
component.
3) we will conduct structured interviews or ask for a brief evaluation report that will help us to develop the
final version of IKS which will also be open source and which will also be open for evaluation. You will receive the full payment of the early adopters grant once we have received your report.
4) The grant scheme is offered to approximately 40 CMS firms (Open Source-based CMS is not a precondition for participation) and each grant is worth approximately 1 person month of effort as described under a), b) and c).
5) We recognize that semantic technology - while offering significant benefits - is still a tough beast to tame
and we recognize that small firms cannot normally afford to spend the cost of a developer's month just on
"trying it out". Here you have the chance of getting at least this initial hurdle paid for, getting the technology
explained before you try it, and being able to use it immediately if it does work for you!
2.2 Evaluation Phases of the IKS Stack
The early-adopters will be able to validate the various versions of the IKS stack and especially the various components. Components will be available across the layers of the stack from the persistence to the user interaction
layer. Such components will include for example a semantic engine to manage ontologies and knowledge models, a semantic editor and a semantic content enrichment engine.
The IKS Stack software will be released in three major iterations. According to the development roadmap the
IKS will build an Alpha (2010), Beta (2011) and final release (2012) of a reference implementation of the envis-
© IKS Consortium
2013
8 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
aged Interactive Knowledge Stack. The timeline for the releases and evaluation by external early-adopters is
listed below.
As stated in the first report from the Early Adopter Report series building up trust in the community must have
priority over a “hard-sell” approach for just signing up adopters to meet the milestones, and the signing up process is crucially dependent on the availability of usable software. This dependency was not fully appreciated by
the authors of the work plan, in 2008 and hence, with hindsight, the definition of (arbitrary) intermediate milestones was not a realistic approach to the issue. Instead of listing the intermediate milestones we prefer to work
with the overall timetable listed below which specifies only the number of early adopters per version of the IKS
stack matched to the likely release date of the software.
Table 1 IKS Stack Release Timetable and External Validation Programme
Version
Likely Release Date
Alpha
Beta
Final Release
22 October 2010
April-June 2011
January-March 2012
Total
Number of Early Adopters
evaluating each version
5
10
25
40
The Alpha release will be validated mostly internally, in the project’s pre-defined use cases. There will also be
small groups of external early adopters asked to evaluate this early version to ensure continuous improvement of
the Interactive Knowledge Stack. The primary focus of the validation phase for the external early adopters will
however be the Beta and final releases (the latter being used to build the Road Show Demonstrators). In the final
phase a larger group of early adopters (minimum 25) will be asked to validate the IKS stack. The validation
process will consist of screencasts/videos of the running system tested onsite with third party content, questionnaires and/or telephone interviews with the IKS team. The external validation partners will receive a training
grant and compensation for writing a validation report as the project's contribution to their acting as early
adopters.
3 Identifying and Selecting Early Adopters
This section introduces the approach taken to sign up CMS providers to the IKS Early Adopters programme. It
includes the communication phases taken. The success of this approach is explained in the next section
© IKS Consortium
2013
9 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Early Adopters Status Report.
3.1 Communication Approach
This section looks at the IKS strategy to launch and sustain a dialogue with CMS providers. We follow the AIDA marketing strategy, which has four basic phases that moves from initial introduction to concrete action:
Awareness, Interest, Demand, Action. In the case of the Early Adopters programme the ultimate action is clear –
obtaining a contractual commitment to validate the IKS Stack.
Phase
Actions
1. Awareness
Educational phase – in this phase we introduce the basic concepts, goals and objectives of IKS to CMS providers. This is usually performed via email and pointing
contacts to relevant documents on the public website. In this phase John Pereira the
IKS Community Manager is the key contact.
Expression of interest – in this phase an expression of interest is sought. Therefore
first step is to check that the contact person is relevant i.e. appropriate decision maker. This usually means an executive for example product development manager. The
CMS provider expresses serious interest usually in a telephone conference call session. Expression of interest is confirmed by joining the IKS Community Mailing List.
In this phase John Pereira is also the IKS key contact.
Alignment of strategic interests - this is a strategic process that involves matching the
CMS providers’ strategic interests to the IKS development plan. Wernher Behrendt
as the IKS Principal Investigator coordinates this phase with the support of the IKS
partners. The result is a decision on the level of involvement and commitment to IKS
based on formulated expected results/outputs.
Commitment of resources – this phase, in the case of the Early Adopters programme
is actually the coordination of involvement, so more administrative - such as signing
of EA contract, and participation in the validation phase. This phase is coordinated by
John Pereira.
2. Interest
3. Demand
4. Action
3.2 Issues to Consider for Contacting CMS Providers
In building relationships with CMS providers we need to be aware of the following points:
1. CMS Providers are mostly small-to-medium sized enterprises: Most of IKS relevant CMS players are highly focused small enterprises with between 10-50 employees. This means that they have tight resource restrictions which in turn means IKS needs to manage the relationship sensibly to ensure a win-win situation.
2. Direct competitors: Some of the CMS providers are direct
competitors to each other. For example there is a clear competitive situation between one IKS partner and an organisation which has expressed
© IKS Consortium
2013
10 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
3.
4.
interest in IKS results, but is reluctant to share information because of this situation.
Aligning IKS with multiple strategic business interests: After the first year of the project it is clear
that only committed CMS players with a clear overlap of their individual strategic interest with IKS (at
the time of contact) will join IKS at some convenient point in time. To align the (partly pre-defined)
IKS development roadmap with the strategies of each of the relevant CMS players is a challenge beyond the normal dissemination work known from other projects.
Balance between code contributors and free-riders: The IKS software code is licensed under the
New BSD license (for more information see IKS Community Policies online at: http://wiki.iksproject.eu/index.php/Softwarelicense ) which means that there are no restrictions on taking the code and
using it for commercial purposes. It is the goal of IKS to create real market impact so this license is the
most appropriate. However as with any open-source project – we have to address the question how to
be fair to those who contribute and how to treat those who are more seen as “free riders”? IKS needs to
keep the motivation high, amongst those who are willing to contribute while at the same time, attracting
a larger group of CMS providers to increase the impact potential of the project.
We have no “text book answers” to these challenges and therefore, we have to balance our pre-conceived strategies with case-by-case tactics, in response to the market, the technical developments in the project and the buzzwords and technology trends appearing in the relevant communities over this period of four years.
3.3 Types of Early Adopters
The primary target group for the IKS Early Adopters Programme are CMS vendors (suppliers). They are asked
to integrate and test the IKS Stack or components in their technology stack against typical user scenarios. As
owner/developer of their technology stack they are seen as key opinion leaders - needed in the broader take-up of
IKS results. The second group are the so-called CMS integrators i.e. companies that provide services and solutions around one or more CMS Stacks. This group can again be divided into those that contribute to the CMS
development community and those who do not. In IKS we are particularly interested in the community active
integrators especially those that can become opinion leaders in their community. To promote this we stipulate the
need for dissemination activities as part of the early adopter proposal. Successful examples of this include Zaizi
demonstrating the benefits of IKS results within the Alfresco community, and Evo42 within the Drupal community. The third group are labelled CMS tool providers. These companies are usually single product focused
providers looking at making their product more interoperable with leading CMS. Solutions include rich editors,
information discovery services, and SaaS based offerings. At present there has only been one early adopter contract accepted from this group.
© IKS Consortium
2013
11 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
4 Early Adopters Status Reports
4.1 Early Adopter Summary 2012
In the final year of IKS report there were a total of 16 new early adopter contracts signed. The total number of
early adopter contracts signed as part of the IKS Early Adopters Programme amounts to 36 plus the 5 from the
UI/X Challenge - this represents a total of 41 IKS early adopters. Of the 16 new early adopter contracts signed in
2012 a great majority of them completed their validation work in the second half of the year. Despite the maturing nature of the IKS technology the challenge for the early adopters of validating a “moving target” continued
throughout 2012. The great work of the IKS development teams helped to overcome this to a certain extent with
individual support and consultation. Most of this support took place directly on the development mailing lists i.e.
Apache Stanbol Development Mailing list and the VIE/IKS Google Groups mailing list. Of the 41 early
adopters: 7 were CMS Vendors, 13 CMS integrators, 12 Tool Providers, 4 End-users and 5 as part of the UI/X
Challenge. The loose term CMS is applied here simply for ease of use. This term however extends to include
document management systems, web content management systems, groupware, and more process oriented content management systems.
Type
CMS Vendors
CMS Integrators
CMS Tool Providers
CMS End-User Organisations
IKS UI/X Challenge Adopters
Total
Signed on
7
13
12
4
5
41
As part of the validation work all early adopters were asked to complete a simple questionnaire consisting of 19
questions. All questionnaires are available on the public wiki: http://wiki.iks-project.eu/index.php/Validation
The 19 questions can be grouped into the 7 main themes:
8.
9.
10.
11.
12.
13.
14.
Do I understand the IKS technology?
Does the IKS technology add value to my technology stack?
Is the IKS technology robust for implementation?
Is the License acceptable?
Can I get involved? Level of community support
Am I confident about the sustainability of IKS technology?
Does IKS technology add direct value to my clients?
The results of the questionnaire grouped according to the 7 themes above are provided in the chart below. A
majority of the IKS early adopters (73%) indicated that they were confident about their understanding of the IKS
technology. They also felt confident about the level of community support and ability to participate in the community development process (65%). There was also strong support for the permissive software license chosen
(62%). 64% agreed that the IKS technology added to their own technology stack. There was however concern
about the maturity of the technology for immediate application (50%), and only 42% were confident about the
long-term sustainability of the technology. These figures improved, especially in terms of sustainability with the
graduation of the Apache Stanbol project and rapid take-up of Create.js in major open source content management systems such as Typo3 and Drupal.
The early adopters were less confident about the immediate value of IKS technology to their current client base.
Although it must be said that most of the adopters listed the questions of whether the technology improves customer retention (loyalty) or help manage business processes as not applicable for their adoption use case. Most
of the adoption use cases were motivated by need to expose themselves to semantic technologies rather than
develop new down-stream applications. So it can be said that the adoption helped the companies bring incremental improvements to their current products rather than launch new downstream semantically enabled products.
© IKS Consortium
2013
12 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
100% 90% 80% 73% 70% 64% 62% 65% 60% 50% 50% 42% 40% 35% 30% 20% Does IKS technology add direct value to Am I conIident about sustainabili
Can I get involved? Level of community Is the License acceptable Is the IKS technology robust for implement
Does the IKS technology add value 0% Do I understand IKS technology 10% 4.2 Early Adopter Summary 2011
At the time of writing a total of 26 early adopter proposals were ready and online at http://wiki.iksproject.eu/index.php/Participants of which 20 are signed contracts. As mentioned below in the first wave of early
adopter recruitment (2010) there were limited IKS components ready for industry validation. The components
available were the enhancement engines. As a result, it was decided to slow the second recruiting phase in 2011
until more components across the IKS stack came online for industry validation. The recruiting therefore, especially in the first half of 2011 was with longstanding contacts. In the second half of 2011 effort was again placed
on attracting new contacts but with a focus on CMS end-users such as web and intranet professionals. The two
workshops both in Paris and Aarhus targeted CMS end-users. We were able to increase IKS visibility in these
new markets; for example, the Aarhus workshop resulted in more than 300 new CMS end-user contacts for IKS
from a broad range of vertical markets such as finance, energy, health, government, news and media, and nongovernment organisations.
In 2011 there were a total of 11 new contracts signed, plus the 5 contracts for the IKS UI/X Challenge. The new
contracts included validation of new IKS components such as Ontonet, the Refactor Engine, and VIE. In 2011
IKS also continued to extend validation in key open source CMS communities with large installation bases, such
as Plone, Alfresco, Confluence, WordPress and Drupal. The full list of adoption and contract is presented below
in the following sections.
The delay in IKS Release 6.0 has also impacted the early adopter-recruiting work. The release 6.0 is now due
end of February 2012. Preparation in the form of evangelising and raising the visibility of IKS in the CMS market is constantly taking place, however it is not possible to begin serious negotiation with potential early adopters
unless the technology has reached a certain level of maturity, and not all early adopters are prepared to work
with Alpha and Beta technology. Therefore, the third major recruiting wave especially with the 45 candidates
classed as “wait and see” will begin in March 2012.
© IKS Consortium
2013
13 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
To overcome the issue of validating technology under continuous development (perpetual beta) is now a greater
involvement of the developers in the recruitment phase. The plan as described in Table 2 below is to have 20
early adopters for the IKS 6.0 (Final Release). A major recruiting drive will include the final IKS community
workshop planned for early June 2012 in Salzburg.
4.3 Early Adopter Summary 2010
In 2010 the early adopters programme was kicked off with the workshop in Salzburg June 2010. In which potential candidates were invited to meet the IKS team and get first impressions of IKS Alpha. At the workshop the
IKS Alpha consisted of the FISE semantic enhancement engine accessed as a RESTful service (see:
http://wiki.iks-project.eu/index.php/FISE). This event was successful with the sign-up of 9 early adopters, see
table below. From this group a selection were asked to present their results at the Amsterdam, December 2010
workshop.
For the first round of early adopters FISE was the only IKS component available for validation. Therefore it was
decided to limit these early adopter contracts to a total of 6 000 Euro instead of 6 500. The exception was evo42
Communications. Evo42 Communications has become a very active partner in IKS and along with participating
in the early adopters programme is also a lead development partner in the IKS Semantic Interaction Framework
(See: http://wiki.iks-project.eu/index.php/Semantic_Editor). As a result they agreed to become the first early
adopters of Apache Standbol (Version January 2011, with the RICK component). For this the contract was set at
7 000 Euro. Along with the validation evo42 Communications has also to play a leading role in demonstrating
the value of IKS within the Drupal community, see the proposal (Evo42 Communications Ltd) below for more
details.
The Table 2 below provides a look at the number of signed early adopters according to timetable and IKS Stack
version. With 9 early adopters for the Alpha stack we have overshot the planned target of 5. The consequence is
that current proposals under discussion have been asked to evaluate the Apache Stanbol version that includes the
IKS components RICK and KReS.
It remains a challenge to sustain the attention of potential early adopters as they wait for the next release of the
IKS stack. This is bridged with on-going technical and strategic discussions between IKS developers and potential early adopters.
Table 2 IKS Stack Release Timetable and Status of External Validation Programme
Version
Alpha
Beta
Final Release
Likely Release Date
22 October 2010
April-June 2011
January-March 2012
Total
Contracted target number
of Early Adopters
5
10
25
40
Actual number of
Early Adopters
9
11
20
Table 3 below provides a breakdown of early adopters according to actual signed-on versus in discussion and
type of early adopter. As shown below the level of participation is highest among CMS vendors, which is the
primary target group for IKS.
Table 3 Summary of IKS External Validation Programme
Type
CMS Vendors
CMS Integrators
CMS Tool Providers
CMS End-User Organisations
IKS UI/X Challenge Adopters
Total
Signed on
4
11
4
1
5
25
In discussion
9
7
4
8
Total
13
18
8
9
28
53
The next sections provide a complete list of the organisations involved in the early adopters programme. The
information lists the organisation name, link, CMS platform and IKS component/s addressed in the proposal.
© IKS Consortium
2013
14 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
4.4 Summary of Signed Contracts
4.4.1 CMS Vendors
Organisation
Contact
Contract Date
Signed / Link
CMS Name / Type
Proposal Link /
Name of IKS Component
QuinScape GmbH
Andreas
Kuckartz
Gentics
Haymo Meran Gentics Content.Node 5.
18 October 2010 Proposal
Goss Interactive
GOSS iCM Commercial with Java,
Gary Ratcliffe .NET and Cold Fusion delivery servers
18 October 2010
Ximdex
Juan Prieto
May 2011
OpenSAGA
4th August 2010
Ximdex CMS
FISE OpenSAGA
Integration
FISE validation proposal
4.4.2 CMS Integrators
Organisation
Contact
CMS Platform
Contract
Signed
Proposal/Components
Klein & Co
Jens W. Klein
Plone
26 July 2010
FISE Plone Integration
Zaizi Ltd
Aingaran Pillai
Alfresco
29 July 2010
FISE Alfresco Integration
SourceSense
Tommaso Teofili
Confluence +Alfresco 29 July 2010
Punkt.netservices
Martin Kaltenböck Drupal
evo42 communications Rene Kapusta
Drupal
FISE Confluence + Alfresco
Integration
18 October
2010
Drupal + FISE integration
22 December
2010
IKS for Drupal
Acuity Unlimited
Martin Dow/Steve
Bayliss
Fedora Commons
KRES Integration
Interact
Andrea Volpini
Wordpress
Interact Apache Standbol integration
Lunaria
David Eccles
Drupal
Apache Stanbol integration
Netmühle Internet
Agentur
Martin Mayrhofer
Apache Sanbol integration
Ectware s.r.l
Alessandra DonniLiferay
ni
Apache Stanbol integration
Object'Ive
Frederic Noel
Apache Stanbol integration
MakoLab SA
Mirek Sopek
Webnodes CMS
Proposal
LOGICELLS
Anil CASSAMCHENAI
DotNet Nuke CMS
Proposal
Drunomics
Wolfgang Ziegler
Drupal
Proposal
4.4.3 CMS Tool Providers
Organisation
Contact
Tool
© IKS Consortium
2013
Contract
Signed
Proposal/Components
15 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
1st August
2010
SalsaDev
Stephane Gamard
Salsadev
FISE engine for Salsadev
Ooffee
Florent Andre
Liip AG
Lukas Kahwe
Smith
Symfony2 PHP
Proposal
CELI France
SAS
Luca Dini
NLP Analysis Tools
Apache Stanbol
SEWEBAR
Andrej Hazucha
Joomla!
SEWEBAR Proposal
Ooffee
Florent Andre
GzEvD
Pablo Mendes
Formcept
Anuj Kumar
Proposal
Proposal
DB Spotlight + Apache Stanbol integration
DB Spotlight
Open Source Semantic Stack
Content Control Andreas Flack
VIE Integration
Rens Admirral
Rens Admiral
Typo3
Typo3 + VIE Integration
Sztakipedia
Mihaly Heder
UIMA Integration
UIMA + Apache Stanbol Integration
Netlabs.org
Adrian Gschwend
Netlabs
Apache Stanbol Integration
Buddycloud
Simon Tennant
Buddycloud
Apache Stanbol Integration
Conatix
David Lehrer
Gnowsis
Bernhard Schandl
Manafactory
Francesca QuaratiTwitstory
no
Fluid Operations Peter Haase
Apache Stanbol Integration
Refinder
Apache Stanbol Integration
Apache Stanbol Integration
Information Workbench
Apache Stanbol Integration
4.4.4 CMS End-Users
Organisation
Contact
Proposal
Integration of Apache Stanbol
Cytogenetics
Maciej Sykulski
SIMsKULTUR
Walter Praszl
Drupal 7
Software AG
Clemens Forster
Alfresco
MarkTheGlobe
Matthias Zeitler
Global SEO
4.5 Proposals Under Discussion but not Awarded
Name
Electronic
1
Beorn Technologies
http://www.beorn-technologies.com/
France
CMS Integrator
2
eZ Systems
http://ez.no
Norway
CMS Vendor
3
Flor de Utopia
http://www.flordeutopia.pt/
Portugal
CMS Integrator
4
InfoAxon Technologies
http://www.infoaxon.com/
India
CMS Integrator
5
Logica
www.logica.dk
Denmark
Computers: Software
6
Nooku
http://www.nooku.org
Belgium
CMS Tool Provider
7
Onehippo
http://www.onehippo.org/
Netherlands
CMS Vendor
8
Quadra
http://www.quadra-informatique.fr
France
CMS Integrator
© IKS Consortium
2013
Country
Industry
16 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
9
Soziales Wien
10
11
Vox Teneo SCRL
World Health Organisation
12
1ntt
13
Alfresco
http://www.alfresco.com/
14
Apache Lenya
http://lenya.apache.org/
15
Arla Foods
http://www.arla.com/
Denmark
CMS Tool Provider
Foods & Nonalcoholic Beverages
16
CKSource
http://cksource.com/
Poland
CMS Tool Provider
17
Freie Universität Berlin
http://www.fu-berlin.de/en/
18
Jadu Limited
www.jadu.co.uk
Germany
Educational Services
United KingCMS Vendor
dom
19
Jahia CMS
http://www.jahia.org/cms
20
Kendra Initiative
http://kendra.org.uk/
Switzerland
CMS Vendor
United KingCMS Integrator
dom
21
http://www.metatheke.com/en/company
Portugal
CMS Integrator
22
Metatheke Software
Morgenavisen Jyllands
Posten
http://jp.dk/
Denmark
News, Media
23
Moxiecode Systems AB
http://www.moxiecode.com
Sweden
CMS Integrator
24
Oxid Esales AG
PAUX Technologies
GmbH
http://www.oxid-esales.com
Germany
CMS Vendor
http://www.paux.de/
Germany
CMS Vendor
sitecore
SunGuard Global Technology
http://www.sitecore.net/
Denmark
CMS Vendor
http://www.sungard.com/infinity
Germany
Computers: Software
25
26
27
www.fsw.at
http://www.voxteneo.com/en/solutions/c
ms
Austria
Government Services
Belgium
CMS Vendor
http://www.who.int/en/
Switzerland
Healthcare
www.1ntt.com
Finland
CMS Tool Provider
United KingCMS Vendor
dom
4.6 IKS UX Winners
The full report for the IKS UI/X Challenge is available in the deliverable 8.4.1. The proposals and result are also
available online at http://wiki.iks-project.eu/index.php/Validation
Organisation
Contact
Contest Presentation
Semantic Content Editor
Liip AG
Loic Schüle
InsideOut10
Andrea Volpini
Salsadev
Nicolas Gamard
Augumented Content Highligher &
Extended Search box
Zaizi
Aingaran Pillai
Semantic Search Tool on Alfresco
KMI Open University
Mathieu Daquin
Personal Web Analytics as Semantically Enriched Web History
© IKS Consortium
2013
WordLift 2.0
17 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
5 Early Adopter Proposals
5.1 CMS Vendors
5.1.1 QuinScape
QuinScape GmbH as the lead committer of the open source project OpenSAGA is going to implement a FISE
adapter for OpenSAGA. OpenSAGA is the premier strategic open source platform for developing eGovernment
applications conforming to the German SAGA standard - Web 2.0 and knowledge management technologies are
an area of top interest for future applications scenarios. Therefore we will provide a generic infrastructure for
plugging FISE into more complex project scenarios. This will include building a model based and declarative
approach for integrating FISE compliant with the way OpenSAGA addresses web development.
Use-Case
FISE-based self-organizing semantic Wiki based on OpenSAGA
Our use case centers around the fact that OpenSAGA is a component based and model driven development platform for e-Government applications. If we succeed in successfully providing a deep integration of FISE in
OpenSAGA, all future projects will be able to benefit from the existing integration by being able to apply it to
project-specific semantic use cases.
Therefor the main goal of our proposal is to provide a full integration of FISE in OpenSAGA by testing it with a
generic use case that can be extended to much more complex real world examples (see the end of this section for
more real world applications).
An OpenSAGA Wiki extension will be created.
Users will be able to view and edit Wiki pages.
Users are not required to provide links in Wiki pages.
The FISE engine will be integrated in order to enhance concepts and terms contained in the Wiki text
by either auto-discovery of important concepts or by referencing manually managed concepts in a dedicated knowledge base.
• The adapter for semantic content sources will only be implemented to such an extend that the viability
of the approach can be verified.
Real world use cases for the basic concept explained above in the OpenSAGA context are e.g.:
•
•
•
•
•
•
•
•
•
OpenSAGA stresses web accessibility. In Germany the standard BITV (and soon BITV 2) as well as
WCAG serve as reference points for defining accessible applications. One important aspect concerning
semantic accessibility is the requirement to provide explanations for abbreviations contained in content.
An obvious approach might be to manage abbreviations in a central knowledge base and then apply
FISE to all output in order to recognize semantically appropriate abbreviations and their context and deliver a meaningful explanation. Note that "meaningful" in the context of web accessibility specifically
means that different forms of presentation might be required for different user groups (e.g. blind people).
Unstructured business data (e.g. in corporate Wikis) will benefit from automated linking to other
knowledge sources (e.g. places to maps, people to social networks, companies to coporate datasheets
and so on). This will specifically simplify knowledge recovery.
Medical Wikis could provide additional information for medical drugs (prescription, usage, risks) based
on the context in which specific drug is being mentioned.
Personalized semantic enhancements are another important real world aspect that has come to our notice in various projects. The idea behind this is obvious: The usefulness of an enhancement strongly depends on the role(s) of the content user - e.g. a manager might want to see different enhancements than
the head of sales who in turn probably is interested in vastly different information than a programmer
(when e.g. viewing a product specification). Thus we specifically will include real-time enhancement
scenarios for our test cases.
Automatically enriching content with RDFa is an important aspect for search engine optimization of user generated content in order to shield the actual content editor from the complexities of RDFa.
© IKS Consortium
2013
18 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
These examples prove the importance of a generic model based integration of FISE into OpenSAGA as the
building block based approach of OpenSAGA will greatly facilitate the adoption of FISE in all projects based on
OpenSAGA.
Validation
The following issues will be checked:
• FISE must be integrat-able into a third-party platform. The openness and extendibility of the FISE API
will be evaluated.
• FISE must be easily extendable with new plugins that use internal content from third party platforms.
Data integration issues will be evaluated.
• FISE must be able to serve and enhance content in scenarios where articles are edited by a live team of
editors (with an un-staged publication process, e.g. a highly dynamic semantic tag environment). Performance will be evaluated.
Planned Tasks
QuinScape will execute the following tasks in order to integrate FISE:
• Models will be added to the OpenSAGA platform in order to activate and connect the FISE engine to
existing data models.
• Action models will be added in order to be able to enhance content programmatically.
• A FISE plugin extension will be added in order to be able to add dynamically derived semantic content
from other OpenSAGA sources.
Performance
See above. Due to the fact that FISE will be used to provide new semantic enhancements automatically derived
from dynamically generated content (live) performance and extend ability as well as dynamic extend ability
capabilities are of prime importance. We will closely evaluate the underlying performance issues in order to be
able to use FISE in environments with 100s of editors.
Online Demo
QuinScape will provide a demo version of the experimental Wiki on the official OpenSAGA website. If the
evaluation results in a Wiki product ready for production use the OpenSAGA website will be extended to include an official OpenSAGA Wiki built upon the FISE-based engine.
Visibility
OpenSAGA being the premier open source framework for eGovernment applications provides a good amount
of visibility for FISE in both eGovernment and knowledge management communities and users of those applications. Additionally the OpenSAGA website serves as the hub of the OpenSAGA community - thus the addition
of a public Wiki based on the FISE engine guarantees a great opportunity for dissemination of the results of the
IKS project.
Other issues
We also would have loved to integrate the Semantic Editor into the Wiki but the AGPL based licensing approach
currently prevents this.
At least it is not obvious what the implications of the AGPL3 are in this case. Must source code for applications
running on the server be released? Which licenses are allowed for editor plugins? Would the Apache Software
Foundation accept a project which in some way depends on this component?
© IKS Consortium
2013
19 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
5.1.2 Gentics
Gentics Software GmbH is an Austrian CMS and Portal Software Provider. We want to integrate FISE into our
main product Gentics Content.Node through the Aloha Editor. The integration is done on client side in javascript
as Aloha Editor plugin which will provide an easy to use live stack of annotations. As one use of the live stack
we implement an automatic live annotation of tags. On server side an extension to the gentics content connector
with FISE will be implemented.
Use-Case
While editing with Aloha Editor (integrated in Gentics Content.Node) the content is sent to the Gentics Content
connector FISE backend. FISE returns a list of tags to add to the content. The tags are automatically added to the
document, so there is no need for further user interaction. A user may discard tags which he thinks are not appropriate, with one single click.
Validation
Online Demo
The implementation will be available to the public on http://demo.gentics.com and the automatic adding of
tags may be tested.
Aloha Editor Annotation plugin
The annotation plugin will be available as opensource under the AGPL license hosted on github. Developer may
test the plugin by using the annotations methods to list annotations, apply annotations to the content or any other
usage. Developers may use the FISE engine of http://demo.gentics.com for testing purposes.
Performance
Please identify a concrete performance issue that is of value to Gentics and define a proper testing procedure for
it. The performance issue should also be of general interest to CMS. (wb)
Note wb: The text below does not describe clearly, a valid performance test, yet. It only provides possible issues
and is based on assumptions.'’’
Concurrent users will write content in the same time and therefore we need to know how many parallel request
are possible. Our target is to achieve realtime annotation (information) therefore we need to have frequent updates of the annotations on the almost same content.
Parallel requests
We will test how many parallel annotation requests can be done and measure the mean processing time on an
average server hardware.
Sequential requests
We will test the mean time for sequential requests with almost the same content (content+1 sentence each request).
Planned Tasks
WP1
•
•
design the live annotation stack API
evaluate FISE and plan the Gentics content connector integration
WP2
•
•
implement the live annotation stack
implement the FISE adapter in the live annotation stack
© IKS Consortium
2013
20 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
•
integrate FISE in the Gentics Content Connector
WP3
•
•
set up the github project for the plugin and integrate automatic building with Aloha Editor
write unit tests, build, deploy and packaging scripts for FISE Gentics content connector integration
WP4
•
•
integrate a preconfigured proxy into Gentics Content.Node to work with Gentics content connector and
FISE
integrate Aloha live annotation plugin into Aloha Editor implementation in Gentics Content.Node
WP5
•
•
develop and roll out Aloha annotation plugin demo
roll out the Gentics demo cms
Online Demo
http://demo.gentics.com http://aloha-editor.com/demos/annotation-plugin
Visibility
We plan to announce the plugin and FISE integration among the Aloha Editor community and website as well as
among the Gentics clients through the Gentics Newsletter and Gentics website. The FISE annotation plugin will
be one of the first plugins based on the new Gentics Content.Node 5 with Aloha Editor integrated coming out
October 2010 and it will be announced broadly as successful integration of Aloha, Gentics and the IKS FISE.
Performance of Contract
•
•
•
•
•
•
•
The terms of the contract are:
Start of contract 1st October 2010
IKS component for validation is the FISE
Demo system available 1st December
Validation interview in December
End of Contract 31th December
Total remuneration for this contract is 6000 Euro.
5.1.3 GOSS Interactive
The proposal is based on our evaluation of the FISE project. This will inevitably be refined as FISE and IKS
evolve. At present the proposal refers only to the FISE component. We are interested in the Aloha/Semantic
editor components but may be limited by browser constraints determined by our customer base.
Proposal
•
•
•
•
The roadmap for GOSS iCM already contains plans for greater semantic capability, particularly in the
area of entity identification and establishing relationships to external held information on those entities.
This will involve automatic identification and classification combined with user interaction to confirm
selections.
GOSS will investigate using the FISE engine for this purpose and, if suitable, integrate it into the iCM
distribution.
GOSS have been looking at a number of different technologies for identifying named entities and resources. If we adopt any of these we will investigate implementing these as additional engines for FISE.
Use-Case
Identifying Related Content
© IKS Consortium
2013
21 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Users of GOSS iCM create content in the form of articles. These articles have a range of related assets like images, meta data and other articles. GOSS iCM can already automatically suggest what internally held assets
should be related. The next requirement is to recommend externally held assets. This requires greater semantic
understanding of the article content in the form of entity identification and classification. This entity information
can then be used to assist the location of external resources.
Semantic Mark-up
Published web content, derived, from articles should contain semantic mark-up, probably using RDFa, to allow
third parties to obtain greater information from the content. This requires the identification and classification of
information within the content and correct tagging of the content.
Entity Identification
We expect most of our clients will be interested in identifying people, places and, possibly, organisations. Because of the regional nature of a lot of our clients we expect they will be more interested in entities that have a
geographically local relevance.
Validation
•
•
•
•
•
FISE must be usable by GOSS iCM as an external service without imposing an unacceptable processing
overhead or installation complexity.
It must be possible to add and configure new engines within FISE.
The available engines must provide results that are acceptable to our users.
Identification of named entities and resources should be accurate in 80% to 90% of instances. This assumes suitable domain training data for engines that support training.
Validation will be performed using real world articles relating to local government in England, Scotland
and Wales.
Performance
•
•
•
•
•
•
•
The terms of the contract are:
Start of contract 1st November 2010
IKS component for validation is the FISE
Demo system available 1st April 2011
Validation interview in April 2011
End of Contract 31st May 2011
Total remuneration for this contract is 6000 Euro, excluding VAT.
Visibility
FISE itself will be either installed on the users server or hosted by GOSS. Initially when an article is being created users will be presented with suggested people and places entities extracted by FISE. They will choose which
ones they wish to be tagged in the article.
For demonstration purposes the use of FISE will be made more explicit. Further uses and interactions are still
under investigation.
5.1.4 Netzmuehle Internet
Use-Case
Integration of semantic web technologies into a new e-commerce solution called neoshopia. Detailled information about neoshopia can be found on the neoshopia.eu website (german only).
The solutions works a lot with stories. In those stories (e.g. a candle light dinner in Rome) products of the shop
should be integrated (a small image, title of the product,...). This combination to sell products via emotional
stories is one of the main USP of neoshopia in relation to traditional online-shop solutions.
© IKS Consortium
2013
22 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
The solution works best with non mass-products e.g. small fashion labels that are not so common and for products which cannot battle with mass-products via the price.
The integration respectively the combination of the products with the stories should be solved via semantic analysis of the text and the most adequate products should be shown in the article (e.g. a bottle of red wine in the line
where the gentleman serves a glass of wine to his beloved).
Validation
§
The solution will be tested in real online-shops with real products and with stories written for these shops.
§
Together with shop dealers the solution will be tested if the automatic selected products apply with the content of the story.
§
It is planned to test the solution with at least three different shops (e.g. lifestyle, deli, start-up)
§
The shops will have a different amount of products
§
Shops will only a handful amount of products but with the possibilty of customization
§
Shop with at least 20 different products in at least 10 categories
§
Shops with 50+ products in dozens of categories
§
The shops are tracked by an online user statistic (Piwik) to measure the conversion rate and user interaction
§
With the measurement we want to prove the theorem that emotional stories combined with appropriate
products lead to higher sales rates
Performance
§
start of contract: 1st January 2012
§
selected components are: Apache Stanbol
§
integration will be done by: Netzmühle Internetagentur OG
§
demo system will be available: 15 March 2012
§
end of contract: 31 March 2012
Planned Tasks
§
Setup experimental scripts to test Apache Stanbol in combination with PHP
§
Integrate the Stanbol web services into Netzmühle ORYZA (CMS) using the Netzmühle CORE (web application framework) web service interfaces
§
Build a Netzmühle BARTHII (Online-Shop) module using the implemented services
§
How it works?
§
1. Create product categories in BARTHII.
§
2. Create your products in BARTHII.
§
3. Add the best matching categories to every product.
§
4. Write a story which refers to some of your products.
§
5. When you save your story the CMS automatically will run a semantic analysis via stanbol.
§
6. The best matching products (found via their categories) will be linked to the story.
§
7. The system automatically generates a small box with an image (and some text) of the product and an
"add to cart" button when the story is shown in the frontend.
© IKS Consortium
2013
23 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
§
8. The system tries to show the matching product as near to the found text phrase which correlates to
the product.
§
Test the consumer behaviour "in the wild"
Online Demo
The integrated solution will become part of the first neospopia best practice stores. Links will be posted below
after the go-live of the projects.
If the test will be successful it is planned to integrate Stanbol as standard-feature into the neoshopia store concept.
Visibility
§
The concrete implementations will be presented on technology conferences and start-up fairs in Germany
but also in other european countries.
§
Use case studies will be published in technology magazines.
§
Parts of the developed solution e.g. the PHP web services will be published as open source.
5.1.5 eZsystems
Early Adoption and Validation Proposal
eZ Publish is a mature open source Enterprise Web Content Management System with a flexible content model
and adaptable to a large variety of use-cases. The scope for this early adopter project is add several of the IKS
project deliverables as extensions to the eZ Publish kernel and search engine, mainly the Apache Stanbol enhancement engine/entity hub and VIE editor.
Use-Case
§
Asssistance to editors by suggesting meaningful tags, categorized in pre-defined domains
§
Enhanced relevance and additional faceting for the search engine eZ Find using entity extraction for structured and unstructered content
§
Integration of the VIE editor and its semantic extensions for a better UX for content editors
Validation
The integration of the IKS deliverables will be done as open source extensions to eZ Publish and an active review and feedback campaign will be conducted with the existing eZ Publish community.
Performance
The terms of the contract are:
§
Start of contract 29th August 2011
§
IKS components for validation Apache Stanbol enhancement engine/entity hub and VIE editor.
§
Demo system available 23rd September 2011
§
Validation interview end of September 2011
§
End of Contract 14th October 2011
§
Total remuneration for this contract is 6500 Euro, excluding VAT.
© IKS Consortium
2013
24 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Planned Tasks
§
Low level PHP API to interact with the Apache Stanbol stack
§
Investigate and document constraints (multilingual aspects, backend requirements, …)
§
Automatic annotation with entity extraction upon indexing content with the eZ Find search engine (Apache
Solr based)
§
Semantic tools for editors: tag suggestion (integration with the existing ez tags extension for eZ Publish)
§
Semantic tools for editors: integration of the VIE editor
§
On-line survey within the eZ Publish ecosystem for initial feedback
Online Demo
An online demo will be provided as part of the review and feedback campaign
Visibility
eZ Publish is in use by a large variety of organisations and companies around the globe. As eZ Publish is available as open source with an active community of users and eZ Systems partners, the IKS integration will be available for the entire eZ Publish ecosystem.
5.1.6 Jadu
Early Adoption and Validation Proposal
Jadu is an enterprise content management provider. We aim to integrate two elements of the IKS into Jadu CMS
in order to provide an enhanced semantic experience to content authors and end users of Jadu web sites. This
will include the integration of FISE into the Jadu (JavaScript-based) content editor as well as creating a new
engine for FISE to enhance content with other Jadu data, for example with services and councillors.
Use-Case
Semantic content enhancement in content editor use case 1
1. A user edits an existing document page.
2. User types a person's name and highlights the text.
3. User clicks "Add name" and is presented with a dialog box (or other suitable UI element) which presents suitable matches*
4. User selects correct person and content is semantically marked up and visually flagged (visual changes
are only shown while editing) as being so.
5. User clicks Save. User views document on front-end - markup can be examined for semantic meaning.
* either via FISE or straight contact lookup
Semantic content enhancement in content editor use case 2
1. A user edits a new document page.
2. A user types some content.
© IKS Consortium
2013
25 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
3. A user clicks Save.
4. Content is sent to FISE/Stanbol.
5. User is prompted to review semantic suggestions before finalising save.
6. User views document on front-end.
Only one of these use cases is likely to be implemented.
FISE Engine use case
1. A user edits a new document page.
2. One of the above use cases is used to submit content to FISE
3. FISE runs content through Jadu created engine and returns XML
4. Jadu use XML to enahce content
Validation
§
A sample of Jadu customers will be used to determine that results are suitable for use on their web site
§
A questionnaire will be developed by Jadu in order to evaluate customerexperience
Performance
§
start of contract: June 2011
§
selected components are: Apache Stanbol Enhance/Entityhub
§
integration will be done by: Jadu Ltd
§
demo system will be available:
§
end of contract:
§
Total remuneration for this contract is 6 000 Euro.
Planned Tasks
Jadu will perform the following tasks in order to achieve the scenarios based in the
use cases:
1. The Jadu content editor will be modified in order to include “add name” functionality, the content from
which will be generated by FISE/STANBOL based on the current content of the page
2. A new FISE/STANBOL engine will be developed that will enhance content with other content within
Jadu CMS. For example if a document talks about a specific person that is defined within the Jadu
“councillors” repository the content will be marked up with that councillor.
Online Demo
Jadu will provide a demo system for members of the IKS project to view the integration that has taken place.
Visibility
Jadu will provide the integration to customers is one of two ways, which has not yet
been confirmed. Either
© IKS Consortium
2013
26 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
1. as a (free or purchasable) plug in module for the CMS
2. as a standard component of the CMS to be released as part of the Jadu roadmap
5.1.7 Liip
Early Adoption and Validation Proposal
The ResolutionFinder.org application is a database concept which was developed across four thematic issues
chosen from the UN agenda. These four thematic issues are:
§
clean drinking water
§
women and education
§
malaria
§
small arms and light weapons
Resolutionfinder.org is particularly unique as it not only supports searching and viewing documents, but also
present the history of documents and more importantly of clauses even across documents.
In order to expand the content of ResolutionFinder.org to include further issues we are looking to partially automate the inclusion of more documents. This will consist of reading in PDF documents and reading metadata
splitting them into clauses using Apache Tika. Additionally the goal is to analyze the content to determine the
source language and content to automatically suggest tags for the content.
Further down we are also exploring cooperations with organizations that provide additional relevant content like
that of the ISN from ETH Zurich. The goal would be to be able to automatically suggest related articles from
these external data sources.
Finally in the long term we are looking to provide alternative interfaces for exploring the content beyond the
current set of properties of documents and tags. In this context it would be interesting to be able to automatically
organize content by content as well as suggest related content from documents and clauses. Additionally we
expect users of the system to both use the system on a daily basis as well as only casually. The first group might
want more flexibility in drilling down into the content while the later group will rather need the system to guide
and explain itself.
Use-Case
In the first step we would want to leverage Apache Stanbol to implement "Story 05: Assistance with Semantic
Tagging" and potentially "Story 09: Similarity based document search" by including third party content sites.
In the long term (out of the scope of this proposal) we might also want to look into the following stories to enhance the search experience:
§
Story 17 : Ontology Navigator
§
Story 20 : Personalized Search
§
Story 27 : Define custom facets for faceted browsing
§
Story 33 : Explain facts and entities
Validation
§
§
jngldrm.org evaluates the quality of the tag suggestion
we expect some level of peer review of the components that will all be released on github.com
Performance
© IKS Consortium
2013
27 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
§
§
§
§
§
§
start of contract: October 2011
selected components are: Apache Stanbol Enhancement Engines
integration will be done by: Liip AG
demo system will be available: at resolutionfinder.org by early November
end of contract: November/December 2011
Total remuneration for this contract is 6500 Euro.
Planned Tasks
Liip AG will implement a service API on top of the Symfony2 PHP application development framework that
will then be leveraged from the existing Symfony 1.x application. Via the service API it will be possible to get
additional tags suggested inside the administration GUI for existing clauses. As part of the Symfony2 application
a StanbolBundle (bundle is Symfony2 lingo for plugin) will be created that will be available independently of
the application to allow community reuse and simplify community feedback even by those not interested in Resolutionfinder.org. The StanbolBundle will make integration of Apache Stanbol in Symfony2 easier by providing
a PHP API to query Stanbol as well as providing some simple CLI commands integrated into the Symfony2 CLI
interface for tasks like starting and stopping. The entire code will be released under the MIT open source license.
§
Create new Stanbol Service Symfony2 Application
§
Implement StanbolBundle to handle all communication with Stanbol including:
§
pre processing f.e via Language Identification Engine
§
Natural Language Processing
§
Linking Suggestions
§
post processing f.e. via the Refactor Engine to map the results to the set of tags used on Resolutionfinder.org
§
Add a button to call the Stanbol Service Application from the Resolutionfinder.org Admin
§
Add a language field to Resolutionfinder.org documents database
§
Add a button to call the Stanbol Service Application from the Resolutionfinder.org Admin to determine
the language of a document
The video "iks_proposal.mp4" shows how one can interfact with the double list to select and deselect tags. The
"iks_proposal.png" gives an idea of the interface changes planned. With the Stanbol integration it will be possible to automatically add a list of not yet selected tags into the right hand side for manual selection.
Online Demo
The application will become part of the Resolutionfinder.org platform. For demo purposes administrative access
can be granted.
Visibility
Resolutionfinder.org is backed by a number of organizations that have supported the development to this point.
The effort is lead by jngldrm.org which has received funding from several European organizations like the UN
Association of Germany and is partnering with organizations like the International Relations and Security Network of the ETH. As such Apache Stanbol will become visible by both academic organizations as well as
NGO's.
© IKS Consortium
2013
28 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Furthermore Liip AG is using Resolutionfinder.org as a case study to show potential clients the possibilities of
modern search technology available as open source.
5.1.8 Ximdex
Early Adoption and Validation Proposal
Open Ximdex Evolution SL wants to integrate Apache Stanbol text enrichment engine services into Ximdex
Semantic CMS as a complement of the current engine based on the service Zemanta and semantic technologies
for manual and automatic recognition (and annotation).
The main proposal is providing Ximdex's WYSIWG Editor, aka ximedit, with semantic tools for enriching textual contents introduced by editor users, through Apache Stanbol Enhancer, a RESTFul engine that, as its own
name says, can enhance textual content.
Ximedit provides a section for including external references on the document. This section will receive related
content from Apache Stanbol and will allow users to automatically enrich their documents. Zemanta directly
provides with images/links/references based on the analysis of the contents the user is editing, while Apache
stanbol will provide with automatic annotations for persons, companies and places. During the project, we will
evaluate if we choose one or both engines in next Ximdex WYSIWYG Editor versions.
Furthermore, we will prove VIE project integrating some RDF annotations in ximedit.
Use-Case
•
•
•
•
•
User creates or edits an existing document using ximedit.
User clicks on '”Load” in “External References” button in ximedit.
System queries Apache Stanbol Enhancer for related content of the current information in Web Editor.
System shows user a tab from each source containing related information about the document.
User selects references (organized on images, links and articles) from sources and add them to the original document, enriching it.
Note: We will integrate in ximedit the possibility of incorporate RDF annotations. We will see if we do it as a
automatic or manual process.
Validation
Interested users will try online demo at Ximdex and Stanbol integration website.
A video demo will be available showing the integration and the co-benefits of IKS and Ximdex integration.
Users may download current module's source code.
Performance
By controlling better the annotation process, Ximdex WYSIWYG Editor should provide better results for content enrichment thanks to Stanbol Integration.
Also should offer a better response time than current Zemanta engine.
Planned Tasks
•
•
•
•
•
•
•
•
•
Installation and configuration of Apache Stanbol.
Installation and configuration of Vienna IKS Editables
Development of a Ximdex Client for retrieving text enrichment from Apache Stanbol.
Development of a Merger for Zemanta and Stanbol results.
Development of Manual or Automatic RDFa integration on ximedit.
Integration and performance tests.
Setup of project website and github project for the code.
Documentation and integration conclusions.
Setup of online demo and screencast.
Online Demo
Ximdex will provide an experimental online demo of Web Editor using Apache Stanbol engine on the official
Ximdex Website.
Visibility
© IKS Consortium
2013
29 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Ximdex is a semantic CMS with well known customers in Spain. The use of IKS technologies will spread IKS
visibility among them.
In addition, on the Community Area of Ximdex website all the information about this project in cooperation with
IKS and its results will be collected, to help expanding the knowledge of IKS project.
Last, the integration of VIE will create first VIE integration on Early Adopters program from IKS project.
Performance of Contract
•
•
•
•
•
•
•
Start of contract 15th May 2011
IKS component for validation is Apache Stanbol & VIE
Demonstrated at Paris Workshop 5-6 July 2011
Demo system available online 31 July 2011
Validation interview in September 2011
End of Contract 15th October 2011
Total remuneration for this contract is - 6500 Euro.
5.1.9 Typo3
Introduction
TYPO3 Phoenix is the Next Generation Content Management System developed by the TYPO3 community. We
use in-page editing for modifying the web-pages contents; built around the EmberJS framework and the Aloha
Editor. We plan to expose all editable content as RDFa; and to then use VIE for driving the editing experience.
Vision
Currently, we are using proprietary HTML5 data attributes which enrich the content of the website and which
drive the editing experience. However, we'd like to replace them by RDFa tags; so that these would contain all
the website information; which would then also be parseable by other programs which support RDFa. After
using RDFa to store information, we will use VIE as the core of our Editing Experience, managing the website's
content. The Aloha Editor and our own UI will be implemented then as VIE Widget. Furthermore, this will enable us to embed other VIE widgets in TYPO3 Phoenix, for example the widgets for enhancement of content.
As we use EmberJS as JavaScript Framework, we need to extend VIE to work with Ember.JS, in addition to
Backbone.
Use-Case
After changing the internals to use RDFa, we plan to run several VIE widgets for semantic enhancement, like the
stanbol enhancement widget. Furthermore, we can use RDFa parsers on the website's content, which will enable
further usage in Linked Data context.
Validation
During implementation we will make VIE integration with the EmberJS framework possible (in addition to
Backbone.js), and improve VIE as needed to accomplish this.
Furthermore, the RDFa we generate must adhere to the RDFa standard, and the content type definitions we generate must be in the correct format for VIE.
Performance
•
•
•
•
•
Start of contract: 01 May 2012
Components for validation are: VIE
Demo system will be available: End of August 2012
End of contract: 12 September 2012
Total Contract: 7000 Euro
Planned Tasks
•
•
•
•
•
Extension of VIE to support EmberJS
Integration of VIE into Phoenix
Generating RDFa annotations based on our Content Repository and content type definitions
Generate the content type definition for VIE from our internal structure
BONUS: Possibility to configure additional VIE widgets for the Phoenix content editing interface
© IKS Consortium
2013
30 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Online Demo
A public online demo will be provided
Visibility
The TYPO3 CMS already has a long history, and is used in thousands of websites all over the world. This community is already using the new FLOW3 framework actively, and TYPO3 Phoenix will over some years be the
replacement of the current TYPO3 branch. Parts of the planned tasks can be split in separate packages making
the work available in TYPO3 Phoenix, but also easily usable for developers using the FLOW3 framework. With
this integration a big community will be reached, and a great amount of companies using the products in a great
variety of markets.
5.1.10
MakoLab
Introduction
This proposal considers an adaptation of IKS Software Stack to support MakoLab’s RSI-CMS system
(http://makolab.pl/en/web-media/case-studies/RSI-CMS). RSI CMS (Renault Site CMS) is the CMS created by
MakoLab used by 40+ countries of the world as a tool to create and maintain international Renault websites.
The proposal will be realized as an extension of existing RSI-CMS. RSI-CMS is an ASP.NET CMS that combines a user friendly interface with a flexible structured (XML based) content engine. In addition to standard
desktop sites, RSI-CMS can easily create mobile sites. It features distributed architecture, with production sites
hosted in numerous data centers and cloud solutions around the globe.
The proposal is put forward by MakoLab SA, a Polish company located in Lodz (www.makolab.com),
Use-Case
1. The user of RSI-CMS will be able to use Stanbol Semantic Enhancement facility to semantically annotate the
entities of content managed by RSI-CMS.
2. The RSI CMS will also implement VIE client-side control for marking up of the content under control of the
CMS system. It will also be used for enhancement of RSI-CMS editing capacities with VIE inline editing feature, particularly in the light of responsive and mobile designs.
Validation
Online Demo
Dedicated web page will be set on our website http://makolab.com/iks containing demo with example data and
tests of implemented functionalities.
Feedback from end users
The semantically enhanced system will be presented to the Renault managmenet. We’ll advise on the usage,
gather feedback from end-users, and produce a report about end-users feedback.
Apache Stanbol Semantic Data Manager plugin for RSI-CMS
The plugin will be submitted to Renault with several examples and test cases. Plugin will allow for data transfer
from RSI-CMS framework to Apache Stanbol, access to Stanbol components, /contenthub), plugin will allow for
queries/enhancements to be presented from within RSI-CMS using VIE,VIE2 widgets.
We will ask several users from large RSI-CMS users community to use the platform at the same time and report
their feeling about performance.
Planned Tasks
1.
2.
3.
preparation of test infrastructure (installing apache stanbol within RSI-CMS framework) configure EntityHub to work with RSI-CMS
implementation of an interface for enhancing the content with linked data from services available
through EntityHub, using VIE^2 widget
Apache Stanbol Semantic Data Manager plugin for RSI-CMS framework
1. transfer data from/to database to Apache Stanbol triplestore
2. simple api to access EntityHub
3. display data (RDF/JSON) retrieved from Apache Stanbol
4. display enriched web page rendered with VIE^2 Widget within a RSI-CMS generated page
5. tests and examples of usage
© IKS Consortium
2013
31 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Online Demo
An online demo will be available on the project website under www.makolab.com/iks .
Link to the demo will be placed on MakoLab & selected RSI-CMS websites
Performance
The terms of the contract are:
1. Start of contract July 2012
2. IKS component for validation is the Apache Stanbol + VIE
3. Demo system available: 15 October 2012
4. Validation interview: 31 October 2012
5. End of Contract: 31 October 2012
6. Total remuneration for this contract is 6 500 Euro, including VAT.
Visibility
The enhanced RSI-CMS system will be presented to the Renault management. We’ll advise on the usage, and
gather feedback from end-users. Public visibility of the early adoption will be provided by the following actions:
1. Dedicated web page on our website www.makolab.com/iks containing demo
2. Link to the demo from both MakoLab & Renault websites
3. Newsletter to developers at Renault and to MakoLab newsgroup
5.1.11
ShqiperiaCom
Introduction
ShqiperiaCom Shpk is an Albanian company with more than 10 years of experience in offering content solutions
to local and regional companies. The company's portofoglio includes a range of clients in both the public and
private sectors. Part of our work involves the creation and maintenance of websites through the in-house built
eRise Content Management System.
The eRise CMS is a commercial product but the company is plannig the launch an open source CMS (codename:
equ.al). Both these CMSs will be based on a LAMP stack and will have incude modular implementation allowing for modules such as as Newssite, RealEstate, Shopping Cart etc. Similar modules will benefit from a strong
semantic organization which will improve the findability of the content in the website and the presence of content in the WWW.
Use Case
We would like to use the VIE Tools and a Apache Stanbol instance as a service on the net. Through VIE we will
enhance content through a connection to Apache Stanbol. Depending on the different scenarios, the content from
the Stanbol instance might be DBPedia for most of the users, but in custom cases it will be annotated through
custom's own proprietary data (ex: RealEstate annotation with local-based information + similar properties).
• Use of VIE Tools for content editing and annotations.
Performance
•
•
•
•
•
•
•
Start of contract:
Selected components are Apache Stanbol + Vie
Application will be done by ShqiperiaCom Shpk
Demo available:
Demo example will be available till
End of contract
Total remuneration for this contract is xxxx Euro.
Planned tasks
Integration of Stanbol on a LAMP server with equ.al running as CMS. Support of front-end operations through
the use of VIE tools.
Online Demo
www.equ.al
© IKS Consortium
2013
32 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
5.2 CMS Integrators
5.2.1 Klein & Partner KG
We, Klein and Partner KG, Innsbruck, member of BlueDynamics Alliance, want to integrate FISE with the CMS
Plone and present the result to the Plone Community.
Use-Case
•
•
Editor adds a new article (HTML or File i.e. PDF, Doc) to Plone. She press "save". Plone stores the article and - additional - Plone sends the page to FISE and gets back FISE semantic enhancements. Plone
stores enhancements as annotations to the article. They are displayed side-by-side with the document.
An add-on developer writes a Plone PortalTransform (output-transformation, i.e. XHTML to semantically enriched XHTML). Developer access some article and easily read its semantic enhancements.
Validation
see also the FISE Python/Plone Integration Validation and Online Demo
Validation through the web.
• A public demo site hosted at our server offers a demo account with role Editor. The site will be reset
approx. every 2 hours.
• Validation 1 After login validating visitor can upload any (supported) type of Plone content. Validating
visitor can inspect the enhancements of each document.
• Validation on code level. Steps documented and reversible for developers.
• Plone add on developers are adding one line to packages setup.py file.
• Validation 2 On build out/easy install time all FISE libraries and integration packages are fetched automatically.
• Add on developer adds a dependency to its Plone Generic Setup profile.
• Validation 3 After activating the add-on in Plone all FISE dependencies are activated.
• Validation 4 Developer writes a Plone Doctest. In the test he adds content programmatically and rereads it. Now he can access the semantic enhancements.
Performance
All tasks are done synchronous. So response time of Plone on save of an article increase with the time FISE
needs to return with the enhancements. At the time of writing the proposal FISE works also only synchronous.
Later on, if FISE is refactored to work asynchronous, the Python and Plone components can be refactored to
work asynchronous.
Planned Talks
Step 1: Create a generic Python API to communicate with FISE over its Restful API. Fetch the FISEEnhancements and provide a simple access Python-API. Release of module as Python-Package at
pypi.python.org under Python Software Foundation License.
Step 2: Write a Plone module which automatically sends the content (if needed as plain text) to FISE and annotates the enhancement to the Original content. Release of module as Python-Package at pypi.python.org under GPL.
Step 3: Create a Plone Portlet (UI) showing some enhancements. Release of module as Python-Package at
pypi.python.org underGPL.
Step 4: Present the results to the Plone Community. Spread the word at blogs, twitter, Facebook, ... Arrange
a Sprint (aka Hackathon, in Zope/Plone world its called Sprint) in Innsbruck for interested community people to
© IKS Consortium
2013
33 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
help pushing FISE integration forward. Take part at other Plone sprints and work on FISE topic. Try to get accepted as speaker on this topic on one of the next conferences (Plone Conference in Bristol, DZUGTagung in Dresden, European Plone Symposium).
Visibility
With step 4 we plan to get an reasonable amount of Python, Zope and Plone community response. Motivating
people to try and use FISE is major goal. Here we support the Plone community if FISE problems raising and
give FISE-developers feedback. We will spread the word in related communities in Zürich, Cologne and Graz
utilizing the BlueDynamics Alliance partners.
Performance of Contract
•
•
•
•
•
•
•
The terms of the contract are:
Start of contract 1st September 2010
IKS component for validation is the FISE
Demo system available 1st December 2010
Validation interview in December 2010
End of Contract 31st December 2010
Total remuneration for this contract is 6000 Euro.
5.2.2 Zaizi Ltd
•
•
•
Integration of FISE and Alfresco. Integrate Alfresco with FISE to enable augmentation of Alfresco content with FISE. Documents / Content uploaded or created within Alfresco are converted to simple text
and sent to FISE for semantic augmentation.
Alfresco User Interface enhancements. Enhance Alfresco Share client's UI to provide navigation with
semantic entities. E.g. clicking on entities to search related content within Alfresco.
We'd also like to integrate Aloha Editor when it is released. For now only the above items. I have been
in touch with Alfresco and they are happy for us to work on this and contribute back to the community.
Further details
•
Level of commitment Alfresco
o Option 1: We can contribute the extensions to Alfresco Forge for use by the Community. This can
be under any open source license.
o Option 2: We contribute it to Alfresco to be bundled with Alfresco. This will require us signing the
Alfresco contribution agreement.
NB Contributing to Alfresco core we can only use libraries / components with permissive open source licenses
such as BSD or Apache. Contribution of Aloha integration will not be possible if it released under GPL.
•
•
Validation process type of testing, data sets, users, scenarios
o Pick the top 2 - 3 use cases as voted by the community and implement them in Alfresco.
o Agree standard data sets with the community for testing across the different CMSs.
o Create test plan of expected outcomes and get it peer reviewed / signed off by the community
Online demo with public access
o This should be possible to host this on an Amazon EC2 instance for public access.
5.2.3 SourceSense
Sourcesense wants to integrate FISE enhancement engine services inside both Atlassian Confluence Enterprise
Collaboration and Wiki Software and Alfresco Open Source Enterprise Content Management System.
© IKS Consortium
2013
34 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
The main focuses are towards the autotagging and entity extraction capabilities that would be very useful for
enriching platforms' contents.
Use-Case
UC1 - Confluence
•
•
•
•
•
•
User writes down a page or blogpost on the System and click the Save button
the System (after default operations) queries FISE engine sending content text
FISE answers to the System sending back entities and tags suggestions extracted from document text
the System puts tags suggestions as tags inside the page to be created
the System gets extracted entities saving them along with the page and then highlights (HTML enrichment: emphasize, linking, etc) the corresponding words inside the page or blogpost text
the System shows the enriched page
UC2 - Alfresco
•
•
•
•
•
the User creates a content inside the System
the System extract text from the content
the System queries FISE with the given text
FISE sends to the System the tag suggestions and entities extracted from the content text
the System decorates the content with the extracted tags and entities as additional metadata
Possible further enhancement: the extracted Entities could be aggregated in Entity-spaces so that a user could
navigate, for instance, the Places space and filter documents by entity instances (e.g.: City of Rome).
The aggregation could use associations in Alfresco maintaining the same relationship structure returned by FISE.
Validation
Confluence - Community driven
The validation phase for the Confluence/FISE integration will occur at first internally on our Confluence internal
instance which has lots of requests per day and subsequently on
our http://opensource.sourcesense.com/confluence .
Alfresco
The validation phase for Alfresco/FISE integration will occur internally on an Alfresco instance prepared for this
scope.
Performance
Enrichment of contents is going to be done synchronously at the time of writing since FISE services aren't asynchronous yet.
Once and when this is possible then data enrichment could be triggered on events asynchronously (periodically
in some cases) without affecting performances and user experience.
The terms of the contract are:
• Start of the contract 1st September 2010
• IKS component for validation is the FISE
• Demo system available 1st December 2010
• Validation interview in December 2010
• End of contract 31st December 2010
• Total remuneration for this contract is 6000 Euro, excluding VAT.
Visibility
© IKS Consortium
2013
35 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
With our opensource.sourcesense.com Confluence instance we could get significant visibility of automatic
resource enrichment with FISE.
As far as both Alfresco and Atlassian are concerned we are planning a series of joint events in all our offices
(London, Amsterdam, Milan and Rome) in H2 2010 during which, among other things, we will present "cool
and upcoming" integrations and FISE would be one of the few presented.
We will also publish and support the Atlassian integration on the Atlassian Plugin Exchange http://plugins.atlassian.com/ and work with Atlassian to publish a blog post on their official news
blog http://blogs.atlassian.com/news/ to promote FISE
Public Demo
A real use case of the Confluence/FISE integration that anyone can run will be available
on http://opensource.sourcesense.com
5.2.4 Punkt.netServices GmbH
punkt. netServices GmbH as Drupal Open Source CMS Integrator would like to implement the FISE semantic engine for automated tagging purposes. The objective is to provide Tag Recommendations for the editors on
the one hand as well as to provide rich Tags and Meta Data per content node / content item on the other hand.
Use-Case
Use Case: FISE engine for Tag Recommendations in Drupal CMS
1) A editor creates a new content item (or edits an existing) one (= content node in Drupal) inside of the CMS
2) As a next step the editor clicks a button for 'Tag Recommendations' embedded in the editor's view of Drupal
3) A for this use case implemented (Drupal) Wrapper will take the content of this node (content item of the
editor) and hands it over to the FISE semantic engine
4) FISE semantic engine will extract the relevant terms & phrases of this content item
5) FISE engine gives relevant phrases back to the Drupal system
6) This automatic generated tags will be shown in the 'tag area' of the Drupal content node in editors mode
7) The editor is able to choose from the given tags (select and un-select)
8) This content node is enriched with automatic generated tags and can be saved
9) The Drupal system shows the node tags in the form of a tag cloud in the public view of the node (front end
view)
10) The editor team saves time to type in tags per content node again and again
Possible expansion: the tags can be embedded as RDFa into the public HTML view of the content node (to discuss)
Validation
punkt. netServices re-builds it existing website (www.punkt.at) at the moment using Drupal Open Source CMS we are willing to implement the given use case into a part of our new company website (provided that the FISE
engine gives required output) as well as we can offer to create a screen cast of the editors view and show this in a
weblog and/or website article about the IKS project (and punkt.l netServices being an early adopter).
Performance
The FISE engine should be able to cover the Drupal requests live and in time - so we do not see performance
issues here at the moment - should the FISE semantic engine be not able to manage several Drupal requests from
a system that is managed by a editor team - enhancements on the side of FISE could be made. But the service on
hand is planned to work on time to give the editor / user the possibility to interact with the tag recommendation
service.
Planned Tasks
Set Up of FISE semantic engine in a development environment of punkt. netServices
© IKS Consortium
2013
36 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Implementation of a Drupal Wrapper for the FISE engine
Implementation of the above given use case
tests (performance, scalability, stability)
Provide output as demo & screen cast
Online Demo
See above & below
Visibility
As mentioned above we would like to implement the use case in a part of our new punkt. netServices website
that will be based on Drupal - furthermore we can offer to provide a screen cast of the editors view of the tag
recommendation service as well as we will show it to our customers if the service works well & is interesting for
them. Furthermore we can show the new Drupal service using FISE on several Drupal events we are participating in the future (as local & national Drupal meetings or a DrupalCon (US and/or Europe) to give the Drupal
community a glue of what the IKS module can provide for Drupal OS Content Management System.
Performance of Contract
•
•
•
•
•
•
Start of contract 1st September 2010
IKS component for validation is the FISE
Demo system available 1st of February 2011
Validation interview in February 2011
End of Contract 28th of February 2011
Total remuneration for this contract is 6000 Euro.
5.2.5 Evo42 Communications Ltd
As discussed at the IKS Early Adopter Workshop in Salzburg evo42 communications Ltd. as Drupal CMS
Integrator would like to give a brief overview about the “IKS for Drupal Module”.
The IKS Project consortium presented the first alpha version of the “Integrated Knowledge Stack” components
to bring semantic technologies to content management systems. With FISE, a RESTful engine that can enhance
textual content, we will develop a module for Drupal 7 which helps editors to add annotations which are suggested via FISE to their content.
Background information about Drupal 7 and RDF/RDFa:
• Drupal 7 and RDF (DrupalCon San Francisco 2010
• RDFa in Drupal 7
Objectives / Visibility
The “IKS for Drupal Module” aims to deliver as much outcome as possible from the EU funded open source
IKS project to the Drupal community and provide the IKS team with feedback, bug fixes and/or contributed
code. The module and information for integration will be provided on the newly created website "IKSforDrupal.net":
•
•
•
•
a live demonstration of the Drupal 7 modules (FISE, semantic editor)
a easy to follow installation and configuration guide for the IKS for Drupal Module – all code is open
source. Information and documentation is provided with creative commons licence.
a basic Drupal installation profile for easy evaluation and custom set-ups -- comparable
to OpenPublish
free API access to a up-to-date FISE Server installation for Drupal adopters/developer (optional)
Benefits
Hundreds of thousands of people and organizations are using Drupal to power an endless variety of web sites.
With Drupal 7 a lot of web properties became semantic aka. open web enabled. With RDF in the core of Drupal
and RDFa output by default thousands of websites start publishing their data to the open web. It's a big chance
© IKS Consortium
2013
37 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
for the IKS project to reach a huge user group and provide help for SME to benefit from the leading edge of
innovation in knowledge technologies.
Use Case
•
•
•
•
•
•
An editor creates a new or edits an existing document.
The content is sent to FISE via manual action (clicking a "get annotations button") or after writing some
text (triggered by time or character count)
The FISE engine analyses the content and returns related terms / concepts to the Drupal module
Depending if there is a Semantic Editor available or not the content in Drupal will be annotated in the
WYSIWYG editor or only added to the "Drupal taxonomy object" of the content node (the Drupal
Hook System will be used for this checks)
The user is able to discard tags which he thinks are not appropriate or add existing annotations which
are available in the system
The chosen annotations are available as RDFa information in the public HTML view of the content
page
Validation
•
•
•
Interested users can try the online demo at the created IKSforDrupal website -- it is possible to try it
with or without a Semantic Editor.
Users can download and install a Drupal version with the integrated modules
A screen cast is available so users can see what are the benefits of the IKS integration
Performance
The FISE engine should be able to return results to the user live and in an appropriate time. We will test the
performance with different amounts of text.
Planned Tasks
•
•
•
•
•
•
•
•
Installation of the FISE engine
Development of a Drupal 7 module to connect to FISE and RICK, and to the Drupal taxonomy Module
Development of a Drupal 7 module for storing the annotations (interaction with a Semantic Editor)
Setup of the project website
Setup of a github project for all code
Performance and Scalability tests
Documentation and information for integration
Setup of an online demo and screencast
Online Demo
An online demo will be available on the project website http://IKSforDrupal.net
Performance of Contract
•
•
•
•
•
•
•
The terms of the contract are:
Start of contract 30th December 2010
IKS component for validation is: FISE, RICK
Demo system available 30th January 2010
Validation interview in February 2011
End of Contract 28th February 2011
Total remuneration for this contract is 7.000 Euro.
5.2.6 Beorn Technologies
Introduction
© IKS Consortium
2013
38 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
The document consists of a presentation of the company and its context, a description of the project and
a draft proposal.
Beorn Technologies
Beorn Technologies is a French company based in Toulouse and founded in 2007. We provide portal
and content management solutions for our customers (public organisations and private companies). The
products are mainly used in the context of intranet and/or internet portals. Our main expertise focuses
on custom services for Liferay portal and CMS and Alfresco CMS. As a service provider we also extend these products with web accessibility (html structure, user friendliness and content), mobile applications (under Android) and e-services (complex and secure forms for public organisations).
As service providers and integrators of open-source solutions we engage in strong community involvement. This gives us a respected visibility within communities and with vendors. We believe in
research and have a strong R&D policy. We dedicate about 20% of our time to R&D.
We now plan on integrating semantic web capabilities to our products in order to enhance accessibility
in a broader sense.
Our customers include:
• City of Toulouse: www.toulouse.fr an internet portal and CMS running a customised Liferay portal
• Novela festival (Toulouse science fair): www.lanovela.fr an internet/extranet portal running
a Liferay portal
• EthnicFlow: www.soukaffaires.ma a classifieds platform running a Liferay portal
• Council of Corse du Sud (French local government): associations.cg-corsedusud.fr a public funding request e-service.
Context
As we focus on content management we are planning to improve our products with regards
to accessibility and information adaptation.
Web accessibility is primarily understood as providing nice formatted and disabled people friendliness.
We advocate for a broader meaning that also include content semantics. The idea is to provide a technically – i.e. structurally – sound product along with ways to understand the contents in a ”show more”
fashion. Hence the ability to provide related internal and/or external contents/links/resources is key to
the understanding.
Driving further on the road leads to information adaptation. The content itself has to be automatically
prepared for the end user, based on existing content. The goal is to automatically provide simplified or
enhanced content upon user request or user navigation profiling. E.g. a scientist may want to see detailed contents with further readings in their speciality whereas a beotian will prefer having simplified,
shortened contents just to understand what it is talked about.
Project
In the context of enhanced information we have identified some semantic web engines among which
FISE is a good candidate. We plan to integrate FISE with Liferay portal to provide the tools necessary
for implementing content improvement.
Goal
The goal is to integrate FISE with Liferay portal. The intended fallouts are:
• a tag-suggestion enhanced editor
• automated annotation of keywords
• semantic navigation
• semantically relevant resource list display
Use cases
© IKS Consortium
2013
39 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
•
•
•
•
•
•
•
Enhanced content editor: content editors may choose meaningful tags from a suggestion list.
Automated annotation: end users may be provided with tool tip-like hover information
on specialised vocabulary.
Ontology enrichment: new contents may be analysed and may enrich the ontology.
Semantic navigation: end users may be able to scroll through content-related semantic data
Statically suggested resources: end users may refer to a resource/link/content navigation block
whose content is related to the main content; references may be internal or external.
Dynamically
suggested
resources:
end
users
may
refer
to
a
profileadapted resource/link/content navigation block whose content is related to the main content; references may be internal or external.
Content adaptation: end users may view an automatically adapted – augmented or simplified –
version of the content; adaptation may emerge from explicit request – i.e. button click – or
from navigation profile analysis.
Draft proposal
The planned tasks are:
•
•
•
•
develop a Liferay plugin as a FISE adapter (choice will be made between kernel extension/ modification and autonomous portlet according to practicability and community/vendor)
tackle use cases 1 and 2 and evaluate model modification breadth
tackle use case 3 and find a suitable 2-way communication pattern between Liferay and FISE
tackle use cases 4 and 5 and enhance previous plugins (time & resources permitting)
Use cases 6 and 7 relate to another field of research that may be addressed as two different projects: linguistics & semantics fundamental research on content adaptation and applied research on advanced web
profiling. As a result these cases will not be included from the beginning.
IKS Team Feedback
•
•
•
Please specify, what you mean with "ontology enrichment"?
Which editor do you want to extend with the tagging capabilities?
We are interested in using Apache Stanbol results (e.g. extracted people or locations) to support user interactions during editing and consuming content (e.g. providing a specific
view/hover for a person recognized within the text)
o http://wiki.iks-project.eu/index.php/SearchSuggestInteraction or
o http://wiki.iks-project.eu/index.php/TailoredActivitiesInteraction
5.2.7 Lunaria
Early Adoption and Validation Proposal
Lunaria provides marketing and design services for a range of clients in both the public and private sectors. Part
of this involves the creation and maintenance of websites.
Lunaria (through its parent company Verinote) deploys and supports the server environment for web-based projects. Typically these would be on LAMP stacks with WHM used to manage the services.
In areas of Social Marketing increasingly clients are looking for solutions which develop the use of the semantic
web: typically in areas of social media, collaborative working and knowledge acquisition within a dynamicCMS.
User engagement is critical in social marketing or social networking, as is allowing related content to be collected and displayed.
Contextual semantic navigation is very powerful for users with memory dysfunction, or for associative learning
and the collaborative acquisition of knowledge.
© IKS Consortium
2013
40 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Use Case
§
a/ Creation of an on-line educational/collaboration tool using the open source CMS Drupal at its core
integrated with Apache Stanbol. The core functionality of the system will be open to adaptation to specific needs of possible end users ranging from education (early learning, youth community projects or
simple social networking) or as an aid to institutional organizations dealing with learning difficulties or
other progressive disabilities.
§
b/ The core of the system will be based on related terms and images in relation to the user, group of users, time and context. Using the system will prompt action or deliberation on the part of the user or
group of users.
§
c/ The content is represented through visual prompts (from images) with the tagging defining the collection of stories as related content.
§
d/ Pages can be readily viewed, reviewed, edited, tags suggested and added.
§
e/ This creates a virtuous cycle for enhancing the contextual semantic navigation.
Validation
First part would be to evaluate the deployment of components, and their practical use. For example do they
work, are they useful, do they add value etc..
We are currently working with several clients who have a level of awareness of the semantic web.
One is based in education and community and is directed through the local Government. We would present an
example of the semantic web working, through this organisation, for feedback from non-technical, professionals
via a structured questionnaire.
The questionnaire would be presented to establish differing levels of awareness and expectations of the Semantic Web and, would seek to identify if the semantic web was better understood having been demonstrated, and in
what areas would people see the benefits applied, and what these might be.
Performance
§
Start of contract: 10th October 2011
§
Selected components are Apache Stanbol + Vie
§
Application will be done by Verinote Limited
§
Demo available: 15 December 2011
§
Demo example will be available till 10th July 2012
§
End of contract 10th January 2012
§
Total remuneration for this contract is 7000 Euro.
Planned tasks
Integration of Stanbol on a LAMP server with Drupal running as CMS.
Creation of a working model, with a presentational layer that meets the expectations of a valid user experience.
Based on a Content Type which allows single image upload, text, tagging and key-date. Outputs would be single
pages and contextual semantic navigation.
Online Demo
www.verinote.org
Visibility
Presentation to political and financial decision makers. Exposure to potential users.
© IKS Consortium
2013
41 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
5.2.8 Acuity Unlimited
Early Adoption and Validation Proposal
Acuity Unlimited as Fedora Commons open source integrator, would like to integrate KReS services to assist
content repository managers acquire and manage semantic metadata about their contents.
Our initial objective is to enable the system to perform semantic computations to aid the effectiveness of search
and discovery services. Specifically, we aim to integrate an established thesaurus with the system’s resource
index and perform computations to enable the use of contextualised faceted semantic search.
Eventually, and beyond the scope of the Early Adopter’s project, a full integration would support the needs of
content cataloguers as well as end users, and provide facilities for lifting from XML schemes and ontology
alignment with other descriptive metadata about content objects, for full semantic interoperability. The first stage
however needs to concentrate on providing a solid foundation for semantic support within Fedora, that is, allowing the use of KReS services over multiple Fedora digital content objects whilst at the same time maintaining
compatibility with facilities relying on Fedora’s existing RDF-based Resource Index and its schema. We will
also endeavour to configure Fedora to access and test the underlying KReS ontology management and scoping
mechanisms.
Use-Case
UC1 - Content Repository Owner
§
Content repository owner can associate nodes of the KReS ontology network to specific repository contents
[via Fedora content model architecture]
§
With the aid of ontology design patterns (ODPs), to allow repository owners to specify alignments between
semantic representations of metadata schema, and therefore make available consistent semantic categories
from differing origins across repository contents.
§
Via KReS scopes, to enable content repository owners to specify boundaries as to which semantic representations apply to which repository contents.
§
To enable content repository owners to specify and run inference procedures over semantic information to
derive new information about contents, and to optionally persist the results back to the repository’s standard
curation mechanisms (identification, index and access mechanisms).
§
Via the KReS session interface and scopes, to provide a configuration to support more specific, specialised
queries, eg ad-hoc semantically-backed faceted browse.
UC2 - End User/Content Search
(Note: there is no standardised user-facing search interface suitable for semantic search out of the box for Fedora
– therefore an end-user interface will be constructed for demonstration purposes to illustrate the correct functioning of the underlying integration; the implementation of the front-end itself will not be the focus).
§
User chooses to search by semantic category - this could potentially be a faceted browse interface allowing
contents to be explored according to constraints specified by the user in a simple-to-use way.
§
Semantic categories are sourced from the current scopes in KReS
§
The user chooses to drill-down using a semantic (SKOS) thesaurus categorisation to constrain search
results.
© IKS Consortium
2013
42 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
§
Constraints are specified using facets drawn from available metadata to further narrow search results to
specific contents.
Challenges
§
Fedora is a framework for content and services. It does not have a user interface out-of-the-box. End-user
demonstrations will need to be bespoke and fairly simple if performed as part of the project; adaptations of
external user interfaces developed will be looked at for demonstration purposes however during the course
of the project.
§
Fedora currently indexes its contents using a single-graph Resource Index. Each triple in this graph does not
currently specify the content object(s) for which the triple applies.
§
The possibility of wrapping KReS as a FISE module has been raised. This may be potentially evaluated as a
means to provide future robustness and interoperability of the overall integrated architecture.
§
Fedora has two patterns for direct integration with its content acquisition (ingest) procedures. The most
appropriate method will be recommended during the course of the project.
Potential Further Enhancements
Here is a list of enhancements beyond the initial scope of development for this Early Adopter’s proposal:
§
Tool support for lifting from existing XML thesauri into SKOS and associating with Fedora contents (for
discovery)
§
Tool support for lifting from existing XML metadata descriptions and associating with Fedora contents
§
Support for the content cataloguer to choose to associate the content with semantic categories from a list
within pre-determined semantic scopes
§
Build the facility to allow content cataloguers to specify their own “local” semantic categories, using SKOS
or OWL, as enhancements or mapped to existing ontologies.
§
Link discovery - the SILK framework could be wrapped by KReS to enable links to be discovered between
repository contents and metadata, and added to the ontology network to grow the number of ontologies
available to the repository owner.
Validation
KReS Team
§
KReS is currently in alpha. The team has offered assistance to the project as it progresses to help ensure a
successful outcome, and it is anticipated the real-world application of KReS will aid KReS development as
it proceeds. We will remain in close discussion throughout the project to ensure maximal outputs for both
development teams working together.
Community-driven
§
Acuity Unlimited has for some time been engaged in applications of Fedora in a semantic web context. We
have begun to engage with key members of the Fedora community with a stake in the deep integration of
semantic web capabilities demonstrated by this proposal.
§
Steve Bayliss is a committer and recent Release Manager for Fedora. He will ensure the committers are
aware of the project and its potential impact, and seek future collaborations and applications of the Fedora/KReS integrations where appropriate.
© IKS Consortium
2013
43 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Client-driven
§
Acuity Unlimited has been in discussion with specific clients regarding the KReS integration. The project
will be developed and tested against appropriate digital material from within a content repository sourced
from one of our clients. The client will be consulted at points during the project in order to validate the design and outcomes. The most recent version of Fedora will be used for development, integration and validation purposes.
The validation phase for the Fedora/KReS integration will initially be internally on our VMWare servers, then
subsequently deployed to a public-facing Amazon EC2 instance (or VPS instance) to a wider community for
evaluation and feedback.
Performance
Performance constraints around the use of KReS are in general yet to be evaluated. Findings will be reported as
part of the project.
There are challenges in “writing into” Fedora’s current RDF database for persistence of Fedora contents with
RDF, eg for curation of lifted or inference results from KReS. Fedora does not currently include its content object identifiers within its single “Resource Index” RDF graph. Experiments to address this limitation have indicated there are performance issues when using Fedora’s natively bundled RDF database, Mulgara, to specify a
named graph per content object. Opportunities for enhancing such performance bottlenecks will be explored and
recommendations to the Fedora and Mulgara projects made as appropriate.
Planned Tasks
Step 0: Project inception: KReS familiarisation - technical setup, familiarisation with the KReS API, KReS
component maturity assessment with KReS developers and confirm roadmap with KReS team.
Step 1: Development and stage environment: Set up running KReS instance. Set up Fedora instance populated
with client-supplied content and metadata records in XML. Verify KReS instance is accessible from Fedora. [1]
Step 2: Configure core KReS scopes within the ONM: KreS will be configured to load and make available Fedora's Resource Index ontology at runtime within the core space of the KReS ONM. SKOS (the base formalism
used to capture and express the thesaurus/controlled vocabulary) will similarly be configured and made available. The KReS instance will be restarted after configuration.
Step 3: Configure custom KReS scopes within the ONM: Custom metadata schema expressed in OWL for the
objects specific to this Fedora repository instance will be managed and made available during runtime within the
mutable and shared custom space feature of the ONM, by calling the ScopeRegistry interface. Key concepts
from the specific SKOS-based thesaurus will be similarly loaded and accessed, in a way that therefore allows
runtime modification if necessary.
Step 4: Ontology persistence: Ontologies will be stored on the KReS side using the OntologyStorage interface.
Step 5: Alignment of ontologies: A reasoning pattern will be implemented to express alignment of the ontologies
referred to above. ODPs will be the preferred practice to model these alignments. The recipe will be added using
the API for the R&I. A reengineering scope in the custom space will be set up via the SEMION Manager's API
to provide access to the results of integration and alignments of these ontologies. The SEMION Refactorer API
will be called to apply the ontology alignment recipe and thereby produce a coherent set of semantic relations in
the ONM custom scope derived from the different ontology sources.
© IKS Consortium
2013
44 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Step 6: Integration with Fedora object relationships: Calls will be made on the ScopeRegistry to set up a custom
scope to hold RDF data pertaining to repository content objects. This data may be significant in size [2]. Therefore the possibility of integration with Clerezza as back-end storage interface for KReS will also be evaluated for
its feasibility within the scope of this development [3]. Fedora Java code will be extended to add the repository's
object-specific RDF data to a custom scope (created with the ONM via the ScopeRegistry API) to hold this instance data.
Step 7: Per-user inferences: Satisfying the per-user discovery use case will depend on satisfying inferences based
on terms found from the thesaurus's controlled vocabulary at SKOS concept (eg artist) and instance level (eg a
specific person). Further constraints might be added by the user deriving from technical object-specific metadata,
eg to specify only certain size of image. At each point after specifying these constraints, a session scope negotiated with the ONM scope representing the fully-reengineered session-based data set will be established, (therefore available for later drill-down by that user), using the SEMION Manager API, and recipe rules corresponding
to the ontology alignment inferences will be applied by calling the SEMION reengineering API. This will yield
the fully populated, “reengineered”, instance data graph applicable to the user's specified search constraints, ie
constituting search results and aiding guided discovery.
If time permits, we will endeavour to also undertake the following steps to assist forward-looking scenarios:
Step 8: Investigate and document the design options for Fedora services to allow the repository manager to selectively filter which objects will contribute to KReS custom scope, and stub prototypes as necessary
Step 9: Document a means to manage lifting of XML content object metadata using the two-step SEMION reengineering process.
[1] Fedora’s reference implementation is with Tomcat. Whilst interest has been shown in deployment of Fedora
in OSGi, we cannot make assumptions at this stage regarding the preferred default. The JavaAPI has been recommended as preferable due to its significantly better performance and ease of use, but using the RESTful API
may be preferred as it will not cause a change to Fedora’s deployment requirements. Therefore potential deployments into GlassFish or a suitable OSGi web extender will be investigated, alongside use of the KReS
RESTful API within a more loosely integrated Tomcat and Felix setup.
[2] https://wiki.duraspace.org/display/FCR30/Triples+in+the+Resource+Index
[3] Potential use of Clerezza backend API has been discussed in this context. Fedora is bundled with Mulgara,
seehttps://wiki.duraspace.org/display/FCR30/Resource+Index. A Mulgara implementation has been developed
for Clerezza, understood to be a possible persistent storage API for KreS.
Tasks will be carried out beginning April 1 2011 and completing by June 30 2011.
Performance of Contract
The terms of the contract are:
Start of contract 1st April 2011
IKS component for validation is KReS
Demo preview available 10th June 2011
Demo system available 30th June 2011
Validation interview in July 2011
End of Contract 31st July 2011
Total remuneration for this contract is 6000 Euro.
Online Demo
© IKS Consortium
2013
45 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
§
The validation phase for the Fedora/KReS integration will initially be internally on our VMWare servers,
then subsequently deployed to a public-facing running instance, accessible on the web to a wider community
for evaluation and feedback.
§
The work will be presented at an IKS workshop in July 2011.
Visibility
§
Steve Bayliss is a committer to the Fedora Commons and recent Release Manager. The work will made
visible at committer level and key community members made aware of the potential of the work.
§
Acuity Unlimited has visibility and influence in the broader marketplace as a services company offering
both Fedora-specific expertise and semantic web expertise.
§
Results will be made visible on the Fedora Commons wiki.
§
Results will be disseminated in presentations or otherwise made visible at events influential to the Fedora
community, such as the Fedora national and European user groups, and OR2011.
§
Fedora is a recognised leading technology in the institutional repository and digital libraries sectors. Advances in Fedora’s capabilities have tended to have an impact on the communities the technologies serve, so
that we would anticipate the semantic capabilities offered by KReS to become visible within the sector.
§
The work will be presented at an IKS workshop in early summer of 2011.
5.2.9 Interact
Interact Egypt is an Internet Company established in Cairo, Egypt focusing on content management and on-line
marketing solutions working for both the Italian and the Egyptian market. We plan to integrate FISE and KReS
into WordPress (WP), a leading Open Source CMS we use with our costumers. The integration will be done
using WP Plugin architecture: a WP Plugin is a program written in the PHP scripting language, that adds a specific set of features or services to WP, which can be seamlessly integrated with the costumer’s website using
access points and methods provided by the WordPress Plugin Application Program Interface (API).
The goal for the integration with IKS is to provide to our WP users (and to the Wordpress community) content
analysis and relevant metadata embedding using RDFa (Microdata and Microformats will also be considered) for
better content findability. More specifically, we will use FISE for semantic lifting of text, and KReS for refactoring data according to specific vocabularies.
Use-Case
The costumer (the new media department of an Italian energy utility company - we’ll name it “Ugo” for the sole
porpose of this document) access WP’s WYSIWYG editor and finds a button “SemW3 Analysis”, after adding
some textual content in italian Ugo clicks the button and the WP Plugin fetches from FISE a list of entities. The
entities are shown into a separate SemW3 frame (available in the content editor window); Ugo selects entities/tags that he finds more relevant for the purpose of his article and selects the proper type and automatically
RDFa (Microdata and Microformats are also valid alternatives for the scope of this project) are added to the
published article. Types are suggested by the Plugin and compatible with Google Rich snippets standards and
might include the following:
§
Business and organization
§
Events
§
People
Products For future implementation an online editor to let Ugo manually define the following types shall be
planned:
© IKS Consortium
2013
46 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
§
Breadcrumbs
§
Events
§
Reviews
§
Review Ratings
§
Video
The online editor is will not be part of the first release of the Plugin and will not be validated.
Flow
The WordPress CMS stores its data in a legacy database system. The database is a plain content representation
(mostly a body).
By using WordPress API, the plug-in loads the post(s) and/or page(s) contents.
A KReS instance will be installed alongside the CMS. From the CMS management interface, the Content Manager will be able to activate the plug-in.
The plug-in passes the legacy data to Stanbol RESTful services in this sequence:
§
enhancement of unstructured text via the /engines method, which outputs structured data (ex. RDF),
§
the RDF is passed to the KReS ONM along with the ontology specifications [1] (/kres/ontology),
§
a KReS session will be started in order to perform the re-engineering (/kres/session),
§
the KReS re-engineering process will be configured by passing the rules (/kres/rule) thus creating the recipe
(/kres/recipe),
§
the re-engineering process will be executed (/kres/refactor),
§
the plug-in will store the output in WordPress, providing enhanced text to WordPress contents.
[1] we'll look for predefined patterns (http://ontologydesignpatterns.org/wiki/Main_Page)
As an additional operation, the User may be able to complement the original pattern with additional ontologies
(from scope to space) in order to provide context-specific definitions. This process shall include a Content Manager interface that allows to "add, modify and remove ontologies within a given scope", as specified
in http://stlab.istc.cnr.it/documents/KReS/KReS-Alpha/node12.html(/kres/ontology method).
Validation
Online Demo
The implementation will be available to a private WP blog published on http://semw3.indemo.it to the costumer.
SEMW3 WordPress plugin
The WP plugin will be available as opensource under the GPL2 license to the WP community.
Performance
Performance will be measured based on concurrent editors requests (2, 5 and 10 editors) acting on different posts
with various content to be analyzed. Performace will be recorded using Google Speed Tracer and the tests will
be performed in a test plant (all components running in the same network).
Planned Tasks
© IKS Consortium
2013
47 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
WP1
•
•
design the WP Plugin (SemW3)
evaluate FISE and plan the integration with the Plugin
WP2
•
•
implement SemW3 using WP Plugin Application Program Interface (API).
integrate FISE and KReS with SemW3
WP3
•
write unit tests, build, deploy and packaging scripts for SemW3
WP4
•
•
•
write Plugin documentation
prepare any additional materials for the Plugin submission and promotion to the WP Plugin Directory
write Plugin usage manual for the end costumer
WP5
•
•
roll out SemW3 Plugin demo for the end costumer (on http://semw3.indemo.it)
roll out SemW3 Plugin on the WP Plugin Directory
Online Demo
http://semw3.indemo.it and a link to the Plugin in the WP Plugin Directory from http://egypt.interact.it.
Visibility
The plugin will be presented to our end costumer and all the team working on WordPress initiatives on behalf of
the end costumer.
Public visibility of the early adoption will be provided by the following actions: • Newsletter to our costumer
base • Dedicated web page on our website • Publishing of the Plugin on http://wordpress.org/extend/plugins/ •
Submission to wp-plugins.ne and wp-plugins.org
Performance of Contract
The terms of the contract are:
§
Contract in the name of the Interact European entity
§
Start of contract 1st April 2011
§
Online public demo for everyone to test run
§
Online demo available in June 2011 (IKS early adopter workshop)
§
Participation to the early adopter workshop (July, Paris)
§
Validation interview in July
© IKS Consortium
2013
48 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
§
End of Contract 31st July 2011
§
Total remuneration: 6.000 Euro
5.2.10
Drunomics
Use-Case
The main goal of this proposal is to build an Stanbol indexer for Drupal structured data, which will enable the
following stories:
• S05: Assistance with Semantic Tagging
• S19: Enriching content with information retrieved from internal sources
• S21: Entity extractor support in editors
• S23 / S29: Enriching content with information retrieved from external sources
• S32: Autolink company names
Although most likely beyond the timeline of this proposal, the following stories should be achievable once the
goals of this proposal have been implemented.
• S01: Search and Disambiguation in Docs
• S06: Context-aware Content Delivery
• S07: Knowledge-based Content Adaptation
• S09: Similarity based document search
• S17: Domain ontology navigator
• S24: Multi-device publishing
Validation
•
•
We will provide demos so that members of the Drupal community can try the tools described in this
proposal and give feedback on the quality and performance.
We will provide screencasts so that users can easily see how to set up things and what the tools give
them.
Performance
•
•
•
•
•
•
Start of contract: September 2012
Selected components: VIE, Apache Stanbol Enhancement Engines, Entity Hub and EntityHub persistent storage.
Integration will be done by: Wolfgang Ziegler, Drunomics
Demo system will be available: on openspring.net (possibly also on viejs.org if the site owners agree)
End of contract: 30 November 2012
Total remuneration for this contract is: 6500
Planned Tasks
Drunomics will build a Stanbol indexer for Drupal. Once Drupal’s structured data is indexed by Stanbol, it will
become available to the rest of the IKS software stack to perform content enhancement tasks such as finding
related content, suggesting relations as content is being authored, and improved search.
The Stanbol indexer will be built on top of the existing Search API module available on drupal.org. Drupal entities will be converted to RDF and sent to Stanbol for indexing. The EntityHub will be used to store relations
between Drupal entities, which can later be queried by the end user. Results are returned in JSON-LD and can be
used by the VIE library for integration in the in-place editor (Aloha or Hallo) for content enhancement.
The entire code will be released under the GPL2 (possibly dual licensed MIT or BSD open source license if
required by IKS). Code will be hosted on drupal.org and github.com.
Online Demo
The application will be available on openspring.net. For demo purposes administrative access can be granted on
request.
Visibility
© IKS Consortium
2013
49 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Drupal is a well known and popular Content Management System running personal blogs as well as corporate,
political and government sites such as whitehouse.gov. Users of Drupal include The Economist, Ubuntu, Sony,
MTY, Warner Music Group, etc. Drupal benefits from an active community constantly improving the quality of
the software and adding new features as web technologies evolve. The work carried out in this project will help
shape the next version of Drupal 8.
5.2.11
Logicells
Introduction
This proposal will be based on our evaluation (and later contribution) to Stanbol, and on integrating VIE into the
DotNet Nuke CMS. This CMS is an Open Source project based on .Net technologies.
Proposal
We are interested in the context of this proposal in the project of coupling DNN with IKS : • enriching the CMS
editing capabilities through VIE
• interacting with Stanbol through a REST architecture
• use Open NLP on french language
• possibly add modules on to the enhancement engine able to idiomatically find some categories based on
text mining techniques like Bayesian networks.
At a final stage, we intend to associate documents with a high-level semantic description of their content. This
will involve automatic extraction of meaning in a knowledge representation language, rdf as an example. So, in
complement, we will write advanced openNLP models and include them in Stanbol. But, as writing such models
require business knowledge and could be time expensive it should be a collective work with other partner using
french language.
Use case
• Briefing notes routing
On a regular basis, I gather potentially valuable information in a professional environment that can have a collective interest for a group of individuals (here a professional association). So, each time I get some valuable information for the group, I just need to send a briefing note (short notes easy and fast to write used in economic
intelligence) to a mailing service or if I have more time to spend to a web interface that allows me to add manually some semantic meta-data to my briefing note. All other members of this group are supposed to do the same.
This service should allow peoples, from the group of individuals, to indicate that they are interested in some
categories of information, using semantic properties for this. Then when a piece of information classified in one
of those categories is added on the site, subscribers get a notification. Regularly, new briefing notes will be added. As each one will be semantically annotated, we would expect at some moment to have a big linked database
that could be used to find briefing notes using the annotations they are related to. I will then be able to query this
database to interpret trends around 'hot' subjects of interest for myself and/or some other members of the group.
Validation
•
•
It is easy to add a brief note and to register to some categories of notes to be notified
Building a request for some kind of note should be easy and the answer should be satisfying to the user
Performance
The terms of the contract are :
• Start of the contract, October 2012
• IKS components for validation is the DNN/VIE integration and the DNN/FISE REST interactions
• Demo system available 20 November 2012
• Validation interview in 30 November 2012
• End of contract 30 November
• Total remuneration of this contract is 6500 Euro
Visibility
We will install STANBOL online on our server in order to interact with DNN portals. A prototype of the brief
note application will be available to be used publicly on the internet. People will be able to create a group and to
© IKS Consortium
2013
50 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
add members to this group. Then inside the group they will be able to publish notes and get notifications. We
will make public to the community any progress on the use of Open NLP in French language.
5.3 CMS Tool Providers
5.3.1 SalsaDev
This proposal has for objective the integration of salsaDev's features (IA & content extension) into FISE and
the deployment of integration for our at least one of salsadev's client.
Goal
To offer salsaDev and current FISE feature for generic user-cases in our product. salsaDev will both extend its
current enhancement engines to meet current product functionality and develop new query engines in joint collaboration with the FISE development team to satisfy its clients' Information Access needs.
Motivation
As an “Information Access” company, salsaDev is interested in participating to the IKS FISE integration project.
Our primary intent is to replicate the stack-ability and general plug-ability design of the content enhancement
engines for query engines to provide a transversal, easy and intuitive Information Access paradigm.
The FISE enhancement engines, as describe in Bertrand’s during the workshop, are considered as plugins. Each
engine is very simple and straight forward, implementing a common data-structure (ContentItem) and methods
(canEnhace and Enhance).
Despite their simplicity enhancement engines can prove to be very powerful when stacked together. Each engine
is specialized into a single enhancement, providing the modularity, lightweight and simplicity supporting the
FISE overall architecture approach. As Bertrand mentioned during the Early Adopters Workshop FISE currently
implements a naïve and simple stacking mechanism for content enhancement engines. It might prove useful to
let engines co-operate between each other in a iterative manner. Such co-operation assures the end-result to be
the best possible process for all enhancements.
It is the simplicity, ease and best of all bread mechanism that we would
like to see in the query engine as well.
Project
salsaDev will develop the project in partnership with one of its client (gaining access to publicly available content) and provide a public access to prototype.
To satisfy salsaDev's product deliveries we will have to work both with enhancement and query engines. Leveraging the content enhancement proposed by FISE while providing a consistent access to information without
circumventing FISE with query engines.
Use-case description
Use cases cover basic information life-cycle within our product:
• supply new content for indexing (enhancement engine)
• categorize content (Story #10 thru enhancement engine)
• get related content (Story #09 thru new query engine)
• query for related content (query engine)
User interface
© IKS Consortium
2013
51 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
The user interface will be based on current sandbox as for public project "EU_Research"
Implementation for enhancement engines
To supply process for the above use-cases salsaDev will extend current enhancement engines
Architecture / process
1)
2)
3)
4)
5)
front-end deals with document's input
front-end submits document to FISE's enhancement engine
FISE submits document to SD for indexing thru enhancement engine
FISE categorizes document thru SD's enhancement engine
front-end provides view & navigation of document
Planned tasks
1)
2)
3)
4)
Link document submission to FISE
Create indexing enhancement engine
Create categorizing enhancement engine
Integrate FISE process in prototype product
Implementation for query engines
As of right now the query engine only supports RDF querying. By constructing a similar architecture for information access than content enhancement one could be able to stack multiple query engines together. This seems
trivial when executing a RDF query, but might take all its sense with non-structured, full-text queries.
The goal is to have multiple query engines (RDF, NLP, Keyword, Sense-based) collaborating and participating
toward the information access and result-set construction. One could also think of integrating external search
engines as Query Engines.
For example here's how a typical "web-related-content-from-document" engine would work with salsaDev and
Google:
•
•
•
•
•
Document to ContentItem Conversion (might be done with FISE enhancement engine)
SalsaDev keyword extraction (might be done with FISE enhancement engine)
Google Query construction (including term disambiguation)
Google Result analysis (remove false positive given sense/content, part of query engine)
return relevant results
Issues / challenges
Stacking & federating several information access engines together raises a few issues. Ranging from the content/structure of the query to the merging of different sources:
• Not all information-access mechanism rely on the same “query” (kw, content, rdf, document,)
• Merging results (ranking) from different engines might be a real challenge
Development
To full-fill prototype specification salsaDev will collaborate with the FISE development team to build a streamlined design/upgrade of Query Engine to support:
• Common Query Entity (Equivalent to ContentItem)
• Map-Reduce type of engine collaboration (including ranking & heuristics)
• Reduce controller with advanced heuristics to merge results from engines.
Architecture / process
•
•
•
Get Information Access query
Evaluate Query and stack engines (canExecute?)
Execute each engine according to heuristics
© IKS Consortium
2013
52 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
•
•
•
Get all engine's result
Evaluate set and rank
Provide sorted set of result
Planned tasks
•
•
•
salsaDev & FISE development team to extend current Query Engine design
salsaDev implements Keyword & full-text Query Engine
salsaDev integrates query engine in FISE process
Licensing and demo access
The code will be licensed as part of IKS code
Demo will be public access
5.3.2 Object’Ive
Object’Ive is a Paris based information technology consulting company.
Beyond our information technology consulting activities (realisation of time & materials as well as fixed price
projects), our internal research activities lead us to develop specific solutions (mobile applications, intelligence
tools, CRM, code translator...)
During the past years, we developed our expertise in both fields of mobile technologies through the mastering of
the main mobile development platforms (iPhone, Android, Windows Mobile and BlackBerry) and knowledge
and content management technologies.
In this context, Object’Ive is currently developing the BlogoMatic tool that automatically generates web sites on
a defined topic.
Based on the Nuxeo CMS platform, BlogoMatic allows the user to automatically generate a web site, either
automatically by gathering contents via trend detection engines like Google Insights or manually by entering key
words in the system.
Many sources coming both from the Internet like Google News, YouTube, Amazon, RSS feeds, and so on and
from Intranet databases can be plugged into the system in order to collect the data in diverse formats that will
then be displayed in the generated web site.
The web site is composed of a general home page displaying some contents of each type of the chosen data (video, article, product...) and of specific pages organised by data type in order to display the contents separately.
As of today, our solution is operational with the connectors we developed for gathering information from various
Internet sources. However, by testing our system on different key words, we observed that, in many cases, the
collected information lacks relevance making the user search experience not optimal.
By adding semantic components to the BlogoMatic tool, we aim to sharply increase the relevance of the gathered
contents and thus, make our solution much more efficient from a user and business point of view. Moreover,
adding semantic components will allow making possible the interoperability of internal enterprise sources which
is a major issue in order to switch from a simple mass storage of raw data to the valuation and management of
the enterprise information asset in a smart and differentiated way.
Use-Case
BlogoMatic will integrates the IKS Stanbol and VIE components.
§
These integrations have the following goals:
§
Add semantic to the collected contents
© IKS Consortium
2013
53 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
§
Enhance their relevance
§
Make possible an automatic tagging and entity extraction
§
Be able to propose to the user relevant linked contents
§
Improve the user experience and research in the generated web site
By using the results rendered by the semantic engine under a triple store model, we will add functionalities that
will allow the extraction of new entities.
These entities will concern other ontologies that we will be brought to describe and then integrate as new indexes
in Apache Stanbol. The triple store model will then be analysed using SPARQL and JENA in order to extract
new entities concerning these new indexes
Through this, we will be able to associate the integration of Apache Stanbol to the following use cases:
§
Story 19: Enriching content with information retrieved from internal sources
§
Story 21: Entity extractor support in editors
§
Story 05: Assistance with Semantic Tagging
§
Story 27: Define custom facets for faceted browsing
Validation
The validation of the Apache Stanbol technology integration in BlogoMatic will be realised by the customers in
which premises we will integrate BlogoMatic.
Our customer will be asked to validate the relevance of the results obtained by the extraction process.
It has to be underlined that we might already have a potential lead to install our solution, first as a Proof of Content, in one of our customers’ IT environment.
Performance
§
start of contract: 1st January 2012
§
selected components are: Apache Stanbol
§
demo system will be available: 15 March 2012
§
end of contract: 31 March 2012
Planned Tasks
Our teams will develop a plug-in, “BMSemantic”, using the Apache Stanbol Engine and VIE, that will be integrated in our solution.
This plug-in will allow in a first step the broadcast of the articles gathered by BlogoMatic to the Apache Stanbol
Engine in order to retrieve the triple store model of the transmitted articles. The triple store model will then be
analysed by the plug-in to extract the requested entities.
In a second step, the plug-in will allow the use of the VIE component that will make it possible for the user to
generate tags.
Besides, we plan to develop VIE widgets using JQuery UI in order to offer to the user the abitility to :
§
validate the relevance enhancement of the information gathered
§
validate the tags
§
update the generated website
Stanbol will be integrated in the keyword research to allow the user to disambiguate his research before the website generation.
© IKS Consortium
2013
54 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Stanbol will also be used to automatically classify the gathered contents by topic basing on the extracted entities
and the inference system.
Online Demo
The online demo of BlogoMatic will be avaialble on a dedicated web page of our web site.
Visibility
BlogoMatic will be accessible through a dedicated web page of our web site as well as through potential customer references who will adopt our solution.
5.3.3 PAUX Technologies
Use-Case
Validation
Evaluation Service for FISE Recommendations
PAUX Technologies GmbH would like to offer an evaluation service for FISE services. These services can be
• entity recognition
• recommendations for links
• other output.
If an output (object) is valuable for an author, they will rate it with a specific quintupel:
1. target group
2. previous knowledge
3. relevancy
4. difficulty
5. quality
E.g. for the term London we receive the fise link recommendation http://dbpedia.org/resource/London. The
PAUX author will then valuate the link as follows:
1. The link is valuable for the target group travellers
2. The target group needs little previous knowledge
3. The link's quality is valuated good
4. The relevancy is valuated low
5. The difficulty is valuated easy
The valuation of our authors will be given back as rdf triples, so they can be processed by FISE.
© IKS Consortium
2013
55 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Simplified example code
<rdf:RDF
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:dc="http://purl.org/dc/terms/"
xmlns:rdfs="http://rdfs.org/sioc/ns#"
xmlns:fise="http://fise.iksproject.eu/ontology/"
xmlns:paux="http://paux.com/ontology/"
>
<rdf:Description rdf:about="urn:enhancement-d6332018-facf-9928-acd5c39f206c4e07">
<fise:end
rdf:datatype="http://www.w3.org/2001/XMLSchema#int">
66392
</fise:end>
<fise:start
rdf:datatype="http://www.w3.org/2001/XMLSchema#int">
66386
</fise:start>
<fise:confidence
rdf:datatype="http://www.w3.org/2001/XMLSchema#double">
0.9857885085023388
</fise:confidence>
<dc:type
rdf:resource="http://dbpedia.org/ontology/Place"/>
<fise:selectioncontext rdf:datatype="http://www.w3.org/2001/XMLSchema#string">
ILLUMINATI PROJECT: MEMO
Illuminatus! Trilogy Seite 62 von 470 8/5
J.M.:
The survival of the Bavarian Illuminati throughout the nineteenth century and
into the twentieth is the subject of World Revolution by Nesta Webster (Constable
and Company, London, 1921). Mrs. Webster follows Robison fairly closely on the early
days of the movement,
up to the French Revolution, but then veers off and says that
the Illuminati never intended to create their Utopian anarcho-communist society:
that was just another of their masks.
</fise:selection-context>
<fise:selected-text
rdf:datatype="http://www.w3.org/2001/XMLSchema#string">
London
</fise:selected-text>
<rdf:type rdf:resource="http://fise.iksproject.eu/ontology/TextAnnotation"/>
<dc:creator
rdf:datatype="http://www.w3.org/2001/XMLSchema#string">
eu.iksproject.fise.engines.opennlp.impl.NamedEntityExtractionEnhancementEng
ine
</dc:creator>
<dc:created
rdf:datatype="http://www.w3.org/2001/XMLSchema#dateTime">
2010-0715T17:07:58.218+02:00
</dc:created>
<fise:extracted-from
rdf:resource="urn:content-item-sha1e18e81c8a39e57572bfbd39ed5d0ad4defd1a721"/>
<rdf:type
rdf:resource="http://fise.iks-project.eu/ontology/Enhancement"/>
</rdf:Description>
<rdf:Description rdf:about="urn:enhancement-aba201e0-8310-d189-fa1a0d827e373dd4">
<rdf:type rdf:resource="http://fise.iksproject.eu/ontology/Enhancement"/>
<fise:extracted-from
rdf:resource="urn:content-item-sha1e18e81c8a39e57572bfbd39ed5d0ad4defd1a721"/>
<dc:created
rdf:datatype="http://www.w3.org/2001/XMLSchema#dateTime">
2010-0715T17:09:06.938+02:00
</dc:created>
<dc:creator
rdf:datatype="http://www.w3.org/2001/XMLSchema#string">
eu.iksproject.fise.engines.autotagging.impl.EntityMentionEnhancementEngine
</dc:creator>
<rdf:type rdf:resource="http://fise.iksproject.eu/ontology/EntityAnnotation"/>
<dc:relation
rdf:resource="urn:enhancement-d6332018-facf-9928-acd5-c39f206c4e07"/>
<fise:entity-reference rdf:resource="http://dbpedia.org/resource/London"/>
© IKS Consortium
2013
56 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
<fise:entity-label rdf:datatype="http://www.w3.org/2001/XMLSchema#string">
London
</fise:entity-label>
<fise:confidence
rdf:datatype="http://www.w3.org/2001/XMLSchema#double">
5.764342784881592
</fise:confidence>
<fise:entity-type
rdf:resource="http://www.w3.org/2002/07/owl#Thing"/>
<fise:entity-type
rdf:resource="http://dbpedia.org/ontology/Place"/>
<fise:entity-type
rdf:resource="http://dbpedia.org/ontology/PopulatedPlace"/>
<fise:entity-type rdf:resource="http://dbpedia.org/ontology/Area"/>
</rdf:Description>
<rdf:Description rdf:about="urn:PAUXreview-765765">
<rdf:type
rdf:resource="http://paux.com/ontology/PAUXReview"/>
<fise:extractedfrom rdf:resource="urn:content-item-sha1e18e81c8a39e57572bfbd39ed5d0ad4defd1a721"/>
<dc:created
rdf:datatype="http://www.w3.org/2001/XMLSchema#dateTime">
2010-0715T12:52:54.194+02:00
</dc:created>
<dc:creator
rdf:datatype="http://www.w3.org/2001/XMLSchema#string">
M. Dreusicke
</dc:creator>
<dc:relation rdf:resource="urn:enhancement-aba201e0-8310d189-fa1a-0d827e373dd4"/>
<paux:usergroup
rdf:datatype="http://paux.com/XMLSchema#usergroup">
traveller
</paux:usergroup>
<paux:previous-knowledge
rdf:datatype="http://paux.com/XMLSchema#previous-knowledge">
little
</paux:previous-knowledge>
<paux:quality
rdf:datatype="http://paux.com/XMLSchema#quality">
good
</paux:quality>
<paux:relevancy
rdf:datatype="http://paux.com/XMLSchema#relevancy">
low
</paux:relevancy>
<paux:difficulty
rdf:datatype="http://paux.com/XMLSchema#difficulty">
easy
</paux:difficulty> </rdf:Description>
</rdf:RDF>
IKS Team Feedback
The process which you describe, is not yet implemented in FISE, therefore it cannot be validated. The idea, to
have an feedback component, which integrates usage feedback is very valuable, I will create an Jira issue for the
Stanbol developers, which addresses this need. To summarize:
It could be possible to validate such a feature with Paux users at a later stage, we will get back to this proposal,
when this feedback component exists.
5.3.4 Intt
Introduction
One Entity Oy is a Finnish company based in Helsinki. We are developing a personal publishing platform called
1NTT. Our area of activity is social networking and website building tools. Current pre-beta release is publicly
available online at http://1ntt.net/
Use-Case
© IKS Consortium
2013
57 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
We want to investigate the feasibility of Stanbol integration into our publishing platform 1NTT by enhancing the
submitted documents with semantic data. The implementation will be done by using the Stanbol engine.
When a user creates a document in 1NTT, the content is sent to Stanbol instance for enrichment. Stanbol should
return a list of RDF annotations, which are automatically added as navigational tags to the submitted document.
The user interface for 1NTT document editor will have the possibilities of selecting which tags are used and
which are discarded.
Validation
Our experience regarding the integration project will be gathered along the project and discussed in the validation interview.
Planned Tasks
•
•
Install Apache Stanbol either as local or external instance.
Write the visual UI component for 1NTT document editor.
Online Demo
The on going development can be viewed from http://1ntt.net/. The solution will be available for all registered
users of 1NTT.
Visibility
In the future when 1NTT reaches final and stable state of development, the service has potential of reaching
millions of users worldwide.
IKS Team Feedback
Our primary concern is that 1ntt is not based around a typical CMS technology stack. Secondly it is still not clear
how 1ntt intends to implement Apache Standbol. At present the focus of IKS is text based semantic enhancement
and from our desktop research 1ntt is multimedia focused with images and video. Our recommendation is to
reconsider this proposal once Apache Standbol is able to offer more functionality for multimedia content.
5.3.5 Apache Lenya
Context
This document is a proposal for the IKS EA program. This proposal has for objective the integration
of FISE feature into Apache's Lenya cms.
© IKS Consortium
2013
58 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
The title of this first proposal is : “AutoClassify component” for document in corpus.
The aim is not to class document in a “static classical hierarchical way” (like OS way). Each document isn't still
in a folder but is a node in a content graph.
Goal
To offer the ability to do automatic classification of documents and to offer to the user various navigation options for the same corpus :
• navigation by author
• navigation by location
• navigation by ontology
• …
• navigation by self build request on rdf meta-datas
In fact, navigation opportunities depend on the RDF description of the document, the most important part of this
RDF description will be obtain throw FISE.
Use-case description
One user comes into one corpus. He adds a new document or a set of unclassified new documents. He retrieves
his document and other with tag navigation.
User interface prototype
The document Media:autoClassify-UI.pdf presents UI ideas for this component.
Implementation for the alpha release
Here is detailed functionalities for the first release of the “AutoClassify” component.
Architecture / process
1.
2.
3.
4.
5.
Lenya deals with document's input
Lenya deals with document's view : each document has at minimum the xhtml representation and the
source document
Lenya submits document to FISE's enhancement engine
Lenya retrieves and saves FISE's results
Lenya offers a navigation based on FISE results
User-interface
The user interface for the alpha version:
• will integrate just one or two input ways (slide 1)
• may not propose the pdf view for each document (slide 2)
• just allows navigation with existing tags (slide 3)
• provides at minimum the xhtml view (slide 4)
Planned tasks
•
•
•
•
•
•
Add RDF view to Lenya's existing views
Build enhancement pipeline :
Transform user's input into xhtml – save it
submit plain text representation to FISE server
save FISE results in the RDF document view
Build navigation : add tag item if they don't exist, add document reference if tag already exists
Licensing and demo access
The code will be licensed on Apache 2.0 license. Demo will be public access
IKS Team Feedback
© IKS Consortium
2013
59 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Can you please provide further details on the end-user and development communities that this proposal is targeting?
End-users advantages
• This implementation will provide two main advantages for end-users :
• Provide a non-normative way for document retrieving :
o In most case, documents are organising by an authoritative group (webmaster, communication
group, person who creates the document tree one day,...) in a hierarchical way. But, this chosen way is not necessarily the "by default" way of retrieving for users.
o Provide automatic and multi-access way (throw metadats) for retrieving document is an enhancement for end-users - that don't have to learn any more the authoritative organisation.
o This approach is complementary of the "search engine" one because here, the user doesn't
have to exactly know good keywords, he is guided by a set of metadata and sees documents
that are really relevant for this metadata.
• Provide a normative way for document retrieving :
o On the opposite side, there is some document's repository spaces under the control of each user.
o So, each end-user has a particular way of thinking and organizing
o When these repositories are shared, it's difficult for other users to navigate throw each particular organisation and to retrieve relevant document.
o A normative navigation based on extracted information allows anyone to retrieve easily document in each personal repository - any document is tagged with auto-extracted-metadata.
Development communities
• This development will be used in communities :
o Lenya :
• This first writing of components for Lenya <-> FISE communication will be reusable by all the Lenya
community (I have commit rights on the Lenya branch)
• Some users in the community are interested in and wait for having usable components.
o Cocoon
• As Lenya is based on Cocoon (http://cocoon.apache.org), if components are enough generics, they
could be integrated into the Cocoon framework, and used by all the cocoon compliant applications
•
One the other hand, working on the Lenya - FISE integration will bring me to send more comments and
improvements on FISE.
Relationship with existing stories
• This use-case is a first step on implementation of this one : http://wiki.iks-project.eu/index.php/Userstories#Story_17_:_Ontology_Navigator
• Some components of this implementation will be useful for achieving this goals :
o http://wiki.iks-project.eu/index.php/User-stories#Story_20_:_Personalized_Search
o http://wiki.iks-project.eu/index.php/Userstories#Story_10:_Automated_document_categorization
5.3.6 Ectware s.r
Introduction
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 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).
© IKS Consortium
2013
60 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
SKOSware has a web-based social interface and a REST interface to publish, search and manage thesauri, and
for interoperability with external applications such as content managers.
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 through concepts included in SKOS thesauri for contents and documents. Metadata enrichment allows also geolocalization and chrono-referencing of CMS contents and Solr-based faceted searches
based on the hierarchical structure of a thesaurus. Metadata enrichments are published inside the HTML pages as
RDFa snippets; geolocalization and chrono-references are used to place contents on a map and on a timeline.
By integrating and customizing Solr we are also able to perform searches and refinements based on dynamic
facets, hierarchically organized. The facet structure is compliant with the of the SKOS thesaurus organization.
Vision
Our vision is to integrate Stanbol in place of our manual metadata enrichment for the CMS contents. This allows
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.
On the SKOSware side, thesauri are enriched and checked using metadata enrichment and semantic inference.
Use-Case
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 (see “Using custom/local vocabularies with Apache Stanbol” ).
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.
Validation
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.
Performance
§
Start of contract: 01 March 2012
© IKS Consortium
2013
61 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
§
Stanbol components for validation are: EntityHub, KeywordLinkingEngine, ContentHub, Rules Engine and
OntoNet (to import in Stanbol the SKOS thesaurus)
§
Integration will be done by: Etcware srl
§
Demo system will be available: 31 April 2012
§
End of contract: 31 May 2012
§
Total Contract: 6500 Euro
Planned Tasks
§
SKOS thesaurus enrichment, using the enhancement engines, and checking its correctness and completeness
using the Rules engine and appropriate inference rules.
§
SKOS thesaurus import into Stanbol (the thesaurus can be exported as RDF from the SKOSware REST
interface).
§
Development of a Liferay-Stanbol adapter, structured as a Liferay service portlet, which enhances contents
with Stanbol enrichment services.
§
Liferay hook portlet development to capture and add the metadata-enriched contents produced by Liferay
Stanbol adapter, during post-process content editing; after that, the enriched content will be indexed in a
Solr search engine with our indexing services.
§
Liferay control panel portlet development, to allow administrators to automatically perform enrichment and
indexing of all contents.
§
Frontend search portlet update to add Stanbol-based search (i.e. with ContentHub results).
§
Frontend display portlet update to add entity highlighting.
Online Demo
The complete online demo with all the features described above will be available on Etcware demo server
(www.baseculturale.it).
Visibility
At the end of the experimental project we are going to organize a workshop inside the Tor Vergata University in
Rome to show our semantic solutions. During the event, a seminary will be dedicated to describe the Stanbol
integration project.
5.3.7 CELI France SAS
Use Cases and Context
CELI (www.celi.it)and CELI France (www.celi-france.com) are two SMES in the field of NLP-based solution
provision. We are requesting to participate in the early adoption context in order to integrate Stanbol technology
with a specific context of use, i.e. CV management via CMS and semantic technologies. The crucial challenge of
this integration is the parametrization of Stanbol to deal with information which has been automatically extracted
from CV. Besides the direct integration results, which will be distributed at the same conditions as Stanbol software, the early adoption project will produce two additional by-products:
1. The provision to Stanbol of classes allowing the connection with Linguagrid (www.linguagrid.org) and
possibly LanguageGrid (http://langrid.org/en/index.html).
2. The verification of the extensibility of Stanbol to languages other than English (The project will concern CVs written in French).
© IKS Consortium
2013
62 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Use-Case 1: Human Resources Department
The context is the one of a Human Resource Department of a big company or any recruitment company. The
basic goal is to provide them with an open source document management system able to deal in an intelligent
way with non structured CV (or "resumes"), i.e. CVs which comes in Microsoft Word, pdf, Open Office etc.
Each time a new CV arrives it is inserted in the document base. Behind the scene this is not just adding a document but passing it to a Standbol server which enhances it with structured information.
This might represent:
1. experiences of the candidate
2. skills of the candidate
3. Education level
4. reference data (name, address etc.)
5. contact data
Some of these data might be slightly more structured than just named entities, but definitely in the representation
power of rdf. Some of them could be even more semantically enriched, by providing external information on
companies, places, specific technologies etc.
As a result of this personnel at the HR department would be able to formulate queries such as (just an exemplification):
§
All CV of people living in Paris older then 27 years
§
All CV of people with skills in SQL server and Java
§
All people who have worked in an high tech company since november 2011.
....
In terms of GUI the user will be confronted with a system that allows easy search and easy population of CV
data.
Use-Case 2: Employment Administration
In the second use case we are keeping into account the needs of public agencies with the institutional role of reintegrating in the labor market persons which loose their job or that are looking for their first job. In particular
we are considering institutions such as the French Pôle emploi (http://www.poleemploi.fr/accueil/ , http://fr.wikipedia.org/wiki/P%C3%B4le_emploi). This institution is in charge of crossing
the demand and the offer on the labor market, in particular by addressing candidates to the right potential employer, suggesting possible educational training, by shaping their skills, etc. In many cases these agencies are
managed at a local rather than a national level, as the market of labor is affected by regional constraints. In this
use case the parametrized CMS has a double goal:
§
Much like in the previous case to allow the fast and intelligent retrieval of CVs out of the document base in
order to answer potential employer needs.
§
To be able to perform Business Intelligence like tasks over the structured information provided by the mass
of analyzed CVs. Of course performing BI analysis is out of the scope of this proposal, but the structuring of
CV information into ontology based classes is definitely the first step towards this direction.
Challenges
From a technical point of view the most interesting challenge consists in integrating the set of Stanbol enhancer,
with the semantic web services provided at www.linguagrid.org. In principle it should not be a different integra-
© IKS Consortium
2013
63 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
tion than what has already been made with OpenCalais WS and Zemanta WS. However there are at least two
major challenges:
§
Multilinguality. The extraction will consider French documents rather than English ones. Moreover, in a
second phase (not covered by the present project, the whole system could be extended to Italian and French.
§
Ontological extension. While CVs typically contains quite a lot of named entities which are already covered
by Stanbol (e.g. geographical names, time expressions, Company names, person names) there are entities
which will need some ontology extension such as skills and education.
§
Structural Complexity. In a CV instances of entities are linked each other in a structurally complex way. For
instance places are not just a flat list of geographical entities, but their are likely to be connected with periods, with job types, with companies, etc. Handling this structural complexity represents an important challenge.
Validation
The work will be conducted in close contact with the Standbol developers, who will validate or not the implementation choices. On this regards all preliminary documentation concerning design and architecture will be
submitted for approval.
Real life validation will be probably undertaken at the premises of Objet Directe
(http://www.objetdirect.com/html/index.html). The company has a very important activity in term of recruitment, and they handle hundreds of CV per week. The final platform will be installed at their premises and used
on a day by day basis for at least one month. An evaluation report will be provided at the end of the period.
Performance
The major performance bottleneck is probably to be found in the CV processing phase when CV-related information are extracted. This is however an off-line phase, which does not impact on the user. Moreover, as the
whole architecture is service based, in case of conditions of particular stress, the infrastructure of
www.linguagrid.org (semantic service provider) can easily scale up, thanks to load balancing mechanisms.
From the point of view of efficiency of storage of CV information and consequent retrieval by the user, we are
not yet in the condition to evaluate it.
Planned Tasks
Task 1: Design and Architecture. In this phase we will proceed to the design of integration between Stanbol
and the CV parsing system, on the one hand, and Stanbol and the CMS for CV management on the other hand.
The resulting document (D1.1) will be submitted to Stanbol developers for validation. In this phase we will also
proceed to the choice of the most relevant OS CMS to adopt.
Task 2: Ontology Adaptation. The point of lack of ontological support for skills and cv data in general is an
challenging point, as there is few support to concepts such as, for instance "skills" in DBPEDIA. There is an
extension of FOAF for CV information, but the ontology does not look like to be maintained, and should be
extended (http://captsolo.net/semweb/). Other possibilities are represented by the Linkedin skill ontology and
administrative ontologies such as the one provided by the French Pole Emploi (http://www.pole-emploi.fr).
Some internationalization issue are raised by the latter (D2.1: Ontology for CVs).
Task 3: Semantic services adaptation. The main "entity provider" for this integration is represented by the
semantic platform www.linguagrid.org which hosts nowadays about twenty different services of semantic analysis and Natural Language Processing. The service for CV extraction is not yet exposed, but it is relevant to notice that in the context of this task we will try the integration of most services, whether they are relevant or not
© IKS Consortium
2013
64 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
for the specific CV task. We hope, in this way, to give a mutual visibility for both projects. (D.3.1. Report on
integration with linguagrid semantic services)
Task 4: CMS Integration. The is the phase of interfacing Standbol with the selected CMS. As integration already took place with a number of CMS system we do not expect this phase raise any major issue, expect for the
parametrization of the CMS and the handly of information which is structurally more complex than simple
named entities.
Task 5: Validation. In this phase the system will be installed at the premises of Objet Directe (and possibly
other beta tester) and the behavior of the operators will be monitored in order to improve the production release.
If available data about saving in terms of time will be provided. (D.5.1: Validation Report)
Time Plan
§
Start of contract: 01 March 2012
§
Stanbol components for validation are: Enhancement Engined, EntityHub, KeywordLinkingEngine, ContentHub, Rules Engine and OntoNet.
§
Task 1 and task 2 due 31 March 2012
§
Task 3 and task 4 due 31 May 2012
§
Task 5 due 30 June 2012
§
A first demo will be available 31 May 2012
§
End of contract: 31 July 2012
Online Demo
Having an online demo concerning CV is problematic, as it raises well known privacy issues. Nevertheless, the
system will be demoed by allowing any user to feed the system with one or more CVs in order to investigate its
semantic capabilities. All traces of the uploaded information will be deleted once the session expires
Visibility
The project will have high visibility, articulated in two main lines:
§
Visibility of the integration between www.linguagrid.org and Stanbol. Visibility of this activity will be
achieved via dissemination in several European projects in which CELI and other linguagrid partners are involved. This theme will also be the object of one talk at LREC. Finally a press release might be issued in fall
2012, reporting the integration of linguagrid with Stanbol and possibly other OS tools for information management.
§
Visibility of semantic processing of CVs: the scope of this dissemination campaign will be more oriented
towards the business world and, at least in a first phase, focused on the French market. There will be announces diffused via specialized press such as the Journals "Entreprendre" and "Presences". The open
source aspect of the initiative will be underlined, even though the press campaign will also emphasize the
capabilities of semantic processing delivered by CELI France.
5.3.8 Content Control
Introduction
CONTENT CONTROL is one of the leading contributors to the open source MidCOM PHP web application
framework. We plan to add a VIE/CreateJS-based editing interface and the necessary infrastructure for automatically generating and rendering RDFa annotations from existing DB schemas.
© IKS Consortium
2013
65 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Vision
Ideally, the system should be fully automated, so that site and application builders will get RDFa-compatible
markup without any extra effort, which will make them more useful in the semantic web context. The library
handling these tasks will be created in a modular fashion and released under a Free Software licence, so that it's
possible to write backends for other content management frameworks. At the same time, the annotations, combined with the necessary access rights, will provide automatic inline editing capabilities, making their websites
behave in line with Tim Berners-Lee's read/write web vision.
Use-Case
The modal nature of the typical CMS/web application interfaces (one page for viewing, another for editing) is
quite counterintuitive and often leads in the case of content management to endless repetitions of edit – view –
edit again cycles. With VIE and the associated libraries, we want to create an interface which allows users to stay
focused on their task by avoiding to constant switching between view and edit states. So the benefit to end users
will be a more usable, intuitive editing interface, which at the same time produces markup that is much more
machine-readable, so that integrations and SEO can be done more easily.
Validation
Our preliminary tests have shown that while VIE/CreateJS shows great promise and users react quite positively
to it, it is still missing some important features for use in real-world applications (like hooks for integrating with
other JS libraries, some commonly-needed widgets and so on). On the basis of two website projects, we will
gather feedback from actual end users to see where the strengths and weaknesses of the VIE-based system are,
and implement improvements where possible.
Performance
•
•
•
•
•
Start of contract: 01 May 2012
Components for validation are: VIE/CreateJS
Demo system will be available: 01 July 2012
End of contract: 12 July 2012
Total Contract: 7000 Euro
Planned Tasks
Creation of a data management library that can
• parse (DB) schemas
• render entities with (configurable) RDFa annotations
• initialize the CreateJS-based management UI
• provide a REST backend for data received from backbone.js
CreateJS-based frontend that can
• handle all content types in the sample projects
• provide integration with the framework functionality
Online Demo
A public online demo will be provided
Visibility
The open source MidCOM framework has quite a long history and there are all kinds of production systems
running on it, ranging from enterprise-level web applications to portals to CMS websites. For all of them, CreateJS would become a natural upgrade path, meaning that they would start generating semantic markup. In addition to that, we want to make the schema parser/RDFa renderer library modular and extensible, so that it can be
reused in other PHP-based frameworks as well.
5.3.9 Formcept
Introduction
FORMCEPT [1] provides a highly scalable content mining infrastructure through proven open source technologies that includes Hadoop, HBase and Solr. FORMCEPT's C3 (Classify, Compare, Correlate) Semantic Engine
is a state of the art technology which provides classification, comparison and correlation for any type of content.
© IKS Consortium
2013
66 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
FORMCEPT's C3 semantic engine can be extended to areas like Competitive Analysis, Financial Analysis, Profile Analysis, Health-care, Trend Analysis, Sentiment Analysis, and more.
Vision
FORMCEPT [1] is an effort to make content analysis accessible to everyone, be it an enterprise, an individual or
a device. We are working on some interesting state of the art products that will be available both as Software as a
Service Model (SaaS) and as installable products.
Use-Case
Analysis of Medical Records - Semantically enrich patient's medical history and aide doctors by recommending
drugs. The options provided will be1. Upload a file or key in the medical record that can be a medical history, report or doctor's prescription
2. Get the enriched medical record having the symptoms, drugs and related medicines marked
3. Also see the timeline for the entire medical history to locate when was a particular symptom recorded
and what was the medicine given
4. Options to add notes and modify the marked entities
Validation
See validation page for full details of validation and demos Validatiaon Page
Performance
•
•
•
•
•
•
Start of contract: 1 May 2012
Stanbol components for validation are: Entityhub, Keyword Linking Engine, New Medical enhancement engine
Integration will be done by: 30 June 2012
Demo system will be available: 15 July 2012
End of contract: 31 July 2012
Total Contract: 7000 Euro
Planned Tasks
•
•
•
•
Understand Stanbol Architecture
Evaluate existing Enhancement Engines
Create an Enhancement Engine for Medical Records
Setup a demo instance for validation
Online Demo
Demo is available online at: http://demo.formcept.com:8080/enhancer
"We are currently annotating drugs, diseases, chemical compounds and few other medical and related domains.
The enhancement engine uses FORMCEPT's knowledge graph that is built on top of DBpedia 3.6 dumps. So,
thanks to DBpedia project as well. We not only annotate the entities but also find the overall broader categories
with the relevant hierarchy. As of now, we are annotating the hierarchy as a path under SKOS_BROADER annotation. A typical annotation looks like"broader": "Health->Diseases and disorders->Symptoms->Symptoms and signs:
"Digestive system and abdomen->Vomiting",
"comment": "Vomiting (known medically as emesis and informally as throwing up and a number of other terms)
is the forceful expulsion of the contents of one's stomach through the mouth and sometimes the nose. Vomiting
may result from many causes, ranging from gastritis or poisoning to brain tumors, or elevated intracranial pressure. The feeling that one is about to vomit is called nausea, which usually precedes, but does not always lead to,
vomiting.",
"created": "2012-07-01T12:23:58.495Z", "creator":
"org.formcept.engine.enhancer.FCHealthCareEnhancer", "end": 768, "extracted-from": "urn:content-itemsha1-09055dcdcb07a20b3b30f64079a9a2779600f801", "selected-text": "vomiting", "start": 760, "type":
"Health"
We are working on benchmarking the overall performance. We will post the details soon.
Please give it a try and provide your feedback"
Visibility
© IKS Consortium
2013
67 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
FORMCEPT [1] was started in the month of September, 2011 at Bangalore, India.
References
[1] FORMCEPT - Your Analysis Platform, www.formcept.com
5.3.10
Sztakipedia
Introduction
The Unstructured Information Management Architecture (UIMA) [1] is a content analytics framework that was
initiated by IBM Research. In 2005 the US Government gave substantial support for the project trough its Defense Advanced Research Projects Agency[2]. This lead to the formation of UIMA Working Group. Under the
umbrella of this working group a couple of related technologies were adapted to UIMA[3] (such as OpenNLP[4]
and GATE[5]), and numerous new components were created in widely ranging topics from standard natural
language processing tasks to bond yield recognition, chemical element annotation, protein and gene annotation,
etc. UIMA became an Apache Incubator project in 2006 [6], and as the framework matured an UIMA OASIS
standard was created in 2009 [7], the first of this kind. Since then substantial work has been done on performance improvements and applications. Asynchronous Scaleout (AS)[8] provides a way for distributed content
analysis, so does Behemoth[9], that enables the execution of UIMA tasks on Hadoop clusters. Deep QA applies
UIMA AS to question answering and was recently applied in the famous Watson project to play the Jeopardy!
game [10].
The proposer is the lead developer of Sztakipedia project[11] in which high performance statistical natural language processing is used, based on UIMA. One important output of the project is the Sztakipedia Harvester[12]
which is able to process more than 80k words of Wikipedia articles in a second, including wikitext parsing, tokenizing, paragraph boundary detection, sentence boundary detection; also category, outlink, infobox indexing
and tf-idf calculation using Apache Lucene.
Motivation
UIMA belongs to a previous generation of technologies in many aspects, but an adapter to the Stanbol Engine
would be very beneficial for both of these Apache projects. Although UIMA can be integrated with web projects,
it was initially designed with desktop and server applications in mind. With Stanbol integration UIMA could be
accessed from the web with state-of-the-art technology. On the other hand, an adapter would enable Stanbol
users to exploit the numerous ready-made UIMA components that are distributed as PEAR packages on the
UIMA Content Repository[13] and elsewhere on the web.
Use Case
The actor in this use case is not the end user, but the Stanbol administrator/CMS developer, who wants to use a
UIMA component downloaded from the web or developed in-house. The actor wants to get annotations from the
UIMA component trough Stanbol with as minimal development effort as possible. This means avoiding the
modification and compilation of either the UIMA component or Stanbol if it is not necessary. Therefore, the user
configures a mapping from the UIMA TypeSystemDescription to RDF triples, and also configures a communication interface between UIMA and Stanbol. As soon as the communication interface and the type mapping is
configured, and the Stanbol adapter is started, the UIMA component is used to analyze incoming content.
Planned tasks
1) Remote UIMA: a) creating an UIMA Adapter Enhancement Engine that communicates via REST with a UIMA deployment that runs in its own JVM b) providing documentation and the necessary software template for
REST-enabling UIMA engines so that they can be used by 1a)
2) Embedded UIMA: creating an Enhancement Engine template that can be used to embed a UIMA engine directly into Stanbol. Maybe it will be limited in some ways, e.g. only one UIMA engine can be deployed in one
Stanbol, only Java UIMA components can be integrated with the proper java version.
3) The creation of a (native Stanbol) Book Finder Enhancement Engine (BFEE) that recommends items from
British National Library and The Open Library, which together has about 25 million records.
Validation
The functionality of the UIMA adapter solution will be evaluated by integrating at least three pear files from the
UIMA Component repository. Without a really good evaluation data set for the book finder, a functional evalua-
© IKS Consortium
2013
68 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
tion will be used with BFEE: a) "significant" works must be found when mentioned literally, or near-accurately
(relying on Lucene proximity search). Significance of works are fixed in the database and are calculated a priory
using dbpedia and other sources. b) when the author(s) and a work title is present in close proximity, and both
the name and the title are uncommon enough (these metrics are also added a priory to the database) This evaluation method and a related Book Recommender component is tested in Sztakipedia project.
Visibility and Demonstration
The UIMA component adapter is not a typical demonstrative artifact for the end users but it will surely be interesting for the UIMA community to which it will be presented on their mailing lists. An on-line accessible Stanbol instance will be provided, that will feature enhancements that come from UIMA components, and also the
Book Finder Enhancements. Also, description and links to the adapter documentation and code will be added to
the UIMA project site, to the Powered by Apache UIMA section.
Performance
•
•
•
•
•
proposed start of contract: July 15 2012
end of contract: 26 August 2012
demonstration of uima adapter: 18 August 2012
demonstration of Book Finder: 18 August 2012
proposed total amount 6000 EUR
References
[1] David Ferrucci and Adam Lally. 2004. UIMA: an architectural approach to unstructured information processing in the corporate research environment. Nat. Lang. Eng. 10, 3-4 (September 2004), 327-348.
DOI=10.1017/S1351324904003523 http://dx.doi.org/10.1017/S1351324904003523
[2] IBM Press Release: http://www-03.ibm.com/press/us/en/pressrelease/7822.wss
[3] UIMA FAQ: http://uima-framework.sourceforge.net/uima_faq.html#3
[4] http://opennlp.apache.org/
[5] http://gate.ac.uk/ie/
[6] http://uima.apache.org/news.html#05 October 2006
[7] http://docs.oasis-open.org/uima/v1.0/uima-v1.0.html
[8] http://uima.apache.org/downloads/releaseDocs/2.3.0-incubating/docs-uimaas/html/uima_async_scaleout/uima_async_scaleout.html
[9] https://github.com/DigitalPebble/behemoth
[10] E Guizzo: IBM's Watson Jeopardy Computer Shuts Down Humans in Final Game - IEEE Spectrum, Feb
17, 2011
[11] Mihály Héder and Pablo N. Mendes. 2012. Round-trip semantics with sztakipedia and DBpedia spotlight. In
Proceedings of the 21st international conference companion on World Wide Web (WWW '12 Companion).
ACM, New York, NY, USA, 357-360. DOI=10.1145/2187980.2188048
http://doi.acm.org/10.1145/2187980.2188048
[12] http://code.google.com/p/sztakipedia-harvester/
[13] http://uima.lti.cs.cmu.edu:8080/UCR/Welcome.do
5.3.11
Netlabs.org
Introduction
netlabs.org is working on a framework which facilitates interfacing RDF based data. We heavily rely on ontologies in our framework, which means we cache them and do quite some reasoning on top of them to figure out
how data can be interfaced and shown in the optimal way. This includes figuring out relationship between ontology classes and attributes. Right now this reasoning is pretty minimalistic and mainly done in code, which means
we analyze triples our self.
The goal of the Early Adopter's project is to implement the reasoning parts on top of Stanbol based RESTful
services. This will allow us to use the power of the Stanbol rules and reasoning services to infer additional relationships between ontologies and also use the ontology manager to cache commonly used ontologies with Stanbol to speed up internal services in our framework.
© IKS Consortium
2013
69 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
We will use Stanbol to:
• cache ontologies: Right now we fetch them from the various official sites which are often very slow and
unreliable
• reason/infere (and cache the reasoned knowledge) relationships between ontologies: This includes figuring out which attribute belongs to which class, which class to which superclass etc. We can do much
smarter matching with Stanbol than we do now in code, which will improve our interfaces
• implement several strategies to figure out matches between RDF data: This again improves our user interface. As an example, an interface could figure out that the attribute foaf:based_near is a spacial thing
and thus can be shown by any interface class which can show a map.
Use Case
•
•
•
•
•
•
•
UC 1 - Framework/data perspective
Create class trees and property trees for ontologies: The goal is to find out how classes and properties
are related to each other. In our framework UI widgets match to RDF properties. But we cannot and do
not want to implement a class for every property so the relationship between properties can help the
system to figure out which widget might be the best choice to interface a certain information, even if the
widget designer did not necessarily think of that upfront.
Clean up consumed RDF data: RDF based data is often incomplete. As an example, many RDF datasets
available in the LOD cloud do not assign the proper classes to URIs but just use the attributes. This
makes it difficult for our framework to figure out what a certain URI is really about and thus it is difficult to match it to the proper UI widgets as well. RDF classes are also used by our framework to match
available views on certain data, this would heavily improve this matching as well.
UC 2 - End users (using applications implemented on our framework)
Much smarter user interfaces that can adopt to the selected (RDF based) data and choose the best representation for that data on a particular device (smartphone might look different than the desktop web
browser)
Faster experience because we cache the ontologies and additional inferred knowledge in Stanbol
Can handle incomplete or partially wrong RDF data better, which makes consuming LOD more convenient
Challenges
•
•
•
•
All ontologies used must be available in the Internet and dereferencable by our framework. This is true
for most commonly used ontologies but there seem to be a few exceptions of the rule.
Poorly made ontologies will provide little or no use for reasoning. While we did not extensively analyze
commonly used ontologies we already did spot some flaws in some referenced ontologies. It will be interesting to see how well our approach scales in the (current) RDF real world.
While our framework does provide basic UI widgets our focus is so far more on the back-end code than
on fancy UI widgets. We currently use the Enyo JavaScript application framework and could theoretically use all available UI components in there. However, there is more work to be done on framework
side to make it look really good so the Stanbol based demo will simply prove the point.
While many ontologies remain pretty static it is still important to handle caching properly. We will run
tests to see if Stanbol handles caching correctly from both client and server perspective while caching
ontologies.
Potential Further Enhancements
The following ideas could be addressed after the initial scope of development for this Early Adopter's proposal:
• It might be useful to have some kind of meta-ontologies which describe and match relationships between classes and attributes among different ontologies in the semantic web. This could improve inference and make matching between similar things easier. We have some ideas about how this could be
implemented and it would be interesting to see how Stanbol can help on that.
• There are several large RDF based knowledge bases available like YAGO2 and/or UMBEL which can
also be used as an ontology. It will be interesting to see how these knowledge bases can be integrated
into our framework using Stanbol to gain additional knowledge.
• The same applies for any vocabulary based on ontologies like SKOS. While it is not completely clear
yet how such vocabularies could be used it would be interesting to play around with it.
Validation
© IKS Consortium
2013
70 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Stanbol Team
•
We got some encouraging feedback on the Stanbol mailinglist about this proposal. We would work
closely with the developers of the various Stanbol components mentioned during this project to assure a
successful outcome.
Community-driven
•
•
•
Our framework will be released as Open Source software under a liberal license later in 2012 (we
hope). We will work closely with the group of current developers which themselves are experienced
open source software contributors for many years.
All work done on top of Stanbol will be documented and released to the public at the end of the project
in September 2012. This could be done in the official Stanbol documentation if requested by the developers.
Adrian Gschwend will do the major work on this particular project and report both success and issues
back to the Stanbol developers.
Client-driven
netlabs.org is involved in a FP7 SME project which starts in July 2012. The outcome of this proposal
would be directly applied there to see how much benefits we have from a client perspective. Also there
are two ongoing projects with the Berne University of Applied Sciences running on which we would also validate the prototype.
The validation for the Stanbol integration will be initially on our FreeBSD jail servers. If necessary we can and
will provide access via OpenVPN to Stanbol developers and at a later stage in the project to a wider community
for evaluation and feedback.
•
Performance
Currently caching of our framework is done purely in our code. We will use Stanbols ontology caching services
to evaluate if we can increase the user experience. Our internal unit test framework can be used to measure the
performance of the Stanbol based implementation of the services.
Planned Tasks
Step 0: Project inception: Stanbol familiarization - required technical setup of Stanbol installations, documentation overview, API overview, sample REST queries, rules and reasoner samples. First contact with the development team in case of open questions.
Step 1: Stanbol bootstrapping: Setup of Stanbol in our FreeBSD jail, first RESTful interaction with our own
Stanbol instance via curl and web interface, loading and unloading of ontologies in the ontology manager.
Step 2: First inference: Implement basic inference samples on top of Stanbol modules: attribute to class mapping
and class to superclass mapping. This is the base to replace the current code-only inference used in our framework.
Step 3: Ontology caching: Extend the dereferencing engine used in our framework to get ontologies via Stanbol
RESTful services instead of fetching them directly. Make sure ontology caching is done properly from a HTTP
caching perspective in both internal and Stanbol based RESTful services.
Step 4: Accessing Stanbol from our framework: Replace the internal inference services in our framework with
Stanbol based RESTful services to do the same mapping (implemented in step 2). This provides the technical
base for more advanced mapping later.
Step 5: First performance tests: Compare the new Stanbol based inference and caching services with the former
internal services. First optimizations in case of performance degradation due to external RESTful calls. This
could be done by pre-fetching some commonly used ontologies and relationships from Stanbol based on usage
statistics.
Step 6: UI widget selection: Up to step 5 the enhancements are purely on a data/ontology level which means that
there is no direct visual benefit yet for the user, it is solely used to provide the base functionality in the back-end
of the framework. In this step we will extend the UI widget matching on the front-end, which means we will be
able to use rules to for example figure out that foaf:based_near is a special case of a WGS84 Spatial Thing. This
will require enhancements on the UI level of our framework and again integration of Stanbol based rules services.
Step 7: Stanbol Rule Deep Dive: Based on the first basic rules we will dive deep into the inference possibilities
and comparing the options Stanbol provides like SPARQL Construct, SWRL and Jena Rules. To provide some
useful examples we will apply this on some more complex (and sometimes wrong) data in the LOD cloud to
© IKS Consortium
2013
71 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
show how this can be used on real world data. An additional goal of this step is to compare the complexity and
power of the different rule syntax from an engineer (not researcher :) perspective.
Step 8: UI verbosity: Based on some more advanced rules gathered in step 7 we will show how a minimal UI
widget implementation can be extended with powerful widgets for particular data. The goal is to show how
UI/widget programmers can easily add new functionality to the UI without bothering about the rest of the
framework. This should also prove that it is possible to add a widget for a particular ontology class/attribute
which can be re-used outside of its original scope by the framework with the help of Stanbol.
Tasks will be carried out beginning July 9 2012 and completing by September 30 2012 (12 weeks).
Performance of Contract
The terms of the contract are:
• Start of contract 9 July 2012
• Demo preview available 17 September 2012
• Demo system available 30 September 2012
• Validation interview in September 2012
• End of Contract 30 September 2012
• Total remuneration for this contract is 6500 Euro.
Online Demo
•
The validation phase for the Stanbol integration will initially be internally on our FreeBSD Jail servers,
then subsequently deployed to a public-facing running instance, accessible on the web to a wider community for evaluation and feedback.
5.3.12
MarkTheGlobe
Early Adoption and Validation Proposal
MarkTheGlobe is a Global SEO startup and would like to evaluate and integrate Stanbol into our Global SEO
Platform satural to help online marketing managers and SEO agencies to identify keyword proposals for SEO
campaigns and to categorize existing keywords to better manage large campaigns.
Our initial goal is to use the system to generate keyword ideas for specific content. These keyword ideas will
then be used as input to our SEO platform to further enrich them with SEO specific information like search volume and competition to propose suitable keywords for SEO campaigns.
Especially for websites with huge amount of content identifying suitable keywords for SEO campaigns is a labor
intensive process. We have already developed several syntactic and statistical approaches to generate keyword
proposals and would like to add a semantic component with Stanbol to get more accurate results.
Being able to use dbpedia ontologies available for currently 15 languages allows us to use the approach for a
wide range of the languages we require for Global SEO.
Use Cases
For the purpose of this evaluation project we will develop a end-user interface that will be available for demonstration purposes and to evaluate the semantic results against our current results to determine effectiveness of the
semantic information for SEO.
UC 1 - Keyword Candidates
To run successful SEO campaigns it is important to target the right keywords (i.e. keywords that are relevant,
can drive traffic and fit the available budget). In most organizations SEO happens after the content is created and
for content is created also for non-SEO reasons. Therefore suitable keywords need to be identified for sometimes
large volumes of content.
For evaluation the following use case will be implemented.
• User enters a URL and language
• The content of the URL is extracted (Title, META, HTML Body)
• The content is parsed into entities
• The entities are analyzed with Stanbol to generate a list of keywords (categories dbpedia) that are either
above or below the entities in the ontology.(->Linking Engine, API of Entity-hub) The steps above and
below should not be too far away from the keyword so the combination makes sense.
© IKS Consortium
2013
72 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Our SEO metric enrichment process is run across the different keyword proposals to rank them for suitability.
• The resolution keyword proposal list should be compared to our current proposals and identify new
proposals that are the result of the semantic technology.
Later (i.e. outside the scope of this proposal) we intend to implement the same functionality as part of our satural
platform to get more keyword proposals, assuming that the semantic proposals prove to be a valuable addition.
Maybe it will be better to use another Source(maybe some kind of open goverment data)
•
UC 2 - Keyword Categorization
To monitor the success of SEO campaigns it is important to see the differences in ranking from month to month.
Ideally the rankings would improve. When working with a large amount of keywords (1000s), then monitoring
on a individual keyword level is quite cumbersome and might not reveal important trends. Therefore we aim to
categorize a set of keywords using Stanbol so that in addition to seeing results on a keyword level, we would
also summarize results on a category level.
For evaluation the following use case will be implemented:
• User enters a list of keywords and language
• For each keyword a dbpedia category tree is retrieved.
• The category trees of all keywords are summarized to extract a suitable amount of categories that can be
used to group all keywords.
Later (i.e. outside the scope of this proposal) we intend to implement the same functionality as part of satural to
allow reporting on a category/group level.
Maybe dbpedia spotlight can be used here.
Challenges
The multilingual aspect is core to our solution. Therefore we aim to only integrate technology that can be scaled
across multiple languages. To use Stanbol for different languages in a production environment we expect a learning curve and customization to make it work across all dbpedia supported languages.
Since integration into satural directly would make evaluation difficult, we intend to build user interfaces specifically for the evaluation and that we can also make available to 3rd parties.
Potential Further Enhancements
We can see several semantic extension points for our solution once we have gained more implementation experience with Stanbol after the evaluation project is completed.
• Integrating with other ontologies
• Development of ontology generation for other languages (not supported by dbpedia)
Validation
MarkTheGlobe Team We will internally check and compare results to determine suitability and fine tune the
results.
Community-driven
Our evaluation interfaces will be available on public websites and we will actively engage with the broader SEO
community to validate the real life value of the semantic proposals. We will aim to identify unmet use cases
during this stage. Our partner agencies and suppliers will be asked to test the solution.
Client-driven
We will use the technology in client projects during project kickoff to generate additional keyword ideas.
Performance
Since we will work with huge amounts of keywords, especially in UC2, we will need to consider some batching
and parallelization of data gathering. We will fine tune our hardware and do a detailed report on performance
findings to define the most suitable query strategy.
Planned Tasks
Step 1: Project setup Introduction of MarkTheGlobe developer to semantic basics, the available Stanbol components and API. Setup of project server.
© IKS Consortium
2013
73 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Step 2: Detailed Specification of solution Documentation of requirements and definition of technical implementation
Step 3: Development Development of UC1 and UC2
Step 4: Configuration Configuration of Stanbol and dbpedia data to be used for evaluation in different languages
Step 5: Testing and Evaluation of results Running several predefined tests and comparing the results with existing technology. Fine tuning parameters to get best keyword proposals.
Step 6. Validation of results Gathering feedback from SEO community, partners, suppliers and clients
Step 7: Documentation Document findings and disseminate results
Performance of Contract
The tasks will be carried out beginning August 1th and ending November 30th
The terms of the contract are
• Start of contract: 1st August 2012
• UC 1 preview: 1st October 2012
• UC2 preview: 30th October 2012
• Online Demo: 1st November 2012
• End of contract: 30th November 2012
Total remuneration for this contract is 7000 Euro
Online Demo
We will develop the evaluation user interfaces into a online demo that accessible to the public. We will also aim
to submit the findings of the work for presentation at a suitable conference.
Visibility
•
•
•
Matthias Zeitler, the founder of MarkTheGlobe, will be the executive sponsor for this project. He will
integrate the findings into general speaking opportunities to raise the awareness for semantic solutions
in general and Stanbol specifically for Global SEO. In the past he was a speaker at events like: Localization World, Internet World, tekom, ad:tech, Convention Camp and several other industry events.
Results will be well documented and disseminated. We will aim to present the finding via a Call for
Speakers at an international event.
We will make the developer of the project available to other IKS member companies via participation/presentation at an upcoming IKS event.
5.3.13
Compusic/buddycloud
Use-Case
buddycloud (https://buddycloud.org/) is a set of Open Source software components implementing a distributed
Social Media platform based on open standards, especially XMPP (Extensible Messaging and Presence Protocol), a standard controlled by the IETF (the same institution controlling the HTTP standard).
XMPP is currently gaining new popularity. A chat application using XMPP is now even supported by Mozilla
Thunderbird since version 15.
buddycloud is one of the main Open Source projects active in creating the Federated Social Web.
Social Media platforms manage and distribute user generated content. Most of this content in buddycloud currently is simple text, maybe including URLs which are automatically converted to links and/or images when
shown to users.
This content is to be semantically enhanced in a way which improves the user experience for the majority of
users and not just those who are geeks.
One particular and demanding task is to make these features available for users of mobile devices. A rapidly
increasing amount of Internet users is using mobile devices as the preferred device to access the Internet. This is
especially true for Social Media applications.
© IKS Consortium
2013
74 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
It is hotly debated which technologies are to be preferred to implement mobile applications. There are web applications, native applications and hybrid applications (using web technologies within a native application). This
proposal is about a web and an hybrid application.
There are two types of users in the use case considered in this proposal: authors of postings or comments and
readers of those postings or comments.
Readers will see more content enhanced by links to relevant web pages which improves their user experience.
Relevant pages might for example be about more or less well-known people, cities etc.
Authors will be able to attract more readers of their content by enhancing the text content they create. Such enhanced content is more attractive for readers. It is expected that the semi-automatic processes used to create the
enhancements will not pose a significant hurdle for authors. In any case authors can choose not to enhance their
text at all. It is important to note that (almost) all users of buddycloud often change their roles between author
and reader.
Validation
This Early Adopter proposal is the first proposing using software created by the IKS project in mobile applications.
A main technical problem to be solved to ensure interoperability is about the transmission of RDFa over XMPP.
The mobile web client will be offered to all users of Buddycloud. Most of the content currently is accessible for
all buddycloud users. It will therefore be easy to watch how users use this feature and communicate with them to
be able to improve the feature.
Performance
Using mobile applications poses additional performance requirements both regarding amount of data transmitted
and transmission delays. A lot of data transmitted can be expensive for some users depending on their contracts
with mobile operators. And in addition to that mobile applications have to deal with the fact that such wireless
connections sometimes break down. Both of these issues will be evaluated.
The terms of the contract are :
• Start of the contract, October 2012
• IKS components for validation is the VIE integration and the Apache Stanbol
• Demo system available 20 November 2012
• Validation interview in 30 November 2012
• End of contract 30 November
• Total remuneration of this contract is 6500 Euro
Planned Tasks
a. the library annotate.js (http://szabyg.github.com/annotate.js/) which is using VIE (http://viejs.org/) and Apache
Stanbol on a server will be modified so that it can be used on mobile devices. For example the disambiguation
process should not display a popup but a user interface which is appropriate for the mobile device. To do that a
library such as jQuery Mobile will be used.
b. the modified annotate.js library and VIE will be used to create a web client so that a user can request semantic
enhancements and then disambiguate when several choices are presented. The code will also be used to create a
hybrid Android app, that is, a native Android application which is implemented by using web technologies
(HTML, CSS, JavaScript).
c. the enhancements will be added to the text as RDFa attributes. To transmit RDFa enhanced text it will be
necessary to define how to do that using XMPP. Currently an XEP (XMPP Extension Protocol) exists, which can
be extended. That XEP is XEP-0071: XHTML-IM (http://xmpp.org/extensions/xep-0071.html). It "defines an
XHTML 1.0 Integration Set for use in exchanging instant messages that contain lightweight text markup". It
currently does not include RDFa. The project will attempt to both define and submit either a revised version of
XEP-0071 or a new XEP enabling the use of RDFa to the XMPP Standards Foundation.
On October 3, 2012, there has been some feedback from the XMPP community suggesting to use RDF/XML
instead of RDFa in the XMPP messages transmitting the enhanced content:
http://mail.jabber.org/pipermail/standards/2012-October/026850.html
d. when the text to be enhanced includes URLs these URLs will be visited and enhancements requested from an
installation of Stanbol. Disambiguation using VIE will be done by the creators of postings using the same kind
of mechanisms as are used to disambiguate semantic enhancements for the core text of the posting.
© IKS Consortium
2013
75 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Online Demo
Both, a mobile web client usable by modern smartphones and an Android application as described in 4. will be
made available on the Internet. While the Android application needs to be installed on an Android device the
web client can be used by user with a modern mobile browser. The source code will be released as Open Source.
Visibility
The software will be promoted to users of the buddycloud software and in other sections of the Open Source
community. This includes the Apache Stanbol community and the W3C Federated Social Web Community
Group. One of the developers who will develop the software is one of the chairmen of that Community Group
and the CEO of buddycloud Ltd. is member of it.
Future / Other aspects
A cool aspect of buddycloud is that a small number of different clients already exists with somewhat different
features and designs but with the same set of users ("roster"). The idea here is to add another client installation
which can be used by the same users but with semantic enhancements as an additional feature.
So far in the proposal it is only planned that enhancements are to be created by the author of the content. It might
also be considered to add an enhancement feature for existing content for readers (including the author). This is
more complex for several reasons when the enhancements are to be stored and it is currently not certain how
much sense this makes from a user perspective.
It is more important that the authors can improve their own content while they create it. It does make sense that
authors can also improve their own content which they already created but so far buddycloud does not allow that.
An XMPP Extension is currently being discussed in the XMPP community which will make changes to existing
chat postings possible. Something similar might be used in buddycloud in the future. But that does not yet exist
and is not implemented. Such a feature could then be used to semantically enhance existing content.
5.3.14
Gnowsis
Gnowsis.com (which is operating the Web service Refinder, see http://www.getrefinder.com ) would like to
implement Apache Stanbol software components for the purpose of automated tagging of content items (files,
documents, notes, Web pages, etc.) stored in the Refinder platform. The objective is to disburden the user from
the load of manual tagging efforts on the one hand, and on the other hand to make search and retrieval operations
more easy for the end user.
Use-Case
Refinder for Teams (see http://www.getrefinder.com/about/content/product) is a Web-based tool that allows
users to collect and manage information that is of importance to the social contexts they are working in (e.g.,
project teams, student groups, management boards, etc.). Refinder brings the data and activities from cloud apps
like Dropbox, Google Apps, Box, Basecamp, etc. into one place, where it can be efficiently shared, filtered,
searched, and discussed.
Refinder Cloud Search (see http://www.getrefinder.com/about/cloudsearch) is a service that can be integrated
into Web and mobile applications, allowing developers to easily integrate search functionality across different
cloud sources into their applications. It disburdens the developers from having to set up their own crawling,
indexing, and search infrastructure.
The use case for Apache Stanbol within the Refinder product suite is to enable automated tagging for users.
Auto-tagging in Refinder is performed in the following steps:
1. Information comes into the Refinder platform either by manually creating it through the user interface, by
using any of the connectors and integration points to feed data into the system (e.g., by sending an email to a
designated address), or by automated crawling from the cloud data sources as mentioned above.
2. After an information item has been loaded into Refinder, a pipeline of information processing steps is applied.
This pipeline includes the following steps:
• fulltext extraction
• metadata extraction
• preview generation
© IKS Consortium
2013
76 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
• tagging
• indexing
3. Apache Stanbol will come into play mostly in the last step. The goal of tagging using Stanbol is to annotate
information items not only with plain keywords, but instead with rich semantic entities that carry more descriptive metadata about the respective entity. The metadata will be indexed alongside the content of the tagged item
and will therefore be available to be used in search requests issued by the user, as well as recommendation algorithms that operate on the data in the background.
4. Additionally, the extracted tags are displayed to the user in a designated "tags" pane, where they can be
browsed and edited.
5. Tags are further used as a filter criterion when the user performs search operations in Refinder.
Validation
Validation of this approach will be done through the existing and future user base and customers of Refinder.
This includes single persons, as well as teams in different size ranges from industries like creative media, accounting, research and development, consulting, architecture, and arts. We plan to collect feedback from these
users by performing structured interviews with them, and plan to collect feedback on how the automated tagging
simplifies their information work and communication processes.
Planned Tasks
1.
2.
3.
4.
5.
Setup of the Apache Stanbol service in a suitable environment
Implementation of a autotagger wrapping component that accepts data from Refinder as input, sends the
data to Stanbol, and converts Stanbol's response into a format appropriate to be further processed in Refinder
Adaption of GUI elements
Tests
Deployment to Refinder's production instances
Online Demo
After the development has been finished, the Stanbol auto-tagger will be deployed to Refinder's main production
instance, which is available at http://www.getrefinder.com. It can be used by any user with prior notice (autotaggers need to be enabled by an administrator on a per-user level). Further, depending on the users' needs, the
Stanbol auto-tagger will be deployed as part of on-premises installations of Refinder.
Visibility
The ability to perform intelligent information analysis is one of the main differentiators of Refinder as a collaboration platform, as well as for the Refinder Cloud Search infrastructure. The autotagging feature based on Stanbol will be heavily promoted as part of any promotion of Refinder itself. Further, members of the Refinder team
are frequent speakers at relevant national and international conferences, where Refinder capabilities (enabled
through integration of Stanbol) will be presented and discussed to a broad audience.
Performance of Contract
1.
2.
3.
4.
Start of contract: October 24, 2012
Demo system available: November 30, 2012
End of Contract: November 30, 2012
Total remuneration for this contract: EUR 6000,- (not including VAT)
5.3.15
Conatix
Company
Conatix UK Ltd (currently in stealth mode) is a Berlin- and London-based startup and a spin-off project of the
Humboldt-Universität zu Berlin developing an online semi-automated business intelligence (business research)
system using machine learning algorithms.
Product
The semi-automated business intelligence system is designed to help companies do market and investment research more effectively by automating components of the business research process while integrating real-time
feedback from the human researchers using the system. The system will be delivered online as a software as a
© IKS Consortium
2013
77 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
service basis. The startup project has been accepted to both the Microsoft BizSpark and the IBM Global Entrepreneur programs, and we are actively exploring integration of our product with their products for archiving,
analyzing and sharing data and information produced by our system.
Vision
Once documents (HTML pages, PDFs, text documents or other formats available on the web and on company
intranets) have been discovered by the business intelligence system, Stanbol can aid in identifying important
terms, which can in turn serve as an input for discovery and relevance classification of further documents, in
addition to inputs and feedback provided manually by users.
Product Use Case
The primary use-case for the semi-automated business intelligence system is the department of a large or medium-sized company or financial institution engaged in external research (sourcing and structuring information
that comes from outside the organization). This could include the new product development department evaluating new product ideas, the marketing department exploring new market segments and competitors, the strategy
or planning department building future macroeconomic scenarios, the legal or compliance department assessing
new and existing regulatory requirements, or the investment analysis department analyzing new investment opportunities. In all of these cases, one or more researchers will use the business intelligence system to organize
their research work and to store and share their research results.
Stanbol and VIE Integration
•
•
•
•
Named entity recognition in web documents: Documents that were found by our users will be enhanced
using Stanbol. This will give a better overall experience to our customers.
Important term mining: Our system will find important terms in user compiled document collections.
Important terms are terms that are specific to a collection and that help to discriminate it from other collections. We will use machine learning techniques to do this. The discovered terms will be fed directly
into a Stanbol-usable knowledge base.
Visualization: Stanbol and VIE will highlight named entities and important terms in documents and will
link them with other documents in the document collection that contain the same term. Those documents will be highlighted dynamically. There will also be some visual cues about how similar other
documents are to the current one, based on similarity induced by the important terms.
User-initiated highlighting in web pages: Users can highlight text in web pages. The highlights will be
stored and can be used as a hint for important terms. We are developing the highlighting based on hallo.js. We have had hands-on training at the IKS Hackathon in Salzburg on VIE editor.
Validation
Validation will be conducted with our pilot customers, such as one of the largest financial institutions in the
world in London which has submitted a letter of intent to test the system. Integration of the business intelligence
system with Stanbol and VIE will be deployed on our own existing dedicated server first to a limited community
including both pilot customers and partners and then in a limited version in a public-facing instance.
Planned Tasks
•
•
•
•
•
•
•
•
Step 0: Project inception and roadmap
Step 1: Development of highlighting mechanism for users
Step 2: Integration of Stanbol NER service into the research system
Step 3: Development of Frequent Term Mining functionality
Step 4: Development and integration of Frequent Term Mining knowledge base
Step 5: Visualization of named entities and frequent terms
Step 6: Visualized term-to-document and document-to-document relations
Step 7: Documentation and user feedback
Potential Further Enhancements
This is a list of enhancements beyond the scope of this Early Adopter’s proposal that could be incorporated in
the business intelligence system in the future:
• It could be used for classification: to develop a classification algorithm for classification of web documents discovered by users of the business intelligence system
© IKS Consortium
2013
78 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
•
More advanced analysis of similarities of documents with other documents can be developed based on a
wider range of attributes: more terms and document metadata.
Performance of Contract
The terms of the contract are:
• Start of contract is November 2012
• IKS component for validation is Stanbol and VIE
• Demo preview available early December 2012
• Limited demo system (showing key features without revealing all proprietary aspects of the pre-release
business intelligence product) available December 2012
• End of contract end December 2012
• Total remuneration for this contract is 6500 euro
Skills
Conatix will assign a developer to the integration project with the following skills: A skilled Javascript and Java
programmer with more than 3 years of full-time experience including selected Javascript libraries such as backbone.js, also knowledgeable about (any) Apache libraries, and with knowledge and experience in CMS. Possible
prior knowledge of Apache Solr and Apache Tika, and above all Apache open source development and integration experience. Machine learning expertise is valuable but not required for this project as it exists elsewhere in
our team.
Online Demo
A semi-public and a (more limited, prior to the full product launch) public demo will be deployed on our dedicated server.
Visibility
•
•
•
The business intelligence startup company will mention the use of Stanbol and VIE in the product website and specification documents
When our business intelligence system product is launched, press releases will mention the IKS project
Marketing of our product will thereby contribute to general awareness on the part of a high-level corporate and financial audience (including their IT departments as well as business functions) of IKS
Contribution
We will contribute selected text classification and/or term mining enhancements to Stanbol to make the term
mining currently in Stanbol better in the future. Stanbol currently has text classification but no term mining. It
would be useful to include term mining in Stanbol because it would enhance capabilities for classifying similar
sentences and phrases.
5.3.16
Fluid Operations
Introduction
The Information Workbench is a platform for developing Linked Data applications in the enterprise. Targeting
the full life-cycle of Linked Data applications, it facilitates the integration and processing of Linked Data following a Data-as-a-Service paradigm. UI development is based on Semantic Wiki technologies, combined with a
large set of predefined widgets for data access, navigation and exploration, visualization, analytics, as well as
data mashups with external data sources.
Data integration is supported through so-called data providers that gather information from the source, convert it
into RDF, and materialize the RDF output in a central data store. Besides built-in mechanisms to integrate semantic data formats such as RDF dumps or data from SPARQL endpoints, the Information Workbench contains
generic providers supporting the fast integration of legacy data sources such as relational databases, spreadsheets, Web data, and enterprise-internal systems. The integrated data is managed as integrated data graph. Resources in the data graph can additionally be associated with unstructured content, in the form of text or media
files. Further, every resource in the data graph is automatically associated with a Semantic Wiki page. The Semantic Wiki thus brings the ability to manage and interlink large amounts of structured and unstructured content
imported from existing sources or generated by end users, who can collaboratively annotate, complete, and up-
© IKS Consortium
2013
79 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
date content. Accounting for the coexistence of structured and unstructured data, the platform implements advanced search and information access paradigms, ranging from keyword search to complex graph pattern-based
search, supporting the user in constructing expressive search queries.
In the Information Workbench, content enrichment components can be used to augment the unstructured content
and contextualize/link it to structured data of the Linked (Open) Data graph. In this way, parts of the unstructured content are annotated with corresponding entities/facts stored in the semantic data repository. These features are particularly important in the context of semantic content publishing scenarios, in which large volumes
of unstructured free-text content have to be created, annotated using the data model, and published. As an example, the Information Workbench is used to support the Dynamic Semantic Publishing at the BBC
(http://www.fluidops.com/solutions/semantic-authoring-publishing/). In such scenarios, automatic content enrichment can be utilised to suggest annotations to the user based on the content of the textual document and,
possibly, highlight the potential interlinks between structured and unstructured content that were originally omitted by the user. Information Workbench supports enrichment of unstructured content by plugging in third party
enrichers (such as OpenUp and Luxid) with a semi-automated tagging workflow. As part of this project, we want
to integrate Apache Stanbol as an enricher for annotating textual content with semantic data and, in particular, to
compare its capabilities with other solutions in the context of semantic media publishing scenario.
Use-Case
In the first step we would want to leverage Apache Stanbol to implement "Story 05: Assistance with Semantic
Tagging". The use case is situated in the domain of Competitive Intelligence. As a part of the demonstration
scenario we will use a corpus of public documents from the domain of business news and use Stanbol Enhancement Engines (in particular, DBpedia Spotlight integrated into Stanbol) to annotate them with semantic data
from DBpedia. These annotations will be used to visualise the collection of documents using different data
presentation widgets implemented in Information Workbench.
In the long term (out of the scope of this proposal), fluid Operations will investigate the possibility to include
semantic content enrichment based on Stanbol as a part of the standard product configuration for semantic content publishing scenarios.
Validation
1. From the usage point of view, the quality of produced annotations will be verified in the test environment where they will be used to present the document collection to the user.
2. From the development point of view, comparison with other content enrichment solutions already integrated with the Information Workbench platform in the past will help to validate the usability of Stanbol APIs and software services.
Performance
1. start of contract: 01 November 2012
2. selected components are: Apache Stanbol Enhancement Engines
3. integration will be done by: fluid Operations AG
4. demo system will be available:
1. as an optional module for the IWB Community Edition (http://www.fluidops.com/informationworkbench/)
2. and as an online, public demonstration system including the Information Workbench solution
utilising Stanbol components installed on premise at fluid Operations by November 30, 2012
5. end of contract: 30 November 2012
6. Total remuneration for this contract is 6500 Euro.
Planned Tasks
fluid Operations AG will implement a solution module for the Information Workbench system (solution) that
will utilise Stanbol enhancement modules to perform on-demand (real-time ?) semantic annotation of textual
documents.
This work will include the following subtasks:
1. Development of the Information Workbench extension module which will realize the interface with the
Apache Stanbol Enhancer API. This module will be responsible for passing the textual content to the
Stanbol service and retrieving the semantic annotations.
2. Development of the visualisation mechanism for presenting the annotated content to the user highlighting the retrieved annotations and providing links to corresponding semantic data entities.
© IKS Consortium
2013
80 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
3.
Implementation of the demonstration scenario applying Stanbol to a corpus of pre-existing media documents from the business news domain (in particular, from New York Times and/or The Guardian
newspaper web sites) and presenting the document collection using existing Information Workbench
visualisation widgets.
Online Demo
The application will be deployed on the fluid Operations web server and made available as an online public
demo.
Visibility
fluid Operations AG is going to use the Information Workbench integrating Stanbol as a show case for potential
customers to demonstrate the advanced possibilities offered by automated semantic content enrichment to facilitate semantic media content authoring and publishing. The integration between the Information Workbench will
increase the visibility of Stanbol both to business organisations performing semantic content publishing, which
are prospective customers of fluid Operations, and to research organisations, which collaborate with fluid Operations through partnership or participation in research projects.
5.3.17
Manafactory
Introduction
Twistory [1] is a social media dashboard to help organizations become Socially Engaged Enterprises, providing
a comprehensive overview to understand and gain insights about social media through metrics, measurement and
analytics reporting.
Most of today’s approaches when looking at influence monitoring take into account the interaction pattern analysis (this is the case for Klout.com or of the LinkedIn InMap social graph); these tools look at the dynamics of the
interaction primarily rather than content; they can determine how far an individual posting that you make will
spread across the people that follow your comments on Twitter or how often on average something you say is
shared and propagated by others. Though extremely valuable the interaction pattern analysis shall be combined
with a real-time trend analysis of semantics [2] that properly augment quantitative data using language detection,
topic analysis and entity recognition against single interactions, historical or targeted streams and contents shared
using short URLs. In the Social Web, specifically on Twitter where interaction are limited to 140 characters, user
engage and share a wealth of contents using links (these links represents accordingly to Twitter 25% [3] of the
overall volume of tweets shared every day), adding a semantic layer to these contents can convey a great deal of
meaning and useful insights on the core topics being analysed. This is particularly true for brand reputation and
crisis management scenarios where in simple words it all comes to meaning and relevancy.
Vision
Twistory is a software and a method to make social media monitoring accessible to everyone, be it an enterprise,
an individual or a small team. The platform is available as Software as a Service Model (SaaS) and it’s bundled
with our consultancy services to help clients interpret the data and take actions over Social Media.
Use-Case
Twistory provides a dashboard allowing users to manage key topics over twitter using keywords and hashtags.
The user can also define a flat taxonomy of topics to organise the overall monitoring task he/ she is performing.
For each keyword/hashtag a request on the twitter firehose is performed on schedule basis; this request returning
a list of tweets and for each tweet its attributes every tweet is stored with its attributes (twitter id, user, date,
reply id, profile image url) and stored on the application DB (MySql) - links are stored separately and connected
with the originating message. The dashboard provides a real-time overview of the activities around each keyword/hashtag letting the user check the single interaction and analyse the overall trend. An extra layer of informations is added to augment the sentiment (positive or negative - added manually) and how the message relates
to the flat taxonomy defined within the monitoring session.
In the use case considered for this proposal the semantic integration will add the possibility to integrate the
metadata of each interaction with three types of entities: persons, organizations and places and with the detected
language. A new record type will also be added for the links (related to the originating interaction) and augment
them with their semantic attributes.
© IKS Consortium
2013
81 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
From the user experience point of view the semantic layer will allow us to implement the following visualizations to the existing reporting:
• a geo map with the entities “places” (for interactions and for links)
• a tree map presenting the semantic entities organized by volume (links only)
• an histogram of entities detected in links
• a cake for the language used (for interactions and for links)
Validation
This Early Adopter proposal is for the first time proposing the evaluation of Apache Stanbol and the IKS framework in a social media monitoring scenario.
The core technical challenges are related to:
• using Apache Stanbol engine for language detection
• using Apache Stanbol content enhancement capabilities analyzing contents in Italian (this will provide a
validation to the Freeling engine implementation (https://github.com/insideout10/wordliftstanbol/tree/master/freeling-engine - a community developed engine supporting Italian)
• providing support for asynchronous job execution
• serving a consistent number of requests in timely fashion (a critical requirement for real-time analytics
tools)
On the commercial side the main challenge is to turn the adoption of content enhancement (and eventually semantic linking) into a sustainable business model to be added and proposed on top of the existing one [4].
The result of this proposal will be tested in the real-world in conjunction with one of our clients: ATAC [5] the
municipal agency in charge of the public transport network of Rome (twitter profiles @atac and @infoatac).
This specific client and more generally social media monitoring applied to public transport infrastructure provides a valuable field for testing the results in terms of: 1) brand awareness, 2) service monitoring and 3) crisis
management.
Performance
In the context of real-time social media monitoring challenging performance requirements in terms of amount of
data (number of calls and frequency) and time required for each textual content to be analysed do require a careful evaluation of the overall service architecture and its scalability.
The terms of the contract are :
• Start of the contract, November 2012
• IKS components for validation is the Apache Stanbol
• Demo system available 18 December 2012
• Validation interview in 22 December 2012
• End of contract 31 December
• Total remuneration of this contract is 6500 Euro
Planned Tasks
•
•
•
•
•
Apache Stanbol will be configured with the required engine (these will include the standard engine and
the Freeling engine)
A set of RESTful APIs will be implemented in order to provide an integration layer between the semantic enhancement capabilities of Stanbol and Twistory - this layer shall be asynchronous
the enhancements related to messages and links will be added as RDFa attributes and stored in the application DB
Disambiguation options (as well as the possibility to remove the detected entity) will be available on the
administration interface
The reporting will be integrated with: a) a geo map with the entities “places” (including a marker to differentiate between location related to messages locations related to links) b) a tree map with semantic
entities organized by type and volume of occurrence and c) an histogram of entities detected in both
links and messages d) a cake to display the language (for both messages and links)
Online Demo
Being Twistory already commercially available a screencast will be published on the website and an online
demo will be accessible to clients requesting access to the tool.
Visibility
© IKS Consortium
2013
82 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
The solution will be actively promoted to the existing client-base with a dedicated section on the website, a
newsletter and an hands-on meetup focusing on Semantic Marketing, Social Media and Content Strategies (to be
organized in Rome, Italy) where the results of this proposal will be presented. The validation will be done in a
real-world scenario (ATAC).
Future / Other aspects
At this stage the proposal highlights a first augmentation of the stream by leveraging on semantic enhancement
of tweets and of textual contents linked in the tweets. The plan of integration also comprises the following:
• Use the annotated content (both tweets and links) to train content classification (using the topic classification engine) hence providing a further layer of analysis of the stream and its associated contents;
• Use semantic indexed content (links only) to provide Enhancement Engine that finds related content
(within a specific range of annotated websites) that can be “suggested” to the Social Media marketing
team (in near real-time) for expanding and/or balancing a specific discussion thread.
These further implementations will provide a significant hedge for both social media and content marketing
strategists. Contents that have been previously semantically indexed (using the various plugins developed within
the IKS project) could be promoted while sustaining the overall social media strategy.
References
•
•
•
•
•
[1] Twistory - Your Social Media Analysis Platform, www.twistory.it
[2] Marie Wallace - Social Analytics is more than just Social Media, allthingsanalytics.com
[3] Techcrunch - Twitter Seeing 90 Million Tweets Per Day, 25 Percent Contain Links,
www.techcrunch.com
[4] Twistory - Pricing structure, www.twistory.it
[5] Atac - Public Transport Agency of the city of Rome, www.atac.roma.it
5.4 CMS End-Users
5.4.1 SEWEBAR
SEWEBAR (Semantic WEB Analytical Report) is a research project the goal of which is to study possibilities
both of presenting results of data mining in the form of analytical reports and of disseminating resulting analytical reports through semantic web technologies. Ambition of this project is to become a framework covering the
whole lifecycle of analytical reports: starting from the elicitation of knowledge from the domain expert, initialization of the data mining tasks, design of the analytical reports, to search over multiple mining results.
Use-Cases
Data Definition
•
•
CMS Admin/Manager defines data sources. Presently data sources are SPARQL endpoint and TMRAP
webservices. In the extension it could be any service provided by FISE engine.
CMS Admin/Manager defines query templates and/or often-repeated queries. These are strongly associated
with data sources to be used with.
Knowledge Usage
•
•
Reporter builds query based on templates and the system sends request to designated data source.
Reporter uses query results inside CMS text editor (presently WYSIWYG editor, possibly Aloha Semantic
editor)
Asynchronous Data Definition/Querying
Tasks in data mining can be very time consuming. In these cases the user would build the query and request the
data source. The response should be received asynchronously so user is not active waiting.
Validation and Visibility
© IKS Consortium
2013
83 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
•
•
•
Internal validation by students of dataminig class
Deploy stable solution to our research partner, where the system is used by cardiologists.
Publishing CMS extensions to Joomla! community.
Performance
The only open performance issue is related to Asynchronous Data Definition and Querying. As far as this is not
solved in FISE it is common objective we want to achieve.
IKS Team Feedback
This is an Academic driven initiative rather than community or industry. We are therefore reluctant to assign an
early adopter contract, however we will revisit this decision in 2011.
5.4.2 Cytogenetics Labs
Early Adoption and Validation Proposal
This proposal considers an adaptation of IKS Software Stack to support genomic data analysis and exploration.
The proposal will be realized as an extension of existing IMID2py service. IMID2py is a tool used by Institute of
Mother and Child, Warsaw, Cytogenetic Lab to gather, analyse, and revise data from Array Comparative Genomic Hybridization (aCGH), performed on DNA samples from patients.
Use-Case
1. User explores aCGH experiment data pre-analyzed and stored in IMID2py service. User selects an interesting genomic region together with enumerated known genes contained inside it.
1. User selects one to many available Linked Data sites (availble through EntityHub) to search
for genes names in the region: (either Entity search, if gene names were matched for appropriate URI before, or Find label based search over all sites). Linked Sites: KEGG Pathway,
GeneOntology, PubMed,...
2. User may click on the object which allows content enhancement, in particular gene symbol or
genomic segment. Widget will allow to search within Linked Data appropriate for the selected content (KEGG Pathway, GeneOntology, PubMed).
1. Returned matching enhancement will be presented to user on the active page within
the widget. User can select which part of the returned content should be saved for
later, as attached to the actually browsed experiment.
2. Enhanced saved content is further extendable with appropriate Linked Data, or user
own comments, or tags/labels.
3. User navigation within a tree of enhancements is resolved using pop-up javascript
widget based on VIE^2 Widgets.
2. User can search within enhancements made to experiments he owns. A summary of hits is presented as
a result.
Validation
Online Demo
© IKS Consortium
2013
84 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Dedicated web page will be set on our website http://bioputer.mimuw.edu.pl/iks containing demo with example
data and tests of implemented functionalities.
Feedback from end users
The semantically enhanced system will be presented to the IMID Cytogenetic Lab. We’ll advise on the usage,
gather feedback from end-users, and produce a report about end-users feedback.
Apache Stanbol Semantic Data Manager plugin for web2py framework
The plugin will be submitted to http://web2py.com/plugins with several examples and test cases. Plugin will
allow for data transfer from web2py framework to Apache Stanbol, access to Stanbol components, /contenthub),
plugin will allow for queries/enhancements to be presented from within web2py using VIE,VIE2 widgets.
Performance
We will ask several people from the cytogenetic labs to use the platform at the same time and report their feeling
about performance.
We will run automatic semantic data enhancement tasks for multiple experiments from our database and measure
an average time required for completion. We will report results on the time-to-query-complexity.
Planned Tasks
§
preparation of test infrastructure (installing apache stanbol and web2py framework) configure EntityHub to
work with bioscience databases (KEGG Pathway, GeneOntology, PubMed,...)
§
implementation of an interface for enhancing genes/regions with linked data from services available through
EntityHub, using VIE^2 widget
§
hierarchical enhancement and annotation of genomic data controlled by a user
§
use /contenthub service to store and retrieve user-enhanced genomic data
§
implement search within user-enhanced data (providing Apache Stanbol /contenthub provides necessary
functionalities)
§
Apache Stanbol Semantic Data Manager plugin for web2py framework
§
transfer data from/to database to Apache Stanbol triplestore (based
on http://web2py.com/semantic and/or KReS/reingeneer)
§
simple api to access EntityHub
§
display data (RDF/JSON) retrieved from Apache Stanbol
§
display enriched web page rendered with VIE^2 Widget within a web2py generated page
§
tests and examples of usage
Online Demo
An online demo will be available on the project website under http://bioputer.mimuw.edu.pl/iks .
Link to the demo will be placed on The Cytogenetic Lab website[1].
Visibility
The semantically enhanced IMID2py system will be presented to the IMID Cytogenetic Lab. We’ll advise on the
usage, and gather feedback from end-users.
Public visibility of the early adoption will be provided by the following actions:
© IKS Consortium
2013
85 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
§
Dedicated web page on our website http://bioputer.mimuw.edu.pl/iks containing demo
§
Link to the demo from IMID Cytogenetic Lab website
§
Submission of the plugin to http://web2py.com/plugins
§
Newsletter to web2py newsgroup http://groups.google.com/group/web2py
Performance
The terms of the contract are:
1. Start of contract 1st October 2011
2. IKS component for validation is the Apache Stanbol + VIE
3. Demo system available: 15 January 2012
4. Validation interview: 30 January 2012
5. End of Contract: 29 February 2012
6. Total remuneration for this contract is 6 500 Euro, excluding VAT.
5.4.3 World Heritage Organisation
Use Case
The problem
In the current situation, links under the various sections of the health topics are added either manually in the
same topic cover, or added to the external access data base and then pulled by the HT topic cover when that page
is published.
This needs to be done in a more automated way because the current situation requires much manual work. Furthermore, we risk not linking to the most updated, relevant content because we don’t know all the content being
published by the departments.
The aim
This proposal sets out the problem of maintaining the health topic
pages in the current system and proposes a way to improve this by:
§
automatically identifying content to be considered for inclusion under each health topic;
§
facilitating the organization of sections on health topics pages; and
§
enhancing the linkage to content through reducing the manual work and increasing the relevance of
links.
Also, it aims at facilitating access to health topics by categorizing content based on its nature and target audience.
The objective of this development is first to use a proper taxonomy to tag and categorize content and second to
give the editor the possibility to select links proposed by the system. While it may not reduce the workload related to maintaining these pages, it should greatly improve the quality of the pages produced.
The process
There are two sub processes:
1. Tagging content (automatic + users)
© IKS Consortium
2013
86 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Content will need to carry keywords to allow for classification within the health topic pages. Without a proper
tagging process, the automatic retrieval of links can not function. Development of this solution should be part of
this project scope.
Tagging needed
The tagging process should include the type of document (i.e. factsheet, PR, etc.). Some types can be detected
automatically and injected in the properties of the document. This will help in two main areas:
a. when deciding where this content should go (under which section)
b. when linking to this content this information is needed to fill automatically the link description tab under the
link text: Women and health: today's evidence tomorrow's agenda Press release (10.11.2009)
Automatic
As it will be difficult to guarantee that users adhere to the new approach of tagging content, the automatic tagging should be
considered as "the solution". This can be a special script or any other application.
In the preview stage, this script should be able to go through the text, analyses its content, checks for key topics,
keywords and countries names (matching predefined lists of controlled vocabulary and countries names variations) and injects this information in the meta data of the document and in the CMS4 DB. If users are not happy
about the findings of the script, they should be able to select alternatives manually, based on the predefined list.
Existing content can be tagged in the same way above—using the same script; all content in the CMS should be
tagged according to the new tagging criteria established for the new content.
User, manual tagging (if automatic tagging is not satisfactory)
For content added to the site once a solution is in place, internal users will need to ensure the content is tagged
and categorized properly in order for the retrieval process to work.
In addition to the tagging with keywords, internal users need to be able to identify which documents are the most
important ones. Tagging of content should be more intuitive in the system (visually distinguished from the rest
of the system components) and should be compulsory.
The following graph shows a proposed scheme for content tagging area in the CMS, based largely on what we
have in place today.
All fields will be filled automatically by the script. But the user will have the chance to modify them - but always
from the predefined lists. All examples above will be presented as drop down menus.
Retrieving links (system)
The editor is automatically notified when new content for a health topic section is added. S/he would be able to
check and decided to include it or not. For example, when users preview their health topics, the system would
know that this parent topic is, for example, "malaria", if the section to update is "general info", it would then
search in the DB for documents with parent topic "malaria" where labels correspond to the subsections of the
health topic page. It would propose a list of matches; the editors would then pick the links they would like to
use.
The presentation
If there are so many links that we can't show all, then we will need to use tabs for the sections. This means that
we will show only 2 links and provide access to the full list of links, for example like this When clicking the "+",
the section expands and shows the rest; This applies to all section.
© IKS Consortium
2013
87 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Manipulating content based on target audience:
If content is tagged based on target audience, we will be able to provide the same content in 3 different ways, but
on the same page using DIVs (hidden/visible).
If we imagine these 3 types of audience: 1. general public 2. health professional 3. media Then we can imagine
the sections on the health topic pages to be shown in 3 tabs (containers):
Clicking on the tab, users will see the content pulled out by the system based on tagging (this is not on-the-fly
retrieval); content has to be validated before by the editors, but not shown unless users click on that tab.
If we assume that visitors click on the "Media" tab, information shown on the health topic will include the flowing sections:
Possible solutions
One solution would come in three parts.
1. Keyword assignment This includes the development of the script to accommodate the new types of keywords
and the addition of the 5 other languages (for
metadata). It also encompasses running the script over existing content to assign keywords for all the legacy
content. A prerequisite for this: a. List of controlled key topics (health topics=Malaria). b. List of controlled
vocabulary (keywords=vaccine, key phrases=mosquito net). c. List of associated topics (intimately related topics
= HIV/TB) d. List of Country names (official + short = Syrian Arab Republic + Syria). e. List of document types
(Factsheet, PR, Guideline; Q&A, FAQ, etc),
2. New WebIt element For each health topic, we could create a WebIt page per language. Each of these pages
would use a new element to present content options. The element would pull all information based on a set of
keywords (i.e. malaria and factsheet) and present this as a list of options for the editor (in preview mode preferably). Then the editor selects which items to include on the health topic page. See mockup below
Each page could have as many elements as needed to categorize the health topic information: new categories can
be added by the editors.
3. Health topic page presentation The health topic page will need to be set up to handle the tabbing option as
requested.
5.4.4 SIMsKultur
Use Case
SIMsKULTUR Online acts as information and promotion platform for cultural events in the DACH region (concerts, operas, theater, dance, movies, ...). We want to test and use the technologies provided by the IKS Project
for a new part of the website where news about events can be published. The editor will be able to create and
maintain content in an easy intuitive way. The editor will get suggestions for related content or background information.
Example: A host of a music event writes a post about an upcoming event. There are two bands playing at the
venue XY.
The developed recommendation system should now provide related media files like images or videos, metadata
about the bands and venue (URLs, address, ...), similar bands, other related events for that venue or available
tickets. An other example could be a story about a new art gallery in a city. The recommendation system could
provide background data from the Linked Open Data cloud about the artists, paintings, other galleries in other
cities or similar events in the region.
1. Semantic Search using Apache Stanbol
2. Quick Navigation for logged in users (create new content, log out, ...)
3. Edit / Save options for CreateJS
4. Related content from own system / Linked Open Data suggestions
© IKS Consortium
2013
88 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
5.
6.
Related images and videos added to the content (annotated)
Inline Editing using CreateJS
Used Components
CreateJS
As front-end technology to enable easy user interaction.
Apache Stanbol
As backend technology to enable semantic analysis.
• Enhancer: Extract Knowledge
• Entityhub: Manage Entities and Topics
• Contenthub: Semantic Search
• CMS Adapter: Sync. CMS with Apache Stanbol (CMIS)
• Reasoners & Rules: validate extracted information
Drupal 7
As CMS extended with improved IKS for Drupal and other community modules.
Validation
The solution will be tested with real data like press releases and posts from customers. The solution will be tested if the automatic suggested data apply with the content of the post (german language). We will ask our customers if such a solution improves there work.
Planned Tasks
•
•
•
•
•
•
•
•
•
Create a new page with Drupal 7 and available communty modules
Use the available IKS for Drupal modules and improve them
Test if CMIS import from Drupal to Apache Stanbol works
Import Data from other sources (Ticketer, Partner, Open Data) into Stanbol
Test OpenNLP for german language and the news / event domain
Integrate CreateJS into Drupal to enable the user to edit content inline
Test different stories / posts for quality of recommendations /enhancements
Use it with “real customers” to get their feedback
Provide schema.org annotations
Visibility
The system will be available on a subdomain of simskultur.net and open for customers / users. Partner and customer of SIMsKULTUR Online will get informed about the new system and it's advantages. Developed / Improved code will be published as Open Source Software.
Online Demo
The system will be available on a subdomain of simskultur.net and open for customers / users.
Performance
•
•
•
•
•
Start of contract: 20th July 2012
Selected components: Apache Stanbol / CreateJS (VIE.js) Integration will be done by: SIMsKultur
Online
Demo system will be available: 20th September 2012
End of contract: 30th September 2012
Total remuneration for this contract is: 7.000 Euro
5.4.5 Software AG
Vision
© IKS Consortium
2013
89 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
For more than 40 years, Software AG has been inventing new and better ways to help organisations achieve
business results faster. Perfect communication is an important factor for business success. It is therefore important that a good knowledge transfer takes place within an organisation.
Use Case
We expect the following value:
• Easy to use
• Expansion of our internal document repository "Alfresco"
• Quickly and easy search of internal information or documents (e.g. by typing in keywords, faceted
search,...)
Validation
The aim of the project is the expansion and improvement of our existing document repository and knowledge
base.
Performance
•
•
•
•
Start of contract: 10 July 2012
Selected Apache Stanbol components are CMS Adaptor, ContentHub, and EntityHub
End of contract: by providing a Screen cast and evaluation report, but not later than 31 December 2012.
Because of the confidential contents of internal documents, the Software GmbH Österreich will make a
screen cast and an evaluation report and the of the IKS project - not later than December 2012.
Planned Tasks
The planned tasks are:
• Implementation of the relevant Apache Stanbol features
• Learn about the selected features
• Extended testing
• Evaluate the possible use within the company (global)
• Creation of an evaluation report and screen cast
Evaluation
Because of the confidential contents of internal documents, the Software GmbH Österreich will make a screen
cast and an evaluation report and the of the IKS project - not later than December 2012.
6 Summary of Evaluations
At the time of writing, 11 of the 20-signed early adopters had completed the contract including the validation
report. All 11 of the validation reports are available in this section. They are also available for the public in full
at http://wiki.iks-project.eu/index.php/Validation. In 2011 all early adopters are asked along with their required
validation contractual requirements such as online demo to also blog about their experiences and results on the
official IKS blog site. Along with this they are also asked to share their experiences on the various development
mailing lists such as the Apache Stanbol list. This dialogue between industry validators and IKS developers is
proving a major success in driving both development and early adopter recruitment. The immediate availability
of developer support on the mailing lists is compensating for the lack of documentation or tutorial material
online for the early adopters. In fact the policy is now that interested early adopters discuss their validation and
use case ideas with the IKS development community in advance of any contractual negotiations.
6.1 CMS Vendors
6.1.1 QuinScape
Demo
Available at http://opensaga.org:8084/iks-wiki
© IKS Consortium
2013
90 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Validation
It was possible to make the FISE engine usable by the OpenSAGA Wiki software. The RESTful service provided by FISE was usable as expected. A problem encountered was a missing Java client library.
This was resolved by using Apache Wink and Jena and learning how to use SPARQL. There were about half a
dozen candidates for a Java REST client library. All of them seem to be usable. Apache Wink was selected because it is already in the Apache Incubator. It was preferred to Jersey because it is not dependent on Oracle.
Jena was selected because it is used within the FISE engine. Potential alternatives such as Sesame were not
looked at.
The integration proved that FISE is able to serve and enhance content in scenarios where articles are edited by a
live team of editors (with an un-staged publication process, e.g. a highly dynamic semantic tag environment).
Several FISE engines were installed during development. Installation could not have been much simpler. No
performance issues were encountered during normal operation. There were no stability problems regarding the
FISE engine.
Lessons learned
We learned quite a few acronyms and fundamentals of corresponding technologies which belong to Semantic
Technologies in general (examples: RDF, SPARQL) or the IKS project. It would have helped to have some
guidelines/howto-articles or client-side Java-libraries which could have been used. But learning the fundamentals
of SPARQL and experimenting with it was worth the time because we now understand much better what can be
done.
As we had hoped in the beginning the integration code itself is not very long. Most of the work is done by either
Apache Wink which makes calling the RESTful service a matter of essentially one line of code or by Jena which
parses the RDF/XML document and executes the SPARQL query. Also the OpenSAGA Wiki software itself
simply calls a single "enhance" method.
We always used very recent snapshots of both FISE and OpenSAGA (internally following the release early release often principle).
Software components used
FISE engine as RESTful service
Apache Wink Client module for consuming Restful FISE web service
Jena
© IKS Consortium
2013
91 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Follow-up Interview and Discussion
Date: Tuesday 8 February 2011
Participants:
• Andreas Kuckartz and Tobias Biskup (Quinscape)
• John Pereira, Andreas Gruber and Rupert Westenthaler (Salzburg Research)
Notes:
è
è
è
è
è
è
FISE successfully integrated and demonstrated via online demo
Demo was presented to end customers
Interest from customers is high
QuinScape looks to integrate more IKS components to complement FISE
Internal project to begin March 2011 – towards a product extension for OpenSAGA
Demo to remain online throughout the next development phase
6.1.2 GOSS Interactive
Overview
The GOSS Semantic Demo is a demonstration of how iCM can be integrated with the IKS/FISE entity
extraction and enhancement framework to enhance articles with semantic data. This information is
then used to generate RDFa mark-up for those pages containing the article text. As well as FISE it
also makes use of the Jena/SDB triple store, the Joseki SPARQL query interface and Pubby to publish
information about the entities we create.
The demo adds a new tab to the iCM article editor (tabbed view only), labelled "Semantic". To retrieve
entities from FISE, the user expands the tree in the left hand pane. This causes the combined article
text (including summary etc) to be passed to the FISE server, which extracts and enhances entities
(people, places, and organisations) and returns these to iCM. An expanded tree is now shown containing entities divided into people, places and organisations. As well as those distinctions, the appearance of different entities reflects their properties as follows: 1) Entities which are already known to iCM
are shown with a black/solid icon representing the type of the entity. They can be expanded to show
any associated resources. If they have already been related to the article then their text is shown in
bold. 2) Entities which are not already known to iCM are shown with a grey icon. If they are enhanced
entities they can be expanded to show the external URIs they link to. A content menu allows external
URIs to be previewed.
An entity can be double-clicked or drag-and-dropped onto a node in the right hand pane to associate it
with the article. It is also possible to double-click a currently associated entity to break the link. Entities
that are known to iCM will be added to the article immediately but when a new entity is added a dialog
box is shown which allows the user to specify the category for the new entity and which external URIs
should be associated with it. The ability to select specific external URIs makes it possible for the user
to resolve ambiguity as to which entity is being referred to.
Newly added entities are immediately added into the iCM metadata system. An event handler adds
newly created entities to the triple store, typically within 15 seconds or so. The actual association between entities and articles is not recorded until the article is submitted; at this point the association
between the metadata representing entities and the article is committed to the main iCM database and
after a few seconds another event handler adds information about the article (including its links to the
associated entities and Dublin Core metadata) to the triple store.
Once the article is published, it is possible to view it in the context of the site. Selecting "view source"
on the article page reveals that there is a hidden 〈div〉 on the page containing RDFa markup. By using
a tool like the W3C RDFa extractor (http://www.w3.org/2007/08/pyRdfa/) or the Sindice inspector
© IKS Consortium
2013
92 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
(http://inspector.sindice.com/) and pointing it at the page, the information extracted can be seen in a
formatted form. This tool also provides links to the URIs for entities that have been generated by iCM,
clicking on these will return a page of information about the entity generated by Pubby. It is also possible to query the triple store directly using SPARQL.
Demo
A YouTube video showing the integration in action can be seen here.
To access the online demo system please send an email to tom.cooke or gary.ratcliffe at gossinteractive.com. We will provide you with a user account and access details.
Validation
A copy of the validation report can be downloaded from here
© IKS Consortium
2013
93 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
!"#$%&'()*%&"+,$&'-%)."/&)
.-#)0--1"2)34%")5677)
!"#$%&'(#)%"*
!"#$%&'()*+,-%&+$(.#/+$%-"+%.+$)0-$%'1%2%3.'(+$$%'1%+420)2-#',%'1%-"+%#,-+5.2-#',%
/+-6++,%#78%2,&%9:;%;-2,/'0<%=#11+.+,-%+,-#->%+?-.2(-#',%2,&%+,"2,(+*+,-%+,5#,+$%
2.+%('*32.+&%2(('.&#,5%-'%.+$)0-$%@)20#->%2,&%20$'%.+$3',$+%-#*+<%!"+%3+.1'.*2,(+%'1%
-"+%/+$-%(',1#5).2-#',%#$%&+-+.*#,+&%-'%/+%$2-#$12(-'.>%1'.%2%1#.$-%$-+3A%/)-%-"+.+%#$%2%
,++&%1'.%*'.+%&'*2#,B$3+(#1#(%C,'60+&5+%-'%/+%242#02/0+%-'%#,(.+2$+%-"+%,)*/+.$%'1%
+,"2,(+&%+,-#-#+$<%
+,-'.#-*/'0.)#1*
!"+%3+.1'.*2,(+%'1%;-2,/'0%1'.%+,-#->%+?-.2(-#',%62$%-+$-+&%)$#,5%DE%&'()*+,-$%1.'*%
F%&#11+.+,-%GH;;%(0#+,-%$#-+$<%%!"+$+%6+.+%$+0+(-+&%-'%/+%.+3.+$+,-2-#4+%'1%GH;;%
(0#+,-$A%-"+.+%2.+%-".++%('),(#0%$#-+$%I',+%J,50#$"A%',+%;('--#$"A%',+%K+0$"LA%',+%,',B
3.'1#-%$#-+A%',+%)-#0#->%('*32,>%2,&%2%,',B3.'1#-%'.52,#M2-#',<%%N.-#(0+$%6+.+%$+0+(-+&%
-"2-%"2&%2-%0+2$-%2%1+6%.+0+42,-%+,-#-#+$%#,%-"+%-+?-%/)-%2.+%'-"+.6#$+%->3#(20%'1%2.-#(0+$%
',%').%$#-+<%
89"%:;<)=/)3:"&)
%
H3+,OPQ%IRL%2,&%SO+-%2.+%-"+%-6'%OJT%+,5#,+$%-"2-%6+%(2,%)$+%0'(200>%2,&%6#-"')-%
-"+%,++&%1'.%2,%NQ9%C+><%%!"+.+%#$%2%6.233+.%1'.%-"+%H3+,OPQ%+,5#,+%&+4+0'3+&%/>%
GH;;%2,&%',+%/)#0-%#,-'%;-2,/'0U%1'.%*'$-%2.-#(0+$%-"+%.+$)0-$%3.'&)(+&%2.+%#&+,-#(20%
/)-%-"+.+%2.+%'((2$#',20%$*200%&#11+.+,(+$<%!"+%&/3+&#2%0''C)3%+,5#,+%62$%2(-#4+%1'.%
-"+$+%-+$-$%2$%6+00%6"#("%2(('),-$%1'.%2%$*200%,)*/+.%'1%-"+%$3).#')$%+,-.#+$%1'.%/'-"%
(',1#5).2-#',$<%
%
&"!
&!!
%!
6-57,+
8)729:;<=(5>
$!
?(+(@,25:;<=(5>
8)729:;/*(2=A'B1)..>
?(+(@,25:;/*(2=+*B1)..>
#!
"!
!
'()*+(
'+,-(.
/01,234,53)2.
%
%
!"+%5.23"%2/'4+%$"'6$%-"2-%1'.%-"+%-+$-%$+-%)$+&A%SO+-%.+-.#+4+$%*'.+%.+0+42,-%+,-#-#+$%
2(.'$$%200%(2-+5'.#+$<%%!"+.+%2.+%*'.+%$3).#')$%+,-.#+$%1'.%SO+-%/)-%-"+%1.2(-#',%'1%
#&+,-#1#+&%302(+$%2,&%'.52,#M2-#',$%-"2-%2.+%.+0+42,-%#$%2(-)200>%/+--+.%1'.%SO+-%-"2,%1'.%
H3+,OPQ<%%%
%
© IKS Consortium
2013
94 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
!"#$%&'()'&)*'"+,$-&"%&"./&'$%0&'1&2$&,"3"'$0&'1&)&4$5&(6%0*$0&51*0-&714'$%&,$--89&:;$'&
"-&)&2$''$*&+(1"+$&41*&)&-"%<,$&$%<"%$=&
!"#$%&'()(*%#+(,-(*%#+(
.13>)*"%<&'($&+132"%)'"1%&14&?>$%;@A&B&:;$'&5"'(&:;$'&),1%$&-(15-&'()'&1%,C&)&
-3),,&%632$*&14&*$,$#)%'&$%'"'"$-&)*$&)00$0&)%0&'($&%632$*&14&->6*"16-&1*<)%"D)'"1%-&
"%+*$)-$-&%1'"+$)2,C=&E($*$&01$-&%1'&)>>$)*&'1&2$&)%&1#$*),,&2$%$4"'&4*13&)00"%<&
?>$%;@A&'1&:;$'=&
&
&$!
&#!
&"!
&!!
6-57,+
8)729:;<=(5>
%!
?(+(@,25:;<=(5>
8)729:;/*(2=A':B:<=(5>
?(+(@,25:;/*(2=A':B:<=(5>
$!
#!
"!
!
'()*+(
'+,-(.
/01,234,53)2.
&
&
*%#+(,-(!"#$./0/1-(
E($&+()*'&2$,15&-(15-&)&+13>)*"-1%&2$'5$$%&'($&:;$'&;FG&$%<"%$&)%0&?>$%.),)"-=&&
?>$%.),)"-&"-&)&5$2&-$*#"+$&'()'&*$H6"*$-&)%&IAJ&K$C=&&J'&+)%&2$&-$$%&'()'&:;$'&)%0&
?>$%.),)"-&*$'6*%&+13>)*)2,$&%632$*-&14&*$,$#)%'&>$1>,$&)%0&1*<)%"D)'"1%-9&5"'(&
?>$%.),)"-&()#"%<&3)%C&4$5$*&->6*"16-&*$-6,'-=&&L15$#$*&?>$%.),)"-&>$*41*3-&
>11*,C&)'&"0$%'"4C"%<&>,)+$&%)3$-=&&?#$*),,&"'&516,0&%1'&2$&51*'(&+1%-"0$*"%<&6%,$--&
'($&>$*41*3)%+$&5"'(&>,)+$-&+16,0&2$&"3>*1#$0=&
&"!
&!!
%!
6-57,+
8)729:;<=(5>
$!
?(+(@,25:;<=(5>
8)729:;/*(2C,+,3.>
?(+(@,25:;/*(2C,+,3.>
#!
"!
!
'()*+(
'+,-(.
© IKS Consortium
2013
/01,234,53)2.
&
95 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
!"#$#%&!"'(")*+*"#&
!"#$%"&'($)#*+,$-"+,-$("#$.'+.+'(/+0$+1$#0(/(/#-$#2('&%(#3$)4$56#($("&($("#$789#3/&$
:++;<.$,&-$&)*#$(+$#0"&0%#=$
$
&"!
&!!
6-57,+
%!
8)729
:)00(-5;5<*(
$!
=(+(>,25
?35@;(A5(02,+
#!
=(+(>,25;(A5(02,+
"!
!
'()*+(
'+,-(.
/01,234,53)2.
$
$
>($-"+,-$("&($1#,$+1$("#$.#+.*#$?#0(/+0#3$/0$("#$-#($+1$&'(/%*#-$,#'#$?&(%"#3$)4$("#$
3).#3/&$*++;<.$#0@/0#A$$!"/-$/-$0+($-<'.'/-/0@$&-$?+-($+1$("#$.#+.*#$?#0(/+0#3$&'#$0+($
0&(/+0&**4$;0+,0$.<)*/%$1/@<'#-A$$B#$0##3$&%%#--$(+$?+'#$3+?&/0C-.#%/1/%$
/01+'?&(/+0$(+$/?.'+D#$("#-#$'#-<*(-A$$E*-+$0+(#$("&($3).#3/&$*++;<.$/0('+3<%#-$&$
0<?)#'$+1$-.<'/+<-$'#-<*(-$C$-+?#$+1$("#-#$&'#$3/11#'#0($.#+.*#$,/("$("#$-&?#$0&?#$&-$
("#$.#'-+0$0&?#3$/0$("#$&'(/%*#$,"/*#$+("#'-$F<-($"&D#$0&?#-$("&($.&'(/&**4$?&(%"A$$>($
,+<*3$)#$<-#1<*$(+$*++;$&($,&4-$+1$'#3<%/0@$("#$0<?)#'$+1$("#-#$.&'(/&*$?&(%"#-$
'#(<'0#3$&-$-+?#$+1$("#?$&'#$G</(#$,#&;A$
$
789#3/&$*++;<.$/-$&)*#$(+$.#'1+'?$-/@0/1/%&0(*4$)#((#'$&($?&(%"/0@$.*&%#-$0&?#3$/0$
&'(/%*#-A$$789#3/&$"&-$#0('/#-$1+'$?&04$G</(#$-?&**$H0@*/-"$(+,0-$#A@A$I(+;#-*#4$/0$
6+'("$J+';-"/'#$"&-$+0*4$&'+<03$KKLL$/0"&)/(&0(-$)<($"&-$&0$#0('4A$E'#&-$,/("/0$
(+,0-M$0&?#-$+1$#*#%(+'&*$,&'3-$#(%$&'#$0+($#2('&%(#3N$?+'#$3+?&/0$-.#%/1/%$?&(%"/0@$
,+<*3$)#$0##3#3$1+'$("#-#A$
$
9#'1+'?&0%#$,/("$#0"&0%/0@$+'@&0/-&(/+0-$%+<*3$)#$)#((#'$C$+'@&0/O&(/+0-$-<%"$&-$
6P5$&03$6PQ$&'#$0+($?&(%"#3M$&*("+<@"$("+-#$+'@&0/O&(/+0-$"&D#$789#3/&$.&@#-$
<03#'$("#/'$1<**$0&?#-A$$!,/((#'$/-$'#(<'0#3$)4$("#$-#&'%"$)<($0+($/3#0(/1/#3$&-$&0$
+'@&0/O&(/+0A$$!"#-#$&'#$*/?/(&(/+0-$+1$("#$3).#3/&$*++;<.$-#'D/%#M$0+($+<'$#0@/0#$
-.#%/1/%&**4A$
$
>$"&D#$&*-+$*++;#3$&($#0(/(4$#0"&0%#?#0($<-/0@$("#$R'##)&-#$#0@/0#N$"+,#D#'$&($
.'#-#0($("/-$#0@/0#$.'+3<%#-$(++$?&04$-.<'/+<-$'#-<*(-$(+$)#$<-#1<*A$$R+'$#2&?.*#M$1+'$
("#$%+01/@<'&(/+0$S.#06:9T56#(TR'##)&-#$("#'#$&'#$UV$+'@&0/O&(/+0-$/3#0(/1/#3$/0$
("#$W6+09'+1/($XW$&'(/%*#M$V$+1$,"/%"$&'#$'#*#D&0(A$$R+'$S.#06:9T56#(T3).#3/&$("#'#$
&'#$YV$+'@&0/O&(/+0-$/3#0(/1/#3M$V$+1$,"/%"$&'#$'#*#D&0(A$
,-++(.%&
!"#$56#($T$3).#3/&$*++;<.$%+?)/0&(/+0$'#('/#D#-$&0$&%%#.(&)*#$.'+.+'(/+0$+1$
?&0<&**4$/3#0(/1/#3$#0(/(/#-$&03$/-$&)*#$(+$#0"&0%#$&$'#&-+0&)*#$1'&%(/+0$+1$.*&%#$
0&?#-A$$Z+,#D#'M$?+'#$3+?&/0$-.#%/1/%$3&(&)&-#-$&'#$0##3#3$/0$+'3#'$(+$&**+,$?+'#$
0&?#3$#0(/(/#-$(+$)#$#0"&0%#3A$
© IKS Consortium
2013
96 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
!"#$%&$'
!"#$%&'(#'&%#$%')*%+,--&'*./%,$01.&%1/%*"&%$&20'*#+%*01%0$%#*%3)&$%')*%4-)5#3&%
+0*&()-#&$%6)-%*"&%-&*,-'&3%&'*#*#&$7%%
()&*&$++",'
!"&%8*0'1).%0,*)*0((&-%#3&'*#6#&$%*"&%9::::%2)$*%+)22)'./%-&6&-&'+&3%314&3#0%
&'*-#&$7%!"#$%044-)0+"%20*+"&$%*))%6&;%&'*#*#&$%;#*"#'%*"&%*&$*%$&*%*)%1&%,$&6,.%0*%*"#$%
*#2&<%*"&%0,*)*0((&-%$&*%#$%2)-&%044-)4-#0*&%6)-%#'*&-'0*#)'0.%'&;$%-&.0*&3%3)+,2&'*$7%%
-..)".'/0&1'.2"30$4'31$,$3&",.'
!"&%+,--&'*%&'*#*/%&=*-0+*#)'%4-)+&$$%3)&$%')*%;)->%-&.#01./%;"&'%&'*#*#&$%+)'*0#'%
0++&'*&3%+"0-0+*&-$%)-%')'?@'(.#$"%.&**&-$<%;"#+"%044&0-%0$%ABA%#'%*"&%-&*,-'&3%
&'*#*#&$7%!"#$%;#..%')*%1&%0%+)22)'%4-)1.&2%6)-%2)$*%)6%),-%+.#&'*$%1,*%3)&$%'&&3%*)%
1&%033-&$$&37%
!"#$%#&'()"*+#",-%(,"*./&"0*
!"#$%&#"'()*"')&'+",%&-#'.#'/%0-#')&'102),3"
<
;
:
9
!"#$%&#"'2)*"
8
=)&">0'?!"#$%&#"'2)*"@
7
6
5
4
4
544
644
744
844
944
:44
;44
%
!"&%01)5&%4.)*%$");$%*"&%-&$4)'$&%*#2&%C#'+.,3#'(%$)2&%4)$*4-)+&$$#'(%;#*"#'%#DEF%
0(0#'$*%*"&%.&'(*"%)6%*"&%0-*#+.&%*&=*%6)-%9G%0-*#+.&$%#'%*"&%HI&*%J%KLM&3#0%.))>,4%
+)'6#(,-0*#)'7%%!"&%.)'(&$*%-&$4)'$&%)1$&-5&3%"&-&%;0$%0-),'3%N7O%$&+)'3$%;"#+"%#$%
;&..%,'3&-%*"&%P:%$&+)'3%*"-&$").3%;&%'&&3%*)%2&&*%#'%)-3&-%6)-%@=*H8%')*%*)%*#2&%*"&%
-&Q,&$*%),*%C;&%+),.3%4-)101./%+)2&%,4%;#*"%0%;)->0-),'3%6)-%*"#$%1,*%.)'(&-%3&.0/$%
0-&%4&-"04$%')*%0++&4*01.&%6-)2%0%,$&-%&=4&-#&'+&%4)#'*%)6%5#&;%0'/;0/F7%
%
!"&%4.)*%1&.);%+)240-&$%*"&%-&$4)'$&%*#2&$%6)-%HI&*J314.))>,4%;#*"%HI&*%J%
KLM&3#0%*)4#+%$&0-+"7%%R#*"%314&3#0G%*)4#+%$&0-+"%)'&%0-*#+.&%#$%;&..%)5&-%*"&%P:%
$&+)'3%*"-&$").3%0'3%0')*"&-%#$%+.)$&%*)%#*7%%S'%0..%+0$&$%*"&%*#2&$%0-&%2,+"%.)'(&-%*"0'%
;#*"%314&3#0%.))>,47%%R&%;#..%'&&3%*)%*0>&%+0-&%*)%&'$,-&%*"0*%*"&%4&-6)-20'+&%)6%0'/%
&'(#'&$%;&%3&5&.)4%#'%*"&%6,*,-&%#$%;#*"#'%0++&4*01.&%+)'$*-0#'*$7%
%
© IKS Consortium
2013
97 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
)!
(!
'!
&!
+,-./0-,1234,15326178.9//:;.
%!
+,-./0-,1234,15326178.,73<#12/.3=1-,<>=6
1
$!
#!
"!
!
"
#
$
%
&
'
(
)
*
"!
""
"#
!
!"#$%&'("#')
"#$!%&'($))!'*!$+,-.,/012!/#$!%$&*'&3,1($!'*!4/,15'-!#,)!06$1/0*0$6!/#,/!/#$!2$1$&,-!
,%%&',(#!0)!)'.16!,16!(,1!%&'6.($!,6$7.,/$!%$&*'&3,1($!20+$1!/#$!&02#/!$1201$!
6$)0218!!"#$!65%$60,!-''9.%!$1201$!%&'+06$)!2''6!$1#,1($3$1/!'*!%-,($!1,3$)8!!
:';$+$&<!;$!;0--!1$$6!$1#,1($3$1/!$1201$)!;0/#!3'&$!6'3,01=)%$(0*0(!91';-$62$!
>$828!6,/,5,)$)!'*!$-$(/$6!3$35$&)!'*!-'(,-!2'+$&13$1/!5'60$)?!01!'&6$&!/'!%&'+06$!
3'&$!$1#,1($3$1/!'*!%$'%-$!1,3$6!01!'.&!6'(.3$1/)8!!!
!""#$%&'(!()(*#+,(%-./0#$,+(
*#+%,#-!"&#$(%).)
*#',(1234(5-6%+7(
@12-,16A'.1(0-!B!
C!*'&3$&!D&0/0)#!AE(-012!(',(#!0)!/'!#$-%!%.%0-)!*&'3!BF!)(#''-)!2$/!/#$!5$)/!*&'3!
/#$0&!509$)!/#,19)!/'!*.16012!*&'3!G$)/!D$&9)#0&$!A'.1(0-!,16!H:4!D$&9)#0&$!G$)/8!
I$-$,)$6!'1!FJ!K,E!FLBB8!
!
C16E!A''9!;0--!5$!/,9012!%,&/!01!(E(-$!/&,01012!*'&!2&'.%)!'*!E'.12)/$&)!01!/#$!5.0-6!
.%!/'!/#$!,11.,-!G022-$!K,210*0A,/!*,30-E!(E(-012!$+$1/!,/!H$;5.&E!I,($('.&)$8!
"#$!%.%0-)!;0--!-$,&1!/'!6$+$-'%!03%'&/,1/!)90--)!*'&!&06012!,)!;$--!,)!#,+012!)'3$!*.1!
'1!/#$0&!509$)8!"#$!/&,01012!;0--!(.-301,/$!01!,!)$&0$)!'*!01/$&=)(#''-!$+$1/)!#$-6!,/!/#$!
I,($('.&)$8!
!
"#$!G022-$!K,210*0(,/!/,9$)!%-,($!'1!4.16,E!BF!M.1$!,16!5&012)!/'2$/#$&!
$N%$&0$1($6!,16!(-.5!(E(-0)/)<!-$0).&$!,16!('33.10/E!(E(-0)/)<!)(#''-!(#0-6&$1!,16!
*,30-0$)!/'!$1O'E!,!2&$,/!6,E!'1!,!509$8!!
!
"#$&$!;0--!5$!*,30-E!,16!(#0-6&$1P)!$+$1/)!;#0(#!,&$!'%$1!/'!$+$&E'1$!01(-.6012Q!/#$!
R0660A,/!F8S!30-$!3.-/0=-,%!(#,--$12$<!/#$!PT'!I06$P!L8S!30-$!2&,))!/&,(9!&,(012!/&,(9!
,16!)/,/0(!509$!/03$!/&0,-!('3%$/0/0'18!!
!
U'&!/#$!,6.-/)!,16!9$$1!(E(-0)/)!/#$&$!,&$!/#&$$!&06$)!,-)'!/,9012!%-,($Q!/#$!K,210*0A,/!
>BFV!30-$)?<!/#$!W1/$&A,/!>XB!30-$)?!,16!/#$!A'33.10A,/!>SB!30-$)?8!
© IKS Consortium
2013
98 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
!
"#$%!&'(#$)*+&#'!#'!+,%!"*-'&(&.*+!/*'!0%!(#1'2!,%$%3!
!"#$"%%&'()*#+(,(*)'*#+(+(*-'
4%#56%7!8'29!.##:!
46*/%;7!<=#'%>!
?$-*'&;*+&#';7!@%;+!A%$:;,&$%!.#1'/&6B!=CD!A%$:;,&$%!@%;+B!@&--6%!"*-'&(&.*+B!
=%E01$9!F*/%/#1$;%!
!"#$%"&'()"*+$,-,
.*/+'0123'456)-7'
G'-6*'2.#1'/&6!H!
!
8E*$2!E&''&'-!/#)5#;%$!)*:%;!I*)0#1$'!J#&/%;!,%*$2!
.%6%0$*+&'-!+,%!/#)56%+&#'!#(!+,%!I*)0#1$'!J#&/%;!5$#K%/+!E&+,!*E*$2!E&''&'-!
/#)5#;%$!F#0%$+!L*$M&;3!
I*)0#1$'!J#&/%;!
!
F%6%*;%2!#'!HN!"*9!HOPP3!
!
I*)0#1$'!J#&/%;!&;!*!1'&Q1%!)1;&/*6!/#))1'&+9!5$#K%/+!(*/&6&+*+%2!09!@%;+!
A%$:;,&$%!.#1'/&6R;!8$+;!S!I%&;1$%!D%$M&/%!+,*+!!,*;!0$#1-,+!9#1'-!5%#56%!($#)!
I*)0#1$'!D/,##6!*'2!)%)0%$;!#(!+,%!E&2%$!/#))1'&+9!+#-%+,%$!+,$#1-,!+,%!;,*$%2!
%T5%$&%'/%!#(!!+,%!M&66*-%R;!&)5#$+*'/%!*;!*!/%'+$%!(#$!,#$;%!$*/&'-3!U,%!!*&)!#(!+,%!
5$#K%/+!E*;!+#!&)5$#M%!1'2%$;+*'2&'-!*'2!*E*$%'%;;!#(!+,%!)*'9!2&((%$%'+!
/#))1'&+&%;!&'!+,%!M&66*-%!09!/%6%0$*+&'-!+,%&$!/#))#'!0#'2B!+,%!,#$;%!$*/&'-!
&'21;+$93!
!!
U,%!/%6%0$*+&#'!%M%'+!E*;!!+,%!/16)&'*+&#'!#(!;%M%$*6!)#'+,;!E#$:!(#$!F#0%$+!L*$M&;!
*'2!(#$!I*)0#1$'!D/,##6!*'2!+,%!E&2%$!/#))1'&+9V!&'/612&'-!+,%!6*$-%!)&-$*'+!
/#))1'&+9!0*;%2!E&+,&'!;+*06%;!*/$#;;!+,%!I*)0#1$'!J*66%9B!;#)%!#(!E,#)!!E#$:!&'!
+,%!*$%*!(#$!#'%!#$!+E#!;%*;#';!*'2!;#)%!E,#!/,##;%!+#!;%++6%!&'!I*)0#1$'!E&+,!+,%&$!
(*)&6&%;3!
!!
F#0%$+!E#$:%2!E&+,!6#/*6!/,&62$%'!+#!/$%*+%!*'!%M#/*+&M%!)1;&/!;/#$%!)*2%!($#)!+*6%;!
#(!+,%!$*/&'-!/#))1'&+9!$%/#$2%2!09!$%;&2%'+;!B!E,&/,!/#)0&'%2!!0%*1+&(1669!E&+,!
;#1'2;!;5%/&(&/!+#!+,%!I*)0#1$'!*$%*!;1/,!*;!!+,%!'*+1$*6!;#1'2;!#(!0&$2!;#'-!!*'2!+,%!
;#1'2;!#(!+,%!-*66#5;B!+,%!(*$$&%$;!*'2!!0%66W$&'-%$;!E,&/,!*$%!1'&Q1%!+#!+,%!*$%*3!
!!
.#1'/&66#$!X$*,*)!L#'%;B!I%*2%$!#(!@%;+!A%$:;,&$%!.#1'/&6!*'2!I*)0#1$'R;!M&66*-%!
5,*$)*/&;+B!;*&2B!YU,%!;/#$%!/*5+1$%;!+,%!%;;%'/%!#(!*!M&66*-%!+,*+!E%6/#)%;!5%#56%!
($#)!*$#1'2!+,%!E#$62!E,&6%!$%+*&'&'-!*!$&/,!/16+1$%!*'2!,%$&+*-%3!!U,$#1-,!+,&;!
$%;%*$/,B!+,%!9#1'-!5%#56%!#(!I*)0#1$'!,*M%!6%*$'%2!*!6#+!*0#1+!+,%&$!6#/*6!,&;+#$9!
*'2!)*2%!M*61*06%!6&':;!E&+,!#62%$!)%)0%$;!#(!+,%&$!/#))1'&+9!!+,$#1-,!+,%!!
/$%*+&#'!#(!!+,%&$!#E'!!%M#/*+&M%!*'2!1'&Q1%!;#1'2!*'2!)1;&/*6!$%/#$23Y!!U%*/,%$;!
,*M%!0%%'!*06%!+#!1;%!*$%*;!(#$!/$#;;W/1$$&/161)!E#$:!&'!'1)%$*/9B!6&+%$*/9B!*$+!S!
2%;&-'!
!!
© IKS Consortium
2013
99 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
!"#$%&'()*'*+*%(,''()*'-".$*%/*'01'2-340"#%'5/)006'/)$6.#*%,'()*$#'7-#*%(8,'76"8'
87*/$-6'&"*8(8'1#03'()*'9$.*#'2-340"#%'/033"%$(:';'3-%:'01'9)03')-.'#*/0#.*.'
()*$#'09%'87*/$-6'3*30#$*8'01'60/-6'#-/$%&'6$1*'10#'()*'7#0<*/(,'')-.'()*'0770#("%$(:''(0'
)*-#'()*'87*/$-66:'/033$88$0%*.'=!'10#'()*'1$#8('($3*>''?04*#('@-#+$8''$%(#0."/*.'()*'
7$*/*8'-%.'-//037-%$*.'()*'(#-/A8'9$()'6$+*'(#0340%*'76-:$%&>'B)*'-".$*%/*')-.'()*'
/)-%/*'(0'+$*9'.$876-:8'01'()*'/)$6.#*%C8'90#A,'$%/6".$%&'.*8$&%8'10#'()*'2-340"#%'
D0$/*8'=!'/0+*#>'B)*:'+$*9*.'7)0(0&#-7)8'-%.'870A*'(0'?04*#('-40"(')$8'90#A'-8'-'
/03708*#,')$8'#06*'$%'()*'7#0<*/('-%.')09'()*'2-340"#%'D0$/*8'/03708$($0%'9-8'
3-.*>'E*(*#'5)*6(0%,'()*'7#*+$0"8')*-.(*-/)*#'-('2-340"#%'5/)006',''&-+*''-'87*/$-6''
()-%A8,'9)$68('7#*8*%($%&'()*'9$%%*#'01'()*'=!'/0+*#'.*8$&%'-9-#.';'F*-#'G'7"7$6'
=$-)#-%'H"$/A';9$()'-'/*#($1$/-(*'-%.'IJK'90#()'01'+0"/)*#8'.0%-(*.'4:'2-340"#%'
2*$8"#*'=*%(#*>'=033*30#-($+*'=!C8'9*#*'7#*8*%(*.'(0'-66'7-#($/$7-%(8'-8'-'6-8($%&'
#*3$%.*#'01'()*'7#0<*/(>'
!"#$"%%&'()*+",*(-'(#*.*.(/'
E*076*L'?04*#('@-#+$8,'M#-)-3'@0%*8,'E*(*#'5)*6(0%,'=$-)#-%'H"$/A'
E6-/*8L''2-340"#%,'2-340"#%'D-66*:'
N#&-%$8-($0%8L'O*8('P*#A8)$#*'=0"%/$6,'2-340"#%'5/)006,'2-340"#%'D0$/*8,'
2-340"#%'2*$8"#*'=*%(#*,'Q#(8'R'2*$8"#*'5*#+$/*'
!"#$%&'()#*'"+%,-,
0()*'1234'56+-/7'
5/0(6-%.=0"%/$6'S'
!*+*6073*%('4008('10#'?-+*%8/#-$&'
5/0(($8)'M0+*#%3*%('-77#0+*8'/0"%/$6C8'ITU3'4"8$%*88'76-%'
?-+*%8/#-$&'0+*#+$*9'
'
E6-%8'10#'-%'-34$($0"8,'3"6($;3$66$0%'7#0<*/('(0'6$%A'5/0(6-%.C8'(90'3-<0#'30(0#9-:8,'
/#*-(*'-'%*9'(09%'/*%(#*'-%.'#*+$(-6$8*'()*'4$&&*8('C4#09%1$*6.C'8$(*'$%'5/0(6-%.')-+*'
4**%'&$+*%'-'3-<0#'4008(>'
'
B)*'5/0(($8)'M0+*#%3*%(')-8'&#-%(*.'7#0+$8$0%-6'-77#0+-6'(0'V0#()'2-%-#A8)$#*'
=0"%/$6C8'ITU3$66$0%'4"8$%*88'76-%'(0'-6609'/0%8(#"/($0%'01'+$(-6'$%1#-8(#"/("#*'0%'()*'
60%&;-9-$(*.'?-+*%8/#-$&'.*+*6073*%(>'
'
B)*'-77#0+-6'%09'07*%8'()*'9-:'(0'4*&$%'$%;.*7()'.$8/"88$0%8'0%'76-%%$%&'-%.'
1"%.$%&'10#'()*'7#0<*/(>'
'
V0#()'2-%-#A8)$#*'=0"%/$6C8'W*-.'01'#*&*%*#-($0%'5*#+$/*8'X-"#**%'X/=0%-/)$*'
8-$.L'YO*'-#*'8(".:$%&'()*'(*#38'01'()*'7#0+$8$0%-6'-77#0+-6'01'()*'4"8$%*88'76-%'-%.'
9$66')-+*'1"#()*#'.$8/"88$0%8'9$()'40()'()*'5/0(($8)'Z"("#*8'B#"8('-%.'8$(*'.*+*607*#8'
?-+*%8/#-$&'2(.'0%')09'4*8('(0'7#0&#*88>'
'
YN4+$0"86:,'0%'-'#*&*%*#-($0%'8/)*3*'01'()$8'8/-6*,'()*#*'-#*'8($66'-'%"34*#'01'.*(-$68'
(0'4*'#*806+*.>'V*+*#()*6*88'9*'-#*'.*6$&)(*.'(0')-+*'7-88*.'()$8'/#"/$-6'3$6*8(0%*>Y'
'
Q8'7-#('01'()*'B-['\%/#*3*%(-6'Z"%.$%&']B\Z^'8/)*3*'60.&*.'9$()'()*'5/0(($8)'
Z"("#*8'B#"8('-'%*9'8*+*%;3$6*;60%&'."-6'/-##$-&*9-:'9$66'8(#*(/)'1#03'()*'=)-7*)-66'
<"%/($0%'01'()*'X_'30(0#9-:,'4*(9**%'`"#0=*%(#-6'-%.'V*9)0"8*,'8A$#('=-#1$%'-%.'
© IKS Consortium
2013
100 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
!"#$$%&'(%$)&(%#*%&'(%*#"+("%,-.(/$!"-)0%$&((1%2#"3$%&#%1)/3%2)&'%4)"51($%,#-6%-/6%
&'(/%&#%&'(%789%+#&#"2-:;%
%
<')$%2)11=%)/%&>"/=%"(1(-$(%?9@A+)11)#/%2#"&'%#*%B").-&(%)/.($&+(/&%*"#+%6(.(1#B("$;%
%
C#>/!)11#"%D(-6("%E)+%7!C-5(%$-)6F%G<')$%.(":%2(1!#+(%-//#>/!(+(/&%)$%-%'>0(%
$&(B%*#"2-"6%*#"%&'(%*>"&'("%"(0(/("-&)#/%#*%,-.(/$!"-)0;%
%
G<'(%<HI%*>/6)/0%2)11%+(-/%&'(%!"(-&)#/%#*%>B%&#%AJJJ%K#5$%#.("%&'(%*)"$&%$)L%:(-"$%#*%
&'(%B"#K(!&%-/6%2)11%-11#2%>$%&#%1(.("%)/%>B%&#%?9@A%+)11)#/%)/%B").-&(%$(!&#"%
)/.($&+(/&;%
%
G<'-&%2)11%1(-6%&#%?M;@%5)11)#/%#*%)/.($&+(/&%#.("%&'(%NJO:(-"%1)*(&)+(%#*%&'(%B"#K(!&%
2)&'%&'(%!"(-&)#/%#*%M@=PJJ%K#5$;%
%
G<'(%!1#$>"(%#*%,-.(/$!"-)0%$&((12#"3$%2-$%-%'-++("%51#2%*#"%Q#"&'%D-/-"3$')"(%
-/6%R!#&1-/6=%5>&%&')$%-11#2$%>$%&#%$(!>"(%-%"(-1%-/6%B"#$B("#>$%*>&>"(%*#"%&'(%$)&(%-/6%
*#"%&'(%-"(-%-$%-%2'#1(;G%
%
7->"((/%7!C#/-!')(%-66(6F%G<'(%)+B#"&-/!(%#*%&')$%B"#K(!&%!-//#&%5(%
>/6("($&)+-&(6;%
%
G<'(%,-.(/$!"-)0%6(.(1#B+(/&%2)11%5")/0%9=AJJ%B("+-/(/&%K#5$%&#%&'(%7#&'("2(11%
-/6%S)$'-2%-"(-$%-/6%-&%1(-$&%AJJ%!#/$&">!&)#/%K#5$%6>")/0%&'(%$)L%:(-"%5>)16)/0%#*%
&'(%&#2/%!(/&"(;%
%
GH*%2(%2)/%*>11%-BB"#.-1=%2#"3%#/%&'(%"#-6%/(&2#"3%!#>16%5(%>/6("2-:%-$%(-"1:%-$%
/(L&%:(-";%
%
G<')$%#/(%"#-6%#B(/$%>B%.-$&%#BB#"&>/)&)($%*#"%&'(%2'#1(%#*%Q#"&'%D-/-"3$')"(%)/%
&("+$%#*%5>$)/($$=%!#++("!(%-/6%"($)6(/&)-1%"(/(2-1;%H&%2)11%"(1)(.(%-%'>0(%&"-**)!%
5#&&1(/(!3%-/6%B>&%7#&'("2(11%-/6%S)$'-2%*)"+1:%5-!3%#/%&'(%+-B;G%
%
T/6("%&'(%<HI%$!'(+(=%Q#"&'%D-/-"3$')"(%C#>/!)1%2#>16%5(%-11#2(6%&#%5#""#2%&'(%
!-$'%/((6(6%&#%!#+B1(&(%&'(%1)/3;%U>$)/($$%"-&($%"-)$(6%*"#+%&'(%/(2%&#2/%!(/&"(%
2#>16%5(%")/0O*(/!(6%-/6%>$(6%&#%"(B-:%&'(%!#$&$;%
%
V>&1)/(%B1-//)/0%B("+)$$)#/%'-$%-1"(-6:%5((/%0"-/&(6%*#"%&'(%2#"3$%2')!'%2)11%$((%
$#+(%(L)$&)/0%+-)/%"#-6$%2)6(/(6=%/(2%6>-1%!-"")-0(2-:$%5>)1&%-/6%-%/(2%
"#>/6-5#>&%/(-"%&'(%+-)/%(/&"-/!(%&#%R&"-&'!1:6(%W-"3;%
%
<'(%*)"$&%B'-$(%#*%6(.(1#B+(/&%-&%,-.(/$!"-)0%)$%2(11%>/6("2-:%2)&'%&'(%!#/$&">!&)#/%
#*%&'(%/(2%?8J+)11)#/%7#&'("2(11%C#11(0(%!-+B>$=%#B(/)/0%#*%&'(%?NM+)11)#/%
,-.(/$!"-)0%,(0)#/-1%RB#"&%I-!)1)&:%-/6%!#+B1(&)#/%#*%&'(%*)"$&%'#>$($%#/%&'(%$)&(;%
%
<'(%(/&)"(%B"#K(!&%)$%(LB(!&(6%&#%&-3(%>B%&#%NJ%:(-"$%&#%!#+B1(&(%)/%-%$(")($%#*%
$&-/6-1#/(%B'-$($%#.("%@J%&#%NJ%:(-"$=%!"(-&)/0%M@=PJJ%K#5$%-/6%-&&"-!&%+#"(%&'-/%
?M;@5)11)#/%)/%B").-&(%$(!&#"%)/.($&+(/&;%
© IKS Consortium
2013
101 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
!"#$"%%&'()*+",*(-'(#*.*.(/'
!"#$%"&'()*+"",'(-.#,)-/0"1'203'(-.)4"'
!%)-"5&'6)7",5-+)081'9-#:%),;1'./)$"/)%%1'<"=/#*5"1'.)+>0,1'<#+:/'?),)+@5/0+"1'
(#:/"+="%%1'A05/)=1'9:+):/-%B;"'!)+@'
C+8),05):0#,5&'9-#::05/'D#7"+,3",:1'<#+:/'?),)+@5/0+"'.#*,-0%1'9-#::05/'E*:*+"5'
F+*5:1'G*+#.",:+)%1'6)7",5-+)08'6"80#,)%'9$#+:'E)-0%0:B1'6)7",5-+)08'?:;1'
(#:/"+="%%'.#%%"8"'
!"#$%&'()#*'"+%,-,
0()*'1223'45+-/6'
9-#:%),;.#*,-0%'H'
./0%;'$+#:"-:0#,')3#,8'4"5:'0,'9-#:%),;'
9"+70-"5'+"-"07"'50I'7"+B'8##;'+"$#+:5'
J,:"+,":'5)>":B'-)3$)08,'
'
./0%;'$+#:"-:0#,'5"+70-"5'0,'<#+:/'?),)+@5/0+"'/)7"'+"-"07";'#,"'#>':/"'4"5:'+):0,85'0,'
9-#:%),;1'0,')'+"$#+:'$*4%05/";'4B'K('J,5$"-:#+):"'#>'G;*-):0#,'LK(JGMN'
'
J,5$"-:#+5'>+#3'K(JG'7050:";'<#+:/'?),)+@5/0+"1':/"'>#*+:/'%)+8"5:'%#-)%')*:/#+0:B'0,'
9-#:%),;1'0,'<#7"34"+'),;'O"-"34"+'%)5:'B")+':#'+"70"=':/"'-/0%;'$+#:"-:0#,'5"+70-"5'
$+#70;";'4B':/"'-#*,-0%'),;'0:5'$)+:,"+51'0,-%*;0,8'9:+):/-%B;"'!#%0-"1'<K9'
?),)+@5/0+"1'),;':/"'./0%;+",P5'6"$#+:"+N'F/"B')%5#'5$#@"':#'-/0%;+",1'$)+",:5'),;'
-)+"+5')4#*:':/"'5"+70-"5':/"B'+"-"07";N'
'
.#*,-0%'?");"+'.#*,-0%%#+'203'(-.)4"1'5)0;&'QF/05'05'),'"I-"%%",:'+"$#+:'=/0-/'
/08/%08/:5':/"'$#50:07"'=#+@'4"0,8';#,"'4B':/"'-#*,-0%'),;'#*+'$)+:,"+5':#'$+#:"-:'
-/0%;+",'>+#3'/)+3N'J:'$+)05"5':/"'$)+:,"+5/0$')$$+#)-/':#':/05'70:)%')+")'#>'=#+@1'
",5*+0,8'0,>#+3):0#,'05'5/)+";'4":="",')8",-0"5':#'$+#70;"':/"'4"5:'$#5504%"'5*$$#+:'
:#'-/0%;+",'),;':/"0+'>)30%0"5N'F/"'0,5$"-:#+5')%5#'+"-#8,05"':/"'/08/'%"7"%'#>'5@0%%5'
),;'$+#>"550#,)%053'#>'#*+'5:)>>'),;':/"'Q#*:5:),;0,8Q'%");"+5/0$'$+#70;";'4B'5",0#+'
#>>0-"+5'),;':/"'./0%;'!+#:"-:0#,'.#330::""N'F/"'50I'P7"+B'8##;P'+):0,85'3"),5'="')+"'
#,"'#>':/"':#$'>07"'$"+>#+30,8'-#*,-0%5'0,':/05'03$#+:),:')+")N'
'
QJ'=#*%;'%0@"':#':/),@'"7"+B#,"'0,7#%7";'0,'#*+'-/0%;'$+#:"-:0#,'5"+70-"5'>#+':/"0+'
-#330:3",:':#'$+#70;0,8'5*-/'R*)%0:B'5"+70-"5':#'5#3"'#>':/"'3#5:'7*%,"+)4%"'
-/0%;+",'0,'#*+'-#33*,0:0"5NQ'
'
A"')+"'3)@0,8')'$#50:07"';0>>"+",-"':#'-/0%;+",P5'%07"51'),;'#*+'5"+70-"5'="+"'
"7)%*):";'):'7"+B'8##;'S':/"'5"-#,;'/08/"5:'%"7"%'S'0,'")-/'#>':/"'50I')+")5'#>'
)55"553",:&'
'
''''T'-/0%;+",')+"'%05:",";':#'),;'+"5$"-:";U'
''''T'-/0%;+",')+"'/"%$";':#'@""$'5)>"U'
''''T'+"5$#,5"':#'033";0):"'-#,-"+,5U'
''''T'3"":0,8',"";5'),;'+";*-0,8'%#,8':"+3'/)+3U'
''''T'5"%>S"7)%*):0#,U'),;'
''''T'03$+#7"3",:5'0,'$"+>#+3),-"N''
'
© IKS Consortium
2013
102 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
!"#$%&'($)#*+),$-./#$0+1#$#2.1*3#0$+4$-++5$*).6,76#$78$9+),"$:.8.);0"7)#<$
7863=578-$>3.?$7,$0.4#<$.8$71.-78.,7/#$*)+-).11#$4+)$@$,+$AB$?#.)$+350$,+$"#3*$6"735)#8$
;##*$,"#10#3/#0$0.4#<$.85$,"#$&+,"#)C#33$D+1#0,76$EF=0#$G6)##878-$&+5#3<$C"76"$
#80=)#0$6"735)#8$-#,$,"#$"#3*$,"#?$8##5$C7,"+=,$5#3.?H$>3.?$7,$0.4#$".0$F##8$5#/#3+*#5$
C7,"$6"735)#8$.85$,#.6"#)0<$"#3*78-$784+)1$6"735)#8$.F+=,$*#)0+8.3$0.4#,?<$4+)$#2.1*3#$
,")+=-"$,"#$0.4#$=0#$+4$1+F73#$*"+8#0$.85$,"#$78,#)8#,H$
$
!"#$)#*+),$5#,.730$,"#$*.),76=3.)$0,)#8-,"0$+4$0#)/76#0$78$9+),"$:.8.);0"7)#$,".,$1.5#$.$
5744#)#86#$,+$6"735)#8$.85$4.1737#0I$
$
$$$$J$E5/76#$.85$*).6,76.3$0=**+),$,+$4.1737#0<$"#3*78-$,"#1$,+$+/#)6+1#$,"#7)$
*)+F3#10$.,$.8$#.)3?$0,.-#H$
$$$$J$E$=8747#5$.**)+.6"$F?$0,.44$.6)+00$0#)/76#0$,+$71*)+/78-$6"735)#8K0$374#$6".86#0H$
$$$$J$G#)/76#0K$*)+1*,$.85$#44#6,7/#$)#0*+80#$,+$4.1737#0$C"+$8##5$"#3*$+=,075#$+4476#$
"+=)0H$
$$$$J$L+);$F?$1.8.-#)0$.85$0,.44$78$)#/7#C78-$,"#7)$C+);$,+$71*)+/#$3+6.3$0#)/76#0H$
$$$$J$M=,0,.8578-$3#.5#)0"7*$.85$57)#6,7+8$*)+/75#5$F?$N"7#4$M4476#)0$.85$,"#$N"735$
>)+,#6,7+8$N+117,,##H$
$
>.=378#$%+--.8<$'85#*#85#8,$N".7)$+4$,"#$9+),"$:.8.);0"7)#$N"735$>)+,#6,7+8$
N+117,,##<$0.75I$O!")+=-"$,"#$N"735$>)+,#6,7+8$N+117,,##<$C#$"./#$C+);#5$".)5$,+$
1.;#$0=)#$*)+4#007+8.30$C+);78-$C7,"$6"735)#8$P$,#.6"#)0<$0+67.3$C+);$0,.44<$8=)0#)?$
0,.44<$8=)0#0<$Q>0$.85$*+376#$P$.)#$4=33?$.C.)#$+4$,"#$700=#0$.85$6.8$75#8,74?$#.)3?$.8?$
6"735)#8$.,$)70;H$!"#$)#*+),$"7-"37-",0$,"70$*.),8#)0"7*$.**)+.6"$.0$C#33$,"#$71*+),.86#$
+4$370,#878-$,+$6"735)#8$.85$4.1737#0<$=078-$,"#7)$/7#C0$,+$784+)1$5#6707+80$.F+=,$,"#7)$
4=,=)#<$.85$,"#7)$4##5F.6;$,+$71*)+/#$0#)/76#0H$
$
OL#$"./#$.30+$78/#0,#5$78$784+)1.,7+8$4+)$,"#$*=F376$.F+=,$,"#$)#0*+807F737,?$+4$
#/#)?+8#$,+$1.;#$0=)#$6"735)#8$.)#$0.4#<$.85$*)+/7578-$.5/76#$+8$C".,$,+$5+$74$?+=$
"./#$6+86#)80$.F+=,$,"#$C#33PF#78-$+4$.$6"735$+)$?+=8-$*#)0+8HO$
$
%&'($780*#6,+)0$.-)##5$+8#$.)#.$4+)$71*)+/#1#8,$C7,"$,"#$*.),8#)0I$,+$71*3#1#8,$
*3.80$,+$4=33?$78/+3/#$"#.3,"$0,.44$78$*3.8878-$78/#0,7-.,7+80H$!"70$".5$.3)#.5?$F##8$
75#8,747#5$F?$,"#$6+=8673$.85$7,0$*.),8#)0$.0$*.),$+4$,"#$0#34$#/.3=.,7+8$*)+6#00H$E0$.$
)#0=3,$+4$,"#$R=.37,?$+4$,"#$)#*+),<$%&'($C733$8+,$1.;#$.8?$1+)#$/707,0$,+$9+),"$
:.8.);0"7)#$78$6+88#6,7+8$C7,"$,"#$780*#6,7+8H$
$
L.8,$,+$;8+C$1+)#S$N376;$+8$,"#$378;0$+8$,"#$)7-",$+4$,"70$*.-#H$
!"#$"%%&'()*+",*(-'(#*.*.(/'
>#+*3#I$T71$&6N.F#<$>.=378#$%+--.8$
>3.6#0I$G6+,3.85<$9+),"$:.8.);0"7)#$
M)-.87U.,7+80I$%&$'80*#6,+).,#$+4$(5=6.,7+8<$%&'(<$G,).,"63?5#$>+376#<$9%G$
:.8.);0"7)#<$N"735)#8K0$V#*+),#)<$N"735$>)+,#6,7+8$N+117,,##<$9+),"$
:.8.);0"7)#$N"735$>)+,#6,7+8$N+117,,##$
!"#$%&'()*+#,-,
0()*'1234'56+-/7'
L.3#0N+=8673$A$
© IKS Consortium
2013
103 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
!"#"$%&%'()*+,"-./"*+-0'(&*1+1/"+,"*1+%(+2-3"*+
!"#"$%&%'(+/-*+4%5"+'4+1/"+.3"-("*1+-($+,"*1+0-(-&"$+,"-./"*+%(+2-3"*+-($+1/-1)*+
'44%.%-36+7,"#8*1981/+:';1/<+="9+>;-8+?-#,';#<+@#-"1/+8+A"(1#"+-1+B3-(&#-(('&<+
7,"#C'#1/+-($+@#"*-%1/+,"-./"*+/-5"+-33+,""(+-9-#$"$+1/"+%(1"#(-1%'(-338+#".'&(%*"$+
D3;"+E3-&+-9-#$+4'#+FGHHI+
!"#"$%&%'(J*+,"-./"*+-0'(&*1+1/"+,"*1+%(+2-3"*+
+
@/"+4%5"+,"-./"*+/-5"+'(."+-&-%(+,""(+#".'&(%*"$+4'#+1/"%#+.3"-(3%("***<+1/"+K;-3%18+'4+
1/"+*"#5%."*+C#'5%$"$+1'+,"-./+;*"#*+-($+1/"+/%&/+*1-($-#$+'4+9-1"#+K;-3%18I+
+
@/%*+8"-#<+="9+>;-8+?-#,';#+,"-./+9%33+,"+438%(&+1/"+.'5"1"$+D3;"+E3-&+4'#+1/"+
19"341/+*;.."**%5"+1%0"<+/-5%(&+9'(+1/"+-9-#$+"5"#8+8"-#+*%(."+FGGGI+
+
!';(.%33'#+L;#483+L5-(*<+!"#"$%&%'(+!-,%("1+M"0,"#+4'#+L.'('0%.+N"5"3'C0"(1+
-($+@';#%*0+/-*+9"3.'0"$+1/"+-9-#$*I++O@/%*+%*+5"#8+"(.';#-&%(&+("9*+-1+1/"+*1-#1+'4+
1/"+1';#%*1+*"-*'(I++@/"+-9-#$*+/-5"+,""(+-./%"5"$+-*+-+#"*;31+'4+-+*;.."**4;3+
C-#1("#*/%C+,"19"""(+-+(;0,"#+'4+!"#"$%&%'(+!';(18+!';(.%3+*"#5%."*<+3'.-3+
#"*%$"(1*<+5'3;(1-#8+&#';C*+-($+1/"+P=BQ)*+3%4"&;-#$%(&+*"#5%."IO+
+
Q(+-$$%1%'(+1'+1/"+D3;"+E3-&*<+HR+'4+!"#"$%&%'()*+,"-./"*+/-5"+#"."%5"$+FGHH+:"-*%$"+
79-#$*+-($+4';#+,"-./"*+/-5"+,""(+-9-#$"$+S#""(+!'-*1+*1-1;*I+
!"#$"%%&'()*+",*(-'(#*.*.(/'
A"'C3"T+L;#483+L5-(*+
A3-."*T+!"#"$%&%'(<+7,"#8*1981/+:';1/<+="9+>;-8+?-#,';#<+@#-"1/+8+A"(1#"<+
B3-(&#-('&<+7,"#C'#1/<+@#"*-%1/<+2-3"*+
U#&-(%*-1%'(*T+D3;"+E3-&<+!"#"$%&%'(+!';(18+!';(.%3<+P=BQ+
!"#$%&'()*+#,-,
0()*'1234'56+-/7'
2-3"*!';(.%3+F+
!"#"$%&%'(+B%,#-#%"*+2'#3$+D''V+N-8+FGHH+!'0C"1%1%'(+
S9"(33%-(+2%3*'(+4#'0+W*&'3+S8(#-$$+7,"#1"%4%+%*+1/"+9%(("#+'4+!"#"$%&%'(+
B%,#-#%"*)+2'#3$+D''V+N-8+FGHH+!'0C"1%1%'(I+S9"(33%-(+/-*+9'(+XHG+'4+,''V+1'V"(*+
1'+*C"($+'(+,''V*I+:/"+9-*+#"9-#$"$+-1+-+*C".%-3+-**"0,38+-1+/"#+*./''3<+W*&'3+
S8(#-$$+7,"#1"%4%+#"."(138I+
!"#"$%&%'(+B%,#-#%"*+2'#3$+D''V+N-8+FGHH+!'0C"1%1%'(+
+
@/"+.'0C"1%1%'(+9-*+1'+('0%(-1"+1/"+D''V+4'#+1/"+N-8Y+-(8+,''V<+-(8+3-(&;-&"+,;1+
1/"+1-*V+9-*+1'+3%*1+1/"+#"-*'(*+4'#+1/"+./'%."I+
+
S9"(33%-(+./'*"+M%./-"3+M'#C;#&')*+)@/"+D"*1+!/#%*10-*+A#"*"(1+%(+1/"+2'#3$)I+?"#"+
-#"+/"#+#"-*'(*+%(+/"#+'9(+9'#$*T+
+
)+Q+3%V"+1/%*+,''V+-+3'1I+Q+3%V"+1/"+*/-C"+'4+1/"+,''VI+Q1+3''V*+3%V"+-+C#"*"(1I+Q1+9';3$+,"+
-+C"#4".1+!/#%*10-*+C#"*"(1+4'#+-(8'("I+Q4+1/"+,''V+9-*+%(+08+*1'.V%(&+Q+9';3$+,"+*'+
/-CC8+,".-;*"+Q+3'5"+1/"+*1'#8+*'+0;./I+
+
© IKS Consortium
2013
104 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
!"#$%"&'()*"+%,-.&"/-'$"0"10."2-.3-.,"0"4%''%)5"6-1"7089$%)&(."/)('%"'$%"4%''%)5"#$%"
4%''%)"/0&"2(:.3".%0)4*"0"$:.3)%3"*%0)&"40'%)"-."0."(43"3%&;"-."0"+(<5"#$%"10."/$("
2(:.3"'$%"4%''%)"/%.'"'("2-.3"7)&"7089$%)&(.5"=$%"/0&"-."0".:)&-.,"$(1%"0.3"/0&"
&-''-.,"+*"'$%"/-.3(/5"=$%"'$(:,$'"'$%"10."/$("+)(:,$'"'$%"4%''%)"/0&"$%)"$:&+0.3"
6-1>"+:'"$%"$03"3-%3"-."'$%"/0)5"#$-&"+)(:,$'"+08;"1%1()-%&"'("7)&"7089$%)&(.5"
"
!"#$%"+%&'"90)'"(2"'$%"&'()*"-&"'$%"4%''%)5"?'!&"@$)-&'10&"0.3"'$%"A)-'-&$"0.3"'$%"B%)10.&"
940*"2(('+0445"#$%*"/%)%"'04;-.,"0.3"3)-.;-.,>"-'"/0&"&9%8-045"?"4-;%3"-'"/$%."'$%*"/%)%"
&-.,-.,"0"80)(45"?'"/0&"!='-44%"C08$'!"D"=-4%.'"C-,$'"0.3"'$%."'$%*"&0.,"0"4('"1()%5"
"
!"@$)-&'10&"-&"0"$099*"'-1%"0.3"?"2%4'"$099*"2()"7)&"7089$%)&(."+%80:&%"&$%"'$(:,$'"
'$0'"6-1"$03")%':).%35"?"2%4'"$099*"2()"6-1"+%80:&%"$%"$03"0",((3"@$)-&'10&"3:)-.,"'$%"
/0)"+:'"?"2%4'"&03"+%80:&%"$%"3-%3"&((."02'%)/0)3&5"
"
!"#$-&"/(:43"+%"0",((3"&'()*"2()"E"D"FG"*%0)"(43&5"?"4-;%"-'"+%80:&%"-'"-&"0"&$()'"+((;"
0.3"%0&*"'(")%035"?"80.")%1%1+%)"-'"044"'$%"'-1%5"?"4-;%"'$%"9-8':)%&"+%80:&%"-'"10;%&"
1%"2%%4"?"80."&%%"'$%"&'()*"0.3"?"$0H%"4%0).%3"0"4('"2)(1"'$%"&'()*5"
"
I-&-'"@0)3-,0."J-+)0)*"'("&%%"B/%.44-0.!&")%H-%/"0.3"'("+())(/"'$-&"&9%8-04"+((;"
*(:)&%42"
"
='0.3-.,"8(19%'-'()&"2)(1"4%2'"'(")-,$'"K4-."70-)>"7-;%*>"C0'0&$0>"B%(),%"0.3"
K4%0.()5"=%0'%3L"8(19%'-'-(."/-..%)"B/%.44-0."7(),0."0.3"@%)%3-,-(."J-+)0)-%&"
4-+)0)-0."M+-,0-4"@)((;5"
!"#$%&#'()'*#+#+',)
N%(94%L"B/%.44-0."O-4&(.>"7-8$0%4"7()9:,(>"6-1"78N$%)&(.>"K4-."70-)>"M+-,0-4"
@)((;"
N408%&L"P.(.%Q"
R),&L"@%)%3-,-(."J-+)0)-%&>"@0)3-,0."J-+)0)*>"S&,(4"B*.)033"M+%)'%-2-"
!"#$#"%&'&
-'"#).//0)12$(,3)
T'-4-'*"F"
7(()40.3"H-&-(."/-.&"8%4%+)-'*"+08;-.,"
"
-10,%"3%9-8'-.,"AA@"=9)-.,/0'8$"9)%&%.'%)"@$)-&"N08;$01"
AA@"=9)-.,/0'8$"9)%&%.'%)"@$)-&"N08;$01"
=(:'$"O%&'"O0'%)!&"0/0)3U/-..-.,"&8$%1%"'(")%V:H%.0'%"/%'40.3&"-."W%H(."0.3"
=(1%)&%'"$0&"/(."'$%"&:99()'"(2"AA@"/-434-2%"%<9%)'"@$)-&"N08;$015"
"
7(()40.3"$0&"+%%."3)0-.%3"2()"H0)-(:&":&%&"2()"(H%)"FXY"*%0)&"+:'"0".%/"9)(V%8'"'("
9:'"'$%"/0'%)"+08;"-."'$%"1-)%&"/-44"$0H%"+%.%2-'&"2()"/-434-2%"D"0.3"%H%)*(.%"/$("
3)-.;&"'09"/0'%)5"
"
A4(8;-.,"'$%"3)0-.0,%"3-'8$%&"%.0+4%&"1(()40.3"'(")%'0-."/0'%)>"$%49-.,"940.'"4-2%"'("
24(:)-&$"0.3"/-434-2%"'(")%':).5"O0'%)"/$-8$"24(/&"3(/."(22"'$%"$-44&"-.'("')%0'1%.'"
/();&"-&"84%0.%)"D"8:''-.,"8(&'&5"
"
© IKS Consortium
2013
105 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
!!"#$%&'()*+,-.#%&/0/(,/&#".&'0#1+-2.+3#'0#/(,.40'+0,'-#+564,#,./#5/(/7',0#,6#
*'898'7/:#;/#0+'9<#=>.'0#'(0%'&'()#%&6?/-,#.+0#,./#%6,/(,'+8#,6#&/+88@#5/(/7',#*'898'7/#
+(9#%8+(,8'7/#'(#,./0/#A',+8#.+5',+,0B#+(9#C#+%%8+49#/A/&@6(/#'(A68A/9:#D/0,6&'()#,./#
3'&/0#+886*0#,./#%8+(,0#+(9#'(0/-,0#,6#)&6*#,.+,#,./#*'898'7/#9/%/(9#6(B#06#CE3#8662'()#
76&*+&9#,6#0//'()#,./#&/,4&(#67#3+(@#7+0-'(+,'()#5'&90#,6#,./0/#+&/+0:=#
#
$64,.#F/0,#F+,/&#?6'(/9#76&-/0#*',.#,./#G(A'&6(3/(,#H)/(-@B#GI366&#J+,'6(+8#1+&2#
H4,.6&',@B#J+,4&+8#G()8+(9#+(9#G()8'0.#;/&',+)/B#+7,/&#&/+8'0'()#,.+,#&/0,6&'()#,./#
3'&/0#*6489#'3%&6A/#&+*#*+,/&#K4+8',@B#-4,,'()#86()L,/&3#-60,0#+(9#&/94-'()#/(/&)@#
40/#*.'8/#./8%'()#,6#04%%6&,#7+&3'():#
#
>./#%&6?/-,#'0#%+&,#67#M%0,&/+3#>.'(2'()B#$64,.#F/0,#F+,/&E0#-4,,'()L/9)/#NO:P#
3'88'6(#%+&,(/&0.'%#,6#'3%&6A/#&+*#*+,/&#K4+8',@#+(9#K4+(,',@B#&/94-/#78669'()#+(9#
&/0,6&/#786&+#+(9#7+4(+#'(#,./#+&/+0#',#40/0#76&#*+,/&#04%%8@:#
#
$64,.#F/0,#F+,/&#G(A'&6(3/(,+8#Q+(+)/&#Q+&,'(#D600#/I%8+'(/9<#=;/+A@#&+'(#
8+(9'()#6(#.+&9#)&64(9#*+0./0#%/+,B#0/9'3/(,B#7/&,'8'0/&0#+(9#9/5&'0#'(,6#,./#&'A/&0B#
*.'-.#.+A/#,6#5/#&/36A/9#+,#64&#*+,/&#,&/+,3/(,#*6&20:#
#
=D/L*/,,/9#+&/+0#+506&5#*+,/&#+(9#&/8/+0/#',#086*8@#06#/A/(#+7,/&#./+A@#&+'(7+88#,./#
*+,/&#,&'-28/0#36&/#)/(,8@#'(,6#,./#&'A/&0:#
#
D/0,6&'()#,./#3'&/0#*'88#./8%#,6#'3%&6A/#786*0#'(#&'A/&0#+(9#0,&/+30#+0#*/88#+0#-4,,'()#
64&#86()L,/&3#-60,0:=#
#
Q+&,'(#5/8'/A/0#,./#%&6?/-,#-6489#&/A684,'6('0/#,./#*+@#,./#*+,/&#'(940,&@#*6&20#'(#
,./#74,4&/:#=>.'0#'0#,./#7'&0,#,'3/#,./#*+,/&#'(940,&@#.+0#8662/9#+,#+88#,./#5/(/7',0#67#
9/+8'()#*',.#,./#064&-/#67#%&658/30#4%0,&/+3B#&+,./&#,.+(#,&@'()#,6#7'I#,./3#
96*(0,&/+3:#$64,.#F/0,#F+,/&E0#-40,63/&0B#+0#*/88#+0#64&#/(A'&6(3/(,B#*'88#&/+%#,./#
5/(/7',:=#
#
Q'&/0#7+-,7'8/#
#
####R#F+,/&#-+&&@'()#0/9'3/(,#'0#4%#,6#STU#36&/#/I%/(0'A/#,6#,&/+,#,.+(#-8/+&#*+,/&#
####R#D/0,6&/9#366&8+(9#'0#+58/#,6#&/8/+0/#*+,/&#76&#86()/&#'(#9&@#%/&'690B#%&6,/-,'()#
&'A/&0#7&63#9&64).,0#
####R#VA/&#WTT#./-,+&/0#67#GI366&#.+A/#+8&/+9@#5//(#&/0,6&/9#
####R#>./#Q'&/0#1+&,(/&0.'%#%8+(0#,6#&/0,6&/#6A/&#SBTTT#./-,+&/0#67#366&8+(9#'(#,./#
(/I,#7'A/#@/+&0#
!"#$"%%&'()*+",*(-'(#*.*.(/'
1/6%8/<#".&'0#1+-2.+3B#Q+&,'(#D600#
18+-/0<#X/A6(B#$63/&0/,B#GI366&#
V&)+('Y+,'6(0<#!!"B#$64,.#F/0,#F+,/&B#G(A'&6(3/(,#H)/(-@B#GI366&#J+,'6(+8#1+&2#
H4,.6&',@B#J+,4&+8#G()8+(9B#G()8'0.#;/&',+)/B#M%0,&/+3#>.'(2'()B#Q'&/0#
1+&,(/&0.'%#
© IKS Consortium
2013
106 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
!"#$#"%&'&
!"#$%&'()%*+,-./%
!"#$%&'(##)&*+,&-+")#,,+&
!"#$%&'(##)&.$/&0"+/#1&234&0,51#&/#($6#&+57*$""/&8%&7.#&24&9#$,/&/8%0#&87&:#6$%;&:57&
$7&<#5:#%=/&>$"?&$7&-+")#,,+&8%&!+,%($"";&#**"5#%7&8/&/78""&18/0.$,6#1&@5/7&+57/81#&7.#&
.$,:+5,A&B""&7.$7&(8""&0.$%6#&(.#%&'+57.&>#/7&>$7#,=/&CD&E8""8+%&),+@#07&8/&
0+E)"#7#1&15,8%6&24FFA&
>87.&$00#//&+%"9&:9&/#$&+,&0"8**;&$""&0+%/7,5078+%&E$7#,8$"/&$,#&:,+56.7&8%&:9&:$,6#&
*,+E&-$,&1+0?/A&B&7#E)+,$,9&/7##"&)"$7*+,E&($/&0+%/7,507#1&7+&#%$:"#&7.#&/$*#&+**G
"+$18%6&+*&E$7#,8$"/A&H)&$:+I#;&7.#&0"8**&.$1&7+&:#&/7$:8"8/#1&/+&$&/.$*7"#//&"8*7&0+5"1&:#&
0+%/7,507#1&7+&#%$:"#&$00#//&7+&7.#&/0,##%8%6&/7$78+%A&
&
B&1,#16#,&156&$&7,#%0.&+%&7.#&/#$&*"++,&*+,&7.#&+57*$""&)8)#A&J%0#&*5""9&$//#E:"#1&7.#&
)8)#&($/&7+(#1&,+5%1&*,+E&-$,&$%1&/5%?&8%7+&7.#&#K0$I$7#1&7,#%0.A&
&
L.#&/0,##%8%6&:58"18%6&($/&E$1#&+*&),#G0$/7&0+%0,#7#&)$%#"/&E$1#&7+&E$70.&7.#&
0+"+5,&$%1&$))#$,$%0#&+*&(#$7.#,#1&,+0?;&7+&.#")&87&:"#%1&8%7+&87/&/5,,+5%18%6/A&J%0#&
0+E)"#7#;&$&="8I8%6=&,++*&(8""&:#&)"$%7#1A&&
&
L.8/&),+@#07&.$/&:##%&$%&8%7#,#/78%6&+%#&(87.&)"#%79&+*&0.$""#%6#/&$"+%6&7.#&($9&15#&
7+&$00#//&,#/7,8078+%/A&L.#&0+E)"#78+%&7.8/&9#$,&(8""&E$?#&$&,#$"&18**#,#%0#&7+&7.#&
.$,:+5,A&
&
M+""+(&),+6,#//&+%&7.#&-+")#,,+&(#:0$E&+%&(((A/+57.(#/7($7#,A0+A5?N)+")#,,+&
01231445%"#$,16$"-%"2$7$7".%
-#+)"#O&P%+%#Q&
-"$0#/O&-+")#,,+;&<#5:#%=/&>$"?;&-$,;&!+,%($""&
J,6$%8R$78+%/O&'+57.&>#/7&>$7#,;&!"#$%&'(##)&
()*+,)-#".&
!"#$%&)89%*+,-./%
S+%-,+*87&F&
B0$/&!+5%08"&,#G$))+8%7E#%7/&
M,81$9&4F&B),8"&24FF&
&
T1($,1&U$I#9;&V8%8/7#,&*+,&TE)"+9E#%7&<#"$78+%/;&!+%/5E#,&$%1&-+/7$"&B**$8,/;&
.$/&,#G$))+8%7#1&W#%%8*#,&T$19&$%1&S80+"$&L#E)"#E$%&$/&!+5%08"&V#E:#,/&7+&7.#&
B1I8/+,9;&!+%08"8$78+%&$%1&B,:87,$78+%&'#,I80#&PB0$/QA&
&
X+7.&$))+8%7E#%7/&$,#&*+,&$&*5,7.#,&7.,##&9#$,&7#,E&0+EE#%08%6&*,+E&F&B),8"&24FF&7+&
YF&V$,0.&24FZ&$%1&$,#&E$1#&8%&$00+,1$%0#&(87.&7.#&J**80#&+*&7.#&!+EE8//8+%#,&*+,&
-5:"80&B))+8%7E#%7/&PJ!-BQ&6581#"8%#/A&
S+7#/&7+&#187+,/&
&
&&&FA&B0$/&$8E/&7+&8E),+I#&+,6$%8/$78+%/&$%1&(+,?8%6&"8*#&7.,+56.&:#77#,&#E)"+9E#%7&
,#"$78+%/A&L.#9&),+I81#&5)G7+G1$7#&8%*+,E$78+%;&8%1#)#%1#%7&$1I80#;&.86.G[5$"879&
© IKS Consortium
2013
107 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
!"#$%$%&'#%(')*"+')$!,'-./0*1-"2'#%('-./0*1--2'!*'2*03-')*"+/0#4-'/"*50-.2'#%('
$./"*3-'/-"6*".#%4-7'8*"-'$%6*".#!$*%'4#%'5-'6*9%('#!')))7#4#27*"&79+7':!'$2'#%'
$%(-/-%(-%!'2!#!9!*"1'5*(1'&*3-"%-('51'#';*9%4$0'*6'!)-03-'4*%2$2!$%&'*6'!,-'<4#2'
;,#$"='-./0*1-"='!"#(-'9%$*%'#%('$%(-/-%(-%!'.-.5-"2'
'''>7'<00'#//*$%!.-%!2'#"-'.#(-'*%'.-"$!'#%('/*0$!$4#0'#4!$3$!1'/0#12'%*'/#"!'$%'!,-'
2-0-4!$*%'/"*4-227'?*)-3-"='$%'#44*"(#%4-')$!,'!,-'*"$&$%#0'@*0#%'"-4*..-%(#!$*%2='
!,-"-'$2'#'"-A9$"-.-%!'6*"'#//*$%!--2B'/*0$!$4#0'#4!$3$!1'C$6'#%1'(-40#"-(D'!*'5-'.#(-'
/950$4'
'
E$*&"#/,$4#0'F-!#$02'
'
@$4*0#'G-./0-.#%',#2'#'8#2!-"2'$%'E92$%-22'<(.$%$2!"#!$*%'C8E<D='F$/0*.#'$%'
8#%#&-.-%!'H-"3$4-2'CF8HD'#%('$2'#'6-00*)'.-.5-"'*6'!,-'<22*4$#!$*%'*6'
<44*9%!$%&'G-4,%$4$#%2'CI8<<GD7'
'
@$4*0#',#2'2/-%!'%-#"01'JK'1-#"2'$%'!,-'6$%#%4$#0'2-"3$4-2'$%(92!"1='!,-'0#2!'LM'#2'#'
H-%$*"'NO-49!$3-'#!'@#!$*%)$(-'E9$0($%&'H*4$-!1='),-"-'2,-'0-('#')$(-'"#%&-'*6'
(-/#"!.-%!2'$%409($%&'P-!#$0'H!"#!-&1='Q"*9/'<9($!='G,$"('R#"!1'H#0-2'#%('!,-'I"#9('
F-/#"!.-%!7'H,-')#2'#%'$%#9&9"#0'.-.5-"'*6'!,-'NA9#0'S//*"!9%$!$-2';*..$!!--'#!'
@#!$*%)$(-')$!,'#%'$%!-"-2!'$%'#00'#"-#2'*6'($3-"2$!17'
'
@$4*0#'$2'%*)'#%'$%(-/-%(-%!'6$%#%4$#0'#(3$2-"='#%('4*#4,$%&')*.-%'$%'!"#%2$!$*%'$%'
!,-$"')*"+T,*.-'0$6-='$%'#(($!$*%'!*',-"'/*2$!$*%'#2'<4#2';*9%4$0'.-.5-"7'H,-'#02*'
2$!2'*%'!,-'E*#"('*6'!,-'U$0!2,$"-'P9"#0'?*92$%&'<22*4$#!$*%7'
'
V-%%1'N#(1'W7;7'$2'*%-'*6'!,-'X-#($%&'N./0*1.-%!'X#)'E#""$2!-"2'$%'!,-'4*9%!"17'
H,-'9%(-"!#+-2'#(3*4#41'#%('#(3$2*"1')*"+'6*"'-./0*1-"2='-./0*1--2='!"#(-'9%$*%2='
-./0*1-"2B'#22*4$#!$*%2='4-%!"#0'#%('0*4#0'&*3-"%.-%!='2!#!9!*"1'4*..$22$*%2'#%('
@QS27'
'
V-%%1'5-4#.-'#'W9--%B2';*9%2-0'$%'>KKM=',#3$%&'/"#4!$4-('#!'!,-'5#"'2$%4-'LYYK='#%('
,#2'#//-#"-('$%'.#%1'*6'!,-'0-#($%&'-./0*1.-%!'4#2-2'$%'"-4-%!'1-#"27'R"$*"'!*'!,$2'
V-%%1')#2'#'.-.5-"'*6'!,-'<!!*"%-1ZQ-%-"#0B2'<ZR#%-0'*6'#(3*4#!-2'#%('#02*'
2!#%($%&'[9%$*"'4*9%2-0'!*'!,-'@\V'#%('@\87'H,-'4*%!$%9-2'!*'5-'$%2!"94!-('$%'#'
%9.5-"'*6'0-#($%&'4#2-2'6*"'!,-'Q*3-"%.-%!'#%('!*'#(3$2-'#%('"-/"-2-%!'!"#(-'9%$*%2'
#%('-./0*1-"2'$%'2!"#!-&$4'#%('!-2!'4#2-2'$%'!,-'6$-0(2'*6'-./0*1.-%!'#%('
($24"$.$%#!$*%'0#)7'
'
V-%%1')#2'#//*$%!-('#2'#%'N./0*1.-%!'V9(&-'$%'>KKL'#%('#';*9%!1';*9"!'P-4*"(-"'
$%'>KKJ7'H,-'$2'#']$4-ZR"-2$(-%!'*6'!,-':%(92!"$#0'X#)'H*4$-!1'#%('#'G"92!--'*6'!,-'
I"--'P-/"-2-%!#!$*%'\%$!7'
'
I*"'.-($#'-%A9$"-2'*%01'4*%!#4!'8#!!'E#"+-"='8-($#'#%('RP'8#%#&-"'*%'K>K'^>LK'
JY>_'*"'X*9'S)-%='8-($#'#%('8#"+-!$%&'S66$4-"'*%'K>K'^>LK'JY>K7'
!"#$"%%&'()*+",*(-'(#*.*.(/'
R-*/0-`'N()#"('F#3-1='V-%%$6-"'N#(1='@$4*0#'G-./0-.#%='8#!!'E#"+-"='X*9'S)-%'
R0#4-2`'C%*%-D'
S"&#%$2#!$*%2`'<4#2='<(3$2*"1';*%4$0$#!$*%'#%('<"5$!"#!$*%'H-"3$4-='S;R<='S66$4-'*6'
!,-';*..$22$*%-"'6*"'R950$4'<//*$%!.-%!2='<22*4$#!$*%'*6'<44*9%!$%&'
© IKS Consortium
2013
108 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
!"#$%&#&'%()*+',&-%.&/"*01&2/&%3*4-#&",5)*6&2,($&7"*817'2*9-1(&%3*:((-#&',&-%)*
+;<)*+;=)*>%/1(,7&'2*?'.*4-#&",5)*@7""*8"A7"("%,',&-%*;%&,)*:B:4*B-1%#&2*
!"#$%"&'()*)
!"#$%&'()%*+,-./%
+-%C7-D&,*E*
4-#&'2*F"/&'*%""/(*,-*G"*,'H"%*("7&-1(25*.'7%(*:#'(*
!$17(/'5*IE*J"#"FG"7*EIKI*
*
!$"*"FA2-5F"%,*7"2',&-%(*("7L&#"*:#'(*$'(*.'7%"/*,$',*,$"*7&("*-D*(-#&'2*F"/&'*#-12/*
(""*F-7"*'%/*/&DD"7"%,*D-7F(*-D*1%-DD&#&'2*1%7"(,*1("/*&%*D1,17"*/&(A1,"(M*
*
!$"*'##"((&G&2&,5*'%/*(A""/*-D*,--2(*(1#$*'(*!.&,,"7)*N-1!1G"*'%/*@'#"G--H*F"'%*
,$',*.-7H"7(*#'%*G"*F-G&2&("/*O1&#H"7*,$'%*"L"7*G"D-7"*'##-7/&%3*,-*:#'(*B$&"D*
B-%#&2&',-7*C","7*9'7.--/M*
*
4A"'H&%3*',*,$"*P-&%,*:#'(*Q*>J4*#-%D"7"%#"*-%*G'73'&%&%3*'%/*&%/1(,7&'2*7"2',&-%(*
A7-(A"#,(*D-7*EIKK*$"*('&/R*
*
****S+".*,"#$%-2-35*&(*#$'%3&%3*,$"*.'5*&%*.$&#$*.-7H"7(*'7"*'G2"*,-*-73'%&("M*
J"F-%(,7',&-%(*'%/*D2'($*F-G(*#'%*G"*'77'%3"/*',*,$"*,-1#$*-D*'*G1,,-%*'%/*,$"5*#'%*
#-FF1%&#',"*&%*("#-%/()*%-,*P1(,*%',&-%'225*G1,*&%,"7%',&-%'225M*?'(,*5"'7T(*.&2/#',*
(,7&H"(*',*,$"*?&%/("5*-&2*7"D&%"75*'7"*'*#'("*&%*A-&%,M*
*
****S!$"*?&%/("5*/&(A1,"*.'(*#$'7'#,"7&("/*G5*,$"*(",,&%3*1A*-D*%",.-7H&%3*37-1A(M*
!$"7"*.'(*'*."G(&,"*'%/*,"U,*F"(('3"*'%/*"F'&2*37-1A()*"%'G2&%3*/"F-%(,7',-7(*,-*
#-FF1%&#',"*7'A&/25*'#7-((*,$"*#-1%,75*'%/*,-*"UA'%/*,$"*'#,&-%*,-*-L"7*,."%,5*-,$"7*
F'P-7*#-%(,71#,&-%*(&,"(*.&,$&%*$-17(M*
*
****S!$"*,$7"',*-D*1%-DD&#&'2*&%/1(,7&'2*'#,&-%*&(*-%"*,$',*G-,$*"FA2-5"7(*'%/*1%&-%(*'7"*
.'75*-DM*!$"*2'#H*-D*-DD&#&'2*2"'/"7($&A*&%*(1#$*/&(A1,"(*F"'%(*%"3-,&',&%3*#'%*G"*
#-FA2"U*'%/*'*7"(-21,&-%*$'7/"7*,-*'#$&"L"M*
*
****SVFA2-5"7(*'%/*1%&-%(*%""/*,-*1%/"7(,'%/*,$"*7-2"*-D*%".*,"#$%-2-35*'%/*%-,*P1(,*
2"'L"*&,*,-*,$"&7*>!*/"A'7,F"%,(MS*
*
;%/"72&%&%3*,$"*&FA-7,'%#"*-D*3",,&%3*&%/1(,7&'2*7"2',&-%(*7&3$,*&%*,$"*D&7(,*A2'#"*,$"*
B$&"D*B-%#&2&',-7*'//"/R*
*
****S+".*F"/&'*#'%*A-("*%".*A7-G2"F(*G1,*,$"*(-21,&-%(*'7"*(,&22*D7-F*,$"*-2/*(#$--2*W*
A7"L"%,&-%*&(*G",,"7*,$'%*#17"M*>,*&(*"(("%,&'2*,$',*"FA2-5"7()*F'%'3"7()*'%/*,7'/"*1%&-%*
7"A7"("%,',&L"(*&FA7-L"*#-FF1%&#',&-%*'%/*"%3'3"F"%,)*(-*,$',*A-,"%,&'2*&((1"(*,$',*
F'5*#'1("*#-%D2&#,*'7"*'&7"/*'%/*2&(,"%"/*,-*'%/*"'725*'#,&-%*,'H"%MS*
*
!$"*#-%D"7"%#"*.'(*#$'&7"/*G5*:#'(*B$'&7*V/*4.""%"5*'%/*(A"'H"7(*&%#21/"/*>J4*
C'5*8"A-7,*V/&,-7*X"%*=12H"'7%*'%/*>J4*9"'/*-D*C'5*Y*98*4"7L&#"(*:2'(,'&7*
9',#$",,M*
*
© IKS Consortium
2013
109 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
!"#"$%&"'(%#')(*"%+,(-+).(/0%'(1*2"-(34"05&26"(7)*8(9%:#)+(;*)(5'",(*2'('<""0*=(
;2&*(>9?'(9).(@""8":=(&)(*2$*#2$*&(&*"(6%#5"()-(%#&"+8%&26"(,2'<5&"(+"')#5&2)8(A/!BC(
D(%('"+620"(;*"+"(/0%'(#"%,'(&*"(;%:E(
(
F"('%2,G(
(
((((HI*"8(/!B(2'(28&+),50",(%&(&*"(6"+:("%+#:('&%$"'(2&(0%8(<+"6"8&(%(,2'%$+""."8&(
,"6"#)<28$(28&)(%8("8&+"80*",(,2'<5&"(;2&*(&*"(,2'&%80"(J"&;""8(&*"(&;)(<%+&2"'(
280+"%'28$(%&("%0*('&"<()-(&*"(0)8-#20&E(
(
((((HK''5"'(%+"(J"'&(+"')#6",(28(&*"(;)+L<#%0"E(B"')#628$(,2'<5&"'(;2&*)5&($)28$(&)(
0)5+&(0%8('%6"(&2."=(.)8":(%8,('&+"''(-)+(J)&*(<%+&2"'EH(
!"#$"%%&'()*+",*(-'(#*.*.(/'
M")<#"G(M"&"+(F%+;)),=(3,(N;""8":=(@"8(O5#L"%+8=(/#%'&%2+(F%&0*"&&=(7)*8(9%:#)+=(
9).(@""8":(
M#%0"'G(P28,'":(
Q+$'G(/0%'=(9;2&&"+=(R)595J"=(S%0"J))L=(K!N=(>9(
!"#$%&'('
0()*'1234'56+-/7'
M)#20"(T(
9+%--20(<)#20"(%+"(%<<"%#28$(-)+(&;)(.)&)+0:0#2'&'(&)(0)."(-)+;%+,(%-&"+(%8("#,"+#:(
;).%8(;%'(28U5+",()8(&*"(>TVWX=(J"&;""8(F"#.'#":(%8,(N&)L"'#":E(
/002,"8&(T(
(
9*"(J2L"+'(-%2#",(&)('&)<(%&(&*"('0"8"(%-&"+(&*"(620&2.=(%(XYZ:"%+Z)#,(;).%8(-+).(
I%+;20L'*2+"=(;%'(L8)0L",(,);8(%-&"+(J"28$(*2&(J:()8"()-(&*"(J2L"'(8"%+(1#%:(>%8L(
0%+(<%+L=(%&(%+)58,(WEV[<.()8(N58,%:(V\(O%:(V[TTE(
(
S)##);28$(&*"(0)##2'2)8(&*"(&;)(J2L"'=(;*20*(;"+"(&+%6"##28$(28(&*"(,2+"0&2)8()-(
N&)L"'#":=('&)<<",(.)."8&%+2#:(%('*)+&(,2'&%80"(5<(&*"(+)%,(J"-)+"(0)8&28528$(&*"2+(
U)5+8":E(
(
M)#20"(%+"(286"'&2$%&28$(&)(&+:(%8,(2,"8&2-:(&*"(+2,"+'()-(&*"(&;)(.)&)+0:0#"'(%8,(%+"(
%<<"%#28$(-)+(%8:(;2&8"''"'(&)(0)."(-)+;%+,E(
(
9+%--20(N"+$"%8&(]"2#(1%.<J"##=()-(])+&*(R)+L'*2+"(M)#20"?'(B)%,(M)#2028$(^+)5<=(
'%2,G(H9*"(.)&)+0:0#2'&'(0)5#,(8)&(*%6"(L8);8(&*"("4&"8&()-(&*"(;).%8?'(28U5+2"'(%8,(
.%,"(8)(%&&".<&(&)(-28,()5&E(
(
HK(;)5#,(%<<"%#(&)(&*"(+2,"+()-(&*"(.)&)+0:0#"(286)#6",(&)(,)(&*"(+2$*&(&*28$(%8,(0)."(
-)+;%+,E(
(
HK(;)5#,(%#')(%<<"%#(&)(&*"('"0)8,(.)&)+0:0#2'&(&)($"&(28(&)50*(;2&*(5'=(%'(*"(.%:(
*)#,(62&%#("62,"80"(%8,(;"(8"",(&)("#2.28%&"(*2.(-+).(&*"("8_52+:E(
(
HK(%.(%#')(28&"+"'&",(28('<"%L28$(&)(%8:)8"(;*)('%;(&*"(0)##2'2)8(2&'"#-()+('%;("2&*"+(
.)&)+0:0#"(<+2)+(&)()+(-)##);28$(&*"(2802,"8&EH(
© IKS Consortium
2013
110 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
!
"#$!%&'(&)!*$)+&,-!#+-!-&,'$!)+.$!+!/00.!*$'0%$*1!2*0)!#$*!&,34*&$-!+,.!5+-!
.&-'#+*/$.!2*0)!6+)$-!7008!90-:&(+;!0,!<0,.+1!=>!<+1!?>@@A!
!
B,10,$!5&(#!&,20*)+(&0,!(#+(!'+,!#$;:!(#$!:0;&'$!5&(#!(#$&*!$,C4&*&$-!&-!4*/$.!(0!
'0,(+'(!"D!E$&;!7+):F$;;G!0*!"*+22&'!70,-(+F;$!H$$!9+4I5$;;G!0,!>JKL!M>!M>!?K!NG!
C40(&,/!*$2$*$,'$!,4)F$*!@?@@>>JNJ?NA!
!"#$"%%&'()*+",*(-'(#*.*.(/'
O$0:;$P!E$&;!7+):F$;;G!H$$!9+4I5$;;!
O;+'$-P!9$;)-;$1G!D(08$-;$1G!Q+*5&'8-#&*$G!7;+1!R+,8!
S*/-P!E0*(#!T0*8-#&*$!O0;&'$G!U0+.!O0;&'&,/!V*04:G!6+)$-!7008!90-:&(+;!
!"#$%&'('
0()*'1234'56+-/7'
O0;&'$!?!
B,(&C4$!F+*0)$($*!F4*/;+*1!,$+*!U&:0,!
!
W$($'(&%$-!+*$!&,%$-(&/+(&,/!(#$!(#$2(!02!+!%+;4+F;$!+,(&C4$!F+*0)$($*A!
"#$!-(0;$,!F+*0)$($*!
!
X(!5+-!-(0;$,G!.4*&,/!+!F4*/;+*1G!2*0)!+!'0((+/$!&,!Q$-(!"+,2&$;.G!,$+*!U&:0,!F$(5$$,!
@>:)!0,!<0,.+1!?=!<+1!+,.!@:)!"4$-.+1!?K!<+1!?>@@A!
!
"#$!?>>Y1$+*Y0;.!-(&'8!F+*0)$($*G!5#&'#!&-!K>&,!(+;;!+,.!)+.$!2*0)!)+#0/+,1!5&(#!+!
-&;%$*$.!F*+--!2+'$G!&-!%+;4$.!+(!Z=>G>>>A!
!
W$($'(&%$!70,-(+F;$![+*;!<&..;$)&--G!02!E0*(#+;;$*(0,!7XWG!-+&.P!\B-!(#&-!&-!+!#&/#;1!
.&-(&,'(&%$!&($)!X!+)!:0-&(&%$!(#+(!:$0:;$!5&;;!*$)$)F$*!-$$&,/!&(A!
!
\X!+)!+::$+;&,/!(0!+,10,$!5#0!#+-!+,1!&,20*)+(&0,!+F04(!(#&-!(#$2(G!0*!8,05-!5#$*$!
(#$!F+*0)$($*!&-!,05G!(0!'0)$!20*5+*.!+,.!'0,(+'(!)$!+-!-00,!+-!:0--&F;$A!
!
\X!+)!:+*(&'4;+*;1!&,($*$-($.!&,!#$+*&,/!2*0)!+,10,$!&,!(#$!+,(&C4$-!(*+.$!5#0!)+1!
#+%$!F$$,!022$*$.!(#$!&($)A!"#$!F+*0)$($*!&-!+,!$+*;1!$I+):;$!02!(#$!50*8!02!60#,!
U4--$;;!5#0!5+-!)+.$!Q+('#)+8$*!(0!9&-!U01+;!9&/#,$--!(#$!O*&,'$!U$/$,(!&,!
@J@@A\!
!
X2!104!'+,!+--&-(!5&(#!(#&-!&,%$-(&/+(&0,!:;$+-$!'0,(+'(!W7![+*;!<&..;$)&--!0*!WD!
B,/$;+!Q$,(!+(!E0*(#+;;$*(0,!O0;&'$!D(+(&0,!0,!>JKL!M>!M>!?K!N!C40(&,/!*$2$*$,'$!
,4)F$*!@?@@>>JKMM?G!0*!7*&)$-(0::$*-G!+,0,1)04-;1G!0,!>J>>!LLL!@@@A!
!"#$"%%&'()*+",*(-'(#*.*.(/'
O$0:;$P![+*;!<&..;$)&--G!60#,!U4--$;;G!9&-!U01+;!9&/#,$--!"#$!O*&'$!U$/$,(G!
B,/$;+!Q$,(!
O;+'$-P!U&:0,G!Q$-(!"+,2&$;.!
S*/-P!E0*(#+;;$*(0,!7XWG!E0*(#+;;$*(0,!O0;&'$!D(+(&0,G!7*&)$-(0::$*-!
!
© IKS Consortium
2013
111 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
The report documents the results obtained when using IKS FISE to identify entities and external resources relating to those entities based on real world data from various UK based organisations:
§
§
§
§
Local government in England, Scotland and Wales.
Non-profit central government organisations.
Utility company.
Police Force
It also compares the performance of different entity extraction engines.
Lessons learned
§
§
§
§
§
§
Modular approach is good.
Build process could be improved to provide more 'cut-down' distribution. For example without
the UI.
Straightforward to interface with service via REST interface.
Steep learning curve for implementing new engines. Maybe a tutorial or similar could be provided.
Dependency on, potentially unreliable, external resources can be a problem. Entity hub is
starting to address this.
Real challenge is the availability of good quality domain specific external resources.
Software components used
The initial development work started with the FISE system. The validation reports was written based
on a build from the Apache Stanbol (incubation) project.
A number of additional extraction and enhancement engines, written by GOSS, were used during the
evaluation:
§
§
§
§
§
§
OpenCalais Named Entity Extraction
OpenNLP-1.5 Named Entity Extraction
JNet-1.5 Named Entity Extraction
DBPedia Lookup Enhancement
Freebase Enhancement
OpenCyc Enhancement
In addition a triple store and SPARQL Endpoint out side of FISE/Stanbol was used.
6.1.3 Gentics
Use-Case
When leaving (ESC or click in the surrounding content) an Aloha Editor editable the content is sent to the
backend FISE engine for a REST response. FISE returns annotations and the top level annotations are used for
the auto tagging. The tags are automatically added to the document, so there is no need for further user interaction. A user may discard tags which he thinks are not appropriate, with one single click.
© IKS Consortium
2013
112 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Validation
Due to the fast response from the FISE developers an implementation could be done straight forward.
Implementation issues
Problems finding the best FISE version to use. We followed the instructions on the google code website but had
problems compiling on a MAC. A hint from the FISE developer team lead to the early adopter precompiled
version, which worked for the first steps.
More issues emerged when requesting from different browsers. The problem could be identified as a content
charset issue and was reported (http://code.google.com/p/iks-project/issues/detail?id=93). A solution was provided in a short timeframe.
There are still some issues open that produce unexpected behavior (http://code.google.com/p/iksproject/issues/detail?id=100)
Online Demo
The implementation is available to the public on
http://labs.gentics.com:8080/Portal.Node/content/Autotagging.html (Login: hmeran, Pass: hmeran)
(we use the FISE engine on the same server http://labs.gentics.com:9000)
and
http://semantic-editor.org/try_it/
Aloha Editor Annotation plugin
The annotation plugin is available as opensource under the MIT license hosted on github
(https://github.com/alohaeditor/Aloha-Plugin-Annotations).
Performance
To enable live annotation on smartcontentchange event high performance responses from the backend are necessary. Therefore a performance test with jemeter has been done. To setup the environment we tested with 100
concurrent requests 100 times with a simple sentence (the same for all requests). The first 1800 requests delivered good response. The last 200 requests and all following failed. The reason was: Fise error message: Error
500 'LocationEnhancementEngine' failed to process content item 'urn:content-item-sha184854eb6802a601ca2349ba28cc55f0b930ac96d' with type 'text/plain': the hourly limit of 2000 credits
for the IP address 188.40.152.152 has been exceeded. Please throttle your requests or use the commercial service.
We reported the problem and the FISE team found the reason: The problem is that the LocationEnhancementEngine (eu.iksproject.fise.engines.geonames.impl.LocationEnhancementEngine) does use the geonames.org webservices. In detail for each Location dedected by FISE it sends up to 5 webservice requests. So a enhanced document with 5 detected locations will use up to 30/2000 free credits/h. That means that the LocationEnhancementEngine can not be used for much more than 100 requests/h.
RICK will provide a solution for the issue. We could not complete our performance tests and
decided to wait for call for evaluation for RICK and than do further performance evalutation.
Visibility
© IKS Consortium
2013
113 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
We plan announced the plugin and FISE integration among the Aloha Editor community and website as well as
among the Gentics clients through the Gentics Newsletter and Gentics website. The FISE annotation plugin is
not yet in a state to be implemented in a production system so the plugin is available for customers to integrate in
Gentics Content.Node 5.
Follow-up Interview and Discussion
Date: Thursday 3, February 2011
Participants:
• Haymo Meran (Gentics)
• John Pereira, Andreas Gruber and Rupert Westenthaler (Salzburg Research)
Notes:
è
è
è
è
è
FISE successfully integrated and demonstrated via online demo
Active partner also in Semantic Interaction Framework
Will integrate future IKS components to extend FISE capabilities
Internal development focus around IKS is set for third quarter 2011
Demo to remain online throughout the next development phase
© IKS Consortium
2013
114 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
6.1.4 Ximdex
Introduction
Open Ximdex Evolution SL (www.ximdex.com) has integrated Apache Stanbol text enrichment engine services
into Ximdex Semantic CMS as a complement of the current engine based on the service Zemanta and semantic
technologies for manual and automatic recognition (and annotation).
This integration provides Ximdex's WYSIWG Editor, aka ximedit, with semantic tools for enriching textual
contents introduced by editor users, through Apache Stanbol Enhancer, a RESTFul engine that, as its own name
says, can enhance textual content.
Ximedit provides a section for including external references on the document. This section will receive related
content from Apache Stanbol and will allow users to automatically enrich their documents. Zemanta directly
provides with images/links/references based on the analysis of the contents the user is editing, while Apache
stanbol will provide with automatic annotations for persons, companies and places. During the project, we will
evaluate if we choose one or both engines in next Ximdex WYSIWYG Editor versions.
Ximdex is a Semantic Content Management System published with a GNU Affero License. To bring IKS technology to our Ximdex CMS integrating Apache Stanbol we decided to extend our service oriented Automated
Annotator module (ximRA, Remote Annotator for Ximdex) evolving its output into tags.
Technical tasks for the team were:
- To integrate Stanbol as a new service to be invoked from ximRA module. - To extend our system for the management of Places, Organizations and People -POP- coming from Stanbol. - To adapt our XML schemas, using
RNG, and Ximdex's transformation pipelines for the generation of RDFa from POP tags.
With the mindset of not only creating a prototype, but a new component fully integrated into Ximdex, using all
its capabilities (searches, format transformations, visual widgets, WYSIWYG editing, ...), and adding additional
power to our WYSIWYM XML editor.
Demo
A video with a short demo of XML content enrichment using Stanbol can be watched
athttp://www.ximdex.org/documentacion/demoIKSvideo.html#IKSshort . The full video showing how the RNG
template is modified to allow the inclusion of tags provided by IKS, the XML of the visually edited content, the
transformation to generate the HTML code including RDFa, and more can be found
at http://www.ximdex.org/documentacion/demoIKSvideo.html#IKSfull .
Accesing the Demo: To enter the demo visit http://cloudximdex.ximdex.tapp.in/x32 with Firefox (7 or higher)
and enter user "ximdex" and password "IKSximdex2011".
Follow the video guide to exercise the Ximdex system. The main steps are:
§
Login into Ximdex (ximdex/IKSximdex2011) [min. 0:15]
§
Editing the selected document with xEdit editor (Projects/Picasso/Picasso_Server/ximdoc/picasso/picasso-ides). [min. 0:20]
§
Loading the External References on the right column. [min. 1:42]
§
Adding a link on the text [min. 1:59]
§
Tagging People Names [min. 2:15]
§
See tags automatically added [min. 2:31]
§
Tag Places [min. 2:42]
© IKS Consortium
2013
115 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
§
§
Saving changes [min. 2:58]
§
Seeing the semantic information included in the final document for exploitation [min. 3:47]
Other features:
§
See the Tree View of the document [min. 0:53]
§
Edit the RNG template [min. 1:10]
§
Search for tagged documents [min. 3:09]
Validation
The proposed use case to validate the development was:
-User creates or edits an existing document using ximedit.
-User clicks on '”Load” in “External References” button in ximedit.
-System queries Apache Stanbol Enhancer for related content of the current information in Web Editor.
-System shows user a tab from each source containing related information about the document.
-User selects references (organized on images, links and articles) from sources and add them to the original
document, enriching it.
Lessons learned
Integration of external annotator has driven us to improve the internal representation of annotations to make
them more flexible.
Visibility
The demo will be soon open to the main public providing different user/pass after registration.
Software components used
Apache Stanbol. VIE was considered but we needed functionalities that, at that time, would be provided by the
new VIE2.
6.1.5 MakoLab
Introduction
This project represents an adaptation of IKS Software Stack to support MakoLab’s RSI-CMS system (
http://makolab.pl/en/web-media/case-studies/RSI-CMS ).
RSI CMS (Renault Site CMS) is the CMS created by MakoLab used by 40+ countries of the world as a tool to
create and maintain International Renault websites.
The proposal will be realized as an extension of existing RSI-CMS.
RSI-CMS is an ASP.NET CMS that combines a user friendly interface with a flexible structured (XML based)
content engine.
In addition to standard desktop sites, RSI-CMS can easily create mobile sites.
It features distributed architecture, with production sites hosted in numerous data centers and cloud solutions
around the globe.
This project is put forward by MakoLab SA, a Polish company located in Lodz ( www.makolab.com ),
Use Case
1. The user of RSI-CMS is able to use Stanbol Semantic Enhancement facility to semantically annotate the entities of content managed by RSI-CMS.
2. The RSI CMS will also implement VIE client-side control for marking up of the content under control of the
CMS system.
© IKS Consortium
2013
116 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
3. It will also be used for enhancement of RSI-CMS editing capacities with VIE inline editing feature, particularly in the light of responsive and mobile designs.
4. The end user experience is greatly enhanced by addition of intelligent "see also" feature and pop-up elements
with descriptions of objects/concepts discovered by Stanbol:
Demo
Demo is available online at: http://cloud-rsiexport.makolab.pl/GCC/discover/history.html
Validation
The enhancement system has been validated in MakoLab team responsible for RSI-CMS (not the "semantic
programming" team that created the solution.
The vocabulary of Renault-oriented terms (see [renault.ttl TTL file]) was validated by our account managers
dealing with Renault.
Types mapping file is here: types.xlsx.
Lessons learned
We appreciate participation in development of Stanbol project and we perceive it as a good increase the awareness of building and developing content management systems enrichment. We helped also report important issue
in indexing process - main problem with Stanbol indexing tool working on Windows OS environment. We perceive our cooperation as a milestone in build our semantic knowledge base process and awareness, especially in
semantic services usage.
© IKS Consortium
2013
117 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Visibility
The semantic enhancement of RSI-CMS will be formally presented to Renault on week 50th, 2012 and will enter
into productions sites in Q1/Q2 of 2013.
Software components used
In our case of IKS Stanbol demo was used in two major purpose: Basic content enhancement and custom vocabularies usage. We focused on creating demo for automotive CMS, therefore custom vocabularies bundle installation was our main activity scope. Our vocabulary was built based on our main customer needs, it was very important to create flexible and well maintained vocabulary and Stanbol met our expectations. Also the VIE Widget served us, as an idea for enhanced content presentation.
In future we plan expand Stanbol integration using factstore - to store and enrich relation between entities, as
well sparql module.
6.1.6 Typo3
Demo
Demo is available online at: http://iks.rensadmiraal.nl/ Explanation blog post: http://blog.iks-project.eu/typo3neos-iks-demo-site/
Validation
As stated in the beginning of the early adaptor program we would implement VIE (based on backbone) in our
interface (working with Emberjs). Both libraries now work together. The RDFa implementation is now fully
done based on a JSON schema generated in TYPO3 Neos, which is based on the content type definition we use.
It would now, without too much effort, be possible to support content types based on such schemas imported
from other sources (like schema.org for example).
Lessons learned
The most important lesson learned is the lesson of cooperation. The project had a slow start, and really fullfilled
all expectations when we had a really productive code sprint in which the TYPO3 Neos team and Henri Bergius
from the IKS community teamed up to add features to VIE and rework TYPO3 Neos to get to this implementation. Because of this effort TYPO3 Neos is now ready for the semantic web.
Visibility
The new content editing module based on VIE and Create.js has been presented on the TYPO3 Conference by
Henri Bergius and Rens Admiraal. The slides of this presentation can be found on
https://speakerdeck.com/u/radmiraal/p/typo3-neos-and As TYPO3 Neos is now released as an alpha product the
entire TYPO3 community will see and use the semantic capabilities of VIE. Besides that we expect contributions
to extend those capabilities even further.
Software components used
We used VIE, Create.js and Hallo editor as the main foundation of our content editing module. Annotate is used
in the demo, and is a serious candidate for integration.
6.1.7 Netzmuehle
Introduction
Netzmühle is a software vendor of web based applications. Our main products are the content management system ORYZA, the online-shop BARTHII and the newsletter system NIVARA.
The products are fully integrated into the CMS. This means a online-shop and the newsleter system are also
managed within the CMS application.
Because it is very simle with our solution to combine content and products into one website we developed an
innovative online-store-concept neoshopia.
The main goal for the integration of semantic web technologies was to make it very easy to match content and
products in an automated and perfect way.
© IKS Consortium
2013
118 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Demo
An online-shop demo is available here: Stanbol Demo-Shop
The demo offers functions to enable/disable stanbol enhancement and debug information to show how the semantic web is useful.
Lessons learned
•
•
•
•
•
•
•
•
Different standards for semantic enhanced information
Setting up Apache stanbol
Creating an own index
Integrate Apache stanbol in commerical scenario
Weak points of the used solution e.g. using good DBPedia indexes is almost impossible
Configuration of indexes is not very easy
Runtime of live analysis of content lasts to long in our use case
Easy generation of useful semantic indexes is the main criteria for using semantic web technologies
Visibility
The demo was first demonstrated at "Lange Nacht der Forschung" 27.04.2012 at the booth of the IKS project.
The next live presentation of this demo will taken place at IKS Showcasing Event 12-13 June 2012, Salzburg,
Austria.
A short introduction into Sematic web in general and our demo project in particular are given to our visitors of
our lectures (e.g. University of Salzburg).
Software components used
•
•
•
•
Netzmühle ORYZA
Netzmühle BARTHII
Apache stanbol
DBPedia databases
6.2 CMS Integrators
6.2.1 Klein & Partner KG
Demo Site
fise.demo.bluedynamics.eu
Validation 1
Requirement from proposal: After login validating visitor can upload any (supported) type of Plone content.
Validating visitor can inspect the enhancements of each document. Validation on code level. Steps documented
and reversible for developers. Plone add on developers are adding one line to packages setup.py file.
© IKS Consortium
2013
119 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
The Python library fise.plone is released at the Python package index and available at github. A short documentation with instruction how to use the API and how to get started is there too.
Validation 2
Requirement from proposal: On buildout/easy_install time all FISE libraries and integration packages are
fetched automatically. Add on developer adds a dependency to its Plone Generic Setup profile.
The Python library fise.client is released at the Python package index and available at github. A short documentation with instruction how to use the API and how to get started is there too. The code is fully tested and the
expressive doctests for theengines and store are included.
Validation 3
Requirement from proposal: After activating the addon in Plone all FISE dependencies are activated.
While buildout runs fise.plone Python-egg fetches fise.client Python-egg which itself fetches all necessary thirdparty libraries. After activating the addon in Plone as documented in the README.rst file of fise.plone FISE
with its dependencies is active as documented.
Validation 4
Requirement from proposal: Developer writes a Plone Doctest. In the test he adds content programmatically and
re-reads it. Now he can access the semantic enhancements.
Using fise.client a developer can do so. How it works is documented at the README.rst deployed with the
python package or in source code.
Further activities, visibility
Jens Klein attended at the Plone Conference 2010 in Bristol as a speaker giving a talk Plone is so semantic, isn't
it? addressing Plone, its lacks of semantic support and how to solve the problem by using FISE.
Its recorded (fwd to 6:00) and the slides are available. At the conference an openspace plone + semantics was
held, where a smaller group of 12-15 interested people attended. FISE was one topic. After the conference a oneday of the sprint was used to continue with FISE Plone integration. After conference acommon blog post about
the plone conference and a specific blog post about IKS FISE at Plone Conference was published.
Follow-up Interview and Discussion
Date: Friday 4, February 2011
Participants:
• Jens W. Klein (Klein & Partner KG)
• John Pereira, Andreas Gruber and Rupert Westenthaler (Salzburg Research)
Notes:
è
è
è
è
è
è
è
FISE successfully integrated and demonstrated via online demo
Integration on UI is not complete only FISE raw data at present
Agreed to improve UI value for editor
IKS developers to support with UI integration – FISE data formats
Partner to document use case in legal domain
IKS team to clarify the role of Apache Stanbol in use case
Demo to remain online throughout the next development phase
6.2.2 Zaizi Ltd
This page describes the integration of IKS FISE with Alfresco ECM by Zaizi. All documentation including links
to online demo are available at http://fise.zaizi.com/.
The code is available for download at http://code.google.com/p/alfresco-fise/.
© IKS Consortium
2013
120 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Features
•
•
•
•
All content uploaded into Alfresco via Web client, CIFS, IMAP, FTP, WebDAV, etc are all converted
to text and posted to standalone FISE server.
When viewing accessing content in Alfresco, the extracted entities from FISE are shown.
The entities can be selected to list all other content classified with that entity.
It is able to handle the following document formats: MS Office, Open Office, Adobe PDF, HTML,
Plain text, etc.
Architecture
•
•
•
•
•
•
•
•
•
The FISE integration code waits for new content creation in Alfresco.
When content is created it starts a background thread to convert the document to text and post to FISE.
Content creation / upload needs to be fast. Therefore we use a background thread.
This asynchronous approach means we can not assume we can update the content once FISE returns the
extracted entities as the content can be locked, checked out or versioned.
So content is stored in FISE and extracted entities are not stored in Alfresco.
Every time content is accessed we call FISE to get the entities.
We run SPARQL query on FISE to get related content IDs for an entity. These are filtered in Alfresco
to only content the user has read access to.
Only content text is sent to FISE. No metadata extracted from documents are sent.
Administrators can select which content they want to be enhanced by FISE by applying aspect via Alfresco content rules.
Issues:
•
•
FISE does not support concurrent creation of content yet. Alfresco thread sleeps for few seconds between content post.
FISE stores content in memory after restart content is lost. Problem if entities are not stored in Alfresco.
Roadmap / Ideas
•
•
Synchronous integration and creation of entities in Alfresco.
CMIS tracker in FISE to track an
Follow-up Interview and Discussion
Date: Thursday 3, February 2011
Participants:
• Aingaran Pillai and Ezequiel (Zaizi Ltd)
• John Pereira, Andreas Gruber and Rupert Westenthaler (Salzburg Research)
Notes:
è FISE successfully integrated and demonstrated via online demo
è WebinAir for Alfresco Community planned end of March
è Online demo information sent to Paul Holmes-Higgins (Alfresco)
© IKS Consortium
2013
121 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
è
è
è
è
è
Demonstrated and pitched to end-customers (finance sector)
Next step pilot demo for specific user scenario (end of March)
Integrate FISE/Apache Stanbol into Liferay+Alfresco environment
Work in collaboration with Beorn Technolgoies (early adopter for Liferay)
Demo to remain online throughout the next development phase
6.2.3 SourceSense
This page describes the work done to integrate IKS FISE inside Atlassian Confluence according to Sourcesense
Proposal (UC1) to enable auto tagging of pages created inside the wiki.
A Maven project has been settled, the Confluence piece of code to enable such an enrichment is PageListener so
a custom page listener has been implemented. Confluence versions used are 3.0.2 (internal) and 3.1.2 (public).
FISE can provide different enrichment engines but what has been exploited is a subset of the whole. In particular
enrichment regarding named entities and labels have been extracted.
An EnrichmentEngineExecutor interface has been created to provide an indirection between the BaseIKSPageListener and the different FISE execution possibilities. In particular an implementation uses HTTP calls to a
separate FISE server while another one uses a bundled FISE Enrichment Engine (making calls programmatically).
The RDF output has been parsed with Clerezza RDF open source libraries.
The result is that after a page creation the tags (labels) extracted by FISE are automatically created at the bottom
of the page.
This module has been deployed as a Confluence plugin.
The plugin has been deployed and tested both on out internal Confluence and on an external public one: it can be
seen athttp://opensource.sourcesense.com/confluence (please note that it's an online system so remember to not
create test pages or so...)
A particular issue faced has been document here: http://markmail.org/thread/lahkerzbbob4sf4n. The plugin has
been released as open source at https://github.com/sourcesense/fise-sourcesense-integration
© IKS Consortium
2013
122 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
6.2.4 Punkt.netservices
IKS Drupal Modul
Dependencys
Modules
Status Report
Configuration
Functionality
API
fise/fise.module
array $tag _processEntityAnnotationEnhancements(array $enhancement);
array $tag _processTextAnnotationEnhancements(array $enhancement);
array $tags fise_tagging_suggestions(int $vid, object $node);
User Interface
Dependencys
Taxonomy ( http://drupal.org/documentation/modules/taxonomy )
RDF with ARC2 ( http://drupal.org/project/rdf and https://github.com/semsol/arc2 )
Tagging ( http://drupal.org/project/tagging modified version of the tagging module to allow custom styling per tag origin:
https://github.com/thomasfr/tagging )
(Optional) "Reload Tag Suggestions" Button
Modules
© IKS Consortium
2013
123 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Status Report
© IKS Consortium
2013
124 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Configuration
Functionality
The tagging module uses the taxonomy module in the core of drupal which is the default for tagging in drupal.
When editing or adding content and retrieving tags, the content of the textarea is sent to tagging module which calls all an internal tagging hooks
for all submodules. The name of that hook is 'MODULENAME_tagging_suggestions'. You have to replace MODULENAME with the name of the
submodule. In case of the FISE module this is fise_tagging_suggestions. This hook - a simple php function - sends an HTTP Post Request to the
configured Fise Endpoint. The Response gets parsed with the ARC2 RDF Library.
Internally the FISE module splits text and entity annotations, but due to limitations of the default drupal tagging (Taxonomy) where it is not
possible to store additional information to tags without code modifications, the FISE module filters duplicated tags out of the result after
© IKS Consortium
2013
125 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
processing the whole response.
The main entry point - the function which gets called from the tagging module - is 'fise_tagging_suggestions'. This function checks if its a entity
enhancement or a text enhancement and calls the appropriate functions. For entity annotation '_processEntityAnnotationEnhancements' gets
called and for text annotations '_processTextAnnotationEnhancements' gets called. The return value of 'fise_tagging_suggestions' gets returned
to the tagging module which in turn renders the array in the frontend.
API
fise/fise.module
array $tag _processEntityAnnotationEnhancements(array $enhancement);
array $tag return value Example:
Array
(
[#weight] => 2
[#name] => Sweden
[#origin] => FISE
[#annotation-type] => text
)
array $enhancement parameter Example:
© IKS Consortium
2013
126 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Array
(
[http://fise.iks-project.eu/ontology/end] => Array
(
[0] => 1206
)
[http://fise.iks-project.eu/ontology/start] => Array
(
[0] => 1187
)
[http://fise.iks-project.eu/ontology/confidence] => Array
(
[0] => 0.4750801327877954
)
[http://purl.org/dc/terms/type] => Array
(
[0] => http://dbpedia.org/ontology/Person
)
[http://fise.iks-project.eu/ontology/selection-context] => Array
(
[0] => Geoffrey Robertson QC, lawyer for Assange, suggested the latter could be extradited
to the United States, on charges concerning the release of 250,000 US diplomatic cables by Wikileaks,
where he could be sentenced to death penalty. His Swedish counterpart, Clare Montgomery QC, stated
that while Assange's trial would be held in private, the arguments raised in the trial would be
released to the public. She also assured that Sweden was going to provide "protection" against the
alleged risk of Assange's extradition to the US, terming it as a "threat and violation."
)
[http://fise.iks-project.eu/ontology/selected-text] => Array
(
[0] => Clare Montgomery QC
)
[http://www.w3.org/1999/02/22-rdf-syntax-ns#type] => Array
(
[0] => http://fise.iks-project.eu/ontology/TextAnnotation
[1] => http://fise.iks-project.eu/ontology/Enhancement
)
[http://purl.org/dc/terms/creator] => Array
(
[0] => eu.iksproject.fise.engines.opennlp.impl.NamedEntityExtractionEnhancementEngine
)
[http://purl.org/dc/terms/created] => Array
(
[0] => 2011-03-22T14:53:40.267+01:00
)
[http://fise.iks-project.eu/ontology/extracted-from] => Array
(
[0] => urn:content-item-sha1-67148ab6123c7b288609c39e78853ca71a6c4262
)
)
array $tag _processTextAnnotationEnhancements(array $enhancement);
array $tag return value example:
© IKS Consortium
2013
127 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Array
(
[#name] => European Court of Human Rights
[#origin] => FISE
[#weight] => 9
[#annotation-type] => text
)
array $enhancement parameter Example:
© IKS Consortium
2013
128 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Array
(
[http://fise.iks-project.eu/ontology/entity-type] => Array
(
[0] => http://dbpedia.org/ontology/BodyOfWater
[1] => http://dbpedia.org/ontology/Place
[2] => http://www.geonames.org/ontology#H.LK
[3] => http://www.geonames.org/ontology#Feature
)
[http://fise.iks-project.eu/ontology/confidence] => Array
(
[0] => 0.616233139038086
)
[http://fise.iks-project.eu/ontology/entity-label] => Array
(
[0] => Sweden Lake
)
[http://fise.iks-project.eu/ontology/entity-reference] => Array
(
[0] => http://sws.geonames.org/6160492/
)
[http://purl.org/dc/terms/relation] => Array
(
[0]
[1]
[2]
[3]
[4]
[5]
=>
=>
=>
=>
=>
=>
urn:enhancement-81db60aa-f16c-bd77-57c1-9e9500cd2fe0
urn:enhancement-563ab04a-0cd5-c472-a7a4-26b406c1233d
urn:enhancement-839a2651-ab4b-20eb-d386-466c8609476c
urn:enhancement-5557568a-542a-7e0c-aa35-e9af55e59c4e
urn:enhancement-1409ba9c-7e0e-20be-8753-505d1eeaa934
urn:enhancement-794b674f-17ec-0269-23ef-d8196b77618c
)
[http://www.w3.org/1999/02/22-rdf-syntax-ns#type] => Array
(
[0] => http://fise.iks-project.eu/ontology/EntityAnnotation
[1] => http://fise.iks-project.eu/ontology/Enhancement
)
[http://purl.org/dc/terms/creator] => Array
(
[0] => eu.iksproject.fise.engines.geonames.impl.LocationEnhancementEngine
)
[http://purl.org/dc/terms/created] => Array
(
[0] => 2011-03-22T14:53:43.159+01:00
)
[http://fise.iks-project.eu/ontology/extracted-from] => Array
(
[0] => urn:content-item-sha1-67148ab6123c7b288609c39e78853ca71a6c4262
)
)
array $tags fise_tagging_suggestions(int $vid, object $node);
int $vid is the taxonomy id
object $node is a standard object with a body property with the content of the node
array $tags return value example:
© IKS Consortium
2013
129 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Array
(
[0] => Array
(
[#name] => Julian Assange
[#origin] => FISE
[#weight] => 3
[#annotation-type] => text
)
[1] => Array
(
[#weight] => 4
[#name] => Paul Stephens
[#origin] => FISE
[#annotation-type] => text
)
[2] => Array
(
[#weight] => 6
[#name] => Clare Montgomery QC
[#origin] => FISE
[#annotation-type] => text
)
[3] => Array
(
[#name] => Asia
[#origin] => FISE
[#weight] => 10
[#annotation-type] => entity
)
[4] => Array
(
[#weight] => 6
[#name] => Sweden Township
[#origin] => FISE
[#annotation-type] => entity
)
[5] => Array
(
[#name] => Assange
[#origin] => FISE
[#weight] => 4
[#annotation-type] => text
)
)
User Interface
© IKS Consortium
2013
130 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
© IKS Consortium
2013
131 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
6.2.5 Evo43 Communications
Demo
A live demo can be found at: http://IKSforDrupal.net/try-it/
§
Create new content and get suggested tags (concepts) from the Enhancer via Aloha Editor
§
Save the Drupal content also in the Enhancer store to enable SPARQL queries
§
Fetch and display information for concepts in the Drupal taxonomy view via Entityhub
Screencasts are available here: http://IKSforDrupal.net/screencast/
§
Overview
§
Linked Data in action
§
Installation & configuration
§
Fronted Editing with VIE -- RDFa enabled contentEditables
Validation
Enough information was provided at the workshops / wiki to implement the functionalities. The IKS team answered questions quickly.
The provided RESTfull services are handy to use. Caching of entities via Entityhub can help to enhance the
performance.
With the tested content the editor/user got fast but not always good results from the Enhancer.
Lessons learned
© IKS Consortium
2013
132 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
With the Apache Stanbol components it was easy to support semantic services in Drupal 7.
The Enhancer component now supports the user with automatic suggestions for content and the Entityhub component is a very useful tool to access data from the Linked Open Data cloud.
The installation of the Enhancer was quite easy, without huge problems und well documented. There were some
troubles with the configuration of the Entityhub at the beginning.
Visibility
The Drupal 7 module was presented at the Aloha Editor Developer Conference in Feb. 2011.
Software components used
§
Aloha Editor
§
Apache Stanbol
§
Drupal 7 (+ Modules: Active Tags, WYSIWYG)
6.2.6 Interact
Introduction
WordLift is a WordPress Plugin to enrich user-created text (a blog post, article or web page) with HTML Microdata and to improve content findability.
WordLift reads pages or blog posts, understands it and enriches it using HTML Microdata. All the information
retrieved can be manually edited by the author before publishing.
More information:
§
WordLift presentation on SlideShare,
§
WordLift screencast.
Demo
The demo site we're using for the testing is http://wordlift.insideout.io and WordLift is currently at the release
1.2. WordLift is available worldwide to any WordPress user on the WordPress Plugin Directory.
Validation
It is straightforward to get a server running. Some extra-configurations are required to enable engines such as
OpenCalais, Zemanta and the Refactor Engine.
The Refactor Engine can be easily configured once the syntax is explained and tested; updating the Refactor
rules may take less than a minute and does not require restarting the server.
Once started the server is stable and runs without interruptions. The logging is extensive and helps trap recognition or communication issues with external services.
We added some custom logging to the Refactor in order to ensure our rules were successfully loaded
[STANBOL-269] and, as sometimes external services, such as DBpedia, return malformed responses, we're
looking into STANBOL-8 to have the server handle those as warnings instead of terminating the whole session.
© IKS Consortium
2013
133 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Lessons learned
The support of the community is strong, never hesitate to ask to the Stanbol mailing list.
The installation and execution of the server is straight-forward (for better performances use at least 1 Gbytes of
RAM or even more).
Adding the non-default engines, such as Zemanta and Refactor Engine is simple as well and their configuration
(including OpenCalais) can be easily accomplished using the Felix Web UI.
Should any issue arise, the logs are quite extensive and can help track down most of the issues and eventually
provide the meaningful information to post on the mailing list for further help and support.
The Refactor Engine uses its own syntax for its rules. The syntax is well documented and, once again, the support is extensive in the Stanbol mailing list. Once the syntax is clear, updating the rules - usually on behalf of
users feedback - is just a matter of seconds and does not have any impact on the already installed plug-ins which
can then benefit of the updates right away.
Visibility
The plug-in has been officially presented the beginning of July 2011 at the IKS Workshop in Paris. The related
materials have been published online:
1. The related presentation has received more than 500 views;
2. A screencast is also available.
3. WordLift product page on LinkedIn.
The WordLift plug-in for WordPress is listed in the official WordPress plug-in directory and has been downloaded from than 150 times in one week, with people each testing specific knowledge fields and providing feedback.
A demo site is available at http://wordlift.insideout.io.
Software components used
§
§
§
§
§
Apache Stanbol
Apache Stanbol - Refactor Engine
WordPress 3.1+
TinyMCE Editor (integrated in WordPress)
jQuery and jQuery UI
6.2.7 Acuity Limited
Demo
The demo available has a simple custom-built user interface designed to demonstrate the operation of the integration between Fedora Commons and Stanbol KReS components, OntoNet and the Rules component. (It does
not attempt to simulate an end-user application backed by Fedora - Fedora does not supply an end-user application out of the box.) The demo is available at http://fedora-stanbol.acuityunlimited.net:18080 and usage instructions are given on the site. The application loads (ingests) Fedora content objects and their metadata into Fedora.
A dedicated Fedora plugin module is installed, and detects that content has been added to Fedora and sends con-
© IKS Consortium
2013
134 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
tent to an OSGi component that then populates OntoNet, primarily by setting up a custom space in an OntoNet
scope. The Rules component is used to enrich the semantic relationships amongst the metadata, computing new
relationships. Ontologies and data is managed using OntoNet and Clerezza for SPARQL query access. Viewing
Fedora's contents is made possible as the demo allows access to Fedora's basic web-based repository inspection
interface. The demo also constructs queries to show the resultant semantic metadata managed within OntoNet.
Metadata ingested into Fedora comes from various sources. Structural queries (collection membership) are enhanced as new relationships between objects are computed from those present in the content ingest. Content- and
domain-specific knowledge is sourced from the VRA image metadata scheme and fields from Getty United
Artist List (ULAN) thesaurus converted to SKOS.
This can be used, for example, to obtain information about the type of image content, in terms of Fedora content
model objects, or about the creator of the associated work. Semantic information is made available to Fedorabacked applications (for example, the basic demo), through underlying queries over data and ontologies managed by OntoNet.
Validation
We have worked with a client to source content and metadata. Use cases based on their researchers' and cataloguers' needs have informed the development. Feedback received about the integration within the community to
date has been positive, awareness raised and comprehensive support for enhancing Fedora with semantic information is regarded as a desirable feature (a further Fedora Commons committer has become active on the Stanbol development mail list).
The integration demonstrates how dedicated content-rich interfaces backed by Fedora can be enhanced to obtain
semantic information; for example, with regards the demo content, about the type of image content or its creator,
whilst promoting flexible configuration of collection structures over the content. Research users could for example, list artists in the collection, to find further related works and images within the content repository, or find
related artists, collaborators, periods of activity etc to aid their research without leaving the repository environment.
We provided input to the Stanbol/KReS developers in order to aid development and refinement of KReS, necessary to the integration but of general application, particularly with regards to scaling to handle larger data volumes, and lifecycle management of semantic information using the OntoNet API.
Lessons learned
A major challenge in terms of effort expenditure was the overhead in working with the Stanbol/KReS Java API
in the context of a Tomcat application to integrate Fedora with KReS. The Java API was required due to the
scale of the information potentially transferred to the KReS components from Stanbol. Previous familiarity with
OSGi development is highly recommended if developing with the Java API.
Additionally, the KReS components used had not reached a stable state; components were not ready to handle
our specific use cases. We were not in a position to use all of the functionality we would have liked to during
integration development timeframe, such as the OntoNet Registry. The Java API took time to figure out in practice, as developments were ahead of documentation, and we were happy to receive the responsive KReS developer support. We encountered various difficulties initially, eg data access via SPARQL/Clerezza, graph identification to relate Fedora content and semantic metadata in OntoNet. Issues when raised were addressed by the
Stanbol/KReS developers, some have been tracked on JIRA. Continued maintenance of the KReS components is
suggested to prove their stability and scalability in a production context.
These obstacles overcome, semantic enhancement of Fedora has been demonstrated and there is momentum in
the institutional sector for further work. Our use cases involving KReS focussed on management and mining of
semantic information within supplied metadata to provide additional value; there is also potential to broaden
scope for realising further value using Stanbol components in conjunction with KReS, such as entity extraction
and enrichment using background knowledge sourced from publishers of linked data sources.
Visibility
Raising awareness and discussion of integration at Fedora development level and with user community, visibility
at Open Repositories conference. Posts authored for the IKS blog. Additional illustrative videocast about the
Fedora/KReS integration demo.
© IKS Consortium
2013
135 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Software components used
Apache Stanbol framework, Apache Clerezza, Stanbol OntologyNetworkManager (ONM), KReS
Rules/Refactor, Duraspace Fedora Commons Duraspace, Duraspace Mulgara, JMS, OSGi DS (Apache Felix)
6.2.8 Lunaria
Demo
This is available via www.lunariaweb.com
The Apache Stanbol installation is publicly accessible at verinote.org:8080
Validation
We have directly worked with some users to add content. This has allowed them to create navigational terms and
prompts which reflect their content. The feedback we have directly received is that this enhances the navigatonal
experience.
Additionally we added semantic enhancements from external resources. The feedback we received on this was
very positive as it served as 'prompts' for learning and/or for additional action by the user.
Lessons learned
The core Apache Stanbol was not stable and this brought challenges.
But, semantic enhancement has plenty of potential in the public sector around the interaction with OpenData. It
has further benefits within the area of personal-learning portfolios ie evidence gathering, learning or as a personal recorder.
Visibility
We have demonstrated the site to a range of potential end-users and clients. This has included a range of agegroups from school children through to the elderly. We have had positive feedback from professionals involved
in a range opf activities from the collection and referencing of data for setting 'care' standards in education,
through to care for the elderly as well as from educatiuonal providers and community groups.
Software components used
Apache Stanbol
Drupal 7
Drupal Apache Stanbol Module
6.2.9 Drunomics
Introduction
This documents represent the validation of the early adopter program to which drunomics participated. The main
goal was to build an Stanbol indexer for Drupal structured data, such that the following stories are enabled: S05:
Assistance with Semantic Tagging S19: Enriching content with information retrieved from internal sources S21:
Entity extractor support in editors S23 / S29: Enriching content with information retrieved from external sources
The indexer has been implemented as a Drupal module, which can be downloaded from here. A screencast presenting the Drupal Stanbol module is available at https://vimeo.com/55163277. Furthermore, the Drupal Distribution IKS Content Enhancement Demo has been created, such that everyone can easily test the IKS tools with
Drupal.
Demo
A public demo of the created Drupal Distribution is available under http://iksdemo.drunomics.com. It makes use
of the Search API stanbol module to send Drupal’s content to the EntityHub. Then, Apache Stanbol’s content
enhancement chains have been configured to leverage Drupal’s entities also. The demo makes use of vie.js and
its widgets annotate.js and the VIE autocomplete, which both leverage the referenced dbpedia index as well as
Drupal’s content.
Benchmark
© IKS Consortium
2013
136 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
We ran a benchmark to see how fast Search API Stanbol was able to index Drupal entities. 10,000 entities were
generated in Drupal (8,000 persons, 1,000 organizations and 1,000 locations). Each entity was composed on
average of 10 triples and 2KB data as RDF/XML. The indexing took 2mins 51s on a macboor air (1.8 GHz,
4GB) with a local instance of Stanbol.
Validation
Apache Stanbol was pretty straight forward to use and configure. The IKS team was very helpful in introducing
the software and answered occurring questions very quickly. While the server is very powerful and offers various helpful services, it can become difficult to get a good overview of all the available features. E.g., we realized
rather late that Apache Stanbol is able to use JSON-LD only when returning text enhancements, but not (yet) at
the EntityHub REST service which we use to index Drupal data. But thankfully, the IKS team was a great help
with exploring Apache Stanbol’s big feature set. The entityhub and enhancer components seem to be a great
companion for Drupal based web applications wanting to enhance their content with remote content. In particular, Apache Stanbol’s entityhub and enhancer components could be a great fit for organizations that are running
multiple websites but want to support their editors with establishing a good integration of the organization’s
distributed content.
Lessons learned
Making use of the existing Javascript libraries in Drupal was more problematic than expected. First off, the provided Javascript libraries partly depend on libraries with newer versions than the versions that Drupal uses. Secondly, some new bugs have been triggered by version combinations other than the ones used in the official examples. Related bug reports have been created (see the appendix). Thus, the work needed to properly integrate
already existing Javascript libraries in a pre-existing environment should not be underestimated.
Visibility
The Apache Stanbol Search API backend module is available as Drupal module on drupal.org. Together, with a
provided pre-configured Apache Stanbol package for use with Drupal this makes it very easy to setup Apache
Stanbol with Drupal!
Furthermore, the demo distribution shows how Apache Stanbol could help editors with content enhancements
and provides a basis for any further custom integrations based on Drupal.
A blog post including screencasts and announcing the distributition and the demo will be published soon.
Software components used
- Apache Stanbol - Vie.js, annotate.js, VIE autocomplete - nicEdit - Drupal 7 and various contrib modules:
Search API, RDF Extensions, Entity API
6.2.10
Logicells
Introduction
Our work is focused on the interactions between VIE, the enhancement engine, the contentHub, and the
SPARQL endpoint. We also tried to use IKS technologies as much as possible to realize a complete and functional application that basically receive messages, and automatically enrich their contents, classify them, and
notify users.
Demo
Demo is available online at: http://thomas-test.mitechnologies.net/
And you can see video demo here: https://vimeo.com/54349086
Validation
Create notes:
Users can add notes with our without manual annotations. In each case, notes are sent:
1. to the Stanbol enhancer through the RESTFULL services where they are enhanced and persisted for later search ;
2. to the Naive Bayes engine in order to be classified in a specific topic ;
© IKS Consortium
2013
137 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
3. the system notifies users who subscribed to the topic.
We used VIE as the user interface for manual annotations.
Search notes:
Once more, we used VIE as the user interface. Users can edit parts of a sentence witch match to a SPARQL
query.
We also had to use parsers to deserialize JSON and XML results in .NET objects to handle them properly in our
business logics (especially for displaying notes based on SPARQL query).
Lessons learned
During test phases, we noticed that the tool (Apache Stanbol) as it is in its actual form is not reliable in extracting entities and has some incoherencies in detecting them. So it has to be more precise and robust in order to
answer our customers’ needs. Nevertheless, we can see its potential and the fact of having a semantic tool next to
our CMS.
Visibility
We will soon present the application to the CGPME.
Software components used
1.
2.
3.
4.
Dotnetnuke
Apache Stanbol : for semantically enriching and persisting contents
VIE : for manual annotating and displaying entities
Naïve Bayes classifier
6.2.11
Content Control
Introduction
See blog: http://blog.iks-project.eu/createphp-mission-accomplished/
Demo
Demo is available online at: http://demo.contentcontrol-berlin.de/
Validation
• Feedback from editors during the website integration project
Initially, the editors' reaction to the Create.js user experience was very positive. It was found to be very easy to
understand and enjoyable to work with. Over the course of the project, this changed a bit, however. Extended
usage revealed a few problems, like quirks in browser's contentEditable implementations, Javascript errors and
exceptions, and a few bugs and usability issues, which have been reported to the relevant issue trackers. But with
the type of site we were working on, the biggest issue was performance. Using Create.js on a page with 50 or
more editable properties caused numerous slow running script errors, browser freezes and crashes, especially in
Firefox. Another thing that became quite obvious after a while were the limited editing options the builtin Hallo
editor offers.3 For authors used to the plethora of options that the current mainstream editors like TinyMCE
offers, it was quite frustrating that even entering hyperlinks required writing them somewhere else and then
copying the resulting HTML into the editable region.
• Create.js from the developer's point of view
Instantiating Create.js for simple use-cases is relatively straightforward, although the requirement to pass essential configuration values (like the URL of the REST service) as functions makes it harder than hoped for to provide a PHP wrapper or widget configuration. When using more elaborate setups with a number of different editor configurations, setup code becomes very verbose and repetitive. Create.js more or less assumes that you can
make a direct mapping between RDF types and properties on the one hand, and storage locations on the other.
For example, if “sioc:Post” entries are always stored in a database table called 'my_articles', and all entries from
that table will always be rendered as “sioc:Post”, configuration handling would be quite simple, but in most
situations, websites are built with a set of default storage classes provided by the CMS that are then tweaked to
fit into a particular context. So entries from the “my_articles” table might be displayed as blog entries in one part
of the site and as static editorial content in another. It can of course be argued that this is bad practice, but the
fact remains that it is also common practice, so requiring potential implementors to adjust their data model every
© IKS Consortium
2013
138 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
time they want to change their RDF output will most probably slow down adoption or lead to wildly inaccurate
RDF information, if people just use defaults provided by their system and don't adapt them to the actual content.
• Working on Create.js
When working with Create.js's code, the list of dependencies provides a barrier to entry. One needs to understand both VIE and Create.js to some degree, and be able to discern what happens in which module (and the
documentation doesn't provide as many hints as would be needed). Additionally, at least some familiarity with
jQuery UI's widget architecture and backbone.js is required. For the Hallo editor, one has to learn Coffeescript
on top of that. Since Hallo, Create.js and VIE all have separate issue trackers, it can already be a challenge to
find the right place to post reports to when starting to work with Create.js. Additionally, the published documentation is somewhat lacking. Ordinarily, JS projects of the complexity of Create.js or VIE at least provide an
overview of configuration options and a range of live demos that show most of the main applications for the
code in question. For Create.js, the primary source of information is one README file on github, and some
linked blog posts, which leaves a lot of ground uncovered. For example, an API documentation that explains
how to interact with the toolbar and the rest of the user interface as well as a description of the plugin interface
would have made it easier to achieve a greater integration in the available amount of time. For VIE, there seems
to be a bit more material available, but it's still kind of hard to grasp VIE's purpose. On the one hand, it provides
a lot of query functionality (that e.g. the demos on the project's homepage showcase), and on the other hand, it
serves as a ORM of sorts, in that it provides an object representation and (at least parts of) a persistence layer by
the way of Backbone.js. Especially strange are the parts where Create.js and VIE differ, for example, in the VIE
documentation, object properties are usually marked in the same notation that is found in HTML as well (e.g.
“dcterms:title”), while Create.js expects to find this in the page's markup, but sends and expects to receive
JSON-LD (where “dcterms:title” is transformed into “<http://purl.org/dc/terms/title>”), which forces the REST
backend to translate between the two, while the benefit from using a different format is not at all evident.
Lessons learned
It has been reaffirmed once again that working with in-development software requires quite a bit of coordination
with the upstream developers and should be avoided in projects on tight deadlines, because there is always the
possiblity that discovered problems need architectural changes to be addressed, which can mean API changes,
which then in turn have to be reflected in derived code.
Apart from that, we learned a great deal about RDFa, which will come in handy in later projects
Visibility
CreatePHP is available on github. It has been integrated into the MidCOM framework, and Symfony CMF, discussions about integrations into other systems are ongoing
Software components used
Mostly Create.js, VIE, Hallo.js and the respective dependencies
6.2.12
Object’Ive
Introduction
Object’Ive is a Paris based information technology consulting company with a focus on semantic web technologies.
Beyond our information technology consulting activities (realization of time & materials as well as fixed price
projects), our internal research activities lead us to develop specific solutions (mobile applications, intelligence
tools, CRM, code translator...).
During the past years, we developed our expertise in both fields of mobile technologies through the mastering of
the main mobile development platforms (iPhone, Android, Windows Mobile and BlackBerry) and knowledge
and content management technologies.
In this context, Object’Ive has integrated Apache Stanbol Enhancement Engines and VIE in its R&D project
Blogomatic based on the CMS platform Nuxeo
Blogomatic allows the user to gather contents (articles, videos and pictures) coming from both Internet and Intranet sources by querying search engines and analyzing what is returned.
Contents are made available to the user through an automatically generated website and are fully administrable
through the back office. They are automatically categorized and entities are being extracted (Tag Cloud).
© IKS Consortium
2013
139 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Blogomatic has been designed with a modular architecture. One of the modules we developed (BMSemantic)
allows the interaction with Apache Stanbol Enhancement Engines through REST calls.
When text content is collected by Blogomatic, it is sent using REST to Apache Stanbol Enhancement Engines
that returns an N3 model.
This N3 model is interrogated thanks to SPARQL requests included in BMSemantic allowing recovering the
desired entities. Using our own SPARQL queries permits us to better adjust the entity extraction (i.e. extraction
of new entities or selection the most relevant entities to extract through a ranking process).
In addition to the existent Apache Stanbol Enhancement Engines indexes (Zemanta, DBPEDIA and Open Calais), we added the following new indexes:
• Reegle
• EDF (subsidiaries)
• EDF (acronyms)
All the extracted tags are stored in a PostgreSQL database used by the CMS platform Nuxeo and available to the
user as a tag cloud.
Demo
A YouTube video presenting the Blogomatic tool is available here.
To access the online demo system, please send an email to [email protected]. We will provide you
with a user account and access details.
There are two URL addresses on the home page:
1. The first one, “Génération et liste sites” (http://cognitive-back.object-ive.eu/blogomatic-back), allows
the user to select the keywords to search, the sources to query and set the name of the website that will
be generated.
2. The second one, “Administration document” (http://cognitive.object-ive.eu/nuxeo/login.jsp), is used for
the administration of the generated websites and their contents.
The generation and consultation process of a website is the following:
➢ Definition of the website parameters:
• Setting of the website name (words without spaces and in lower case)
• Insertion of the keywords to search (auto-completion is made available through VIE)
• Selection of the language
• Selection of the sources to query
➢ Website generation:
• Gathering of the content in each selected source
• Sending of the content to the BMSemantic module that allows, by interaction with Stanbol, the extraction of tags and their backup in the database as well as the classification of the content. This classification is realized using a classifier algorithm developed by Object’Ive.
• Backup of the generated website and its content into the CMS platform Nuxeo.
➢ Website consultation and navigation:
• After the website is generated, it is consultable at the URL address included in the website name in the
home page.
• The navigation within the website is made possible by source (upper menu), by extracted tag, by extracted category or thanks to the search bar included in it.
• When selecting an article, it can be modified directly from the web browser thanks to VIE. The generated annotations on the contents using VIE are not backed up in the database with the other tags extracted
by Stanbol that compose the tag cloud.
Validation
The use case proposed to validate the developments on Blogomatic was the following:
• The user sets a website name, enters the keywords to search with auto-completion provided by VIE, selects the sources to query and launches the website generation
• The user can then navigate within the website by source, by tag, by category or using the website search
bar
• The user can modify the website contents directly from the web browser as well as create annotations
on them using VIE
© IKS Consortium
2013
140 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Lessons learned
Apache Stanbol does not include for the moment an NLP model for the French language. As a consequence, it
was a significant challenge in order to obtain relevant annotations in the frame of Blogomatic when querying
French sources. By using a ranking process on the extracted items included in the N3 model analyzed by the
SPARQL requests we implemented, we managed to enhance the relevance of the annotations.
The semantic components (Apache Stanbol Enhancement Engines and VIE) that we implemented in the
Blogomatic solution allowed us to greatly better of both the functionalities of our tool and the user experience.
We are confident in the potentialities of the components developed in the frame of the IKS project and will follow with interest the future advances to see how we can spread them.
Visibility
A YouTube video presenting the integration of the IKS components is available here.
To access the online demo system, please send an email to [email protected]. We will provide you
with a user account and access details.
Software components used
•
•
Apache Stanbol Enhancement Engines
Vienna IKS Editables (auto-completion, annotation)
6.2.13
Ooffee
Introduction
The European funded project Linked Heritage aims to provide culture heritage data and thesauris to Europeana.
Ooffee participate in this project around the building of a thesauri import, management and mapping website.
On the user part, this website has to be feature rich and easy to use. On the data part, they have to be fully skos
and semantic.
Demo
The demo website is available here : http://www.culture-terminology.org/
Mains part of the actual version are :
• 1° Import : http://www.culture-terminology.org/import/
o This form collect metadata about the thesaurus and :
§ transform CSV file to skos compliant thesaurus
§ or process your rdf/xml file and import it in the system
§ or allow you to create a graph from scratch
• 2° Modify and map : http://www.culture-terminology.org/mapping/?uri=http://www.cultureterminology.org/thesaurus/flotest/flotest
o This interface allow you :
§ to graphically edit you thesaurus (with drag and drop and double click)
§ to map you thesaurus to another one in one click
§ to explore the different languages of you thesaurus
• 3° Edit has wiki : http://www.culture-terminology.org/edit/wiki/
o This interface propose a beta version of a wiki edit of your thesaurus. You can then simply
navigate throw your thesaurus and edit your concepts
• 4° search : http://www.culture-terminology.org/search/
o This part bring the search feature to the user. This search is cross website's thesauris and also
find information in the wikipedia dataset.
Validation
•
•
•
Modular architecture of Stanbol help to build your "own Stanbol" really easily : - The bundleList feature allow you to select witch modules you want - The bundleConfig feature allow you to configure directly configure your services when the server start.
The entityHub is a great feature that provide fast and reliable access to local data but also to external
LOD repositories
The project choice of using Felix and Clerezza made the "hacking" of Stanbol for particular need really
easy to do.
© IKS Consortium
2013
141 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
•
•
•
•
•
•
•
•
API definition is clear, well documented and easy to use.
The UI part of the IKS project (Hallo editor, vie and annotate.js), seems really promising but may lack
of some documentation and concrete examples for lower down the learning curve.
Lessons learned
Stanbol framework is easy to use at the REST api level but also provide comprehensive structure that
allow to dive more deeper in the implementation and create specific implementations
Entityhub is a great feature to get access to LOD repository and locally create data in an efficient manner.
o Many call options are offered that allow great customisation at an implementation level.
Onthonet functionalities seems now ready to use. When the linkedHeritage project start this functionalities are in deep modifications and not clearly documented. So they where not directly integrated. But
recent improvements on this will lead to a new consideration of this features.
Stanbol is a schema agnostic framework that allow to deal with any kind of ontology with minimal configuration and offer great flexibly for addressing real use cases.
Production readiness of the project, server is stable and some utilities allow to manage a Stanbol in production.
Visibility
•
•
•
•
The linkedHeritage project site : http://linkedheritage.org/
The Culture-Terminology site : http://culture-terminology.org/
The GitHub repository : https://github.com/florent-andre/LinkedHeritage
IKS blog post about a first version of the culture-terminology website : http://blog.iksproject.eu/thesaurus-management-tool-linked-heritage-project/
Software components used
Apache Stanbol framework Apache Stanbol EntityHub Apache Clerezza SingleTdbDatasetTcProvider Hallo
editor D3.js Rdfquery
6.3 CMS Tool Providers
6.3.1 SalsaDev
Overview
This page, initially intended to provide custom built enhancement engines for classification and information retrieval for FISE goes a bit beyond.
We integrate our categorization engine as a FISE enhancement engine (cf proposal), and given the
code quality and community support/responsiveness we largely integrated FISE components into our
own engines.
Integrating FISE allowed us to concentrate on our core competencies while delivering state of the art
software. We've refactored and redesigned major parts of our own software stack while taking into
account engine pattern-designs, content-enhancement and chaining methods developed within the
FISE project.
Demo
§
A Fise demo instance is available http://fise.salsadev.com (downtime may apply)
§
A Fully loaded salsaDev sample account which showcases FISE internal integration is available http://api.salsadev.com/demo(downtime may apply)
© IKS Consortium
2013
142 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Validation
We managed to supply our categorization engine as a FISE enhancement engine while keeping the
flexibility and ease of use of salsaDev's categorization scheme intact. While not a RDF-based company, the support of the community has been very helpful in delivering namespace that fits the salsaDev's categorization rdf-less schema.
We also managed to replicate the content/engine pattern design from FISE into our own software
stack. While our architecture is does not run on OSGI we've still be able to leverage the chaining, separation of concerns and specialization introduced in FISE for semantic analysis.
As a conclusion we can now both run our categorization engine within FISE, or embed dedicated FISE
engines into our stack.
Lessons Learned
There are multiple lesson learned from the early-adopter FISE project both at "software design" and
"semantic meaning" level. The main lesson though is pretty straight forward:
despite all beliefs there are no common/standard conception of what defines classification & information-retrieval.
The FISE project - and its Stanbol software initiative - is a step forward in semantic lingo/application
standardization while maintaining a high level of agility.
Fise makes it possible to seamlessly mix different technologies together while leverage each engines
to its full extent!
Software components used
§
Apache Stanbol Enhancer
§
Glassfish Application Server
6.3.2 Ectware s.r.l
Introduction
Etcware is an italian company with a focus on semantic web and technologies.
In a research project we developed SKOSware (http://www.skosware.it), a product for the social implementation
of SKOS thesauri. The first SKOSware integration is in Italian Data Protection Authority portal that has been
developed using a Liferay Integration platform. In this portal we have implemented manual contents enhancement functionalities: contents can be enriched with topics, time events and they can be georerefenced. We integrated also SOLR and a SKOS thesaurus based search: after a first full text search it is possible to refine search
by browsing in thesaurus.
In the early adoption project we added the automatic enhancement of contents, and we integrate SKOSware
generated thesaurus with enhancer by creating Keyword Linking engines and installing them in the enhancement
default chain of Stanbol.
Demo
A YouTube video is available for [1]. The video shows the integration with Stanbol.
Validation
A YouTube video is available for [2]. The video shows the integration with Stanbol.
Lessons learned
We continue to explore the capabilities of Stanbol. In particular, the functions related to rules and the inference
engine because, we think in this way to complete our solution.
© IKS Consortium
2013
143 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
The architecture of Stanbol, based on interfaces REST, it is absolutely aligned with the architecture of our solutions and we intend to use other Stanbol services, but in particular the enhancement chains to integrate other
engines.
Visibility
A YouTube video presenting the integration with Stanbol. To access the online demo system, please send an
email to [email protected].
Software components used
Enhancer with custom engines based on keyword linking engine. Content-hub where we stored all Liferay contents, by using Liferay asset identifier as URN.
Moreover we are using rules to validate our SKOS thesaurus.
6.3.3 CELI France SAS
Introduction
This documents represent the validation of the early adopter program to which CELI France participated. There
where four main challenges:
• Integrate semantic processing for languages other than English in Stanbol.
• Integrate specific named entity extraction for the domain of CV management.
• Prove the facility of the integration with mostly used open source DMS thanks to the adoption of Stanbol.
After the program, Stanbol adopter now dispose of tools integrated into Stanbol for performing multilingual
analysis ranging from simple lemmatization to named entity extraction. CELI, on the other hand could easily
integrate its CV parsing technology into two different Open Source DMS, namely Alfresco and Nuxeo.
Demo
Putting a public web demo about CV parsing on the web is a delicate matter, for obvious reasons of privacy
protection and security. Nevertheless, as an output of these program, a public showcases (with fictive CVs) of
the integration of CV parsing with alfresco is available here here.
There are also two other possibilities for testing the technology developed during this pilot project. On the one
hand the main release of Stanbol now embeds the plugin for accessing CELI multilingual services. They are
available for instance here and here. On the other hand, there is a stateless (i.e. non information preserving, non
caching) demo on CV parsing available [193.252.185.82:8081/cvparser-webapp/home here] (only for French
CVs).
Validation
Validation of the integrated solution was so far validated at the premises of the industrial user "Objet Direct"
which adopted it for managing the vast amount of CVs they receive every days. Apart from that some validation
in terms of accuracy and precision was carried on in a laboratory context, by using well known methodologies in
the domain. Both structural parsing and Named Entity extraction where evaluated on gold standards, and it
emerged that results are state-of-the-art compared with other results obtained in academic competition and far
above the state-of-the-art if compared with current market offering.
Lessons learned
The most important lessons that was learned from this integration is the absolute need of standardization and
convergence between Linked Data and linguistic data. This convergence will open up a wide set of possibilities
both on the research side and on the commercial one.
On the more technical side, CELI enhancement engines are service based and perform the textual enrichment
process by invoking proprietary Web Services. The Web Service clients embedded in the enhancement engines
access the services via a HttpURLConnection urlConn. Integrating the services using standard SOAP clients (by
means automatic code generation tools) proved to be problematic. CELI enhancement engines connects to proprietary services that need a license key in order to be accessed. A guest account without license (but with the
access limited to 100 requests per day) is available to all user in order to test the services. It is important to include in the control panel of the service a facility to enable/disable the engine in order to activate the trial license
© IKS Consortium
2013
144 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
only when they want to and not by default. If an enhancement engine is willing to handle entities/concepts different from the "usual" ones, involving a specific domain ontology, it would be helpful to have guidelines.
Visibility
The optimized results of industrial validation will become soon a product line of CELI France. In the context of
the envisaged marketing actions (web site, press release, techno/business publication,...) a big emphasis will be
put on the fact that the service stems out as a side effect of an important European research effort.
Software components used
CELI enhancement engines doesn't depend on software component external to the project, with the exception of
the default libraries included as general dependencies (i.e apache commons, log4j).
6.3.4 FORMCEPT
Introduction
FORMCEPT is an effort to make content analysis accessible to everyone, be it an enterprise, an individual or a
device. We are working on some interesting state of the art products that will be available both as Software as a
Service Model (SaaS) and as installable products.
FORMCEPT entered the early adopter program with the use case of analyzing medical records. As a part of
early adopter, FORMCEPT created a new Healthcare enhancement engine to enhance the medical records with
drugs, diseases, and other health related entities. For more details, please take a look at the blog.
Demo
Demo is available online at: http://demo.formcept.com:8080/enhancer
The knowledge base that is used by the enhancement engine is built on top of DBpedia 3.6 and specifically these
domains1. Drugs and Diseases
2. Chemical Compounds
3. Species
4. Others, like- Health, Microbiology, Medical Diagnosis, Medicine, Perception and Biology
The enhancement engine not only annotate the entities but also find the overall broader categories with the relevant hierarchy. As of now, the hierarchy is stored as a path under SKOS_BROADER annotation. A typical annotation looks like• "broader": "Health->Diseases and disorders->Symptoms->Symptoms and signs: Digestive system and
abdomen->Vomiting,
• "comment": "Vomiting (known medically as emesis and informally as throwing up and a number of
other terms) is the forceful expulsion of the contents of one's stomach through the mouth and sometimes
the nose. Vomiting may result from many causes, ranging from gastritis or poisoning to brain tumors, or
elevated intracranial pressure. The feeling that one is about to vomit is called nausea, which usually
precedes, but does not always lead to, vomiting.",
• "created": "2012-07-01T12:23:58.495Z",
• "creator": "org.formcept.engine.enhancer.FCHealthCareEnhancer",
• "end": 768,
• "extracted-from": "urn:content-item-sha1-09055dcdcb07a20b3b30f64079a9a2779600f801",
• "selected-text": "vomiting",
• "start": 760,
• "type": "Health"
For more details, please take a look at- http://formcept.com/blog/healthcare-stanbol/
Validation
Validation was done by running the tests against the CALBC Corpora. As of now, the enhancement engine has
been tested against 1,725 (42,368 words) test cases. For more details on the benchmark and performance, please
take a look at- http://formcept.com/blog/healthcare-stanbol/
Lessons learned
© IKS Consortium
2013
145 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Apache Stanbol provides a unified stack for text analysis that is modular and customizable.
Visibility
FORMCEPT will be promoting Apache Stanbol with its Healthcare analysis. There are two blogs that have been
setup to explain the details of the work done as a part of early adopter programme1. Healthcare - Analyzing Medical Records | FORMCEPT
2. Apache Stanbol - Introduction
More screencasts and blogs may be added based on the continued effort of integrating Apache Stanbol with
FORMCEPT Big Data Analysis Stack
Software components used
Apache Stanbol Enhancer and Enhancement Engines
6.3.5 Netlabs.org
Introduction
This is a review of the Early Adopters Project for netlabs.org, proposed and implemented by Adrian Gschwend,
[email protected]. The project is defined at http://wiki.iks-project.eu/index.php/Netlabas_Proposal.
Review of the Workpackages
1.
2.
3.
4.
5.
6.
Step 0, Project inception: This was very straight forward. The Stan- bol setup was well documented,
compiling Stanbol from latest Subversion source was straight forward. In the beginning launching the
full launcher resulted in some memory issues which could easily be fixed with giving more memory to
the Java VM. Stanbol team was helpful and supportive on the mailing list.
Step 1, Stanbol bootstrapping: Setting up Stanbol in a FreeBSD Jail was no problem either, the Stanbol
instance was deployed in the Intranet. First interaction with the web interface for storing ontologies was
straight for- ward. Curl worked as well for the ontologies tested at this point. Deleting was not possible
yet as it was not implemented in the Ontonet component at this point. Later I discovered that I could not
create ontologies with a given identifier, Stanbol only assigned UIDs for the ontologies which lead to
some problems later, see remarks in Step 3.
Step 2, First inference: On this task I lost quite some time. I oriented myself on the rules example in the
documentation of the Rules endpoint. Unfortunately this did not work, interacting with Stanbol at this
point just resulted in HTTP error messages. After several mails on the mailing list I figured out that I
did not properly clean the packages in my “stanbol” directory which I started from the root directory of
the source. Even when I compiled the source later I always used the original build of the extensions.
The old source had wrong examples of the SWRL syntax on the page so that explained some of the errors I got back. The REST API itself was not documented, after posting to the mailing list Andrea
helped me on that and started documenting the examples. End of October all issues were finally solved
and I could process the rules I defined. To my knowledge the only open problem is that one cannot use
arbitrary strings for the recipe identifiers, it has to be a URI instead. This is still wrong in the documentation at the time writing (the given examples do not work).
Step 3, Ontology caching: I first started testing it via CURL which worked pretty good, later I implemented a Node.js based module which gets called by our framework. The framework first checks if the
ontology is already cached in Stanbol. If this is not the case it fetches the ontology and pushes it to
Stanbol. This worked fine with one exception: If there is no owl:Ontology class assigned to a URI in the
ontology Stanbol does not know how to call the ontology and comes up with a unique identifier. Like
this the ontology is cached but for our framework it is not possible to get it, as we do the lookup based
on the prefix of the ontology. I talked to Alessandro about this issue and he proposed to add an alias
functionality to it. The feature was added mid November and since then caching works fine, also from
my Node.js code.
Step 4, Accessing Stanbol from our framework: To integrate the ontology caching was pretty straight
forward, we adopted our dereference method to look up the ontology in Stanbol first. Since the extension in Ontonet mid November this works well.
Step 5, First performance tests: Using Stanbol for ontology caching makes ontologies a lot more predictable. On my development machine (MacBook Air 2011, SSD) we reached response times of around
270ms per request for a cached ontology, on the virtualized test system I get a response in about 300ms
(ping RTT 2-4ms). This is a huge improvement to the reality in the (semantic-) web, unfortunately
some ontologies are hosted on unreliable and slow links. From our experience ontologies hosted at
© IKS Consortium
2013
146 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
7.
8.
9.
W3C servers can be reached in Switzerland within 200-350ms, depending on the daytime and mood.
purl.org had a response time between 200 and 500ms, depending on what ontologies got requested. The
most unpredictable ontology (although also the only one we currently use a lot for our tests) is FOAF,
which is hosted at xmlns.com. Here the response time was anything between a few 100ms to no response at all. Using Stanbol for ontology caching does certainly make sense, however 300ms is still a
long time when the goal is to deliver an answer as fast as possible. For that reason it makes sense to
cache the ontology loaded from Stanbol also in our own (Node.js-) code, like this we are able to deliver
a response for our (still simple) demo in less than 80ms without any special performance tuning. We
think providing a fast response is essential for the adoption of semantic web based services, this area
has to be improved on all involved layers.
Step 6, UI widget selection: We first thought that the “superclasses” we figure out on the Rules endpoint are required to provide this functionality. While implementing it we realized that this is actually
not needed at all for this step. All we need to take care of is the rdfs:domain attribute in the referred ontology. The superclass feature will only be used for recipe selection in the Uduvudu process. For more
information about that see our paper Uduvudu: A Powerful User Interface Framework for Linked Data.
Step 7, Stanbol Rule Deep Dive: I successfully replaced the SWRL rules by SPARQL CONSTRUCT
queries, this is pretty straight forward. First I thought that SPARQL CONSTRUCT is way easier to
write coming from a SPARQL background. What is annoying on the CONSTRUCT queries is that one
has to duplicated a lot of text to create the new graph. This is a benefit of SWRL rules as it does that for
me and I do not have to repeat myself all the time. So I think for simple things SWRL does make more
sense. At the time writing Stanbol does not support to run SPARQL CONSTRUCT queries on the rules
endpoint but judging from discussions I had with Andrea there is a fair chance this will be added one
day.
Step 8, UI verbosity: We implemented a basic but working example of how this could work. Currently
we do the following steps: Load the FOAF file of a person, load the FOAF ontology, apply a recipe to
the FOAF file and the ontology, process the meal an display it using the appropriate UI classes. In the
demo-code the UI “widget” classes are implemented in a simple JavaScript function which gets the object of the triple plus a full graph (might only be needed in more complex widgets). Selection of the appropriate UI widget is done based on rdfs:range definitions. We simply match to the URI of the range
and have a default match in case there is none. Implementing new classes is very straight forward like
this, although we just implemented simple examples so far. The demo is running on a test server at
http://147.87.98.156:443/. Source code is available upon request, we can also explain it via screensharing & Skype.
Summary
After the IKS workshop in Salzburg I was very impressed by the results of this FP7 project. When I first heard
about it I expected something completely different which I did not consider as very interesting for me at that
point. A few weeks after the IKS workshop in June we had the kickoff for our Fusepool FP7 project in Brussels.
WP2 of this project is building a platform on which we can run our and external services which enrich content in
a linked data way. I started talking to Stephane Gamard from Searchbox (former SalsaDev) and we agreed that it
would make a lot of sense to have a closer look at Stanbol. After spending some time together and posting some
questions on the Stanbol mailing list about multi-tenancy and security we decided to choose Stanbol as the base
of the platform for our project. A few weeks later we now work on implementing a security layer into Stanbol,
which at the same time provides the base for the multi-tenancy implementation on top of it. We get support by
Reto Bachmann-Gmuer which joined our Fusepool project and is a tremendous support for the work we have to
do. We are confident that this will also help Stanbol to get some more visibility and manpower which encourages other people and hopefully companies to join the project. The only real problem during the work was that
the documentation of the two modules I used did not really match the reality, which was quite annoying as I
couldn’t get it to work properly in the beginning. But both Andrea and Alessandro were very helpful during the
process and helped me. Alessandro also added the missing alias feature which I needed to be able to implement
caching properly.
6.3.6 Sztakipedia
Introduction
In the Early Adopter project “Sztakipedia” the work has been carried out in two main areas.
The first goal was to make Apache UIMA Annotation Engines or Aggregate Annotation Engines (AEs and
AAEs: these are UIMA terms) usable in Apache Stanbol as Enhancement Engines (EEs : this is in Stanbol ter-
© IKS Consortium
2013
147 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
minology). This task resulted in two alternative solutions, one which uses the REST interface and another one
which works in native java.
The other task was to provide a Book Spotter EE for Stanbol that relies on British National Bibliography (BNB)
and Open Library (OL) data. This work also involved inspection and heuristic filtering of the library records to
ensure proper enhancements. The created EE is able to find useful book occurrences quickly, based on a database that contains 5.6 million titles. The connection between these two tasks is that both UIMA adaptation and
book spotting happen to be implemented in the Sztakipedia project.
The Early Adopter Program provided a great opportunity to re-implement these functions in a much better fashion, to integrate them with the great Apache Stanbol project; and at the same time to open source the work in an
ecosystem that ensures that it will have a future and impact.
Demo
UIMA demo is available at: http://pedia2.sztaki.hu:9090/enhancer
At this endpoint the analyzed content is processed by an UIMA Hidden Markov Model Tagger Annotator that is
trained on the Brown Corpus. http://uima.apache.org/d/uima-addonscurrent/Tagger/hmmTaggerUsersGuide.html
The Annotator runs in the same JVM as Stanbol itself. The results of the AE are processed by the UIMA To
Triples EE, that is configured to pass only the noun-type tokens to the RDF tree. Therefore, in the list of the RDF
annotations you should find TextAnnotations only for nouns.
Book Spotter demo is at: http://pedia2.sztaki.hu:9090/enhancer/chain/bookspotter It creates Entity Annotations
for the spotted books that refer to the appropriate resource pages of either BNB or OL.
Validation
With the UIMA Remote and UIMA Local solutions three different UIMA Aggregate Engines where tested
(HMM Tagger, Language Recognizer, Snowball Stemmer). In the Remote UIMA setting it is quite easy to set up
the connection between Stanbol and UIMA AE-s that use the UIMA SimpleServlet interface. Multiple UIMA
AE-s can be used without any issues and these UIMA sources can be turned on or off runtime in Stanbol. Hosted
on the same machine the overhead of REST communication is in the tolerable range of 0.05-0.1 s. The advantage of this solution is that the components can be distributed to many hosts, and what is more, the UIMA
endpoint itself might be just an interface to an UIMA Asynchronous Scaleout deployment, that spans over a
cluster of hosts. Also, version changes in either UIMA or Stanbol are quite unproblematic, as long as the XML
Serialization of UIMA Feature Sets does not change, which is highly unlikely. More information on this topic:
http://blog.iks-project.eu/uima-apache-stanbol-integration-2/
In case UIMA is deployed in the same JVM, there is no overhead. However, this approach requires that first the
UIMA AEE is converted to a bundle because of the different class loading schemes of OSGi and UIMA. This
step should not take more than an hour, provided that the developer has a deep understanding of both UIMA and
the concept of Bundles that can be a problem. Therefore, this step is facilitated by a detailed tutorial:
http://blog.iks-project.eu/running-uima-engines-in-stanbol-using-the-same-jvm/
The UIMA to Triples Enhancement Engine converts UIMA FeatureSets to RDF triples in case the Feature Sets
are directly needed in Stanbol’s output, or in other EEs that rely on UIMA. UIMA to Triples offers a quite flexible configuration scheme detailed here: http://blog.iks-project.eu/running-uima-engines-in-stanbol-using-thesame-jvm/ Note, that in real life cases one expects that UIMA Engines play the role of pre-processor on which
other Enhancement Engines rely. In these cases the developers of the relying EE might decide to use the raw
output of UIMA Remote or Local directly and skip the conversion to triples.
The Book Spotter Engine was tested on corpus of 25 English documents. For detailed results, see:
http://pedia2.sztaki.hu/stanbol/bookspotter/Bookspotter_tests.pdf
The corpus was collected from various areas and web sites. With the 5.6M title set a 46.66% recall was achieved,
which can be considered an acceptable result, as the number of all book titles is approximated well over 100M.
There are plans to test a 9M set, but the recall is not expected to increase proportionally.
This recall was achieved having a 59.57% precision. But the percentage of the precision is not a good measure in
this case, as the results also have a confidence measure associated with them and the false positives tend to be
associated with a low confidence. The principle of this development was that recall should be favored over precision. That is because the results of this module is expected to be presented as suggestions from which the user
can choose the proper ones.
© IKS Consortium
2013
148 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Lessons learned
Overall, Stanbol is a very advanced and fairly large system. Stanbol relies on a deep stack of libraries and
frameworks. The development process of Stanbol uses state-of art technology.
Therefore, developing modules for Stanbol requires the simultaneous understanding of many technologies, like
maven, OSGi and Felix and the corresponding maven plugins, RDF formats and technologies, etc. Getting the
first Enhancement Engine running and its results into the output is not easy. The fact that Stanbol is open source
helps a lot, as one can investigate how others have written their EEs. I think that right now only people trained in
software engineering or other IT fields can be realistically expected to produce enhancement engines.
But there is another kind of people that are potential authors of EEs: linguists, mathematicians, chemists, economists, physicists, etc. In general, experts of different domains. Today it is not hard to find hacker types in these
communities who can turn their ideas to code, but when it comes to industrial software engineering tools they
get stuck very easily. The same often applies to the juniors from IT education as well. To reach the mass of these
potential contributors, I think template codes, Eclipse and Netbeans example projects, or even complete pre-set
Virtual Machines (a’la the DBpedia appliance) should be provided in which they only have to find the “//your
code comes here” part.
Also, apart from UIMA community there are other established communities in language processing around the
python-based NLTK or the NooJ tool that is written in .net. They are locked in by their technology in many
respects when it comes to web frontends, that are becoming more and more important. These communities could
really benefit from Stanbol’s capabilities: e.g. its nice web presentation and from its connections to many CMSs. In my opinion Stanbol should have a standardized REST interface not only at the “top” (for the CMS-s) but
also at the “bottom” (towards non-java Enhancement Engines), similar to the Remote UIMA tool provided by
this project. Naturally, in this latter case, the Stanbol would be the HTTP client. The data format could be some
serialization of RDF in this case, similar to the output of Stanbol.
After the issues of getting started, working with Stanbol is a really delighting experience. Its modular design
facilitated by OSGi and Felix makes the development of custom Enhancement Engines really easy. The web
interface of Felix is a great help, and the possibility to run-time install-remove bundles helps a lot in iterative
development. Also, the granularity of the modularization is optimal in Stanbol: in return for a small amount of
work spent on a custom module, one gets a great functionality from the system.
For the same reason, Stanbol would be an ideal teaching tool for software engineering students. Once the students can get started, they can write EE-s that work immediately; also they can exercise collaboration. I can see
myself making students collaborate while creating an enhancement chain, everyone contributing their own bundle. It is also ideal for getting experience with the aforementioned software engineering tools.
One small obstacle is that it is not easy to find information on what exactly certain EE-s produce. This is important if one wants to develop an EE that relies on the output of another EE. In UIMA, the Type System XML
defines rather precisely what comes out of an AE. A similar standardized descriptor might be useful for Stanbol
EEs as well. Also, as the number of EEs grow, a repository might be useful - similar to the UIMA Component
Repository that is out of order nowadays, but it contains many dozens of UIMA modules.
From a production point of view, the stability and performance of Stanbol seems to be good. Also, Felix and its
run-time configuration capabilities are a great help to provide a good uptime. However, at some point systems
integration tools, like System V init scripts, munin, nagios, icinga, etc. plugins will be necessary for managing
and monitoring. Also, at the definition of enhancement chains, configurable timeouts for Enhancers would be
useful to ensure graceful degradation when a sub-system fails.
For training the Enhancement Engines, a common feedback REST interface could be helpful in which the CMS
could notify Stanbol about which Enhancement was accepted and which rejected.
Finally it appears to be a strength of the system that most of the state-of-the art technologies from DBpedia to
Zemanta or OpenCalais are integrated (this also highlights the significance of the Early Adopter Programme). I
expect this to be a strong argument in favor of Stanbol while making technology decisions in many projects in
the future.
Visibility
About this Early Adopter Program altogether five blog posts were written:
Running UIMA Engines in Stanbol using the same JVM: http://blog.iks-project.eu/running-uima-engines-instanbol-using-the-same-jvm/
© IKS Consortium
2013
149 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Introducing BookSpotter Enhancement Engine by Sztaki: http://blog.iks-project.eu/introducing-bookspotterenhancement-engine-by-sztaki
Creating Enhancement Engines for Stanbol 0-10-0 incubating using netbeans 7-1-2 http://blog.iksproject.eu/creating-enhancement-engines-for-stanbol-0-10-0-incubating-using-netbeans-7-1-2/
UIMA-Apache Stanbol Integration (REST) http://blog.iks-project.eu/uima-apache-stanbol-integration-2/
UIMA-Apache Stanbol Integration (Project Introduction) http://blog.iks-project.eu/uima-apache-stanbolintegration/
Also, there IKS project in general and the deliverables of this will be referenced in MTA Sztaki’s (Hungarian
Academy of Sciences Institute for Computer Science and Control) web site and in its annual report.
Software components used
Apache Stanbol 0.10.0
6.3.7 MarkTheGlobe
Introduction
MarkTheGlobe is a Global SEO startup and would like to evaluate and integrate Stanbol into our Global SEO
Platform satural to help online marketing managers and SEO agencies to identify keyword proposals for SEO
campaigns and to categorize existing keywords to better manage large campaigns.
Our initial goal was to use Stanbol to generate keyword ideas for specific content. These keyword ideas will then
be used as input to our SEO platform to further enrich them with SEO specific information like search volume
and competition to propose suitable keywords for SEO campaigns. A secondary objective was to use Stanbol to
categorize different keywords into related topics. This makes it easier to manage large amounts of keywords in
groups.
Especially for websites with huge amount of content identifying suitable keywords for SEO campaigns is a labor
intensive process. We have already developed several syntactic and statistical approaches to generate keyword
proposals and Stanbol’s semantic engine is a great addition to get more accurate results.
Demo
A demo is available online at: http://tools.marktheglobe.com/stanbol/semantickeywords and
http://tools.marktheglobe.com/stanbol/semantictopics
Validation
One important aspect was to compare if the results from Stanbol are actually improving our proposed keyword
candidates. To receive good keywords, we not use categories and hierarchies/levels but Entities and Subjects. So
we don’t use vertical way but the horizontal. If the result-keywords are good or not, depends on the keyword,
indices and ini-file. For example when searching for mozarteum, the api returns the following keywords:
© IKS Consortium
2013
150 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
After manually testing the API, we have decided to create own indices from dbpedia for specific languages and
found good values for the ini-file of the API. For finding good main-categories for some keywords, we also
found a strategy. The API searches for categories for each keyword, and compares the categories till only a
few(depends on the number of input keywords) main categories are found which refer to the keywords. For example when categorizing the words: Ahorne, Arboristik, Forstpflanze, Westamerikanische Lärche, Bambus,
Billia, Bonsai, Buchen, Teebaum, Wildbirne, Strandpflanze, Alge, Gras, Eichen The API finds the categories:
Baum and Pflanzentyp
Lessons learned
By default the dbpedia English is tuned for English category and subject information. We have created our own
indexes that only contain data that we need for our use cases and for all languages. This approach provides higher quality results and uses less resources than the default index. Working with semantic technology is not exact.
We got very different results depending which keyword or topic we used for testing. The coverage of the index
differs and therefore also our keyword candidates and grouping success differs significantly. However since we
are using as an additional technology in a whole stack of different statistical and semantic technologies, we nearly always get an overall improvement. Adding additional indexes improves the results, so we expect that while
the Stanbol data sources mature we will also automatically benefit from these developments with our use cases.
Visibility
We have launched the „Keyword Explorer“ feature that contains the Stanbol functionality as part of our product
satural a few weeks ago. Since then we have demonstrated it at two conferences and multiple customer presentations. The general reception is quite positive and we aim to continue to highlight the functionality.
Software components used
We are mostly using PHP/Yii in the API layer. We developed and deployed on CentOS and Apache. As database
we use Percona/MySQL.
6.3.8 Compusic/buddycloud
Introduction
This IKS Early Adopter project had certain specific features:
© IKS Consortium
2013
151 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
It is the only EA project integrating IKS components with an Open Source Social Media platform, buddycloud.
• It is the only EA project aimed at using VIE on mobile devices, especially Android smartphones.
• The software is operated by users who generally are neither IT experts nor experts in semantic technologies.
VIE and an Apache Stanbol service (using the default set of enhancement engines) are used to enable users to
semi-automatically create semantic annotations for text which is entered by them.
The project was implemented by Andreas Kuckartz.
•
Demo
Demo will be available online on December 20, 2012 at: http://compusic.de
To use it you will need to register at http://demo.buddycloud.org. Then use the account data to log in at
http://compusic.de. The account name to be entered there must include the "@buddycloud.org" at the end, for
example "[email protected]". No https access is provided by compusic.de for this demo, therefore
better do not reuse the password.
The user interfaces for postings and comments make it possible to enter simple text, then in the first step HTML
with RDFa is created. Then disambiguation can be done using the annotate.js interface. In the next step the enhanced HTML RDFa code is again converted to text with URLs (from the RDFa-annotations) which are sent to
the server at demo.buddycloud.org.
Validation / Lessons learned
• Integrating moving targets
All of the components (IKS components, JavaScript libraries Backbone and Underscore, buddycloud, DBpedia
services, Apache Cordova etc.) to some extent were moving targets because all of them are being developed.
That is a good sign as it indicates that these Open Source projects are living.
But it occasionally led to problems. Even some of the official examples provided by VIE had stopped working
due to DBpedia changes for some time - but when notified the developers quickly modified the software to work
again under the changed circumstances. But this experience indicates that it is necessary to closely watch external services because they can break ones own service.
(While writing these paragraphs accessing DBpedia resulted in this text: "The web-site you are currently trying
to access is under maintenance at this time. We are sorry for any inconvenience this has caused.")
• Integration with lots of libraries
Both VIE annotate.js and the buddycloud web client use backbone.js.
Other JavaScript-libraries used by VIE / annotate.js:
• Underscore (annotate.js)
• jQuery (annotate.js)
• jQuery UI (annotate.js)
• hallo.js
• jquery.rdfquery
• VIE and annotate.js themselves
These dependencies resulted in increased complexity, especially while debugging when the software did not
work as expected.
• Integration with Apache Cordova / PhoneGap
Apache Cordova can be used to make it easy to install a web application. PhoneGap currently is just a different
name used by Adobe for the same software. The author had heard from others that it can be quite difficult to
even get very simple PhoneGaps apps working properly. This fortunately has not been the case here.
Currently no specific PhoneGap-features are used to access hardware. Such features can easily be added. One
example might be to enable users to take photographs and post them. Or the location can be accessed and a location-base service be used.
One potential solution to some of the limitations encountered with the Android browser is to use another browser
such as Firefox, but then there are other issues to deal with, in particular:
• It needs to be installed on the mobile device which creates significant additional effort for users (and the
Firefox installation package is about 20 MB, which is large for a mobile device).
• The WebView used in Apache Cordova is tied to the Android browser (Webkit) and so far nobody
seems to have been able to replace it by a Firefox WebView.
© IKS Consortium
2013
152 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
It therefore is not possible to create a Apache Cordova Android App using Firefox (or another browser) instead
of the Android Browser.
• Test suite for mobile browsers is needed
It is obvious that the main target platforms for the IKS components are desktop operating systems and browsers
because these are normally used by Content Management Software. Using them for mobile applications therefore was a bit risky.
The more complex VIE examples did not seem not have been tested on mobile devices. While the examples
"Find the capital of Mongolia", "Get enhancements for text", "Height of the Eiffel Tower" worked (at least most
of the time) the "Load the schema.org ontology" most of the time did not work.
Most importantly it turned out that the annotate.js example did not run on any of the five mobile browsers tested:
• Android Browser 2.2.1
• Firefox 17
• Firefox 18 Beta
• Opera Mini
• Opera Mobile
In the end and after a lot of time spent to find the cause it turned out that browser settings (popup blocker, character encoding) prevented the Android browser from executing the example correctly.
Researching that issue it turned out that the popular (non-IKS) utility library underscore.js which is used in the
example itself has issues in those browsers. Several tests of the Underscorce "Test & Benchmark Suite" currently
fail. One of the errors reported by the author will likely lead to a new release of Underscore
(https://github.com/documentcloud/underscore/issues/908).
Many of the infamous incompatibility issues which have plagued desktop browsers for many years seem to have
been resolved. Now incompatibilities of mobile browsers have replaced them.
It would help a lot to add a test suite for mobile browsers (use cases) because the "normal" one (https://travisci.org/bergie/VIE/builds) likely will not catch such specific issues.
• (non-)availability of contentEditable in mobile browsers
In desktop environments it usually is possible to require a modern web browser. This often is not that simple on
mobile devices. The first version of the Android browser supporting the contentEditable attribute is provided
with Android 3.0 (http://caniuse.com/#feat=contenteditable). Updating the browser regularly requires updating
the complete Android operating system, and that can be risky and time consuming or not possible at all for many
devices (installing CyanogenMod unfortunately is no option for many users). In other words: contentEditable
can not be used on many Android phones which have been bought only two years ago.
That is one reason why simple textarea elements are used by the buddycloud web client to enter postings and
comments. But these are only suitable for entering simple text, not RDFa enhanced content.
That makes entering enhanced content tricky because several stages are required to created enhanced content:
1. enter simple text in textarea
2. create DOM from that text
3. disambiguate using annotate.js
No good solution is known on how to best edit the text of existing HTML RDfa content.
Bandwidth used
It turned out that a lot of data is transferred to the mobile device during the enhancement process. While this
normally is no problem on desktop computers connected to the Internet with high bandwidth DSL-connections
etc. this often is a significant problem on mobile devices for two reasons: cost and time. Unrestricted high bandwidth still costs money and if the bandwidth is restricted the transmission of the data sometimes takes several
minutes instead of seconds. This unfortunately leads to a inferior user experience.
The main lesson here is that most of this data traffic should be avoided by moving it to a server. VIE can run on
a server (nodejs), but this has not yet been implemented for the buddycloud integration.
Timeouts
Latency and a low bandwidth can result in timeouts on mobile devices. This is even more problematic because
they normally are not reported as such but just result in failed operations. The more information is reported in
error messages the better.
Entity disambiguation
© IKS Consortium
2013
153 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
The disambiguation dialog worked most of the time as expected after the problem with the browser settings
(popup blocker) was resolved.
User experience regarding linked content
For most users the main and immediately usable result of the enhancements are the URLs added to text content
(postings or comments). These URLs link to DBpedia-pages which look far less attractive to human users than
normal WikiPedia pages.
Working examples help
It is good that several VIE examples are provided. These are the main source of information on how VIE can be
used. When they broke due to external changes (DBpedia) the developers corrected them.
Debugging
Debugging using mobile web browsers is more time consuming and complex than using desktop browser. A
helpful small tool is the "Show Dom Html" in the annotate.js example. It simply displays the enhanced DOM the mobile Android browser itself does not provide such a tool.
Documentation
While the documentation for the IKS components is significantly better than that provided by many other Open
Source projects it still can be improved. Some brief "Howto" texts would be particularly helpful.
Visibility
These communities will be informed about the project and the results:
• the W3C Federated Social Web Community Group
• the Google+ Federated Social Web Community and other Google+ Communities
• the buddycloud developer mailing list
• users of the buddycloud Federated Social Web
• Software components used
• Apache Stanbol
• VIE (annotate.js)
• Apache Cordova / PhoneGap
• buddycloud components
6.3.9 Conatix
Introduction
The IKS Early Adopter project provided an opportunity for Conatix that we would not otherwise have had at this
stage of our software development. Conatix is a startup and spin-off project of the Humboldt-Universität zu
Berlin building a semi-automated business intelligence (business research) system to help companies do market
and investment research better, faster and cheaper. Part of our system is a machine learning-based document
recommendation system. Our team has advanced background in machine learning but limited experience incorporating semantic web-based technologies into applications. At the same time, since we are working with large
numbers of web-based documents, we knew that semantic web features could provide additional functionality to
our users in manipulating web documents and text discovered by our system.
As a startup, we have been able to attract strong advisors also in semantic web technologies but had limited resources to apply existing technologies in practice. The Early Adopters program was very valuable to because it
enabled us to incorporate Stanbol and VIE features into our beta at the same time that relevant parts of our beta
are being built, rather than after the fact, and this has also extended our own conception of what our system will
be able to offer users. Conatix uses Stanbol and VIE to add named entity recognition, user customized notes and
user-defined important term mining to our semi-automated business intelligence system.
The project was implemented by Amin Alizadeh, Rico Possienka and Rashedul Khan.
Demo
Because our product is still in beta development and essentially in stealth mode, we are not yet making a public
demo available. We do have a private demo which we have shown to project administrators and it could also be
© IKS Consortium
2013
154 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
possible to show it directly in a brief one-on-one session to interested parties. Please email [email protected] if
you would be interested in arranging a private demo, which may require a brief non-disclosure agreement. When
our beta is completed in early 2013 and in pilot customer testing, we plan to make a public version of the demo
available online.
Validation/ Lessons Learned
• Usefulness
The aim of the project was to test the hypothesis that the IKS CMS could be useful for dynamic real-time content
management by non-technical business users as they process new and existing documents recommended to them
by the Conatix business intelligence system. We found that Stanbol and VIE features are indeed useful for content management not only at the point of direct user contact with content in our system (in the frontend user
interface), but that Stanbol can also enhance the process of new content discovery by the backend of our system.
IKS text enhancement functionalities add value to the business research process by making it possible to visualize important and useful terms within a given text. Furthermore, the Apache Stanbol Engine extends the
knowledge derived from a text by the user by proposing terms that are in some ways connected to the initial text.
Our system can then feed these new terms into our own machine learning-based integrated web crawler/classifier
engine to enhance the relevant result values even more. We demonstrated that semantic web applications and
services can be useful for us and do not conflict with the main stream of our development even though our product incorporates machine learning technology.
• Retraining Models and Results Enhancement
One good idea complementing our machine learning-based approach to web crawling and classification that
came from then Stanbol engine is the relation of labels in the response from Stanbol’s text enhancement service.
When we feed text into the Stanbol search engine, we get a set of labels as a response, which link to entries of
DBPedia. This information can then be fed into our own database. With this information we can improve the
overall quality of our models which are enhanced and broadened by the Apache Stanbol service. These results
may not contain then same important terms as in the initial training sets extracted solely from user input documents, but they include similar concepts which in most cases are desirable for users.
• Complexity
We increased our competence and experience in integration by merging complex applications and services with
our own.
• Functional Programming
VIE has a lot of dependencies which encouraged us to apply a more functional programming style. With the help
of underscore.js and functional programming techniques we were able to minimize our code and make our application much more readable and reliable.
• Level of Abstraction
Another dependency of VIE is backbone.js which works as an MVC framework. While it is a powerful and
widely used library for professional single page HTML applications, we were not satisfied with the level of abstraction. In our search for a different approach we discovered Angular.js which aims for a more readable approach. Angular.js enabled us to write template-free HTML in a very readable programming style.
• Cross-Domain Calls
Creating a proprietary JSON API can cause inconvenient slowdowns in the development cycle. One important
issue which should be considered early in the process is the issue of cross-domain calls. When HTML applications run locally on the client, POST calls to a server will be suppressed. Every browser handles this issue differently, but in most cases the developer has to set an internal flag or option in order to be able to call against an
API. It is best to decide early in the process how the application will be hosted on the server.
• User-Defined Highlighting
At the beginning of the project, we had the impression that Stanbol tools or widgets provide user-defined highlighting within a block of text and we wanted to integrate such functionalities into our system. When the user
selects a block of text, the selected text is highlighted in a different color so it attracts attention the next time the
user views the same document/page. This concept was originated by our development team because of the highlighting feature of Annotate.js which made us think of implementing it within our own system. In fact there is no
such feature in VIE.js or Annotate.js that makes user-defined text highlighting possible. However this misconception did not impede us from taking another approach to implementing such a functionality into our system.
• Documentation Format
The IKS project uses Doco for documentation. It documents the source code but in fact it would be better not to
show so much source code in the documentation if the goal is to produce an API that is easy to understand. With
too much source code, the documentation is confusing even for a programmer. A little source code in the documentation would be OK, but not too much.
© IKS Consortium
2013
155 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
• Documentation Accessibility
It would have been easier if clearer forms and instructions could have been provided, even including this form
that we are filling out right now for the validation. The project also promised tutorials and a clear support protocol. In general the tools were much less accessible than we expected. When we asked for support the typical
answer after several days was to look at a webpage. On the webpage there was typically vague or missing documentation. Communication in general could have been better. At the same time, the tools themselves at times
were easier to use than we expected once we figured them out, but still the documentation and support environment could be improved.
Visibility
Customer visibility: At the moment Conatix is in stealth mode as we complete our beta. We have demonstrated
our IKS integration to Salzburg Research. Within the first months of 2013, when our beta is launched to pilot
customers, we will begin showing them the role played by IKS enhancements in our product.
Public visibility: We will include discussion of the project on the Conatix website and in our presentations. Because we participate actively and frequently in high-profile public and also private investor pitching events for
technology-based startups throughout Germany and Europe, this will provide ongoing visibility. We have added
the logo for the IKS project to our presentations and will include discussion of the project in press releases when
our beta and eventually the production version of our software is launched.
Software Components Used
•
•
•
•
•
•
•
•
•
•
Hallo.js
Annotate.js
VIE.js
Jquery
Angular.js
Underscore.js
Bootstrap
Backbone.js
Apache Jackrabbit
Conatix API
6.3.10
Gnowsis
Introduction
Refinder for Teams (see http://www.getrefinder.com/about/teams) is a Web-based tool that allows users to collect and manage information that is of importance to the social contexts they are working in (e.g., project teams,
student groups, management boards, etc.). Refinder brings the data and activities from cloud apps like Dropbox,
Google Apps, Box, Basecamp, etc. into one place, where it can be efficiently shared, filtered, searched, and
discussed.
Refinder Cloud Search (see http://www.getrefinder.com/about/cloudsearch) is a service that can be integrated
into Web and mobile applications, allowing developers to easily integrate search functionality across different
cloud sources into their applications. It disburdens the developers from having to set up their own crawling,
indexing, and search infrastructure.
The purpose of this demo is to showcase the usage of Apache Stanbol software components to add automatic
tagging functionality to both Refinder services as described before. In this context, by "tags" we denote resources, which are identified using HTTP URLs, and feature rich metadata (including multilingual labels and
relations to other resources) expressed in RDF. Tags are generated by Stanbol's enhancer service, which takes as
input the full textual description of items in Refinder (including possibly related content and user-generated
content like comments). Stanbol analyzes the content and matches it to resources from DBpedia, which are in
turn represented as tags in Refinder. These tags can be used to find and retrieve content, whereas (through the
usage of tag descriptions) more diverse search options are available to the user. For instance, it is now possible to
search for tags in multiple languages, since translations for tag labels are provided by DBpedia.
Demo
© IKS Consortium
2013
156 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Demos are available online at https://www.getrefinder.com/accounts/login/ (Refinder for Teams) and
https://www.getrefinder.com/s/login/ (Refinder Cloud Search). A demo account (which has already been populated with data from different sources, including RSS feeds, Twitter streams, and Dropbox files) exists:
Username: [email protected] Password: stanboldemo12
Currently, the Stanbol-based enrichment service is not activated by default for every user, so if you want to try it
with your own Refinder account, contact us at [email protected] so that we can enable the enrichment service
for you.
To see the service "in action", issue a search request, e.g., for "social media":
https://www.getrefinder.com/s/search/#q=social%20media
In the result list, you will see tags that are associated to the result documents. These tags are clickable: by clicking on a tag the results will be reduced to items that are associated with that tag. (The same functionality can be
triggered by selecting a tag from the "Tag" filter panel on the left side of the screen.
Validation
The implementation of the functionality presented above was carried out based on information provided at the
IKS Early Adopter workshop, as well as information from the Web (including the project wiki). This information and the documentation of the system was sufficiently detailed to guide the implementation without significant problems.
The services provided by Stanbol (in particular, the Enhancment service used in this showcase) were straightforward to use and can be integrated into existing infrastructure and software easily.
The quality of results obtained from the Enhancement service depends greatly on the type of information. In
general the results seem reasonable, although there are false positives from time to time. The answering time of
the service also depends on the number of entities returned; in our showcase, no real-time response was required
(as the auto-tagging takes place in the background), so the current response times are acceptable. Still, we decided to host the Stanbol service on a separate server so that it does not affect the performance and response time of
the core Refinder application.
Lessons learned
The integration of Stanbol has triggered an improvement of Refinder's internal handling of semantic tags, which
has been extended to support rich RDF descriptions and multi-lingual labels. Lots of work has been put into
developing data structures that allow for faster retrieval of tag descriptions, in order to implement more responsive user interfaces.
Visibility
There is some work left to do regarding the performance of semantic tag descriptions on the Refinder side. As
soon as they are solved, the Stanbol tagger will be released to all Refinder users (currently nearly 3,500 registered). Further, the Stanbol-Refinder integration will be promoted at suitable events (e.g., conferences and exhibitions).
Software components used
- Refinder - Apache Stanbol Enhancement service - RDFlib (for parsing Stanbol responses)
6.3.11
Fluid Operations
Overview
This page describes the integration of IKS Apache Stanbol with Information Workbench by fluid Operations.
The running online demo instance is available at http://stanbol.fluidops.net. The demo is implemented as a solution module, which can be deployed on an Information Workbench CE instance. The solution can be downloaded from http://stanbol.fluidops.net/upload/stanbol.zip.
Introduction
This page describes the integration of IKS Apache Stanbol with Information Workbench by fluid Operations.
The running online demo instance is available at http://stanbol.fluidops.net. The demo is implemented as a solution module, which can be deployed on an Information Workbench CE instance. The solution can be downloaded from http://stanbol.fluidops.net/upload/stanbol.zip.
© IKS Consortium
2013
157 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Features
1.
2.
3.
4.
5.
6.
Content documents (text documents in PDF, MS Word, Open Office, or plain text) are uploaded to the
running Information Workbench instance via the web-based interface (IWB File upload widget).
The documents are processed by the Stanbol web service DBpedia spotlight EE.
Text content is enriched with hyperlinks pointing to relevant DBpedia entities and shown on the corresponding wiki pages.
For each uploaded document, the user can see companies, places, and persons mentioned in the text as
well as the list of most similar documents (similarity is judged by the number of mentions of entities
common between them).
Visualization widgets are applied to show data of specific types: e.g., mentioned places are presented
using Google Maps, the most popular entries are compared using a chart, etc.
Additional information about selected entities can be pulled from external sources: e.g., in the demo we
extract additional news information about selected companies using the New York Times API.
Architecture
1.
2.
3.
4.
5.
6.
7.
8.
9.
Content documents (text documents in PDF, MS Word, Open Office, or plain text) are uploaded to the
running Information Workbench instance via the web-based interface (IWB File upload widget).
The documents are processed by the Stanbol web service DBpedia spotlight EE.
Text content is enriched with hyperlinks pointing to relevant DBpedia entities and shown on the corresponding wiki pages.
For each uploaded document, the user can see companies, places, and persons mentioned in the text as
well as the list of most similar documents (similarity is judged by the number of mentions of entities
common between them).
Visualization widgets are applied to show data of specific types: e.g., mentioned places are presented
using Google Maps, the most popular entries are compared using a chart, etc.
Additional information about selected entities can be pulled from external sources: e.g., in the demo we
extract additional news information about selected companies using the New York Times API.
Semantic annotations together with annotated text content are stored in the RDF repository of the Information Workbench.
Information Workbench Wiki templates are used to visualize the document collection and related
DBpedia resources (companies, people, places).
For extracted DBpedia entities (companies), an option to follow relevant news can be selected. When
switched on, Information Workbench searches and downloads abstracts and link to relevant articles
from the New York Times REST API. These abstracts are in turn also enriched with DBpedia entities
using Stanbol.
Issues:
1. Stanbol requires the content type to be set: would be good to be able to send any file to the Stanbol web
service and leave processing to the server (Tika running locally is able to distinguish PDF from plain
text files).
2. Problem with processing MS Word documents (persists only on local installation of Stanbol).
3. Precision of annotations (both in default and dbpedia-spotlight chains).
Roadmap/Ideas
1.
2.
Implementing Stanbol integration components as part of the standard Information Workbench distribution.
Using Stanbol to improve user interaction in the semantic content publishing context: e.g., for tag suggestion.
Demo
Demo is available online at: http://stanbol.fluidops.net. The demo scenario involves maintaining a collection of
documents uploaded to the system (upload is available for registered users), which have been semantically annotated using Stanbol. The user can navigate the collection via the DBpedia semantic data model by accessing
relevant entities (companies, people references, and locations) and browsing the links between the entities and
relevant documents. Moreover, the user has a possibility to follow relevant news about specific companies retrieved from the New York Times web site: the abstracts of the news articles are downloaded and also annotated
by the Stanbol API.
© IKS Consortium
2013
158 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Validation
We integrated the Information Workbench with the Stanbol Enhancer API in order to realize semantic annotation
of free-text content such as documents uploaded by the user or retrieved from external sources. In the initial
proof-of-concept integration demo we have used the Stanbol Content Enhancement component. Information
Workbench implements a Java client utilizing the Stanbol REST API. This client is in turn used by two Information Workbench plug-in modules: the file upload widget (UI component), which is responsible for uploading
disk files into the system for storage and access, and the news data provider, which uses the New York Times
Article Search API to retrieve relevant news articles and them to corresponding data instances. The file upload
widget sends the uploaded file to the Stanbol Enhancement REST API to retrieve semantic annotations (we used
the DBpedia Spotlight chain for our demo) and to retrieve plain text content, if necessary (Tika engine). Retrieved annotations are used to visualize relations between semantic entities and to render the text of the documents with hyperlinks to corresponding entities. The news data provider enriches the content of semantic data
repository by searching relevant articles’ abstracts using the Article Search API from New York Times, annotating them using Stanbol DBpedia Spotlight chain, and storing them in the semantic repository. The goal of this
proof of concept integration demo was to be able to demonstrate to our customers the possibilities to link semantic data with free text content and facilitate document management. This is particularly important for the use of
Information Workbench in the context of semantic content publishing scenario, where large amount of free text
content has to be maintained. The use of Stanbol components helps to organize, visualize, and browse the collection of free text documents structuring it according to the semantic data model.
Lessons learned
The goal of this proof of concept integration demo was to be able to demonstrate to our customers the possibilities to link semantic data with free text content and facilitate document management. This is particularly important for the use of Information Workbench in the context of semantic content publishing scenario, where large
amount of free text content has to be maintained. The use of Stanbol components helps to organize, visualize,
and browse the collection of free text documents structuring it according to the semantic data model. However,
we found out that Stanbol components are not yet fully robust and completely suitable for industrial production
environment. Because of this, for now we are going to evaluate the suitability of using Stanbol for specific scenarios on case-by-case basis. With the development progress of Stanbol components, we expect these issues to
be fixed within reasonable time interval.
Visibility
The developed prototype demo implementation is available to the general public for viewing. It will also be used
by fluid Operations AG as a show case for potential customers to demonstrate the advanced possibilities offered
by automated semantic content enrichment to facilitate semantic media content authoring and publishing.
Software components used
1.
2.
3.
Information Workbench
Apache Stanbol
New York Times Article Search API
6.3.12
Manafactory
Introduction
Twistory [1] is a social media dashboard built over WordPress to help organizations become Socially Engaged
Enterprises, providing a comprehensive overview to understand and gain insights about social media through
metrics, measurement and analytics reporting.
Most of today’s approaches when looking at influence monitoring take into account the interaction pattern analysis (this is the case for Klout.com or of the LinkedIn InMap social graph); these tools look at the dynamics of the
interaction primarily rather than content; they can determine how far an individual posting that you make will
spread across the people that follow your comments on Twitter or how often on average something you say is
shared and propagated by others. Though extremely valuable the interaction pattern analysis shall be combined
with a real-time trend analysis of semantics [2] that properly augment quantitative data using language detection
and entity recognition against single interactions, historical or targeted streams and contents shared using short
URLs. In the Social Web, specifically on Twitter where interaction are limited to 140 characters, user engage
and share a wealth of contents using links (these links represents accordingly to Twitter 25% [3] of the overall
volume of tweets shared every day), adding a semantic layer to these contents can convey a great deal of mean-
© IKS Consortium
2013
159 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
ing and useful insights on the core topics being analysed. This is particularly true for brand reputation and crisis
management scenarios where in simple words it all comes to meaning and relevancy.
Vision
Twistory is a software and a method to make social media monitoring accessible to everyone, be it an enterprise,
an individual or a small team. The platform is available as Software as a Service Model (SaaS) and it’s bundled
with our consultancy services to help clients interpret the data and take actions over Social Media. One of the
key challenges for the Validation was to enable access to Apache Stanbol over the cloud and be able to charge
clients for semantic enhancements by monitoring the transactions.
Demo
A live demo of Twistory with the semantic plugin activated can be found at
http://www.twistory.it/radar/example1/wp-login.php (login and password are available upon request) while the
reporting developed for keeping track of the resource consumption related to the semantic enrichments is available at http://idntik.it/ (see below).
1. Entities Recognition: Automatic entity recognition is used for Tweets and Links.
2. Entities Database: Store the entities in the local WordPress database (Persons, Organizations and Places).
3. Semantic Tweet Pie Chart: Visual representation of the entities divided into Persons, Organizations and
Places related to tweets.
4. Semantic Link Pie Chart : Visual representation of the entities divided into Persons, Organizations and
Places related to links
1. of Calls: Visual representation of the number of calls directed to Apache Stanbol from Twistory (and other apps) http://idntik.it/#/reports/calls.
2. of Units: Visual representation of the number of data-processing-units consumed by Twistory
(and other apps) http://idntik.it/#/reports/units
5. Traffic: Visual representation of the traffic measured in KB generated by Twistory (and other apps)
http://idntik.it/#/reports/traffic
The website of Twistory can be found at http://www.twistory.it/.
Validation
The functionalities described above have been implemented in collaboration with the Insideout10 team (an IKS
Early Adopter that has been working on WordLift – a WordPress plugin for Semantic Enhancements as well as
other custom built engines for Apache Stanbol) and have been based on the documentation we received from
them (https://github.com/insideout10/wordlift-home) along with the information available on the Web.
The enhancement service and the asynchronous job calls were straightforward to use but we faced some instability issues when performing the analysis of contents provided by reading remote URLs. As the PoS tagging is
performing by relying on some native code, the more the parsed content isn’t clean, the more the chance that the
underlying dependencies fail with unmanaged exceptions, thus terminating the whole Stanbol instance. In order
to remedy this issue two steps have been taken: the first one to incrementally move some functions outside of the
core servers, hence the Stanbol Façade project, which provides simple developer-oriented APIs as well as
cleansing of data before submitting it to the Stanbol core functions; and second the implementation of the readability.js library in order to parse and clean the remote URLs and provide a coherent text for a later analysis.
The quality of results obtained for the italian language using the combination of Freeling Part-of-Speech Tagging Engine and Freebase Entity Recognition Engine (along with the rest of the chain – see below) is reasonable,
although there is still a good margin for improvements.
The answering time of the service depends on the number of entities the system returns but it is acceptable for
our scope.
Lessons learned
Apache Stanbol provides powerful APIs for content enhancement and is extremely flexible. Being able to access
the service with RESTful APIs from our client application written in PHP while preserving the flexibility of
adding modules (like we did for the Stanbol Façade) in Java is a great competitive advantage.
Testing the platform behind a gateway and be able to monitor resource consumption it’s key to implement the
semantic layer within our existing business model.
Visibility
© IKS Consortium
2013
160 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
The developed prototype implementation is available for our clients, it is currently being tested by ATAC [4]
and it will be used as a showcase to demonstrate the advanced possibilities offered by automated semantic content enhancements for social media monitoring.
Software components used
1.
2.
3.
4.
5.
6.
Apache Stanbol
IDNTIK.IT – for user management, API gateway and service metering
WordPress 3.0+
jQuery and jQuery UI
Stanbol Façade, a custom API front-end for Stanbol (OSGi) – this components includes Rhino and
Readability.js for content parsing of Web pages.
Stanbol Engines:
1. Freeling Language Identifier Engine
2. Freeling Part-of-Speech Tagging Engine
3. Text-Annotations Model Engine
4. Freebase Entity Recognition Engine
5. Schema.org Refactorer Engine
References
1.
2.
3.
4.
Twistory – Your Social Media Analysis Platform, www.twistory.it
Marie Wallace – Social Analytics is more than just Social Media, allthingsanalytics.com
Techcrunch – Twitter Seeing 90 Million Tweets Per Day, 25 Percent Contain Links,
www.techcrunch.com
Atac – Public Transport Agency of the city of Rome, www.atac.roma.it
6.4 CMS End-Users
6.4.1 Cytogenetics Lab
Introduction
This is a realization of the http://wiki.iks-project.eu/index.php/Cytogenetic_Proposal , a part of IKS Early
Adopters.
The demo presents integration of Apache Stanbol with software used at IMID Cytogenetics Labs. The purpose
of the integration is to allow geneticists to annotate experiment data with relevant content: information about
genes, genetic diseases, scientific publications, and more, and later allow for searching through, and summarized
reports of the annotated content.
The demo features:
1. annotation of biological content (in this case it's a result of aCGH experiment) with relevant Linked Data: user may add enhancements found with engines, and create his own tree of enhanced content.
2. a set of semi-automated enhancers which communicate with Apache Stanbol and search Linked Data
for relevant entries
3. faceted search through content annotations provided by Apache Stanbol Contenthub.
For the purpose of this demo UNIPROT linked data was indexed using Apache Stanbol tools (the resulting index
is 10GB in size)
• UNIPROT RDF release
• This UNIPROT relase also contains following Linked Data: Gene Ontology terms, PubMed abstracts
• the site was built on web2py
• A Stanbol connection module in Python was created for the puprose of this integration.
• a set of content enhancers in Python for web2py were created for the purpose of this integration.
Demo
•
The demo site
Lessons learned
© IKS Consortium
2013
161 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
•
•
•
Apache Stanbol is useful in providing access to data from Linked Open Data cloud
indexing of Linked Data is crucial to useful data access later and efficient queries
constructing useful queries requires ontologies to be loaded and handled
Visibility
•
•
•
The demo site: http://bioputer.mimuw.edu.pl:9442/welcome/
The project site: http://bioputer.mimuw.edu.pl/iks/
Repository, tracker: http://bioputer.mimuw.edu.pl:33000/
Software components used
•
•
Apache Stanbol: Entityhub, Contenthub, Enhacer, Ontonet (very basic use)
VIE autocompletion
6.4.2 GzEvD
Introduction
For a general introduction and details about the integration of DBpedia Spotlight in Apache Stanbol, please refer
to our blog post on the subject http://blog.iks-project.eu/dbpedia-spotlight-integration-in-apache-stanbol-2/
Demo
Demo is available online at: http://spotlight.dbpedia.org/stanbol/
Validation
As described in the blog post, DBpedia Spotlight goes through the entire annotation process (spotting, candidates
selection and disambiguation). The available RESTful endpoints on our side were three at that time:
1. annotate – spots the potential mentions, retrieves the candidate DBpedia resources, disambiguates them
if needed, and links the mentions to the best one
2. candidates – same as annotate, but does not disambiguate the candidates for each mention. Rather it returns the top K ones.
3. disambiguate (soon to be deprecated) – does not do spotting, it just selects the candidates for the given
mentions and does disambiguation.
In order to integrate DBpedia Spotlight in a way Apache Stanbol users would benefit most from, required some
modifications and additions to these REST endpoints. It made sense to break up the process in different stages,
and implement an enhancement engine for each one. This way Apache Stanbol users can choose if they want to
use the entire functionality of DBpedia Spotlight or just some of it in combination with other enhancement engines. The enhancement engines we implemented were four:
1. dbpspotlight.spot – detects mentions of possible candidates (NER, phrase detection, etc)
2. dbpspotlight.candidates – given a set of mentions (in DBpedia Spotlight they are called surface form
occurrences), their possible candidate resources are selected
3. dbpspotlight.disambiguate – given a set of mentions (in DBpedia Spotlight they are called surface form
occurrences), their disambiguated DBpedia resources are selected
4. dbpspotlight.annotate – in order to still be able to use the full functionality of DBpedia Spotlight in one
step, we implemented this enhancement engine, which uses the /annotate REST endpoint of Spotlight
After the engines were implemented, we used them in enhancement chains in order to demonstrate different
scenarios. In one scenario we used the spot enhancement engine in combination with3 Stanbol's dbpediaLinking,
in another one we combined Stanbol's NER with Spotlight's candidates and disambiguate, and of course, one
which deals with the whole annotation process. DBpedia Spotlight has been thoroughly evaluated on large corpora. We wanted to compare it's performance with the Stanbol default chain. Therefore we enabled the conversion of our evaluation data sets into the Stanbol's benchmark tool input format, and shared one dataset. Unfortunately the Stanbol benchmark tool was intended for user based (document per document) evaluation, as opposed
to an automated process for large corpora. We opened a JIRA issue [2] proposing a new style of benchmarking,
so that this evaluation can be done at a later point.
The enhancement engines for DBpedia Spotlight are deactivated by default and can be manually activated, configured and used in their own enhancement chain.
Lessons learned
1.
Use the project mailing list more often;
© IKS Consortium
2013
162 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
2.
Both user-based small scale evaluation and large scale evaluation is necessary. It is important to look at
individual examples in order to understand what works and what does not, but it is also important to
have an overall accuracy estimate over thousands of test examples;
Visibility
We are proud to say that the Integration of DBpedia Spotlight has become part of the Apache Stanbol Stack, so it
is already included, when users check out the latest trunk. DBpedia Spotlight's integration with Stanbol has been
disseminated on several channels, including:
1. Twitter (https://twitter.com/pablomendes/status/247693784870170624),
2. Public mailing lists (http://lists.w3.org/Archives/Public/public-lod/2012Jul/0049.html ),
3. Blog posts (http://blog.iks-project.eu/dbpedia-spotlight-integration-in-apache-stanbol-2/)
Moreover, the support from IKS for the integration with Stanbol has been acknowledged in the main page of
DBpedia SpotlightDBpedia Spotlight's source code is available on github: https://github.com/dbpediaspotlight/dbpedia-spotlight
Software components used
DBpedia Spotlight, Apache Stanbol ( Enhancer and Chain ), Benchmark
6.4.3 SIMsKULTUR
Introduction
Create an online tool for easy publishing of press reports / news items from different users and use or link to
related content featured on the SIMsKultur Online platform. The project aims at integrating the Apache Stanbol
software components to assist at creating of news articles with facts and media. This IKS Early Adopters project
should help to explore the usage of Linked Open Data and assist the user with an easy to use user interface to
create semantically annotated (schema.org) content.
Related blog post on the IKS blog: http://blog.iks-project.eu/stanbol-and-simskultur-online-publish-pressreports/
Demo
The demo is available online at: http://kulturnews.simskultur.net
Like described in the proposal it was first planned to use Drupal for this "news publishing application" but it
turned out it would maybe be better to create an own little application (JavaScript / PHP / HTML / CSS) and use
Apache Stanbol as data hub for it.
Instead of RDFa the data shown in the HTML page is annotated with Microdata (Schema.org) -- so VIE / Create
was not used.
Validation
The most features of Apache Stanbol are described good and provide helpful examples. The IKS team was also
very helpful in answering questions which where harder to figure out. The RESTful API is very useful although
it would be great to get for all services / [error] responses (also) as JSON-LD.
There are interesting possibilities where / how one can use Apache Stanbol. In our case we created an application
where users can create news articles related to events in the D / A / CH region. All data for an article is stored in
it's HTML file. No traditional database is needed. Where we can support the user with (meta) data we'll interact
with Apache Stanbol -- e.g. all (meta) data for shows, venues, tickets or media files is stored in the entity hub
and will presented to the user when it's needed (e.g. when looking up a venue for a show or adding related
events) To enable search functionality over all created articles (UI not yet implemented) the included Apache
Solr server is a good fit (whole news articles are stored in the content hub on creation/update)
As all news articles are in German the enhancer / openNLP is not working that good. The performance should be
fine in our use case as there are no big data sets which will be enhanced in a batch.
The next goal is the import more related data from different sources and explore the rdf schema mapping possibilities of Stanbol.
Lessons learned
The goal of the application was to provide an easy way for users to publish news articles related to cultural
events and assist them with meta data / linked open data (eg. images can be added from the wikidata project;
venue data is available through type ahead; content is annotated with the schema.org vocabulary for better SEO.
© IKS Consortium
2013
163 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
There are a lot of new topics to explore which are not used in traditional web application development when
you'll start a new application using Apache Stanbol.
The more different "state-of-the-art" / "new" libraries / techniques are used the more issues / problems arise
when they should play together (JavaScript libraries / HTML5 markup / standard PHP dom/JSON parser / ...)
Visibility
The application will be part of the SIMsKultur Online website and available to the public. Customers of SIMsKultur will be introduced to the new service / users will be informed with the "Kulturletter" (Newsletter).
Software components used
•
•
•
Apache Stanbol Entity Hub / Content Hub
HTML / CSS / JavaScript / PHP for the application
Aloha Editor for editing
6.4.4 Software AG
Introduction
Software AG is the global leader in Business Process Excellence. We offer our customers end- to-end business
process management (BPM) solutions delivering low Total-Cost-of-Ownership and high ease of use. Our industry-leading brands – ARIS, webMethods, Adabas, Natural, CentraSite and IDS Scheer Consulting – represent a
unique portfolio encompassing like process strategy, design, integration and control; SOA-based integration and
data management; process-driven SAP implementation; strategic process consulting and services.
The variety of projects requires a special knowledge management, which guarantees the transfer of knowledge
within the company. For this reason, an appropriate document management system and a good search engine are
necessary to find the right information easily and quickly.
Validation
In order to find a simple and quick full-text-search engine, which also offers services that are able to obtain additional semantic information, we tested the Apache Stanbol “ContentHub”. Apache Stanbol provides a set of
services for semantic management and offers a connection to direct usage from web applications. In that case,
the “CMS Adapter” was also required for the connection between our existing content management “Alfresco”
and Apache Stanbol, and the extension with semantic services.
Apache Stanbol divided the contents of documents in certain subjects, in order to get a better overview of the
contents. In addition the tool “ContentHub” provided the service that adds semantic information from the internet to our document information.
Software components used
Currently a large amount of internal and customer documents are stored and managed in Alfresco. The document
filing by the users and the document search are done via LabCase, the internal SAG User Interface. LabCase is
mainly used as a document repository for customer projects and offers employees a structured filing system. It
commonly provides storage, security, versioning and indexing.
© IKS Consortium
2013
164 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
With the support of the Apache Stanbol, documents can not only be found quickly and easily just by entering
keywords – but in addition, the tool offers services for semantic management in connection with web applications. Therefore it is possible to get information from the internet, which is related to the search in context.
Demo/Screencasts
Due to the internal privacy nature of the content used in this live validation exercise no online public demo is
possible. Instead the validation work is documented in the slideshow and screencasts below.
• Slideshow: Slideshow of validation exercise
• Screencast: Apache Stanbol + Alfresco Validation
• Screencast:Software AG enterprise validation
Lessons Learnt
The topic of the “Document Management System” is very complex, but extremely interesting. Various systems
offer a set of additional services in order to assist in daily business. In the last years, there was a great progress in
development, but it still requires a lot of technical know- how and documentation.
To take advantage of the Apache Stanbol Services, we had to install the “CMS Adapter” at first, but the installation was in our case very time-consuming and problematic. This was due to the outsourcing of the internal document management and also the complexity of available information in internet especially IKS homepage.
Therefore, a detailed installation guide would be very helpful.
7 Contact Database
This section provides the list of CMS vendors/integrators/OS Communities that are on the IKS radar. These
organisations have been sourced from a number of reliable monitoring agencies such as:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
CMSWatch,
AIIM International,
Allesovercontenet.nl
CMS Forum
CMS Matrix
CMSWire
Content Management Connection
Content Management Professionals
Content Wrangler
Contentinople
Contentmanager
Econtent
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
Enterprise Content Manager
Fierce Content Manager
Golem.de
InformationWeek
Javaboutique
JavaLobby
JSF Central
LeMag
Iwn.net
Osdir
Real Story Group
T3n
There are many CMS providers in Europe focusing on various areas of digital content production, management
and publication. To ensure that we target a representative set of CMS providers within the resources allocated we
© IKS Consortium
2013
165 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
orient ourselves according to the CMS technology radar put together by the CMSWatch and similar groups
(CMSWire, CMS Review, T3N, and others).
Copyright http://www.cmswatch.com/Research/Vendors/
7.1 Contacts Summary
The section of the IKS contact database presented here focuses only on the content types CMS Vendor, Integrator, Tool provider, OS Community and end-users organisations – that are of relevance for the IKS Early
Adopters Programme. The contacts are categorised according to their current active status in IKS. The contacts
are named by organisation only and not the specific IKS contact.
Definition of contact status:
1.
2.
3.
4.
5.
Active Member: Participates in one or more of the following ways – has subscribed to one of the IKS
development mailing lists, is involved in the IKS Early Adopters Programme, has participated in an IKS
workshop or Hackathon, and/or provides specifications or requirements feedback to IKS developers.
Wait and See: Has been introduced to IKS, wants to receive project updates, is waiting on more relevant results before getting involved.
Not Interested: Is not interested in participating or receiving future project updates.
No Response: Has not responded to IKS contact (email campaign)
No Contact: Missing key contact to begin dialogue.
The process is to move from “no contact” to “active member”. Effort is focused on strategic relevant contacts.
The decision is based on the broad uptake of IKS technology so duplicate key contacts for like technology CMS
stacks of communities will be avoided. However it is not always possible to find like motivated people/organisations across the open source CMS sector.
© IKS Consortium
2013
166 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Active Member: Participates in one or more of the following ways – has subscribed to one of the IKS development mailing lists, is involved in the IKS Early Adopters Programme, has participated in an IKS workshop or
Hackathon, and/or provides specifications or requirements feedback to IKS developers.
Active Companies
154 201 33 Year 2010 Year 2011 Year 2012 Wait and See: Has been introduced to IKS, wants to receive project updates, is waiting on more relevant results
before getting involved.
Wait & See
45 47 22 Year 2010 Year 2011 Year 2012 © IKS Consortium
2013
167 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
No Contact: Missing key contact to begin dialogue.
No Contact
569 566 252 Year 2010 Year 2011 Year 2012 No Response: Has not responded to IKS contact (email campaign)
No Response
644 538 140 Year 2010 Year 2011 Year 2012 © IKS Consortium
2013
168 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
7.2 Active Members
Name
URL
Country
United
Kingdom
United
Kingdom
Industry
Computers:
Software
Consulting
1
Aboynejames
http://www.aboynejames.co.uk/
2
Acuity Unlimited
http://www.acuityunlimited.net/
3
Age Of Peers
http://www.ageofpeers.com/
4
Alfresco
http://www.alfresco.com/
Germany
United
Kingdom
5
Alma Media
http://www.almamedia.fi/
Finland
News, Media
6
Anis Association
http://www.nord-internet-solidaire.org/
France
7
ANT'inno
http://www.antinno.fr
France
8
http://lenya.apache.org/
9
Apache Lenya
Apache Software Foundation
www.apache.org
USA
10
Apogado
http://www.apogado.com
Belgium
11
Appstylus
http://appstylus.com/
Spain
12
Arisem
www.arisem.com
France
13
Arla Foods
http://www.arla.com/
Denmark
Research
CMS Tool Provider
CMS Tool Provider
Computers:
Software
Computers:
Software
Semantic Tool
Vendor
Semantic Tool
Vendor
Foods & Nonalcoholic Beverages
14
ASFINAG
http://www.asfinag.at/
Austria
Transportation
15
Austria Presse Agentur
http://www.apa.at/
Austria
16
http://bassistance.de/
Germany
17
bassistance.de
Bausparkasse Wüstenrot
AG
News, Media
Computers:
Software
http://www.wuestenrot.at/
Austria
18
BBRZ GRUPPE
http://www.bbrz-gruppe.at/
Austria
Banking
Educational
Services
19
BEKK Consulting
http://www.bekk.no/
Norway
Consulting
20
Beorn Technologies
http://www.beorn-technologies.com/
France
21
BOC Asset Management
GmbH
http://www.boc-group.com/
Austria
CMS Integrator
Business Information Management
22
Bourgogne University
http://www.le2I.com
France
Research
23
Bradmcevoy.com
24
CELI France SAS
http://www.celi-france.com/fr/
France
25
Centre INFFO - Département Edition-Multimédia
France
26
chuengu
Switzerland
27
CINECA
http://www.cineca.it/
Italy
28
CKSource
http://cksource.com/
Poland
Educational
Services
CMS Tool Provider
29
clarities Software GbR
www.clarities.de
Germany
Consulting
30
CoCo new media GmbH
http://www.drupal-internet-agentur.de/
Germany
CMS Integrator
© IKS Consortium
2013
CMS Integrator
CMS Vendor
Computers:
Software
Educational
Services
169 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
31
Collaboratif-info
France
News, Media
Consulting Network
http://www.collaboratif-info.fr
http://www.feegooconsulting.de/jürgen
-böhm/
32
Germany
33
CONTENT CONTROL
http://www.contentcontrol-berlin.de/
Germany
Consulting
Computers:
Software
34
CoreMedia AG
www.coremedia.com
Germany
CMS Vendor
35
Danmarks Radio
http://www.dr.dk/
Denmark
News, Media
36
Datao
http://datao.wordpress.com/
France
37
Diagnosia
http://www.diagnosia.com/
Austria
38
Digital Bazaar
Digital Enterprise Research Institute (DERI)
http://digitalbazaar.com/
USA
www.deri.ie
Ireland
Consulting
Computers:
Software
Computers:
Software
Semantic Tool
Vendor
http://digitalsociety.ro/
Romania
CMS Integrator
41
DigitalSociety
dm drogerie markt
GmbH
http://dm-drogeriemarkt.at/
Austria
Retailing
42
Drunomics
http://www.drunomics.com/
Austria
43
Drupal
44
Dutch Cancer Society
http://drupal.org/
http://dcs.kwfkankerbestrijding.nl/Page
s/Home.aspx
CMS Integrator
CMS-Open
Source Community
Netherlands
45
EAST Team
http://www.east.ps/
Palestine
46
http://edenhofer.de/
Germany
47
Edenhofer
Energie AG Oberösterreich
Healthcare
Knowledge
Management
Vendor
Computers:
Software
http://www.energieag.at/
Austria
48
Epimorphics
http://www.epimorphics.com/web/
United
Kingdom
49
Epitech
http://www.epitech.eu/
France
Energy
Knowledge
Management
Vendor
Educational
Services
50
Erste Group Bank AG
http://www.erstegroup.com/
Austria
Banking
51
Etcware
http://www.etcware.it/
Italy
52
Euriware
http://euriware.areva.com/
France
53
European Environment
Agency
http://www.eea.europa.eu
54
European Patent Office
http://www.epo.org/
Austria
55
Europeana
www.europeana.eu
Netherlands
56
Europol
https://www.europol.europa.eu/
Netherlands
CMS Integrator
Computers:
Software
Environmental
& Waste Management
Government
Services
Educational
Services
Government
Services
57
Ever Team
www.ever-team.com
France
CMS Vendor
58
evo42 Communications
http://evo42.net/
CMS Integrator
59
EXist Solutions GmbH
http://www.adamretter.org.uk/
Austria
United
Kingdon
60
eZ Systems
http://ez.no
Norway
CMS Vendor
61
Ezenia
http://www.ezenia.it/
Italy
CMS Vendor
39
40
© IKS Consortium
2013
CMS Integrator
170 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
62
FatWire Software
www.fatwire.com
Germany
CMS Vendor
63
fCMS
http://fcms.de/en/site/index.xml
Hamburg
64
Findologic GmbH
http://www.findologic.com/
Austria
65
Findwise
www.findwise.com
Sweden
CMS Vendor
Knowledge
Management
Vendor
CMS Tool Provider
66
Flor de Utopia
http://www.flordeutopia.pt/
Portugal
CMS Integrator
67
FMSH
http://www.msh-paris.fr/
France
68
Formcept
http://formcept.com/hr/
India
News, Media
Semantic Tool
Vendor
69
http://www.gbconcept.com/
France
Consulting
70
GB Concept
Gemeinnützige Salzburger Landeskliniken
Betriebsges.m.b.H
(SALK)
http://www.salk.at/
Austria
Healthcare
71
Gentics Software GmbH
www.gentics.com
Austria
CMS Vendor
72
GoalGorilla
http://www.goalgorilla.com/
CMS Integrator
73
GOSS Interactive
www.gossinteractive.com
Netherlands
United
Kingdom
74
Greiner Holding AG
http://www.greiner.at/
Austria
75
http://www.gridsolut.de
76
Gridsolut
Health Protection Agency
http://www.hpa.org.uk/
Germany
United
Kingdom
Retailing
Computers:
Software
77
Heise
http://h-online.com/
Germany
78
Henry Gladney
http://home.pacbell.net/hgladney/
80
USA
New ZeaHundDesign
http://huntdesign.co.nz
land
ICS-FORTH - Institute of Computer Science, Foundation for Research and Technology
81
Immobilien Scout GmbH
http://www.immobilienscout24.de
Germany
82
iNfigo
http://www.infigo.fi/en/
Finland
83
InfoAxon Technologies
India
84
Infonova
Information Processing
Institute
http://www.infoaxon.com/
http://www.infonova.com/en/index.htm
l
http://lis.opi.org.pl
http://www.linkedin.com/company/insi
deout10
Poland
http://www.bcm.edu/geneticlabs/
Poland
79
85
86
Austria
Healthcare
News, Media
Computers:
Software
CMS Integrator
Research
Computers:
Software
Computers:
Software
CMS Integrator
Computers:
Software
Educational
Services
CMS Tool Provider
87
InsideOut10
Institute of Mother and
Child in Warsaw, Department of Medical
Genetics, Cytogenetics
Labs
88
Integrated Semantics
http://www.integratedsemantics.com/index.html
Research
Knowledge
Management
Vendor
89
Interact
INTERSPORT Austria
Gesellschaft mbH
http://www.interact.it/1
Italy
CMS Integrator
http://www.intersport.at/
Austria
Retailing
90
© IKS Consortium
2013
Italy
CMS Vendor
171 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Semantic Tool
Vendor
91
Intrafind Software AG
http://www.intrafind.de
Germany
92
Istos
http://www.istos.it/
CMS Integrator
93
Jadu Limited
www.jadu.co.uk
Italy
United
Kingdom
94
http://www.jahia.org/cms
http://www.jenitennison.com/consultin
g/
Switzerland
United
Kingdom
CMS Vendor
95
Jahia CMS
Jeni Tennison Consulting
Ltd
96
KaraCos
http://karacos.org
CMS Vendor
97
Kendra Initiative
http://kendra.org.uk/
France
United
Kingdom
98
Klee Group
http://www.spark-archives.com
Paris
CMS Integrator
CMS Tool Provider
99
Klein & Partner KG
http://bluedynamics.com
100
KMI - Open University
http://kmi.open.ac.uk/
Austria
United
Kingdom
CMS Integrator
Educational
Services
101
Laposte.net
http://www.laposte.net
France
Transportation
102
lbi
http://www.lbisweden.com/
Sweden
103
Liip AG
http://www.liip.ch/
104
Linuxfr.org
http://linuxfr.org
Switzerland
Luxembourg
CMS Integrator
Computers:
Software
105
Logica
www.logica.dk
Denmark
106
Logicells SAS
107
www.lunaria.co.uk
108
Lunaria
Magnolia International
Ltd.
http://www.magnolia-cms.com/home.html
CMS Vendor
109
MakoLab S.A
http://www.makolab.com
Poland
CMS Integrator
110
Manafactory
http://www.manafactory.it
Italy
111
MarkTheGlobe
http://www.marktheglobe.at/
Austria
112
Mediabistro
http://www.mediabistro.com
USA
113
Mediamatic
http://www.mediamatic.nl
Netherlands
114
Mergeflow AG
http://www.mergeflow.com
Germany
News, Media
Educational
Services
Semantic Tool
Vendor
115
Message srl
Italy
Consulting
116
Metatheke Software
http://www.messagegroup.it/
http://www.metatheke.com/en/compan
y
Portugal
www.mt.com
Switzerland
http://www.metu.edu.tr/
Turkey
CMS Integrator
Industrial and
Analytical Instruments
Educational
Services
CMS-Open
Source Community
Computers:
Software
Educational
Services
France
Scotland
118
Mettler-Toledo International Inc.
Middle East Technical
University
119
Midgard
http://www.midgard-project.org/
120
Mind Alliance
http://www.mind-alliance.com/
USA
121
Ministère de la Culture
http://www.culture.gouv.fr/
France
117
© IKS Consortium
2013
CMS Vendor
Consulting
News, Media
Computers:
Software
Computers:
Software
Digital Publishing Solutions
Semantic Tool
Vendor
172 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
122
http://modera.net/
Estonia
CMS Vendor
123
Modera
Morgenavisen Jyllands
Posten
http://jp.dk/
Denmark
124
MTA SZTAKI
http://www.sztaki.hu/?en
Hungary
News, Media
Educational
Services
125
Nansen
http://www.nansendigital.com/
Sweden
126
National University of Ireland, Galway
Ireland
127
Neofonie GmbH
http://www.neofonie.de
Germany
128
netgen
http://www.netgen.hr/eng
Croatia
129
http://www.networkvb.com/
France
http://www.netzmuehle.at/
Austria
CMS Integrator
131
NetworkVB
Netzmühle Internet
Agentur
Netzreform Neue Medien
GmbH
CMS Integrator
Computers:
Software
http://www.netzreform.de
Germany
132
Nexource Software
http://www.nexource.ro
Romania
133
Nooku
http://www.nooku.org
Belgium
134
Object-ive
http://www.object-ive.com/
France
CMS Integrator
Computers:
Networking
CMS Tool Provider
Computers:
Software
135
Onehippo
http://www.onehippo.org/
Netherlands
136
Ontotext
http://www.ontotext.com/
Bulgaria
137
Ooffee
http://ooffee.eu/
France
138
OpenContent
www.opencontent.it
Italy
139
http://hertzel.tumblr.com/
Israel
140
OPTinity eSolutions
PAUX Technologies
GmbH
CMS Integrator
Computers:
Software
http://www.paux.de/
Germany
CMS Vendor
141
Perceptive Software
http://www.perceptivesoftware.com/
CMS Integrator
142
Pharm2Phork Project
143
Philippe Ameline
http://pharm2phork.org/
http://philippe.ameline.free.fr/index_en
.php
USA
United
Kingdom
144
Plone
http://plone.org/
145
Pronovix
www.pronovix.com
Belgium
CMS Integrator
146
punk.netservices Gmbh
http://www.punkt.at/
Austria
CMS Integrator
147
Quadra
http://www.quadra-informatique.fr
France
CMS Integrator
148
QuinScape
www.quinscape.de
Germany
CMS Vendor
149
Radiometer Medical
http://www.radiometer.com/
Denmark
150
rdworth.org
[email protected]
USA
151
http://www.reaklab.com/
Belgium
152
Reaklab
Red Bull Media House
GmbH
www.redbullmedia.com
Austria
Healthcare
Computers:
Software
CMS Tool Provider
Broadcasting &
cable
153
RedTurtle
http://www.redturtle.it/it
Italy
CMS Integrator
154
Renault
http://www.renault.com/pages/index.as
France
Autos & Auto
130
© IKS Consortium
2013
France
CMS Integrator
CMS Tool Provider
Computers:
Software
CMS Vendor
Semantic Tool
Vendor
CMS Tool Provider
Agribusiness
Computers:
Software
CMS-Open
Source Community
173 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
px
Parts
155
Salsadev
http://www.salsadev.com
http://www.sapient.com/dede/sapientnitro.html
156
Sapient GmbH
157
Saplo
158
159
SDL
Semantic Technology
Institute
160
SEO Skeptic
http://www.sti-innsbruck.at/
http://www.seoskeptic.com/aaronbradley/
161
SEWEBAR
162
http://www.sdl.com/en/
Switzerland
Germany
Sweden
United
Kingdom
CMS Tool Provider
Consulting
Semantic Tool
Vendor
CMS Vendor
Austria
Research
Consulting
http://sewebar.vse.cz/
Canada
Czech Republic
Silverpeas
http://www.silverpeas.com
France
163
SimKultur
http://www.simskultur.net/
Austria
164
Social Web Architect
http://bblfish.net/
165
Sorbonne
166
Sourcesence
http://www.sourcesense.com/en/home
Italy
167
www.fsw.at
Austria
http://spar.at/
Austria
169
Soziales Wien
SPAR Österreichische
Warenhandels-AG
SunGuard Global Technology
http://www.sungard.com/infinity
Germany
170
Technical University of Warsaw
Poland
171
Telecom Italia
http://www.telecomitalia.com/
Italy
172
Telecom ParisTech
http://www.telecom-paristech.fr/
France
173
Trialox
http://trialox.org/
174
Trinity College Library
https://www.scss.tcd.ie/
Ireland
175
Tuna Development Ltd
http://www.tunanor.com/
Norway
176
Typoplanet
http://typoplanet.de/
Germany
177
http://sosmeta.fi/
179
Universita of Lisbon
University of East Finland
University of Economics,
Prague
http://www.vse.cz/index-en.php
Finland
Czech Republic
180
University of Karslruhe
http://www.kit.edu/english/
Geramny
CMS Integrator
Educational
Services
Educational
Services
Educational
Services
Educational
Services
181
University of Leipzig
http://aksw.org/Projects/limes
Germany
Research
182
http://www.cs.ox.ac.uk
183
University of Oxford
University of Virginia
Library
184
University of York
http://www.york.ac.uk
United Kingdom
Educational
USA
Services
Educational
Services
168
178
France
Portugal
http://www.lib.virginia.edu/
© IKS Consortium
2013
CMS Integrator
CMS-Open
Source Community
Computers:
Software
Educational
Services
CMS Integrator
Government
Services
Retailing
Computers:
Software
Educational
Services
Telecommunications
Research
CMS Tool Provider
Educational
Services
CMS Tool Provider
174 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
185
University Stuttgart
http://www.uni-stuttgart.de/home/
Germany
186
Vaadin
http://vaadin.com/home
Finland
Educational
Services
Computers:
Software
187
VERBUND AG
http://www.verbund.com/
Austria
Energy
188
VerVieVas
Austria
Advertising
189
190
Vox Teneo SCRL
VU University Of Amsterdam
http://vervievas.com/
http://www.voxteneo.com/en/solutions/cm
s
Belgium
Netherlands
191
Vulcan
CMS Vendor
Educational
Services
Investment
Services
192
http://www.vu.nl/nl/index.asp
USA
Wacher Chemie AG
www.vulcan.com
http://www.wacker.com/cms/de/home/ind
ex.jsp
193
Weinfreak
http://weinfreak.at
Austria
194
Wienerberger AG
http://www.wienerberger.com
Austria
195
http://www.who.int/en/
Denmark
Switzerland
Consulting
196
Word Design
World Health Organisation
197
Ximdex
http://www.ximdex.com/
CMS Vendor
198
Yanel
http://www.yanel.org/en/about.html
Spain
United
Kingdom
199
Yerbabuena Software
www.yerbabuena.es
Spain
200
zAgile
www.zagile.com
201
Zaizi
http://www.zaizi.com/
USA
United
Kingdom
CMS Integrator
Semantic Tool
Vendor
Germany
Chemicals
Foods & Nonalcoholic Beverages
Industrial and
Analytical Instruments
Healthcare
CMS Vendor
CMS Integrator
7.3 Wait and See
Name
URL
Country
Industry
CMS Tool Provider
Government Services
1
1ntt
www.1ntt.com
Finland
2
arbeiterkammer
http://www.arbeiterkammer.com/
Austria
3
Arrabiata Solutions
http://www.arrabiata.de
Germany
4
Attensity
www.attensity.com
USA
CMS Integrator
Semantic Tool
Vendor
5
Axinom International
Germany
CMS Integrator
6
BASF IT Services
http://www.axinom.com/
http://www.informationservices.basf.com/itr/BISInternet/en/portal
Germany
7
Canto
http://www.canto.com/
Germany
Chemicals
Media Asset Management
8
Capgemini
9
Danny Ayers
http://danny.ayers.name/
Italy
Consulting
10
EPiServer
http://www.episerver.com
Sweden
11
Flimmit GmbH
www.flimmit.com
Austria
CMS Integrator
Broadcasting &
cable
Consulting
© IKS Consortium
2013
175 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Semantic Tool
Vendor
CMS-Open Source
Community
12
Fluid Operations
http://www.fluidops.com
Germany
13
Geeklog
http://www.geeklog.net/
Germany
14
getit GmbH
http://www.getit.de/
Germany
15
Gnowsis
http://www.gnowsis.com/about/
Austria
CMS Integrator
CMS Tool Provider
16
http://www.grundfos.dk/
Denmark
Energy
17
Grundfos
Hepp Research
GmbH
http://www.heppnetz.de
Germany
18
Hochschule Luzern
http://www.hslu.ch/
Switzerland
19
http://www.hyperwave.com
Austria
20
Hyperwave AG
International Neuroinformatics
Research
Educational Services
Knowledge Management Vendor
http://www.incf.org/
Sweden
Healthcare
21
Jarn
http://www.jarn.com/
Norway
22
Joomlatools
23
Malmö Hogskola
http://www.mah.se/
Sweden
CMS Integrator
CMS Tool Provider
Educational Services
24
Massive Art GmbH
www.massiveart.com
Austria
CMS Integrator
25
http://www.mediawiki.org/wiki/MediaWiki
27
Mediawiki
Medical Sciences
Division
Moxiecode Systems
AB
28
CMS Vendor
http://www.medsci.ox.ac.uk/
United
Kingdom
http://www.moxiecode.com
Sweden
Nexxacon
http://www.nexxacon.com/
Austria
29
Nilfisk Advance
http://www.nilfisk-advance.com/
Denmark
30
Osor.eu
http://www.osor.eu/
Netherlands
Building Industry
Computers: Software
31
Outerthought
http://outerthought.org/en/index.html
32
Oxfam GB
http://www.oxfam.org.uk/
33
http://www.oxfam.org/
CMS Vendor
Non-Government
Organisation
Non-Government
Organisation
34
Oxfam International
Oö. Gesundheitsund Spitals-AG
Belgium
United
Kingdom
United
Kingdom
Healthcare
35
Paul Geraghty
Austria
United
Kingdom
36
http://www.phpkit.com
Germany
37
PHPKit
Q7 media GmbH &
Co. KG
http://www.q-7.de
38
Redmonk
http://redmonk.com/
Germany
United
Kingdom
CMS Vendor
Computers: Software
39
Semsol
http://semsol.com
Germany
40
sitecore
http://www.sitecore.net/
Denmark
41
Smile
SPORT EYBL &
SPORTS EXPERTS
GmbH
http://www.smile-oss.com/en/
France
CMS Vendor
CMS-Open Source
Community
http://www.eybl.at/
Austria
Retailing
26
42
http://www.gespag.at/
© IKS Consortium
2013
Healthcare
CMS Integrator
Learning Content
Mgmt System
Consulting
News, Media
Semantic Tool
Vendor
176 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
43
Squiz UK
http://www.squiz.co.uk/
United
Kingdom
44
Uberblic Labs
http://uberblic.com/
Germany
CMS Integrator
Computers: Software
45
Videinfra
http://www.videinfra.com/
Latvia
CMS Vendor
46
XhostPLUS
http://www.xhostplus.at
Austria
47
Zemanta
www.zemanta.com
Slovenia
CMS Integrator
Semantic Tool
Vendor
7.4 No Response
Name
URL
Country
Industry
1
1genia
www.1genia.com
France
2
3F
Denmark
3
3M
http://forsiden.3f.dk/
http://solutions.3mbelgie.be/wps/portal/3M/nl_B
E/EU2/Country/
CMS Vendor
NonGovernment
Organisation
Belgium
Chemicals
4
3ma media KG
42media services
GmbH
www.oserva.de
Germany
CMS Vendor
http://www.42mediagroup.com/
Germany
CMS Vendor
http://www.5th-floor.de/#cm-system
Germany
CMS Vendor
http://www.69grad.de
Germany
CMS Vendor
http://www.maersk.com/Pages/default.aspx
Denmark
www.a1.net
Austria
Energy
Telecommunications
http://www.a3systems.com
Germany
http://www.ah.dk/
http://www.aalborgkommune.dk/Sider/Forside.a
spx
Denmark
http://www.aarhus.dk/da.aspx
Denmark
http://www.au.dk/
Denmark
15
5th Floor GmbH
69° media solutions
A.P. Møller Mærsk
A1 Telekom
Austria AG
a3 systems
GmbH
Aalborg Handelsskole
Aalborg Kommune
Aarhus Kommune
Aarhus Universitet
Aarhus Universitetshospital
http://www.aarhussygehus.dk/
Denmark
16
AarhusKarlshamn
http://www.aak.com/
Sweden
Healthcare
Foods &
Nonalcoholic
Beverages
17
ABIDAT GmbH
http://www.abidat.de/
Germany
CMS Vendor
18
ablony ag
www.ablony.de
Germany
19
ABN Amro
http://www.abnamro.com/en/index.html
Denmark
CMS Vendor
Financial
Services:
Diversified
20
absolute media
http://www.absolute-media.de
Germany
21
Accso
http://www.accso.de
Germany
22
Achmea
http://www.achmea.nl/Paginas/default.aspx
Netherlands
5
6
7
8
9
10
11
12
13
14
© IKS Consortium
2013
Denmark
CMS Vendor
Educational
Services
Government
Services
Government
Services
Educational
Services
CMS Vendor
CMS Integrator
Financial
Services:
177 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
Diversified
http://acquia.com/
Belgium
CMS Tool
Provider
24
Acquia
Actelion Pharmaceuticals
http://www.actelion.com/en/index.page
Switzerland
Healthcare
25
Active3
http://www.active3.gr
Greece
CMS Vendor
26
Activis
http://www.activis.net
France
CMS Vendor
27
Addition
http://www.addition.dk/
Denmark
Consulting
28
ADMON CMS
http://www.bauer-kirch.de
Germanay
CMS Vendor
29
31
Aegon
Aftonbladet Nya
Medier
Agentur Ehe &
Janneck
32
23
Netherlands
CMS Vendor
http://wwwc.aftonbladet.se/abinfo/nyamedier.ht
ml
Sweden
News, Media
www.eheundjanneck.de
Germany
CMS Vendor
Agora Gazeta
http://www.agora.pl
Poland
33
Agrana
http://www.agrana.at/
Austria
News, Media
Foods &
Nonalcoholic
Beverages
34
Airbus
http://www.airbus.com/
Germany
Aviation
35
Aiyoota! CMS
Alexandra Institutet
http://www.aiyoota.com
Germany
CMS Vendor
http://www.alexandra.dk/dk/sider/default.aspx
Denmark
http://www.alka.dk/
Denmark
38
Alka
All-Dynamics
Software GmbH
Research
Telecommunications
http://www.all-dynamics.de
Germany
CMS Vendor
39
Aller
http://www.aller.dk/
Denmark
News, Media
40
Allianz Insurance plc
41
Allmedia
http://www.staempfli.com
Switzerland
42
Alm. Brand
http://www.almbrand.dk/abdk/Privat/index.htm
Denmark
43
Altoma GmbH
http://www.altoma.de/
Germany
44
AMAG Austria
Metall
http://www.amag.at/
Austria
45
Amaxus
http://www.amaxus.com/
United Kingdom
46
Amnesty International
http://www.amnesty.ch
Switzerland
47
Anantasoft
http://www.anantasoft.com/index.php?Home
48
Ancedis GmbH
http://www.ancedis.de/amilia
Germany
49
AP Pension
http://www.appension.dk/
Denmark
50
APLAWS
https://fedorahosted.org/aplaws/
CMS Vendor
Financial
Services:
Diversified
CMS-Open
Source
Community
51
arago DocMe
http://www.arago.de/
Germany
CMS Vendor
30
36
37
Insurance
© IKS Consortium
2013
CMS Vendor
Financial
Services:
Diversified
CMS Integrator
Industrial
and Analytical Instruments
CMS Vendor
NonGovernment
Organisation
CMS-Open
Source
Community
178 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
52
Arbejdstilsynet
http://arbejdstilsynet.dk/da/
53
Ariadne
http://www.ariadne-eu.org/
54
Arkitema
http://www.arkitema.com/
Denmark
55
Artsen Zonder
Grenzen (MSF)
http://www.artsenzondergrenzen.nl/
Netherlands
56
Arup
http://www.arup.com/
United Kingdom
Government
Services
CMS-Open
Source
Community
Building
Industry
NonGovernment
Organisation
Graphic Arts
& Design
57
Arvato Systems
http://www.as-T.de
Germany
DM Vendor
58
Assetlink AG
Switzerland
CMS Vendor
59
ATP
http://www.assetlink.com
http://www.atp.dk/X5/wps/wcm/connect/ATP/at
p.dk/
Denmark
60
http://www.auros.co.uk/
United Kingdom
http://www.ada.gv.at/
Austria
Government
Services
http://www.onb.ac.at/ev/index.php
Austria
Research
http://www.anacom.pt
Portugal
64
Auros
Austrian Development Agency
ADA
Austrian National
Library
Autoridade
Nacional de Comunicações
Außenministerium Österreich
Insurance
CMS Integrator
http://www.bmaa.gv.at/
Austria
Government
Services
Government
Services
65
avaris webdesign
http://cms-administrator.de
Germany
CMS Vendor
66
avenit AG
http://www.avenit.de/
Germany
CMS Vendor
67
http://www.axa.co.uk/
United Kingdom
68
AXA UK
BAE Systems
Detica
69
BaneDanmark
http://uk.bane.dk
Denmark
70
Bank of Finland
http://www.suomenpankki.fi/en/Pages/default.as
px
Finland
71
Bankdata
http://www.bankdata.dk/
Denmark
Insurance
Computers:
Software
Transportation
Financial
Services:
Diversified
Computers:
Software
72
http://group.barclays.com/Home
United Kingdom
Banking
http://www.batix.com/www/batix/
Germany
CMS Vendor
74
Barclays
Batix Software
GmbH
Baumit Beteiligungen
GmbH
http://www.baumit.at/
Austria
Building
Industry
75
Bavarian Nordic
http://www.bavarian-nordic.com/
Denmark
76
BAWAG PSK
http://www.bawagpsk.com/BAWAG/PK
Austria
Healthcare
Financial
Services:
Diversified
77
BBC
BBC Future
Media & Technology
www.bbc.co.uk
United Kingdom
News, Media
http://www.bbc.co.uk
United Kingdom
Broadcasting
& cable
61
62
63
73
78
Denmark
http://www.baesystemsdetica.com/
© IKS Consortium
2013
179 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
79
BDigital Media
Ltd
http://www.bdigital.biz/
Cyprus
80
Belron
http://www.belron.com/
United Kingdom
CMS Vendor
Autos &
Auto Parts
81
Berlingske Media
Berlingske
Tidende
http://berlingskemedia.dk/
Denmark
News, Media
http://www.b.dk/
Denmark
http://www.bestseller.com/
Denmark
http://www.bibliotekogmedier.dk/
Denmark
85
Bestseller
Biblioteksstyrelsen
Billund Kommune
http://www.billund.dk/cms/site.aspx?p=23
Denmark
86
Billund Lufthavn
http://www.billund-airport.dk/
Denmark
87
Bisnode
http://www.bisnode.com/
Denmark
News, Media
Apparel &
Footwear
Government
Services
Government
Services
Transportation
Financial
Services:
Diversified
88
Biznet IIS
http://www.biznetiis.com/
United Kingdom
89
biznetIIS
http://www.biznetiis.com
United Kingdom
Consulting
CMS Integrator
90
BNP Paribas
www.cortalconsors.fr
France
Banking
91
BoConcept
Boehringer
Ingelheim
http://www.boconcept.com/
Denmark
Retailing
http://www.boehringer-ingelheim.at/
Austria
https://www.borger.dk/Sider/default.aspx
94
Borger.dk
Bornholms Regionskommune
http://www.brk.dk/brk/
Denmark
95
Bose Belgium
http://www.bosebelgium.be/BE/splash.jsp
Belglium
Healthcare
Government
Services
Government
Services
Consumer
Electronics
96
BRAMAC
http://www.bramac.at/
Austria
97
BRFkredit
http://www.brf.dk/
Denmark
98
British Council
http://www.britishcouncil.org/new/
United Kingdom
99
10
0
10
1
10
2
10
3
10
4
10
5
British Library
British Telecom
Group Plc
Brodrene A&O
Johansen
http://www.bl.uk/
United Kingdom
http://www.btplc.com/
United Kingdom
http://www.ao.dk/
Denmark
Broström
http://www.brostrom.com/Pages/default.aspx
Sweden
Brother
brox IT-Solutions
GmbH
http://www.brother.fr/
France
Machinery
Transportation
Computers:
Hardware
http://www.eccenca.com
Germany
CMS Vendor
Brunner AG
http://cms.mirusys.ch/
Switzerland
Brüel og Kjær
http://www.bksv.com/
Denmark
CMS Vendor
Industrial
and Analytical Instruments
82
83
84
92
93
10
6
© IKS Consortium
2013
Energy
Financial
Services:
Diversified
Government
Services
Government
Services
Telecommunications
180 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
10
7
10
8
10
9
11
0
11
1
11
2
BTC AG
Bundesbeschaffung
Bundeskanzleramt
Bundesministerium Finanzen
http://www.btc-ag.com/
Germany
http://www.bbg.gv.at/
Ausgtria
http://www.bka.gv.at/
Austria
https://www.bmf.gv.at/
Austria
Bunge
http://www.bunge.com/
Denmark
http://www.bupl.dk/
Denmark
11
3
11
4
11
5
BUPL
Burmeister &
Wain Scandinavian Contractor
Camindo Systems
Canon Europe
Ltd
Energy
Educational
Services
http://www.bwsc.com/
Denmark
Energy
http://www.camindo.de/de/site.php/754
Germany
http://www.canon-europe.com/
United Kingdom
11
6
Canoo
http://www.canoo.com/
Germany
11
7
Cantonal Bank of
Bern
http://www.kantonalbank.ch/e/kontakt/kantonalb
anken.php
Switzerland
Carlsberg IT
Caversham Finance Ltd
http://www.carlsberg.dk/
Denmark
CMS Vendor
Consumer
Electronics
Knowledge
Management
Vendor
Financial
Services:
Diversified
Foods &
Nonalcoholic
Beverages
http://www.brighthouse.co.uk/
United Kingdom
Retailing
cekom GmbH
www.cms-laurin.de
Germany
CMS Vendor
CENSIS
Centrum
Wiskund & Informatica
http://www.censis.de/
Germany
CMS Vendor
http://www.cwi.nl/
Netherlands
Research
Cheminova
http://www.cheminova.dk/
Denmark
Chemicals
Christies
http://www.christies.com/
United Kingdom
City of Tampere
http://www.tampere.fi
Finland
Clifford Chance
http://www.cliffordchance.com
United Kingdom
CMS Made Simple
http://www.cmsmadesimple.org/
Retailing
Government
Services
Legal Services
CMS-Open
Source
Community
CMS-Channel
http://www.cms-channel.be/
Belgium
Consulting
cmsbox GmbH
Coextant Systems International AG
http://www.cmsbox.com
Switzerland
CMS Vendor
http://www.coextant.com
Germany
CMS Integrator
Coloplast
http://www.coloplast.com/
Denmark
Healthcare
11
8
11
9
12
0
12
1
12
2
12
3
12
4
12
5
12
6
12
7
12
8
12
9
13
0
13
1
© IKS Consortium
2013
Consulting
Government
Services
Government
Services
Government
Services
181 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
13
2
13
3
13
4
13
5
13
6
13
7
13
8
13
9
14
0
14
1
14
2
14
3
14
4
14
5
14
6
14
7
14
8
14
9
15
0
15
1
15
2
15
3
15
4
15
5
15
6
15
7
15
8
Colruyt
communicode
GmbH & Co. KG
http://www.colruyt.be/
Belgium
Foods &
Nonalcoholic
Beverages
http://www.communicode.de/
Germany
CMS Vendor
Composite
www.composite.net
http://www.consoleo.de/consoleoCMS/m3l1/consoleo.html
Denmark
CMS Vendor
Germany
http://www.duropack.de/
Austria
CMS Vendor
Packaging &
Promotional
Material
www.contens.de
Germany
Contensis
http://www.contentmanagement.co.uk/
United Kingdom
CMS Vendor
CMS Integrator
Content XXL
http://www.contentXXL.de
DE
CMS Vendor
Coop Danmark
http://webshop.coop.dk/
Denmark
Retailing
Corena
http://www.corena.com
http://www.cowi.dk/menu/home/Pages/home.asp
x
Denmark
CMS Vendor
Building
Industry
creatics
Creative Internet
Consultants
http://creatics.de/
Germany
www.cic.de
Germany
Credit Suisse
https://www.credit-suisse.com
Demark
Crisplant
crossbase mediasolution GmbH
http://www.crisplant.com/
http://www.crossbase.de/cbx/cms/DE/DE/web/h
ome/index
Denmark
CWSnetwork
Cyberpark
GmbH
CYNETIC SYSTEMS GmbH
Dagbladet
Børsen
Dagbladet Information
http://www.cwsnetwork.com
Germany
CMS Vendor
CMS Integrator
http://www.cyberpark.de/
Germany
CMS Vendor
www.cynetic-systems.de
Germany
CMS Vendor
http://borsen.dk/nyheder.html
Denmark
News, Media
http://www.information.dk/
Denmark
Daimler
http://www.daimler.com/
Germany
News, Media
Autos &
Auto Parts
Dalum Papir
http://www.dalumpapir.dk/Forside
Denmark
News, Media
Dalysco
www.dalysco.com
France
CMS Vendor
Danfoss
http://www.danfoss.com/Austria
Austria
Danfoss
http://www.danfoss.com/Austria
Denmark
Danisco
http://www.danisco.com/
Denmark
Consulting
Building
Industry
Foods &
Nonalcoholic
Beverages
Consoleo
Constantia Duropack
CONTENS
Software GmbH
Cowi
© IKS Consortium
2013
Denmark
Germany
CMS Vendor
CMS Integrator
Banking
Transportation
182 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
15
9
http://www.danishcrown.com/
United Kingdom
http://www.dgi.dk
Denmark
http://www.dif.dk/
Denmark
http://www.nationalbanken.dk/
Denmark
http://www.dn.dk/
Denmark
http://www.dst.dk/
Denmark
Government
Services
Government
Services
http://www.dtu.dk/
Denmark
Educational
Services
http://www.dbu.dk/
Denmark
Dansk Byggeri
http://www.danskbyggeri.dk/
Denmark
Recreation
Building
Industry
Dansk Standard
Dansk Supermarked
Danske Advokater
http://www.ds.dk/
Denmark
Consulting
http://www.dsg.dk/da/Pages/Forside.aspx
Denmark
Denmark
Danske Bank
http://www.danskeadvokater.dk/
http://www.danskebank.com/enuk/Pages/default.aspx
Retailing
Legal Services
db-central gmbh
www.db-central.com
Germany
dbc GmbH
deduktiv consulting
www.dbc-gmbh.com
Banking
CMS Integrator
CMS Integrator
http://www.deduktiv.de/
Germany
CMS Vendor
Der Standard
Det Danske Klasselotteri
Det Kongelige
Bibliotek
www.derstandard.at
Austria
http://www.klasselotteriet.dk/
Denmark
http://www.kb.dk/da/index.html
Denmark
Deutsche Börse
http://deutsche-boerse.com
Germany
DFDS
Die InformationsGesellschaft mbH
http://www.dfdsseaways.dk/
Denmark
News, Media
Lodging &
Gaming
Government
Services
Financial
Services:
Diversified
Transportation
http://www.informationsgesellschaft.com
Germany
CMS Vendor
Die Mobiliar
http://www.mobi.ch/mobiliar/live/index_de.html
Switzerland
18
2
Diem
http://diem-project.org/
Insurance
CMS-Open
Source
Community
18
Diferior
http://diferior.com/
CMS-Open
16
0
16
1
16
2
16
3
16
4
16
5
16
6
16
7
16
8
16
9
17
0
17
1
17
2
17
3
17
4
17
5
17
6
17
7
17
8
17
9
18
0
18
1
Danish Crown
Danish Gymnastics and Sports
Associations
Danmarks
Idræts-Forbund
Foods &
Nonalcoholic
Beverages
Danmarks Nationalbank
Danmarks
Naturfredningsforening
Danmarks Statistik
Danmarks
Tekniske Universitet
Dansk BoldspilUnion
© IKS Consortium
2013
Denmark
Educational
Services
Government
Services
Financial
Services:
Diversified
183 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
3
18
4
18
5
18
6
Source
Community
digimaker
digital concepts
OEG
http://cms.digimaker.com
Norway
CMS Vendor
http://www.digital-concepts.com
Austria
CMS Vendor
dimedis GmbH
www.dimedis.de
Germany
Djurslands Bank
http://www.djurslandsbank.dk/
Denmark
CMS Vendor
Financial
Services:
Diversified
DLG
http://www.dlg.dk/uk/
Denmark
Agribusiness
DSB
http://www.dsb.dk/
Denmark
19
0
DuMont
http://www.dumont.com/
19
1
DynPage
http://www.dynpage.net/
Germany
19
2
DynPG
http://www.dynpg.org/
Germany
Döhler
http://www.doehler.com/en/homed
Germany
Tourism
Industrial
and Analytical Instruments
CMS-Open
Source
Community
CMS-Open
Source
Community
Foods &
Nonalcoholic
Beverages
e-Spirit AG
www.e-spirit.com/en/
Germany
CMS Vendor
E. ON Ruhrgas
http://www.eon-ruhrgas.com
Germany
Energy
Easyconsole
www.easyconsole.com
Cyprus
CMS Vendor
easywebmanager
www.easywebmanager.com
Lithuania
CMS Vendor
eBOS
Ecclesiastical
Insurance Group
plc
echonet communication GmbH
Edelweiss | medien agentur
www.ebos.com.cy
Cyprus
CMS Vendor
http://www.ecclesiastical.com/
Unided Kingdom
Insurance
http://www.echonet.at/de/produkte/content-life
Austria
http://www.edelweiss-agentur.com
Switzerland
CMS Vendor
CMS Integrator
Educational
Services
www.eesy.de
Germany
CMS Vendor
www.eggheads.de
Germany
CMS Vendor
http://www.egoditor.com
Germany
CMS Vendor
www.egotec.com
Germany
CMS Vendor
18
7
18
8
18
9
19
3
19
4
19
5
19
6
19
7
19
8
19
9
20
0
20
1
20
2
20
3
20
4
20
5
20
6
Education Group
eesy eService
System
eggheads CMS
GmbH -Cross
Media Solution
Egoditor - The
Publishing Solution
EGOTEC GmbH
© IKS Consortium
2013
184 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
20
7
20
8
20
9
21
0
21
1
21
2
21
3
21
4
21
5
21
6
21
7
21
8
21
9
22
0
22
1
22
2
22
3
http://www.einsgmbh.de/cms/servlet/Query?node=1207&langua
ge=1
Germany
Electrolux
elements.at New
Media Solutions
GmbH
http://www.electrolux.dk
Demark
CMS Vendor
Consumer
Electronics
http://www.elements.at
Austria
CMS Vendor
EmagicC
http://cmsnet.com
http://www.energimidt.dk/Privat/Sider/Privat.asp
x
Belgium
CMS Vendor
Denmark
http://www.eogs.dk/
Denmark
Energy
Telecommunications
ESONO KG
Estonian Defence
Forces
www.esono.de
Germany
http://www.mil.ee/index_eng.php
Estonia
Et Netera
http://www.etnetera.cz/
Czech Republic
CMS Vendor
Government
Services
CMS Integrator
EUMETSAT
http://www.eumetsat.int/Home/index.htm
Denmark
News, Media
Government
Services
EINS-GmbH
EnergiMidt
Erhvervs- og
Selskabsstyrelsen
Europa-Kommissionen
European Centre
for Disease Prevention and Conhttp://ecdc.europa.eu/en/Pages/home.aspx
trol (ECDC)
European Free
Trade Associahttp://www.efta.int
tion
European Medihttp://www.ema.europa.eu/
cines Agency
European Space
http://www.esa.int/esaCP/index.html
Agency
Government
Services
Government
Services
France
Healthcare
Aerospace &
Defense
Government
Services
European Union
www.europa.eu
http://www.evn.at/
Austria
Energy
22
4
EVN AG
EWEA (European Wind Energy
Association)
http://www.ewea.org/
Belgium
22
5
Exalead
http://www.exalead.com/software/
France
22
6
Exozet Berlin
GmbH
http://www.exozet.com
Germany
Energy
Business
Information
Management
Digital Publishing Solutions
CMS-Open
Source
Community
22
7
http://www.exponentcms.org/
22
8
22
9
Exponent
fabrique d' images ebusiness
GmbH
factline Webservices GmbH
23
FDM
http://www.fabriquedimages.de
Germany
CMS Vendor
http://www.factline.com/
Austria
CMS Vendor
http://www.fdmgroup.com/
Denmark
Financial
© IKS Consortium
2013
185 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
0
23
1
23
2
23
3
23
4
23
5
23
6
23
7
23
8
23
9
24
0
24
1
24
2
24
3
24
4
24
5
24
6
24
7
24
8
24
9
25
0
25
1
25
2
25
3
25
4
25
5
Services:
Diversified
FEDNET
Ferring
Lægemidler
http://www.ifrc.org
http://www.ferring.dk/FlashPage.aspx?area=5&p
age=40&flash=1&menu=0
Switzerland
Healthcare
Denmark
Healthcare
FH Hagenberg
FHOberösterreich
http://www.fh-ooe.at
http://www.fh-ooe.at/campussteyr/campus/personen/forschung-entwicklung/
Austria
Austria
Research
Educational
Services
Financial Times
Financial Times
Deutschland
Fischer Computertechnik
www.ft.co.uk
United Kingdom
News, Media
http://www.ftd.de/
Germany
News, Media
http://www.fct.de
Germany
http://www.fpf.co.nz/
New Zealand
http://www.flagbit.de
Germany
CMS Vendor
Financial
Services:
Diversified
CMS Integrator
Flexive
http://www.flexive.org/
Austria
FLSmidth
flying dog software
http://www.flsmidth.com/
Denmark
http://www.flyingdog.biz
Germany
Folketinget
Fondazione Edmund Mach
http://www.ft.dk/
Denmark
http://www.iasma.it/
Italy
Forestsoft
Forsvarets MedieCenter
Fredericia Kommune
Frederikshavn
Kommune
Freie Universität
Berlin
http://www.forestsoft.de/
http://forsvaret.dk/fmc/Pages/forsvarets_mediece
nter.aspx
http://www.fredericia.dk/Borger/Sider/default.as
px
Germany
http://www.frederikshavn.dk/da/menu/
Denmark
http://www.fu-berlin.de/en/
Germany
Frequentis
http://www.frequentis.com/en/at/home/
Austria
Føroya Tele
Faroe Islands
Faroe Islands
gamper media
www.dynpg.ch
Switzerland
Fisher & Paykel
Finance
Flagbit GmbH &
Co. KG
Gauss Interprise AG
GDF SUEZ
Gemeente Eindhoven
Denmark
Denmark
Germany
http://www.gdfsuez.com/
Switzerland
http://www.eindhoven.nl/web/show
Netherlands
© IKS Consortium
2013
CMS Vendor
Industrial
and Analytical Instruments
CMS Vendor
Government
Services
Government
Services
CMS Integrator
News, Media
Government
Services
Government
Services
Educational
Services
Industrial
and Analytical Instruments
Telecommunications
CMS Vendor
CMS Integrator
Energy
Government
Services
186 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
25
6
25
7
25
8
25
9
26
0
26
1
26
2
26
3
26
4
26
5
26
6
26
7
26
8
26
9
27
0
27
1
27
2
27
3
27
4
27
5
27
6
27
7
27
8
27
9
28
0
28
1
28
2
Gemeente Leiden
http://www.leiden.nl/gemeente
Netherlands
Government
Services
Genzyme Europe
http://www.genzyme.eu/
Netherlands
Healthcare
Geus
http://www.geus.dk/geuspage-uk.htm
Denmark
News, Media
GFK Group
GlaxoSmithKline
UK
Global Happiness
Sweden AB
Glostrup Kommune
gradwerk interaktive medien
gmbh
http://www.gfk.com/
Germany
Consulting
http://www.gsk.com/
United Kingdom
Healthcare
www.consolocms.com
Sweden
http://www.glostrup.dk/
Denmark
CMS Vendor
Educational
Services
http://www.gradwerk.de
Germany
CMS Vendor
Greenpeace
Greenwich
Council
Guardian News
and Media
Göteborgs universitet
http://www.greenpeace.org
http://www.royalgreenwich.gov.uk/site/
United Kingdom
Government
Services
http://www.gmgplc.co.uk/
United Kingdom
http://www.gu.se/
Sweden
Haas Waffelmaschinen
Group
http://www.haas.com/index.php
Austria
hamburg.de
http://www.hamburg.de/
Germany
News, Media
Educational
Services
Industrial
and Analytical Instruments
Government
Services
HanseMerkur
HELLMEDIA
GmbH
http://www.hansemerkur.de/
Germany
Insurance
http://www.hellmedia.de/
Germany
Helma
Hjørring Kommune
http://dev.helma.org/
Austria
http://www.hjoerring.dk/
Denmark
CMS Vendor
Computers:
Software
Government
Services
HK
HMP Software
Solutions GmbH
Holstebro Kommune
Denmark
http://www.hmp-solutions.com/startseite/
Germany
http://www.holstebro.dk/
Denmark
Home
Home Of The
Brave
Homepage
Toolbox
Horsens Kommune
http://home.dk/
Denmark
CMS Vendor
Government
Services
Building
Industry
http://home.of.the.brave.de
Germany
CMS Vendor
http://www.homepage-toolbox.com/home.html
Germany
http://www.horsens.dk/
Denmark
CMS Vendor
Government
Services
Hotel Mediapark
Houses of Parliament UK
http://www.hotel-mediapark.de/
Germany
http://www.parliament.uk/
United Kingdom
© IKS Consortium
2013
CMS Vendor
Government
Services
187 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
28
3
28
4
28
5
28
6
28
7
28
8
28
9
29
0
29
1
29
2
29
3
29
4
29
5
29
6
29
7
29
8
29
9
30
0
30
1
30
2
30
3
Hvidovre Kommune
hyperCMS Content Management
Solutions
http://www.hvidovre.dk/
Denmark
Government
Services
http://www.hypercms.net
Austria
CMS Vendor
i-WAG GmbH
http://www.i-wag.ch/
Switzerland
i3
IBM Software
Central and Eastern Europe/Middle
East/Africa
http://www.wearei3.com/
Northern Ireland
CMS Vendor
CMS Integrator
http://www01.ibm.com/software/data/services/contactsemea
.html
Germany
Ibuildings
http://www.ibuildings.nl/
Netherlands
IconParc GmbH
http://www.iconparc.de/ebusiness
Germany
Computers:
Software
CMS Integrator
Computers:
Software
IKEA
Denmark
Retailing
iKiss 5
http://www.ikea.com/
http://www.cmsuebersicht.de/enterprisecms/ikiss.html
Germany
CMS Vendor
Imperia AG
http://www.imperia.de/start/
Germany
inCaptiva
www.incaptiva.dk
Denmark
incca GmbH
Indenrigs- og
Sundhedsministeriet
http://www.incca.de/home.htm
Germany
CMS Vendor
CMS Integrator
CMS Integrator
http://www.im.dk/
Denmark
Indicom
Indoqa Software
Design und
Beratung GmbH
www.indicom.dk
Denmark
Healthcare
CMS Integrator
Austria
Consulting
INDUAL GMBH
http://www.indoqa.com
http://www.indual.ch/produkte/yourbureau/index
.php
Switzerland
CMS Vendor
infoAsset AG
http://www.infoasset.de
Germany
InfoServ AG
http://www.infoserv.de
Germany
CMS Vendor
Computers:
Software
ING
http://www.ing.nl/particulier/index.aspx
Netherlands
Banking
Initiva AB
www.initiva.se
Sweden
http://www.insiders-technologies.de/
Germany
CMS Vendor
Knowledge
Management
Vendor
www.offis.de
Germany
http://www.int-ag.ch/ch-de/
Switzerland
Energy
CMS Tool
Provider
www.interconcept.de
Germany
CMS Vendor
http://www.interlogics.de/
Germany
CMS Inte-
30
4
30
5
30
6
Insiders Technologies GmbH
Institute For
Information
Technology
INT Informatik
AG
Interconcept
GmbH
30
InterLogics
© IKS Consortium
2013
188 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
7
GmbH
30
8
30
9
Internet Marketing Service
www.easy4you-cms.de
Germany
CMS Vendor
InterRed 12
http://www.interred.de
Germany
Investec
IPAX Internet
Services
http://www.investec.co.uk/
United Kingdom
http://www.ipax.at
Austria
CMS Vendor
Financial
Services:
Diversified
CMS Integrator
IQDoQ GmbH
Irmler ITSolutions
http://www.iqdoq.de/
Germany
CMS Vendor
http://www.irmler.at
http://www.dk.issworld.com/Pages/Frontpage.as
px
Austria
Denmark
CMS Vendor
Building
Industry
http://www.bluepage-cms.com/
Germany
CMS Vendor
iT-config GmbH
http://www.it-config.de/
Germany
ITABS GmbH
IXSOL - innovative solutions
gmbh
http://www.itabs.de
Germany
CMS Vendor
CMS Integrator
http://www.ixsol.at
Austria
CMS Vendor
jalios
John Lewis Partnership
www.jalios.com
France
CMS Vendor
http://www.johnlewispartnership.co.uk/
United Kingdom
Retailing
JP/Politikens Hus
http://jppol.dk
Denmark
Jugat
http://www.jugat.org/
Austria
Jyske Bank
Karolinska Institutet University
Library
http://jyskebank.com/wps/portal/jbpb_COM/
Netherlands
News, Media
Computers:
Software
Financial
Services:
Diversified
http://kib.ki.se/en
Sweden
KBC
https://www.kbc.be
Belgium
31
0
31
1
31
2
31
3
31
4
31
5
31
6
31
7
31
8
31
9
32
0
32
1
32
2
32
3
32
4
32
5
32
6
32
7
32
8
32
9
33
0
33
1
33
2
33
ISS Danmark
ISS-Oberlausitz
e.K.
grator
Keleo
Germany
Educational
Services
Financial
Services:
Diversified
CMS Integrator
CMS Integrator
Kentico
http://www.kentico.com
Keva
http://www.keva.fi/en/Pages/Default.aspx
Finland
Key Solutions
http://www.key.at/KS
Austria
Insurance
CMS Integrator
KIGG GmbH
http://www.kigg.de/
Germany
Computers:
Software
Kinetiqa GmbH
http://www.kinetiqa.de/
Germany
CMS Vendor
Klopotek
http://www.klopotek.de/
Germany
Digital Pub-
Keytrade Bank
© IKS Consortium
2013
189 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
3
33
4
33
5
33
6
33
7
33
8
33
9
34
0
34
1
34
2
34
3
34
4
34
5
34
6
34
7
34
8
34
9
35
0
35
1
35
2
35
3
35
4
35
5
35
6
35
7
35
Kneib Development
Kommunernes
Landsforening
lishing Solutions
CMS Integrator
Educational
Services
http://www.kneib.com/
Netherlands
http://www.kl.dk/
Denmark
Kompan
http://www.kompan.com/
Sweden
KONE
http://www.kone.com
Denmark
Kopenhangenfur
http://www.kopenhagenfur.com/
Denmark
Krifa
http://www.krifa.dk/
Denmark
Kronvold
Kræftens
Bekæmpelse
Kungliga
Tekniska högskolan
Kungälvs Kommune
http://kronvolds.dk/
Denmark
Clothing
Telecommunications
Computers:
Software
http://www.cancer.dk/
Denmark
Research
http://www.kth.se/
Sweden
http://www.kungalv.se/
Sweden
Kurier.at
www.kurier.at
Austria
Kvik
http://www.kvik.com/
Denmark
Københavns Digitale Bibliotek
Københavns
http://www.kk.dk/
Kommune
Københavns
Kommune Kultur- og
http://www.kk.dk/FaktaOmKommunen/Forvaltni
Fritidsforvaltnger/KulturOgFritidsforvaltningen.aspx
ningen
Københavns
http://www.ku.dk/english/
Universitet
Landstinget Halhttp://www.regionhalland.se/
land
Ledernes
Hovedorganisahttps://www.lederne.dk/lho/Forside.htm
tion
Denmark
Toys
Building
Industry
Educational
Services
Government
Services
News, Media
Building
Industry
Government
Services
Government
Services
Sweden
Government
Services
Educational
Services
Government
Services
Denmark
Consulting
Toys
CMS Integrator
Denmark
Denmark
LEGO
www.lego.com
Denmark
Lemon42 GmbH
lindner software
& consulting
GmbH
Linköpings universitet
www.lemon42.com
Austria
www.lisocon.de
Germany
http://www.liu.se/?l=en
Sweden
CMS Integrator
Educational
Services
Lise Aagaard Copenhagen
Living Interachttp://www.living-ilabs.com/
tive Labs GmbH
Denmark
Austria
Computers:
Software
living-e AG
Germany
Knowledge
http://www.attensity.com/home/
© IKS Consortium
2013
190 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
8
35
9
36
0
36
1
36
2
36
3
36
4
36
5
36
6
36
7
36
8
36
9
37
0
37
1
37
2
37
3
37
4
37
5
37
6
37
7
37
8
37
9
38
0
38
1
38
2
38
3
38
4
38
Management
Vendor
Financial
Services:
Diversified
Lloyds TSB
International
Private Banking
https://www.llb.li/de/privatkunden/privatebanking
Germany
LM Wind Power
http://www.lmwindpower.com/
Denmark
logMEDIA
London Borough
of Islington
http://www.logmedia.at
Austria
http://www.islington.gov.uk/
United Kingdom
Energy
CMS Integrator
Government
Services
LSZ Consulting
http://www.lsz-consulting.at/
Austria
Consulting
M2 Technologies
www.optimalsite.com
Lithuania
macio GmbH
Magistratsdirektion Stadt Wien
http://www.macio.de/
Germany
http://www.wien.gv.at/mdbd/
Austria
Malmberg
Mariagerfjord
Kommune
http://www.malmberg.nl/
The Netherlands
http://www.mariagerfjord.dk/
Denmark
CMS Vendor
Computers:
Software
Government
Services
Educational
Services
Government
Services
Marticco
Martin Breitenlechner
Mayflower
GmbH
http://www.marticco.dk/Pages/Marticco.aspx
Denmark
News, Media
http://www.breitenlechner.com/
Austria
www.mayflower.de
Germany
MC-Informatik
http://www.mc-informatik.de/
Germany
CMS Vendor
CMS Integrator
Computers:
Software
media2cms
www.media2cms.dk
Denmark
CMS Vendor
Medtronic
MemHT
Deutschland
http://www.medtronic.com/
Switzerland
Healthcare
www.memht.de
Germany
menttes
www.menttes.com
USA
CMS Vendor
CMS Integrator
Merck
Michael Daum
Consulting
http://www.merck.com/index.html
Denmark
http://michaeldaumconsulting.com
Germany
Microsoft Russia
www.microsoft.com
Russia
Miljøministeriet
Ministry for
Foreign Affairs
of Finland
http://www.mim.dk/
Denmark
http://formin.finland.fi/public/default.aspx?cultur
e=en-US&contentlan=2
Finland
mk-webservices
Mobilistics
GmbH
http://www.mk-webservices.de/
Germany
http://www.raphael-gmbh.de/
Germany
MOC Systems
http://moc.net/
Denmark
Government
Services
Computers:
Software
Computers:
Software
CMS Integrator
Modul University
http://www.modul.ac.at/
Austria
Educational
© IKS Consortium
2013
Healthcare
CMS Integrator
Computers:
Software
Government
Services
191 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
5
38
6
38
7
38
8
38
9
39
0
39
1
39
2
39
3
39
4
39
5
39
6
39
7
39
8
39
9
40
0
40
1
40
2
40
3
40
4
40
5
40
6
40
7
40
8
40
9
41
0
41
1
41
Services
motionmill
www.motionmill.com
Belgium
CMS Integrator
MRNET
www.mrnet.pt
Portugal
CMS Vendor
MT Højgaard
http://mth.com/
Denmark
http://www.openeyesystems.de/
Germany
Energy
Digital Publishing Solutions
www.mum.lu
Luxembourg
CMS Vendor
http://www.msf.org/
France
Healthcare
nbsp GmbH
Neologic Software AG
www.nbsp.de
Germany
CMS Vendor
www.neologic.ch
Switzerland
CMS Vendor
Nets
http://www.nets.eu/en/Pages/default.aspx
Denmark
Banking
NHS Choices
http://www.nhs.uk/Pages/HomePage.aspx
United Kingdlom
Nokia
Norddjurs Kommune
http://www.nokia.com
Finland
http://www.norddjurs.dk/
Denmark
Healthcare
Telecommunications
Government
Services
Nordea Danmark
Nordea Invest
Fund Management
Nordisk Ministerråd
NORDJYSKE
Medier
Norges forskningsråd
Northumbria
University
Norwegian Ministry of Foreign
Affairs
http://www.nordea.dk/
Denmark
http://www.nordea.com/Denmark
Denmark
http://www.norden.org/en
Denmark
Banking
Financial
Services:
Diversified
Government
Services
http://www.nordjyske.dk/
http://www.forskningsradet.no/no/Forsiden/1173
185591033
Denmark
Tourism
Norway
http://www.northumbria.ac.uk/
United Kingdom
Research
Educational
Services
http://www.regjeringen.no/en/dep/ud.html
Norway
Government
Services
Novartis
http://www.novartis.com/
Germany
Healthcare
Novo Nordisk
http://www.novonordisk.at
Austria
Healthcare
Novozymes
http://www.novozymes.com/en/Pages/default.aspx
NRGi
http://www.nrgi.dk/
Denmark
Energy
Nuon
Ny Carlsberg
Glyptotek
Nyborg Kommune
http://www.nuon.com/
Netherlands
http://www.glyptoteket.dk/
Denmark
http://www.nyborg.dk/
Denmark
Energy
Educational
Services
Government
Services
NYK Group
http://www.nykeurope.com/
MT Medientechnik GmbH
MUM internet
solutions
Médécins Sans
Frontières
© IKS Consortium
2013
Healthcare
Transporta-
192 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
2
41
3
41
4
41
5
41
6
41
7
41
8
41
9
42
0
42
1
42
2
42
3
42
4
42
5
42
6
42
7
42
8
42
9
43
0
43
1
43
2
43
3
43
4
43
5
Europe Limited
tion
Financial
Services:
Diversified
Nykredit
Object Dynamix
AG
Odense Centralbibliotek
Odense Kommune
Oesterriches
BundesBahn
Office for Official Publications
of the European
Communities
Office Of The
High Commissioner For Human Rights
http://www.nykredit.com/corporate
Denmark
http://www.emotix.ch/website/ueber_uns.htm
Switzerland
https://www.odensebib.dk/forside
Denmark
http://www.odense.dk/
Denmark
www.oebb.at
Austria
CMS Vendor
Educational
Services
Government
Services
Transportation
http://publications.europa.eu/index_en.htm
Luxembourg
Government
Services
OK
http://www.ok.dk/english/
Denmark
OKKAM
http://www.okkam.biz/
Italy
omeco GmbH
www.omeco.de
Germany
OmegaCMS
http://omega.no/
Norway
CMS Vendor
CMS-Open
Source
Community
OMV Petrom
Onedrop Solutions GmbH &
Co KG
http://www.omv.com
Austria
Energy
http://www.1drop.de
Germany
CMS Tool
Provider
OpenText
http://websolutions.opentext.de/
OpenWGA
http://www.openwga.com/home.en.html
Germany
Optaros
http://www.optaros.com/blog
Switzerland
Oticon
http://oticon.com/
OTIS
http://www.otisworldwide.com/
Germany
Outokumpu
Stainless Steel
Oy
http://www.outokumpu.com/
Finland
CMS Vendor
CMS Integrator
Consumer
Electronics
Building
Industry
Industrial
and Analytical Instruments
Ovum
Patent- og
Varemærkestyrel
sen
http://www.ovumkc.com/
United Kingdom
Consulting
http://www.dkpto.dk/
Denmark
Per Aarsleff
http://www.aarsleff.com
Denmark
Government
Services
Building
Industry
Percussion
http://www.percussion.com/
United Kingdom
CMS Vendor
Government
Services
http://www.ohchr.org
© IKS Consortium
2013
Energy
Computers:
Software
CMS Vendor
193 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
43
6
43
7
43
8
43
9
44
0
44
1
44
2
44
3
44
4
44
5
44
6
44
7
44
8
44
9
45
0
45
1
Pfizer
http://www.pfizer.com/home/
phaziz.com
Austria
Healthcare
Germany
Consumer
Electronics
Financial
Services:
Diversified
Industrial
and Analytical Instruments
Legal Services
Philips
http://www.philips.at/
Netherlands
Pictet & Cie
http://www.pictet.com/
Switzerland
Pipelife
Plesner Svane
Grønborg
http://www.pipelife.com/com/
Austria
Denmark
Pohjola Bank
http://www.plesner.com/cms/Startside-1437.aspx
https://www.pohjola.fi/pohjola?id=300000&kieli
koodi=en
Politiet
https://www.politi.no/
Norway
Insurance
Government
Services
polopoly
www.polopoly.com
United Kingdom
CMS Vendor
posOS GmbH
www.posos.net
Switzerland
PostNord
http://www.postnord.com/
Denmark
Practical Law
http://uk.practicallaw.com/
United Kingdom
CMS Vendor
Government
Services
Legal Services
Finland
Prodevion GmbH
Professionshøjskolen UCC
http://www.ucc.dk/
Demnark
Protego
http://www.protego.de/en/
Denmark
protendics Ltd.
www.protendics.de
Germany
Proxml
http://www.proxml.be/linked-data.html
Belgium
CMS Vendor
Knowledge
Management
Vendor
www.puma.com
Switzerland
Clothing
http://www.pxp.eu
Austria
CMS Integrator
45
5
Puma
PXP interactive
services & solutions AG
querform.at –
projekte & design
OG
http://querform.at/
Austria
45
6
R-Solution (Raiffeisen IT)
http://www.r-solution.at/
Austria
Rabobank
http://www.rabobank.com/content/
Denmark
Radagio
http://www.radagio.com/
The Netherlands
Raiffeisen
http://www.raiffeisen.ch/web/home_de
Switzerland
45
2
45
3
45
4
45
7
45
8
45
9
Germany
© IKS Consortium
2013
Educational
Services
Building
Industry
Consulting
Financial
Services:
Diversified
Financial
Services:
Diversified
Consulting
Financial
Services:
Diversified
194 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
46
0
46
1
46
2
46
3
46
4
46
5
46
6
46
7
46
8
46
9
47
0
47
1
47
2
47
3
47
4
47
5
47
6
47
7
47
8
47
9
48
0
48
1
48
2
48
3
48
4
48
5
Raiffeisen Informatik GmbH
Randers Kommune
ReadyWeb
GmbH
http://raiffeiseninformatik.at
Austria
http://www.randers.dk/
Denmark
http://www.readyweb.de
Germany
Realnetworks
http://www.realnetworks.com/
Austria
Rebild Kommune
recon Enterprise
CMS
http://www.rebild.dk/+
http://www.recon-cms.de/recon/enterprisecontent-management/produktuebersicht.html
Denmark
Recticel
Region
Hovedstaden
Region Midtjylland
Region Nordjylland
http://www.recticel.be/
Belgium
http://www.regionh.dk/menu/
Denmark
http://www.regionmidtjylland.dk/
Denmark
http://www.rn.dk/
Denmark
Region Sjælland
http://www.regionsjaelland.dk/
Denmark
Region Skåne
http://www.skane.se/
Sweden
Rezidor
Richemont International SA
http://www.rezidor.com/
http://www.richemont.com/
Switzerland
Ricoh Nederland
http://www.ricoh.nl/
Netherlands
Rigshospitalet
http://www.rigshospitalet.dk/menu/
Denmark
Rigspolitiet
http://www.politi.dk/da/ompolitiet/rigspolitiet/
Denmark
Riksdagen
Rikspolisstyrelsen
RLS jakobsmeyer GmbH
http://www.riksdagen.se/
http://www.polisen.se/Om-polisen/Polisen-iSverige/Organisation/Rikspolisstyrelsen/
Sweden
http://www.rls.de/
Germany
Robolo
http://www.robolo.de/
Germany
www.tesch.de
Germany
http://www.rhs.dk
Denmark
http://roth-programmierung.de/
Germany
Roxen
www.roxen.com
Sweden
RWA
http://www.rwa.at/
Austria
Rockwell Automation
Roskilde Handelsskole
Roth Programmierung
© IKS Consortium
2013
Germany
Denmark
Banking
Government
Services
CMS Tool
Provider
Computers:
Software
Government
Services
CMS Vendor
Industrial
and Analytical Instruments
Government
Services
Government
Services
Government
Services
Government
Services
Healthcare
Lodging &
Gaming
Apparel &
Footwear
Digital Publishing Solutions
Healthcare
Government
Services
Government
Services
Government
Services
Computers:
Software
CMS Integrator
Industrial
and Analytical Instruments
Educational
Services
Computers:
Software
CMS Vendor
Industrial
and Analyti-
195 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
cal Instruments
48
6
48
7
48
8
48
9
49
0
49
1
49
2
Rzeczpospolita
Rådet for sikker
trafik
http://www.rp.pl/
Poland
http://www.sikkertrafik.dk/
Denmark
Saab
http://www.saab.com
News, Media
Government
Services
Autos &
Auto Parts
Sanoma
http://www.sanoma.com/
Denmark
News, Media
Sanoma Data
http://www.sanoma.com/
Finland
News, Media
Santaris Pharma
http://www.santaris.com/
Denmark
Healthcare
SAS
http://www.sas.dk/
Denmark
Sauer-Danfoss
http://www.sauer-danfoss.com/
Denmark
Aviation
Industrial
and Analytical Instruments
Saurus
www.saurus.info
Estonia
Saxo Bank
http://www.saxobank.com/
Denmark
Scania Danmark
http://www.scania.dk/
Denmark
SCHEMA GmbH
Scholl Communications AG
SCREAMDESIG
N GmbH
http://www.schema.de
Germany
http://www.scholl.de/scholl/index.php
Germany
http://www.screamdesign.de/en/
Germany
CMS Vendor
CMS Integrator
sdl tridion
SDL Web Content Management
Solutions Division
www.tridion.com
Netherlands
CMS Vendor
http://www.sdl.com/en/wcm/
Germany
CMS Vendor
Selbstdenker AG
http://www.selbstdenker.ag/
Germany
50
3
50
4
Serena Software
GmbH
http://www.serena.com/
Germany
CMS Vendor
Knowledge
Management
Vendor
Servicestyrelsen
http://www.servicestyrelsen.dk/
Denmark
50
5
50
6
50
7
50
8
50
9
Siemens AG
Wien
Siemens AG,
I&S IS
http://www.siemens.com/answers/cee/de/
Austria
www.siemens.de/hybrix
Germany
Silhouette
Silkeborg Bibliotekerne
http://www.silhouette.com
Austria
http://silkeborgbib.dk/
Denmark
Simple Xoops
http://www.myxoops.org/
Germany
49
3
49
4
49
5
49
6
49
7
49
8
49
9
50
0
50
1
50
2
© IKS Consortium
2013
CMS Vendor
Financial
Services:
Diversified
Autos &
Auto Parts
CMS Integrator
Healthcare
Business
Information
Management
Computers:
Software
Healthcare
Educational
Services
CMS Tool
Provider
196 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
51
0
51
1
51
2
51
3
51
4
51
5
51
6
51
7
51
8
51
9
52
0
52
1
52
2
52
3
52
4
52
5
52
6
52
7
52
8
52
9
53
0
Simploo GmbH
http://www.simploo.de/
Germany
CMS Vendor
CMS Integrator
Sitefinity
http://www.sitefinity.com/
SiteOS AG
Six Offene Systeme GmbH
www.siteos.de
Germany
CMS Vendor
www.six.de
Germany
SJ
Skanderborg
Kommune
http://www.sj.se/
Sweden
http://www.skanderborg.dk/
Denmark
SKAT
http://www.skat.dk
Denmark
Skatteministeriet
http://www.skm.dk/
Denmark
skurrilewelt
Software Competence Center
Hagenberg
Sony Ericsson
Mobile Communications
http://www.skurrilewelt.de/
Germany
CMS Vendor
Transportation
Government
Services
Government
Services
Government
Services
CMS Integrator
http://www.scch.at/
Austria
Research
http://www.sonymobile.com/
Sweden
Consumer
Electronics
SOS-Kinderdorf
http://www.sos-kinderdorf.at/
Austria
Sourcefabric
http://www.sourcefabric.org
Czech Republic
Spar Nord
Sparkassen Rating und Risikosysteme
Spar Nord
Denmark
http://www.s-rating-risikosysteme.de/
Germany
Specsavers
http://www.specsavers.co.uk/
United Kingdom
Spitfire
SRPA RufferPaniagua GbR
http://spitfire.clausmuus.de/
Germany
www.srpa.com
Germany
Statens IT
http://www.statens-it.dk/
Denmark
CMS Vendor
Government
Services
Statkraft
http://www.statkraft.com/
Norway
Energy
Statoil Danmark
http://www.statoil.dk/FrontServlet
Denmark
http://www.stibosystems.com/
Germany
Energy
Knowledge
Management
Vendor
Germany
CMS Vendor
Computers:
Software
53
1
53
2
53
3
53
4
STIBO Systems
GmbH
Stibo Systems
GmbH
studio adhoc
GmbH
subshell
Germany
53
Sulzer Ltd Schweiz
Switzerland
http://www.stibosystems.de
http://www.studioadhoc.de/
© IKS Consortium
2013
CMS Vendor
Foods &
Nonalcoholic
Beverages
Financial
Services:
Diversified
Healthcare
CMS-Open
Source
Community
197 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
5
53
6
53
7
53
8
53
9
54
0
54
1
54
2
54
3
54
4
54
5
54
6
54
7
54
8
54
9
55
0
55
1
55
2
55
3
55
4
55
5
55
6
55
7
55
8
55
9
56
0
56
1
56
2
Sundhed.dk
https://www.sundhed.dk/
Denmark
Supergros
http://www.supergros.dk/
Denmark
Sure connections
Healthcare
Computers:
Software
United Kingdom
SVT
Sweden ScienceNet
http://svt.se/
Sweden
News, Media
http://www.sciencenet.se/
Sweden
Swisscom
http://en.swisscom.ch
Switzerland
Research
Telecommunications
Sydbank
Syddansk Universitet
Syddanske Medier
Sygehus Lillebælt
http://sydbank.com/
Denmark
http://www.sdu.dk/
Denmark
Banking
Educational
Services
http://www.sdm.dk/
Denmark
News, Media
http://www.sygehuslillebaelt.dk/wm223295
Denmark
Systematic
http://www.systematic.com/
Denmark
Healthcare
Computers:
Software
Systime
http://www.systime.net/
Denmark
T-Online
Tampere University of Applied
Sciences
http://www.t-online.de/
Germany
http://www.tamk.fi/media
Finland
Tate Modern
http://www.tate.org.uk/
United Kingdom
TDC Services
Teknisk
Erhvervsskole
Center
Telegraph Media
Group (The)
http://www.tdcservices.co.uk/
United Kingdom
Research
Educational
Services
Building
Industry
http://www.tec.dk/tec/site.aspx?p=23
Denmark
Educational
Services
http://www.telegraph.co.uk/
United Kingdom
Telmore
https://www.telmore.dk/
Denmark
News, Media
Telecommunications
terminalfour
www.terminalfour.com
Ireland
CMS Vendor
TerraMG
textformer mediendesign
http://www.terramg.net/
Germany
http://textformer.de/
http://www.the451group.com/about/bio_detail.p
hp?eid=294
Germany
News, Media
CMS Integrator
USA
News, Media
The 451 Group
The Global Fund
TheMemoryChai
n
time4you.de
TIMETOACT
Software & Con-
http://theglobalfund.org/en/
http://thememorychain.com/
http://www.time4you.de/ibt/site/time4you/ibt/en/
page/home/main.page
United Kingdom
http://www.timetoact.de
Germany
© IKS Consortium
2013
Germany
CMS Vendor
Telecommunications
Healthcare
Computers:
Software
Computers:
Software
CMS Integrator
198 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
sulting GmbH
56
3
56
4
56
5
56
6
56
7
56
8
56
9
57
0
57
1
57
2
57
3
57
4
57
5
57
6
57
7
57
8
57
9
58
0
58
1
58
2
58
3
58
4
58
5
58
6
58
7
58
8
CMS Tool
Provider
TinyMCE
TIWAG-Tiroler
Wasserkraft AG
http://tinymce.moxiecode.com/
TNT
top concepts
Internetmarketing
GmbH
http://www.tnt.com/portal/location/en.html
http://www.topconcepts.de
Germany
CMS Integrator
Topdanmark
Trader Media
Group
Transportministeriet
Transportstyrelsen
http://www2.topdanmark.dk/
Denmark
Insurance
http://www.tradermediagroup.com/
United Kingdom
http://www.trm.dk/da/
Denmark
http://www.transportstyrelsen.se/en/
Denmark
Tre
http://www.tre.se/
Sweden
News, Media
Government
Services
Transportation
Telecommunications
TrioVis GmbH
http://www.triovis.de/
Germany
CMS Vendor
TrygVesta
http://www.tryg.com/en/home/index.html
Denmark
Insurance
TUI Travel plc
http://www.tuitravelplc.com/
Germany
TV2
TXT e-solutions
GmbH
http://tv2.dk/
Denmark
http://www.txtgroup.com/
Germany
http://www.tiwag.at/
Austria
Energy
Transportation
UK - Department of Trade and Industry
UK Cabinet Ofhttp://www.cabinetoffice.gov.uk/
fice
United Kingdom
United Kingdom
Tourism
Broadcasting
& cable
Computers:
Software
CMS-Open
Source
Community
Government
Services
Financial
Services:
Diversified
Government
Services
Government
Services
Government
Services
Umicore
UN International
Strategy for Disaster Reduction
http://www.umicore.de/
Germany
Machinery
Unibet
http://www.unibet.com/start
United Kingdom
Government
Services
Lodging &
Gaming
UNICEF
http://www.unicef.org/
Unilever UK
http://www.unilever.co.uk/
United Nations
http://www.unisdr.org/
Typo3
Tønder Kommune
UBS Financial
Services Inc.
Udenrigsministeriet
Switzerland
http://www.toender.dk/
Denmark
http://www.ubs.com/
Switzerland
http://um.dk/
Denmark
http://www.unisdr.org/
© IKS Consortium
2013
Healthcare
United Kingdom
Agribusiness
Government
Services
199 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
58
9
59
0
59
1
59
2
59
3
Educational
Services
Educational
Services
Educational
Services
Educational
Services
Government
Services
Paper &
Forest Products
Universiteit Gent
Universitetet i
Bergen
University of
Leicester
University Passau
http://www.ugent.be/
Belgium
http://www.uib.no/
Norway
http://www2.le.ac.uk/
United Kingdom
http://www.uni-passau.de/6.html?&L=1
Germany
UNOPS
http://www.unops.org/english/Pages/default.aspx
UPM
Uptime InformationsTechnologie
GmbH
http://www.upm.com/en/Pages/default.aspx
Finland
http://www.uptime.de/
Germany
UST GmbH
http://www.ust-gmbh.de/
Germany
Utdanning.no
http://utdanning.no/
Norway
Computers:
Software
Computers:
Software
Educational
Services
V. Guldmann
http://www.guldmann.com/
Denmark
Healthcare
VAMED
Van der Hoven
Stichting
http://www.vamed.com
http://www.hoevenstichting.nl/client/1/?websitei
d=1&contentid=1
Austria
Healthcare
Denmark
Healthcare
Vattenfall
United Kingdom
Vejdirektoratet
http://www.vattenfall.com/en/index.htm
http://www.vejdirektoratet.dk/vejdirektoratet.asp
?page=company&objno=11
Vejen Kommune
http://www.vejenkom.dk/
Denmark
Vejle Bibliotek
http://vejlebib.dk/
Denmark
Velfac
http://www.velfac.com/
http://www.vemag.de/gestaltung/frame/index.ht
ml
Denmark
Energy
Transportation
Government
Services
Educational
Services
Building
Industry
Germany
Machinery
www.konsument.at
Austria
Versatel
http://www.versatel.de/versatel-ag/
Germany
Consulting
Telecommunications
Vestas
http://www.vestas.com/
Denmark
Energy
Vesterli
http://www.vesterli.com/
61
1
vestjyskBANK
https://www.vestjyskbank.dk/
Denmark
61
2
61
3
via knallgrau
GmbH
Via University
College
www.knallgrau.at
Austria
http://www.viauc.com/Pages/default.aspx
Denmark
Consulting
Financial
Services:
Diversified
Digital Publishing Solutions
Educational
Services
61
Viborg Kom-
http://viborg.dk
Denmark
Government
59
4
59
5
59
6
59
7
59
8
59
9
60
0
60
1
60
2
60
3
60
4
60
5
60
6
60
7
60
8
60
9
61
0
Vemag
Verein für konsumenteninformation
© IKS Consortium
2013
Demark
200 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
4
mune
61
5
61
6
61
7
61
8
61
9
62
0
62
1
62
2
62
3
Videncentret for
Landbrug
62
4
62
5
62
6
62
7
62
8
62
9
Værdipapircentralen
WDPX - Wollweber
63
0
63
1
63
2
63
3
63
4
63
5
63
6
63
7
63
8
63
9
64
0
Services
http://www.vfl.dk/Videncentretforlandbrug.htm
Denmark
Agribusiness
Virgin Atlantic
Virthos Systems
GmbH
http://www.virgin-atlantic.com/en/us/index.jsp
United Kingdom
Aviation
http://www.virthos.net/
Germany
Virtual Creations
VisionConnect
GmbH
http://www.virtualcreations.de
Germany
http://www.visionconnect.de/
Germany
Vizrt
http://www.vizrt.com
Norway
Voest Alpine
http://www.voestalpine.com/group/en
Austria
CMS Vendor
Computers:
Software
CMS Integrator
Media Asset
Management
Building
Industry
VRT
http://www.vrt.be/
Belgium
News, Media
VYRE Software
www.vyre.com
United Kingdom
https://www.vp.dk/
Denmark
http://www.wdpx.de
Germany
We4IT GmbH
http://www.we4it.com/en/
Germany
CMS Vendor
Financial
Services:
Diversified
CMS Integrator
Computers:
Software
Web Arts AG
Web Integrations
Ltd
Webdynamix
GmbH
Weitkämper
Technology
GmbH
www.web-arts.com
Germany
http://www.webintegrations.co.uk/
United Kingdom
http://www.webdynamix.de/
Germany
http://www.weitkamper.de/
Germany
CMS Vendor
CMS Integrator
Computers:
Software
Knowledge
Management
Vendor
Wetpaint
http://www.wetpaint.com/
USA
News, Media
Widex
http://www.widex.dk/
Denmark
Wien IT
http://www.wienit.at/eportal/
Austria
WindowMaster
http://www.windowmaster.com/
United Kingdom
Healthcare
Computers:
Software
Building
Industry
WPG uitgevers
http://www.wpg.be/start/
Belgium
News, Media
WPP
WWCConsulting
GmbH
YGG
Workgroups
http://www.wpp.com/wpp
United Kingdom
Consulting
http://www.wwc-consulting.de/
Germany
www.ygg.de
Germany
YHA UK
http://www.yha.org.uk/
United Kingdom
Yntegral
www.yntegral.com
United Kingdom
© IKS Consortium
2013
CMS Integrator
CMS Integrator
Tourism
Knowledge
Management
Vendor
201 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
64
1
64
2
64
3
Yousee
Århus Købmandsskole
Österreich Werbung
64
4
Österreichisches
Rotes Kreuz
http://yousee.dk/
Denmark
http://www.aabc.dk/
http://www.austriatourism.com/xxl/_site/intde/home.html
Denmark
http://www.roteskreuz.at/home/
Austria
Austria
Digital Publishing Solutions
Educational
Services
Tourism
NonGovernment
Organisation
7.5 No Contact
Name
URL
Country
1
1024cms
http://1024cms.org
Pakistan
2
2S-CMS
http://www.2f-cms.com/
Germany
3
42 Objects
www.42sbs.com
United Kingdom
4
4homepages
http://www.4homepages.de/
Germany
5
60cycle.net
Canada
6
abmedia GmbH
http://60cycle.net/source/60cycleCMS.php
http://www.abmedia-online.de/hameln/cmssocial-media.php
7
Above All
Software
www.aboveallsoftware.com
USA
8
Access Innovations, Inc.
www.dataharmony.com
USA
9
Active Navigation
www.activenavigation.com
USA
10
Activedition
http://www.activedition.com/
United Kingdom
11
www.adaptiveblue.com
USA
12
AdaptiveBlue
add.min Content
Management
http://www.addmin.de/
Germany
13
Adobe Systems,
Inc.
www.adobe.com
USA
14
Aduna
www.aduna-software.com
Netherlands
© IKS Consortium
2013
Germany
Industry
CMS-Open
Source
Community
CMS Vendor
Semantic
Tool Vendor
CMS-Open
Source
Community
CMS-Open
Source
Community
CMS Integrator
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS Tool
Provider
Semantic
Tool Vendor
CMS Integrator
Semantic
Tool Vendor
Semantic
Tool Ven-
202 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
dor
15
Aegir CMS
http://www.midgard-project.org/documentation/aegir/
16
Agent Logic
www.agentlogic.com
USA
17
Agent Software
www.agentsoftware.com
USA
18
Agilense, Inc.
www.agilense.com
USA
19
Agility
http://www.agilitycms.com/home.aspx
USA
20
AKT
www.aktors.org/technologies/3store
United Kingdom
21
Altova, Inc.
www.altova.com
USA
www.amblit.com
USA
http://www.amethon.com/
Australia
23
Amblit Technologies
Amethon Solutions
24
AneCMS
http://anecms.com/
25
Apache Cocoon
http://cocoon.apache.org/
26
Apache
Jackrabbit
http://jackrabbit.apache.org/
27
Apache Slide
28
ApacheAxKit
http://axkit.org/
29
Apelon
www.apelon.com
30
AppRain
[email protected]
31
Articulate Software
www.articulatesoftware.com
22
© IKS Consortium
2013
USA
USA
CMS-Open
Source
Community
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Computers:
Software
CMS-Open
Source
Community
CMS-Open
Source
Community
CMS-Open
Source
Community
CMS-Open
Source
Community
CMS-Open
Source
Community
Semantic
Tool Vendor
CMS-Open
Source
Community
Semantic
Tool Vendor
203 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
32
Artnets
www.artnets.lv
Latvia
33
AskMe
www.askmecorp.com
USA
34
AskMeNow
www.askmenow.com
USA
35
Aspasia
www.aspasia-systems.de
Germany
36
Astoria Software
www.astoriasoftware.com
USA
37
At Home Multimedia
http://www.homemultimedia.at/
Germany
38
AT&T Research
http://public.research.att.com/
USA
39
ATG NA Headquarters
www.atg.com
USA
40
Atlassian
http://www.atlassian.com/
Australia
41
Auto CMS
http://ventics.com/autocms/
42
http://www.automne.ws/
France
43
Automne
Autonomy/Interwoven
http://www.interwoven.com/
United Kingdom
44
AxCMS.net
http://axcms.net/
45
Axontologic
www.axontologic.com
USA
46
BAE Systems
http://www.baesystems.com/
USA
47
BBN Technologies
www.bbn.com
USA
48
BEA Systems
USA
49
bechold.net
www.bea.com
http://bechold.net/contentmanagement/index.html
50
Bigace
http://www.bigace.de/
Germany
51
Biowisdom
www.biowisdom.com
United Kingdom
© IKS Consortium
2013
Germany
CMS Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Movies &
Home
Entertainment
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS Vendor
CMS-Open
Source
Community
CMS-Open
Source
Community
CMS Vendor
CMS Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS Vendor
CMS-Open
Source
Community
Semantic
Tool Ven-
204 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
dor
52
Bitflux
http://bitfluxeditor.org
53
Bitweaver
http://www.bitweaver.org/
54
BloofoxCMS
http://www.bloofox.com/
Germany
55
Blue Oxide
Technologies
www.blueoxide.com
USA
56
blueKiwi
http://www.bluekiwi-software.com/
France
57
Boeing Phantom
Works
www.boeing.com/phantom/
USA
58
Bouvet
www.ontopia.net
Norway
59
BravoSolution
www.bravosolution.com
Italy
60
Bricolage
http://bricolagecms.org/
61
Brightlabs CMS
http://www.brightlabs.com.au/
Australia
62
Brightlemon
http://brightlemon.com/
United Kingdom
63
Business Semantics
www.businesssemantics.com
United Kingdom
64
Cabacos CMS
http://www.cabacos-cms.de/
Germany
65
Callisto
66
Campsite
http://www.sourcefabric.org/
Czech Republic
67
Carsten Euwens
http://www.euwens.de/index/menuid/8
Germany
68
Celcorp
www.celcorp.com
USA
69
CheckMI
www.CHECKMi.com
USA
70
chillyCMS
http://chillycms.bplaced.net/chillyCMS/core/show.site.php
© IKS Consortium
2013
Switzerland
CMS-Open
Source
Community
CMS-Open
Source
Community
CMS-Open
Source
Community
Semantic
Tool Vendor
Computers:
Software
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS-Open
Source
Community
CMS Vendor
CMS Integrator
Semantic
Tool Vendor
CMS Vendor
CMS-Open
Source
Community
CMS-Open
Source
Community
CMS Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS-Open
205 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
71
Cisco Systems,
Inc.
www.cisco.com
72
CitusCMS
http://www.citus-cms.org/
73
ClanSphere
2010
http://www.csphere.eu/
74
Clarabridge
www.clarabridge.com
75
ClearForest
Corp.
www.clearforest.com
USA
76
Clickability
77
ClipBucket
http://www.clipbucket-fr.com/
France
78
CMS Builder
http://www.interactivetools.com/
79
CMS Laurin
http://www.cms-laurin.de/
Germany
80
CMScout
http://www.cmscout.co.za/
South Africa
81
CMSimple
http://www.cmsimple.org/
Denmark
82
CocoBlog
http://cocoblog.sourceforge.net/
83
Cogito
www.cogitoinc.com
USA
84
CognIT a.s
www.cognit.no
Norway
85
Cognition
Technologies
www.cognition.com
USA
86
Cognium Systems SA
www.cogniumsystems.com
France
87
Cohereweb
www.cohereweb.net
United Kingdom
© IKS Consortium
2013
USA
Source
Community
Semantic
Tool Vendor
CMS-Open
Source
Community
CMS-Open
Source
Community
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS Vendor
CMS-Open
Source
Community
CMS Vendor
CMS Vendor
CMS-Open
Source
Community
CMS-Open
Source
Community
CMS-Open
Source
Community
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
206 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
88
Collarity
www.collarity.com
USA
89
Collexis, Inc.
www.collexis.com
USA
90
CommonSpot
http://www.paperthin.com/
USA
91
CompactCMS
http://www.compactcms.nl/
Netherlands
www.compositesw.com
USA
www.ca.com
USA
http://www.ecomas-cms.de/
Germany
94
Composite
Software, Inc.
Computer Associates International, Inc.
conceptcomputer Vertriebsgesellschaft mbH
95
conceptcms
http://www.conceptcms.com/pg/home.html?p
=DE,,,1.6,,,
Germany
96
Concrete5
http://www.concrete5.org/
USA
97
Conet
http://conet.de/
Germany
98
Connotate
www.connotate.com
USA
99
Constructr CMS
http://www.phaziz.com/
100
Contao Open
Source CMS
http://www.contao.org/
Germany
101
Contenido
http://www.contenido.org/
Germany
www.contentanalyst.com
USA
http://www.cm4all.com
Germany
92
93
103
Content Analyst
Company, LLC
Content Management AG
104
Contentteller
http://www.contentteller.com/en/
105
Contextware,
Inc.
www.contextware.com
102
© IKS Consortium
2013
USA
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS Vendor
CMS-Open
Source
Community
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS Vendor
CMS-Open
Source
Community
CMS-Open
Source
Community
Knowledge
Management Vendor
Semantic
Tool Vendor
CMS-Open
Source
Community
CMS-Open
Source
Community
CMS Vendor
Semantic
Tool Vendor
CMS Vendor
CMS Vendor
Semantic
Tool Vendor
207 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
106
Contivo
www.contivo.com
USA
107
Contrexx
http://www.contrexx.com/en/
Switzerland
108
Convera
www.convera.com
USA
109
Copernic, Inc.
www.copernic.com
Canada
110
Correlate
www.correlate,com
USA
111
Cotonti
http://www.cotonti.com/
112
Cougaar Software, Inc.
www.cougaarsotware.com
113
CouroCMS
http://www.courocms.com/
114
Coveo
www.coveo.com
USA
115
CrownPeak
http://www.crownpeak.com
United Kingdom
116
Crystal Semantics
http://www.crystalsemantics.com/
United Kingdom
117
CureHunter
www.curehunter.com
USA
118
Cycorp, Inc.
www.cyc.com
USA
119
Dassault Systemes
www.3ds.com
France
120
DBPrism CMS
http://www.dbprism.com.ar/en/j2-CMS/
Argentina
121
Deepa Mehta
http://www.deepamehta.de/
Germany
122
Design Power
www.dp.com
USA
123
deskmaster
www.deskmaster.com
Norway
124
Det Europæiske
Miljøagentur
http://www.eea.europa.eu/da
Denmark
125
DGI
http://www.dgi.dk/English/relations.aspx
Denmark
© IKS Consortium
2013
USA
Semantic
Tool Vendor
CMS Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS-Open
Source
Community
Semantic
Tool Vendor
CMS Vendor
Semantic
Tool Vendor
CMS Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS-Open
Source
Community
Semantic
Tool Vendor
Semantic
Tool Vendor
Household
Durables
Government Services
Educational Services
208 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
126
127
DiCom Group
plc
www.dicomgroup.com
United Kingdom
www.dharbor.com
USA
www.digitalreasoning.com
USA
128
Digital Harbor
Digital Reasoning Systems,
Inc.
129
Discovery Machine Inc.
www.discoverymachine.com
USA
130
DocuWare
http://www.docuware.com
Germany
131
DotCMS
http://dotcms.com/
132
DotNetNuke
133
DreamFactory
Software, Inc.
www.dreamfactory.com
USA
134
DROW GmbH
http://www.drow.de/drow-gmbh.html
Germany
135
Dubsite
http://www.dubsite.net/
136
e107
http://www.e107.org/news.php
137
EasyAsk
www.EasyAsk.com
138
eazyPortal
http://www.eazyportal.com/
139
Econtent
http://www.econtentmag.com/
140
Editland
http://www.editland.de/
Germany
141
EffectiveSoft
Ltd.
www.intellexer.com
Russia
142
Eikona
http://www.eikona.de
Germany
143
Ektron
www.ektron.com
USA
144
Ekumo
http://www.ekumo.de
Germmany
145
elevateIT
http://www.elevateit.org/
© IKS Consortium
2013
USA
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Media
Asset Management
CMS Vendor
CMS Vendor
Semantic
Tool Vendor
CMS Vendor
CMS-Open
Source
Community
CMS-Open
Source
Community
Semantic
Tool Vendor
CMS-Open
Source
Community
News,
Media
CMS Vendor
Semantic
Tool Vendor
CMS Integrator
Semantic
Tool Vendor
CMS Vendor
CMS-Open
Source
Community
209 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
146
eliteCMS
http://elitecms.net/
147
Elxis 2009
http://www.elxis.org/
148
EMC Corporation
http://software.emc.com/
149
EMC Deutschland GmbH
Germany
150
EMC Documentum
USA
151
Emojo Ltd
www.emojo.com
UK
152
Empolis
www.empolis.com
Germany
153
Enano
http://enanocms.org/index
154
Endeca
http://www.endeca.com
United Kingdom
155
ENDECA
Headquarters
www.endeca.com
USA
156
Engenium
Search
www.engenium.com
USA
157
Enigmatec New
York
www.enigmatic.net
USA
158
Entrieva, Inc.
www.entrieva.com
USA
159
eNvolution
http://www.envolution.com/
160
EOAM CMS
www.epam-cms.com
161
eoCMS
http://eocms.com/
162
Epistemics
www.epistemics.co.uk
© IKS Consortium
2013
USA
Hungary
United Kingdom
CMS-Open
Source
Community
CMS-Open
Source
Community
Semantic
Tool Vendor
Business
Information
Management
Semantic
Tool Vendor
CMS Vendor
Semantic
Tool Vendor
CMS-Open
Source
Community
Business
Information
Management
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS-Open
Source
Community
CMS Vendor
CMS-Open
Source
Community
Semantic
Tool Vendor
210 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
163
Erol
www.erolonline.co.uk
164
http://epp.eurostat.ec.europa.eu/portal/page/portal/eurostat/home/
165
Eurostat
EWERK IT
GmbH
www.ewerk.com
Germany
166
eWorks GbR
http://eworks.de/produkte.html
Germany
167
Expert System
www.expertsystem.it
Italy
168
ExpertMaker
AB
www.expertmaker.com
Sweden
169
eZ Publish
http://ez.no/de/
Germany
170
http://dhost.info/compmaster/
171
F3Site
Fabasoft Distribution GmbH
http://www.fabasoft.com
Austria
172
Factiva
www.factiva.com
USA
173
Fair Isaac Corporation
www.fairisaac.com
USA
174
Family Connections
http://www.familycms.com/index.php
175
FancyCMS
http://fancycms.com/
176
Fast Search &
Transfer
www.fastsearch.com
USA
177
fidion GmbH
http://www.fidion.de/
Germany
178
Foresee International Ltd
www.foresee.be
Belgium
179
Fortent
www.fortent.com
USA
180
FourthCodex
www.fourthcodex.com
USA
181
Franz Inc
http://www.franz.com
USA
© IKS Consortium
2013
United Kingdom
CMS Integrator
Government Services
CMS Integrator
CMS Integrator
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS-Open
Source
Community
CMS-Open
Source
Community
CMS Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS-Open
Source
Community
CMS-Open
Source
Community
Semantic
Tool Vendor
CMS Integrator
Business
Information
Management
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
211 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
182
CMS-Open
Source
Community
http://www.madebyfrog.com/
184
Frog
FUF // Frank
und Freunde
GmbH
Fujitsu Laboratories of America, Inc.
185
Fundanemt
http://www.fundanemt.com/
186
fusionsquare
http://www.fusionsquare.com/
Germany
187
http://www.fuzzylime.co.uk/?r=cms
United Kingdom
188
FuzzyLime
GAX technologies
www.gax.com
Luthuania
189
Gekko Web
Builder
http://www.babygekko.com/site/html/gekko_web_builder/
190
General Dynamics Information
www.gdit.com
USA
191
Generate
www.generateinc.com
USA
192
GeoReference
Online Ltd.
www.georeferenceonline.com
Canada
193
glFusion
http://www.glfusion.org/
194
Global 360, Inc.
www.global360.com
USA
195
Google
www.google.com
USA
196
Groxis, Inc.
www.groxis.com
USA
197
Gruppometa
www.gruppometa.it
Italy
198
GuppY
http://www.freeguppy.org/
199
H5
www.h5technologies.com
183
http://www.fuf.de/
Germany
www.fujitsulabs.com
USA
© IKS Consortium
2013
USA
CMS Integrator
Semantic
Tool Vendor
CMS-Open
Source
Community
CMS Vendor
CMS-Open
Source
Community
Consulting
CMS-Open
Source
Community
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS-Open
Source
Community
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS-Open
Source
Community
Semantic
Tool Vendor
212 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
200
hakia, Inc.
www.hakia.com
USA
201
hanseaticon
http://www.hanseaticon.com/
Germany
202
HBS Consulting
HewlettPackard Company
www.hbsconsult.com
www.hp.com
USA
http://www.hico.at/de/
Austria
205
Hicco
hitcom new
media gmbH
http://www.hitcom.de
Germany
206
html-edit CMS
http://www.html-edit.org/
207
Hyland
http://www.hyland.com/fr
France
208
i2 Inc
www.i2inc.com
USA
209
IAC Search &
Media
http://sp.ask.com/en/docs/about/company_ove
rview.shtml
USA
www.ibm.com
USA
www.icrossing.de
Germany
http://www.ict.ag/
Germany
203
204
212
IBM Corporation
ICrossing
GmbH
ICT Solutions
AG
213
Icy Phoenix
http://www.icyphoenix.com/
214
id praxis
www.idpraxis.de
215
iGaming CMS
http://www.igamingcms.com/
216
ILOG, Inc.
www.ilog.com
USA
217
Image Matters
LLC
www.imagemattersllc.com
USA
218
iMorph, Inc.
www.imorph.com
USA
219
ImpressCMS
http://www.impresscms.org/
210
211
© IKS Consortium
2013
Germany
Semantic
Tool Vendor
CMS Integrator
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS Vendor
CMS Vendor
CMS-Open
Source
Community
CMS Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS Tool
Provider
CMS Integrator
CMS-Open
Source
Community
CMS Vendor
CMS-Open
Source
Community
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS-Open
Source
Community
213 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
220
ImpressPages
http://www.impresspages.org/
221
Infolution bv
www.infolution.com
Netherlands
222
Infopark AG
http://www.infopark.de/
Germany
www.informatica.com
USA
www.infoextract.com
USA
225
Informatica
Corporation
Information
Extraction Systems
Information
Managment
Solutions Consultants
226
223
224
www.imsc.us
USA
InforSense LLC
www.inforsense.com
USA
227
InfoSys
www.infosys.com
USA
228
Ingeniux
http://www.ingeniux.com/
USA
229
Injader
http://www.injader.com/
230
Innodata Isogen,
Inc.
www.innodata-isogen.com
USA
231
Intellesemantic
www.intellisemantic.com
Italy
232
Intellidimension, Inc.
www.intellidimension.com
USA
233
Intelligent Automation, Inc.
www.i-a-i.com
USA
234
Intellisophic,
Inc.
www.intellisophic.com
USA
http://www.interconomy.de/
Germany
www.enomic.com
Germany
www.invention-machine.com
USA
235
236
237
238
239
Interconomy
Intermediate
GmbH & Co.
KG
Invention Machine Corporation
inxire GmbH
Iona Technologies
CMS-Open
Source
Community
Semantic
Tool Vendor
Computers:
Software
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS Vendor
CMS-Open
Source
Community
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Computers:
Software
CMS Vendor
Semantic
Tool Vendor
Germany
www.iona.com
© IKS Consortium
2013
Semantic
Tool Ven-
214 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
dor
240
Iron Mountain
www.ironmountain.com
241
ISAAC
http://www.isaac.nl
Netherlands
242
isens-evolution
www.isens-evolution.com
France
243
ISO International Organization for Standardization
244
iSOCO BARCELONA
www.isoco.com
Spain
245
ISYS Search
Software
www.isysusa.com
USA
246
Janya, Inc.
www.janyainc.com
USA
247
Jarg Corporation
www.jarg.com
USA
248
Jaws
http://www.jaws-project.com/
249
jCore
http://jcore.net/
250
JE CMS
http://joenasejes.cz.cc/
251
Jetspeed
http://portals.apache.org/jetspeed-2/
252
Jive
http://www.jivesoftware.com/
253
jLibrary
http://jlibrary.sourceforge.net/4/usecases.html
254
Joomla
http://www.joomla.org/
255
Joostina CMS
http://joostina.ru/
256
Jpublish
http://code.google.com/p/jpublish/
257
Justsystems
http://na.justsystems.com/index.php
© IKS Consortium
2013
USA
United Kingdom
Semantic
Tool Vendor
CMS Integrator
CMS Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS-Open
Source
Community
CMS-Open
Source
Community
CMS-Open
Source
Community
CMS-Open
Source
Community
Computers:
Software
CMS-Open
Source
Community
CMS-Open
Source
Community
CMS-Open
Source
Community
CMS-Open
Source
Community
Business
Infor-
215 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
258
K2
www.k2.com
USA
259
Kajona
http://www.kajona.de/
Germany
260
Kalido
www.kalido.com
USA
261
Kapow technologies Inc.
www.kapowtech.com
USA
262
Kennen Technologies
www.kennentech.com
USA
263
KickApps
http://www.kitd.com/kickapps/
USA
264
Knewco, Inc.
www.knewco.com
USA
265
www.knova.com
USA
www.kbsi.com
USA
269
Knova Software
Knowledge
Based Systems,
Inc.
Knowledge
Computing
Corporation
Knowledge
Foundations,
Inc.
Knowledge
Systems, Al
Laboratory
270
266
267
268
www.knowledgecc.com
www.knowledgefoundations.com
USA
www.ksl-stanford.edu
USA
Kofax
www.dicomgroup.com
USA
271
Krang
http://www.krangcms.com/
272
Kroll Ontrack
Inc.
www.engenium.com
USA
273
Kryn.cms beta
http://www.kryn.org/
Germany
274
Kyield
Language and
Computing Inc.
http://kyield.com/
USA
www.landcglobal.com
USA
275
© IKS Consortium
2013
mation
Management
Semantic
Tool Vendor
CMS-Open
Source
Community
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Computers:
Software
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS-Open
Source
Community
Semantic
Tool Vendor
CMS-Open
Source
Community
Semantic
Tool Vendor
Semantic
Tool Ven-
216 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
dor
276
Language Computer Corporation
www.languagecomputer.com
277
Lanius CMS
http://www.laniuscms.org/
278
Laserfiche
http://www.laserfiche.com/en-us
279
LEGO Americas
http://mindstorms.lego.com/
280
USA
USA
http://www.letteron.de
Germany
281
Letteron
Level9 Medienproduktion
GmbH
http://www.level9.de/
Germany
282
Leximancer
www.leximancer.com
Australia
283
Lexxe
www.lexxe.com
Australia
284
Liferay
285
286
LightNEasy
LimeSoda Interactive Marketing GmbH
287
Liminal Systems
www.liminalzone.org
288
Linguamatics
Ltd
www.linguamatics.com
United Kingdom
289
LinkSpace
www.linkspace.net
USA
290
Lockhead Martin
www.lmco.com
USA
291
LogicLibrary,
Inc.
www.logiclibrary.com
USA
292
LoveCMS
http://www.lovecms.org/modules/content/index.php?id=1
293
Lucene
294
Lymba Corpora-
USA
http://www.lightneasy.org/
http://www.limesoda.at
www.lymba.com
© IKS Consortium
2013
Austria
USA
Semantic
Tool Vendor
CMS-Open
Source
Community
CMS Vendor
Semantic
Tool Vendor
CMS Vendor
CMS Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS-Open
Source
Community
CMS-Open
Source
Community
CMS Integrator
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS-Open
Source
Community
CMS Tool
Provider
Semantic
217 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
tion
295
Mac's CMS
http://sourceforge.net/projects/macs-framework/
296
Magenta Technology
www.magenta-technology.com
United Kingdom
297
Makna Semantic Wiki
www.apps.ag-nbi.de/makna/
Germany
298
Mambo
http://mambo-developer.org/
299
Mandriva
www.mandriva.com
France
300
Mark Logic
Corporation
www.marklogic.com
USA
301
Mason
http://www.masonhq.com/
302
MatchMine
www.matchmine.com
USA
303
MAXdev
http://www.maxdev.it/
Italy
304
McDonald
Bradley Inc.
www.mcdonaldbradley.com
USA
305
MediaCore
http://getmediacore.com/
306
MemHT
http://www.memht.com/
307
MetaCarta, Inc.
www.metacarta.com
USA
308
MetaIntegration
www.metaintegration.net
USA
309
Metallect
www.metallect.com
USA
310
Metatomix, Inc.
www.metatomix.com
USA
311
Metaview 360
www.metaview360.com
USA
© IKS Consortium
2013
Tool Vendor
CMS-Open
Source
Community
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS-Open
Source
Community
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS-Open
Source
Community
Semantic
Tool Vendor
CMS-Open
Source
Community
Semantic
Tool Vendor
CMS-Open
Source
Community
CMS-Open
Source
Community
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Ven-
218 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
dor
312
Metaweb
http://www.metaweb.com/
313
Metaweb Technologies Inc.
www.metaweb.com
314
MiaCMS
http://miacms.org/
315
Micro CMS
http://www.micro-cms.com/
316
Midgard Lite
317
MigasCMS
http://www.sebrac.altervista.org/
318
Mind-Alliance
Systems, LLC
www.mind-alliance.com
319
Mindful Data
www.mindfuldata.com
320
Mindtouch
USA
USA
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS-Open
Source
Community
CMS-Open
Source
Community
CMS-Open
Source
Community
CMS-Open
Source
Community
Semantic
Tool Vendor
Semantic
Tool Vendor
USA
321
MiniCWB
322
Miosoft
www.miosoft.com
USA
323
MMBase
http://www.mmbase.org/
Netherlands
324
Mobilytics
http://www.mobilytics.net/
USA
325
Modulant
www.pdit.com
USA
326
Modus Operandi, Inc.
www.modusoperandi.com
USA
327
MODx
http://modxcms.com/
328
Molecular
www.molecular.com
329
Mondeca
www.mondeca.com
© IKS Consortium
2013
France
CMS-Open
Source
Community
Semantic
Tool Vendor
CMS-Open
Source
Community
Computers:
Software
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS-Open
Source
Community
Semantic
Tool Vendor
Semantic
219 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
330
Moresophy
gmbh
www.moresophy.com
331
Motorola Labs
www.motorola.com
332
Moveable Type
333
mozilo
Germany
Germany
334
mSpace
335
Multi-Support
Deutschland
GmbH
www.mspace.fm
http://www.multisupport.com/international/about_us/contact/multi
_support_germany/
336
MySource
http://www.mysource.coop/
337
www.metier.com
338
Métier, Ltd.
ncm - net communication
management
gmbh
http://www.ncm.at/
Austria
339
nectil
www.nectil.com
Belgium
340
http://www.nedstat.de
Germany
341
Nedstat
NeoGeo New
Media GmbH
http://www.neogeo.com/
Germany
342
Nervana, Inc.
www.nervana.com
USA
United Kingdom
www.netezza.com
USA
http://www.netfutura.eu
Germany
Germany
USA
344
Netezza Corporation
netfutura GmbH
& Co. KG
345
Netlabs
www.netlabs.org
346
NetMap Analytics Pty Limited
www.netmapanalytics.com
Australia
347
neurokSoft
soft.neurok.com
USA
343
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS-Open
Source
Community
© IKS Consortium
2013
Semantic
Tool Vendor
Knowledge
Management Vendor
CMS-Open
Source
Community
Semantic
Tool Vendor
Digital
Publishing
Solutions
CMS Integrator
Business
Information
Management
CMS Integrator
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS Integrator
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
220 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
348
Newgen Software Technologies
http://www.newgensoft.com/homepage
United Kingdom
349
Nielsen BuzzMetrics USA
www.nielsenbuzzmetrics.com
USA
350
NOEO GmbH
www.noeo.de
Germany
351
Noetix
www.noetix.com
USA
www.nokia.com
Finland
www.northropgrumman.com
http://www.noxum.com/en/products/publishin
g-studio/
USA
354
Nokia Head
Office
Northrop
Grumman Corporation
Noxum Publishing Studio
355
nqcontent
www.nqcontent.com
Cyprus
356
nStein
www.nstein.com
Canada
357
Nukes
http://www.nukes.org/
358
NuTech Solutions
www.nutechsolutions.com
USA
359
O3Spaces
http://www.o3spaces.com/Home
Netherlands
360
ocPortal
http://ocportal.com/start.htm?keep_session=97304311&keep_has_js
=1
361
OmniUpDate
http://omniupdate.com/
362
OneCMS
http://www.onecms.net/
363
Ontology Works
www.ontologyworks.com
USA
364
Ontomantics
www.ontomantics.com
France
365
Ontoprise
GmbH
http://www.ontoprise.com
Germany
366
ontoprise®
GmbH
www.ontoprise.de
Germany
367
Ontos International AG
www.ontos.com
Switzerland
352
353
© IKS Consortium
2013
Germany
USA
CMS Vendor
Semantic
Tool Vendor
CMS Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS Vendor
CMS Vendor
Semantic
Tool Vendor
CMS-Open
Source
Community
Semantic
Tool Vendor
CMS Vendor
CMS-Open
Source
Community
CMS Vendor
CMS-Open
Source
Community
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
221 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
368
OntoSolutions,
Inc.
www.ontosolutions.com
369
Opal
http://www.hulihanapplications.com/projects/opal
370
OpenACS
http://openacs.org/
371
OpenAmplify
Limited
http://www.openamplify.com
372
OpenCMS
http://www.opencms.org/opencms/en/
373
OpenRat
http://www.openrat.de/
374
375
376
377
Oracle Corporation
OrbiTeam
Software GmbH
& Co. KG
OS Reviews
CMS
otris software
AG
PANVISION
GmbH
papaya Software
GmbH
USA
United Kingdom
www.oracle.com
USA
http://www.bscw.de
Germany
http://www.osreviews.net/cms
www.otris.de
Germany
http://www.panvision.de/
Germany
http://www.papaya-cms.com/
Germany
http://www.paperthin.com/
USA
http://www.pc-ware.com/pcw/de/de/main.htm
Germany
382
Paperthin
PC-Ware Information Technologies AG
PC-WARE
Portal Solution
http://portalsolution.pc-ware.de
Germany
383
Phenotype
http://www.phenotype-cms.com/
384
PHP MicroCMS
http://www.apphp.com/php-microcms/index.php
385
PHP-Fusion
http://www.php-fusion.co.uk/news.php
378
379
380
381
© IKS Consortium
2013
Semantic
Tool Vendor
CMS-Open
Source
Community
CMS-Open
Source
Community
Semantic
Tool Vendor
CMS-Open
Source
Community
CMS-Open
Source
Community
Semantic
Tool Vendor
CMS Vendor
CMS-Open
Source
Community
CMS Vendor
Computers:
Software
CMS Vendor
CMS Vendor
Computers:
Software
CMS Vendor
CMS-Open
Source
Community
CMS-Open
Source
Community
CMS-Open
Source
Community
222 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
http://www.polygon3.de/
Germany
CMS-Open
Source
Community
CMS-Open
Source
Community
CMS-Open
Source
Community
CMS-Open
Source
Community
CMS-Open
Source
Community
CMS-Open
Source
Community
Semantic
Tool Vendor
CMS-Open
Source
Community
CMS-Open
Source
Community
CMS-Open
Source
Community
CMS-Open
Source
Community
CMS-Open
Source
Community
CMS-Open
Source
Community
CMS-Open
Source
Community
CMS Vendor
www.polymeta.com
Hungary
Semantic
386
phpCMS
http://www.phpcms.in/
387
PhpMySport
http://phpmysport.sourceforge.net/en/
388
PHPNuke
http://www.phpnuke.org/
389
phpSlash
http://sourceforge.net/projects/phpslash/
390
phpwcms
http://www.phpwcms.de/
Germany
391
phpWebSite
http://phpwebsite.appstate.edu/
USA
392
PhraseTrain
www.phrasetrain.com
USA
393
pimcore
http://www.pimcore.org/
Austria
394
PivotX
http://pivotx.net/
395
Pixie
http://www.getpixie.co.uk/
396
Pligg CMS
http://www.pligg.com/
397
Pluck
http://www.pluck-cms.org
398
PLUME CMS
http://pxsystem.sourceforge.net/
400
Podcast Generator
polygon3 technologies UG
401
Polymeta
399
http://podcastgen.sourceforge.net/
© IKS Consortium
2013
223 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
402
polymita technologies
www.polymita.com
Spain
403
PostCore
http://www.postcore.de/
Germany
404
Postnuke
http://www.postnuke.com/
405
Powerset, Inc.
www.powerset.com
406
pragmaMx
http://www.pragmamx.org/
407
Primitive CMS
http://www.bouzouste.info/
408
www.profium.com
Finland
409
Profium
Progress Softwrae Corporation
www.progress.com
USA
410
Proximic.com
www.proximic.com
USA
411
PTC
www.ptc.com
USA
412
pTools
www.ptools.com
Ireland
413
Quark
http://www.quark.com
Germany
414
Quigo - U.S.
headquarters
www.quigo.com
USA
415
Radar Networks
www.radarnetworks.com
USA
416
Rattle
http://www.rattlecentral.com/
United Kingdom
417
Raytheon Company
www.raytheon.com
USA
418
Readware
www.readware.com
USA
419
Recommind, Inc
www.recommind.com
USA
© IKS Consortium
2013
USA
Tool Vendor
Business
Information
Management
CMS Vendor
CMS-Open
Source
Community
Semantic
Tool Vendor
CMS-Open
Source
Community
CMS-Open
Source
Community
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS Integrator
CMS Tool
Provider
Semantic
Tool Vendor
Semantic
Tool Vendor
Digital
Publishing
Solutions
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
224 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
420
Red Hat
www.redhat.com
421
Redaxscript
http://redaxscript.com/
422
Reddot
http://websolutions.opentext.com/
423
Reenineering
LLC
www.reengineeringllc.com
USA
424
Reinvent Technology
www.reinvent.com
Canada
425
ReOS- Real
Estate Open
Source
http://reos.elazos.com/
426
Revelytix
www.revelytix.com
USA
427
RuleBurst
www.ruleburst.com
USA
428
RunCMS
http://www.runcms.org/
429
SAIC
www.saic.com
USA
430
SaltLux
www.saltlux.com
Korea
431
Sandpiper Software, Inc.
www.sandsoft.com
USA
432
SAP AG
www.sap.com
Germany
433
Saperion
http://www.saperion.com
Germany
434
SAS Institute
Inc.
www.sas.com
USA
435
SchemaLogic
Inc.
www.schemalogic.com
USA
http://www.schwarzmedia.ch
Switzerland
437
Schwarz Media
screenbox multimedia ltd.
http://www.screenbox.net
Switzerland
438
Seagull
http://seagullproject.org/
436
© IKS Consortium
2013
USA
Semantic
Tool Vendor
CMS-Open
Source
Community
CMS Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS-Open
Source
Community
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS-Open
Source
Community
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS Integrator
CMS Vendor
CMS-Open
Source
Community
225 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
440
Semandex Networks, Inc.
Semansys
Technologies
BV
441
Semantic Discovery
www.semanticdiscovery.com
USA
442
Semantic Insights
www.semanticinsights.com
USA
439
www.semandex.com
USA
www.semansys.com
Netherlands
444
Semantic IQ,
Inc.
Semantic
Knowledge ACETIC
445
Semantic Light
www.semanticlight.com
446
Semantic Research Inc.
www.semanticresearch.com
USA
447
Semantic Search
www.semantic-search.com
USA
448
Semantic System AG
www.semanticsystem.com
Switzerland
449
SemanticSolutions LLC
www.semanticsolutions.com
USA
450
Semantra, Inc.
www.semantra.com
USA
451
Semaview
www.semaview.com
452
SemperWiki
http://semperwiki.org/
454
SERENA Software, Inc,
SF Software &
Friends GmbH
www.serena.com
http://www.softwarefriends.de/startseite/index.html
455
Shinobu
http://shinobu.61924.nl/
456
SiberLogic Inc.
www.siberlogic.com
Canada
457
Siderean Software, Inc.
www.siderean.com
USA
443
453
http://semantiq.com//
http://www.semantic-knowledge.com/
© IKS Consortium
2013
France
USA
Germany
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Computers:
Software
CMS-Open
Source
Community
Semantic
Tool Vendor
Semantic
Tool Vendor
226 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
458
Sierra Nevada
Corp
www.sncorp.com
USA
459
SilkRoad Technology
www.silkroadtech.com
USA
460
Silva
http://infrae.com/products/silva
461
SilverStripe
http://www.silverstripe.org/
USA
462
Sinequa
http://www.sinequa.com
France
463
Sirma Group
Corp.
www.ontotext.com
Bulgaria
www.site-box.dk
Denmark
465
site-box
SITEFORUM
GmbH
http://www.siteforum.com/de/
Germany
466
Sitepark GmbH
http://www.sitepark.com/index.php
Germany
467
Slither
468
SmartLogic
Semaphore
www.smartlogic.com
United Kingdom
469
Smartsite
http://smartsiteecm.com
Netherlands
470
sNews
http://www.snewscms.com/
471
Soar Technology, Inc.
www.soartech.com
USA
472
Socialtext
www.socialtext.com
USA
473
www.softwareag.com
Germany
474
Software AG
Solidstate
Group
http://www.solidstategroup.com
United Kingdon
475
Spine
http://spine.sourceforge.net/
464
© IKS Consortium
2013
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS-Open
Source
Community
CMS-Open
Source
Community
Business
Information
Management
Semantic
Tool Vendor
CMS Integrator
CMS Integrator
CMS Integrator
CMS-Open
Source
Community
Semantic
Tool Vendor
CMS Vendor
CMS-Open
Source
Community
Semantic
Tool Vendor
Business
Information
Management
Semantic
Tool Vendor
CMS Vendor
CMS-Open
Source
Community
227 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
476
SpringCM
http://www.springcm.com/
USA
477
SRA International, Inc.
www.sra.com
USA
478
SRI International
www.sri.com
USA
479
sTeam
http://store.steampowered.com/
480
Stellent
www.stellent.de
Germany
481
Sumodesign
http://www.sumodesign.co.uk/home.html
United Kingdom
482
Sun Microsystems, Inc.
www.sun.com
USA
483
SunGard
www3.sungard.com
484
Sybase, United
States HQ
www.sybase.com
485
SyndeoCMS
http://www.syndeocms.org/
486
synkron
www.synkron.com
Denmark
487
Synomos
www.synomos.com
Canada
488
Syntax CMS
http://www.syntaxcms.org/
489
synType CMS
http://syntype.org/
490
SYS Technologies
www.systechnologies.com
USA
491
System One
www.systemone.at
Austria
492
TACIT
www.tacit.com
USA
493
Talis
www.talis.com
United Kingdom
494
TangoCMS
http://tangocms.org/
© IKS Consortium
2013
USA
CMS Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS-Open
Source
Community
CMS Vendor
CMS Integrator
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS-Open
Source
Community
CMS Vendor
Semantic
Tool Vendor
CMS-Open
Source
Community
CMS-Open
Source
Community
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS-Open
Source
Community
228 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
495
Tangora Software A/S
www.tangora.com
496
Target CMS
http://targetcms.com/
497
Taxonomy
Strategies
www.taxonomystrategies.com
498
Tea Trove
http://www.teatrove.com/
499
Telligent Systems
http://telligent.com
United Kingdom
500
Teradata Corporation
www.teradata.com
USA
501
Teragram Corporation
www.teragram.com
USA
502
TextDigger
www.textdigger.com
503
TextPattern
http://textpattern.com/
504
www.textwise.com
USA
505
Textwise
The Brain
Technologies
Corp.
www.thebrain.com
USA
506
The METADATA Company
www.metadata.com
USA
507
Theeta CMS
http://www.mntechsolutions.net/
508
Thetus
www.thetuscorp.com
USA
509
Thinkmap, Inc.
www.thinkmap.com
USA
510
Thomson Corporation
www.thomson.com
USA
511
Thomson Reuters
http://thomsonreuters.com/
USA
512
Thunderstone
www.thunderstone.com
USA
© IKS Consortium
2013
Denmark
USA
CMS Vendor
CMS-Open
Source
Community
Semantic
Tool Vendor
CMS-Open
Source
Community
Business
Information
Management
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS-Open
Source
Community
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
229 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
513
TikiWiki CMS/
Groupware
http://info.tikiwiki.org/tiki-index.php
514
tinfeX CMS
http://www.tinfex.com
515
Tinypug
http://code.google.com/p/tinypug/
516
TomatoCMS
http://tomatogallery.yzx.se/
Sweden
517
Toolpark pc3
http://www.toolpark.com
Switzerland
518
ToQuadrant,
Inc.
www.TopQuadrant.com
519
Totalcom
http://www.totalcom.info
Italy
520
TRIBIQ CMS
http://www.tribiq.com/
United Kingdom
521
Troux Technologies
www.troux.com
USA
www.trueknowledge.com
United Kingdom
http://www.typoheads.at
Austria
Germany
523
True
Knowledge
Typoheads
GmbH
524
Témis Group
www.temis-group.com
France
525
Ultimus
www.ultimus.com
USA
526
www.ultralingua.com
USA
527
Ultralingua, Inc.
unternehmen
online GmbH &
Co. KG
http://www.unternehmenonline.de/de/Technologien.htm
Germany
528
Valuenetics a/s
www.valuenetics.com
Denmark
529
VaselinEngine
http://code.google.com/p/vaselinengine/
530
http://www.vasont.com/
USA
531
Vasont
Versatile Information Systems,
Inc.
www.vistology.com
USA
532
Verticalnet
www.verticalnet.com
USA
522
© IKS Consortium
2013
CMS-Open
Source
Community
CMS Vendor
CMS-Open
Source
Community
CMS-Open
Source
Community
CMS Vendor
Semantic
Tool Vendor
CMS Integrator
CMS-Open
Source
Community
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS Integrator
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS Vendor
CMS Integrator
CMS-Open
Source
Community
CMS Vendor
Semantic
Tool Vendor
Semantic
Tool Ven-
230 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
dor
533
www.vignette.com
USA
534
Vignette
Visible
Measures
http://www.visiblemeasures.com/
USA
535
Vitria
www.vitria.com
USA
536
Vivisimo, Inc.
www.vivisimo.com
USA
537
Vivomind Intelligece
www.vivomind.com
538
w3studiocms
http://www.w3studiocms.com/
539
WAND, Inc.
www.wandinc.com
540
WebDAV
http://www.webdav.org/
541
542
webEditor
WebEngine
Benelux
www.webengine.be
543
Webessence
CMS
http://www.webessence.nl/
544
WebGUI
http://www.webgui.org/
545
WebJaxe
http://media4.obspm.fr/outils/webjaxe/en/
546
WebLayers, Inc.
www.weblayers.com
547
Webmatic
http://www.valarsoft.com/index.php?categoryID=1&subcategoryID
=1&productID=1&action=10
548
Website Baker
http://www.websitebaker2.org/de/home.php?lang=DE
549
webSPELL
http://www.webspell.org/
© IKS Consortium
2013
USA
Netherlands
USA
USA
Semantic
Tool Vendor
News,
Media
Semantic
Tool Vendor
Semantic
Tool Vendor
Semantic
Tool Vendor
CMS-Open
Source
Community
Semantic
Tool Vendor
CMS-Open
Source
Community
CMS-Open
Source
Community
CMS Integrator
CMS-Open
Source
Community
CMS-Open
Source
Community
CMS-Open
Source
Community
Semantic
Tool Vendor
CMS-Open
Source
Community
CMS-Open
Source
Community
CMS-Open
Source
231 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
550
Wedia
www.wedia.fr
France
551
WhiteCrane
http://dev.ameoto.com/whitecrane
Germany
552
Widen
http://www.widen.com/
USA
553
WiredReach
www.wiredreach.com
554
Wolf CMS
http://www.wolfcms.org/
555
Wordmap Inc.
www.wordmap.com
556
WysGui
http://www.wysgui.com/
557
Xaraya
http://www.xaraya.com/
558
XIMS
http://xims.info/
559
XOOPS
http://www.xoops.org/
560
XSB, Inc.
www.xsb.com
561
Yammer
562
Yupi Cms
563
Zeit CMS
564
Zepheira
http://zepheira.com/
565
Zikula
http://zikula.org/
566
Zimplit
http://www.zimplit.com/index.html
USA
USA
USA
http://yupi-cms.com/
© IKS Consortium
2013
USA
Community
CMS Vendor
CMS-Open
Source
Community
DM Vendor
Semantic
Tool Vendor
CMS-Open
Source
Community
Semantic
Tool Vendor
CMS-Open
Source
Community
CMS-Open
Source
Community
CMS-Open
Source
Community
CMS-Open
Source
Community
Semantic
Tool Vendor
Computers:
Software
CMS-Open
Source
Community
CMS-Open
Source
Community
Semantic
Tool Vendor
CMS-Open
Source
Community
CMS-Open
Source
232 / 232
Deliverable 8.7.4 Early-adopters Report 2012 – 13 th February 2013
567
ZoomInfo
www.zoominfo.com
USA
568
ZykeCMS
http://www.zykecms.com/
France
569
ZyLAB North
America LLC
www.zylab.com
USA
© IKS Consortium
2013
Community
Semantic
Tool Vendor
CMS-Open
Source
Community
Semantic
Tool Vendor