IKS Public Report 2010 - CORDIS
THE SEMANTICCMS COMMUNITYIKS Public Report 20102009201020112012IKS - Interactive Knowledge Stack is an IntegratingRTD Project part-funded by the EuropeanCommission to provide an open source technologyplatform for semantically enhanced contentmanagement systems.“In only two years, the Interactive Knowledge Stack (IKS) project hasreleased its first working demo of a semantic knowledge engine and ismaking quite a stir, as early adopters begin integrating it into their contentmanagement software. Recent events have also seen part of the resultsacceptance as an Apache incubator project named Stanbol”CMSWire Nov 30, 2010www.iks-project.euCo-funded by the European UnionPage 1 of 16
Summary 2010From Requirements to Validation2010 was the second of four years for IKS and saw four important transitions: fromrequirements to early prototypes; from the prototypes to the design of the ReferenceArchitecture; from the architecture to the first implementation of the interactive knowledgestack, and finally to the early adoption of the IKS software through external CMS companies.In the first half of 2010, the extensive requirements capture process of the first year came to itsclose and designs for the IKS Reference Architecture as well as the first prototypes of IKSComponents emerged. After a successful project review in April, we increased disseminationactivities with an early adopters workshop in Salzburg, demonstrating the first of the IKScomponents to external CMS companies.During the summer the first prototype of the IKS, known as the “Alpha Stack” was furtherdeveloped and soon after that, the first batch of external early adopters began to use themodules and reported their experiences. The development process was kick-started in early2010 when DAY Software and NUXEO led a workshop in which an initial framework based onOSGi and RESTful services was created. This initial prototype focused on semanticenhancements for non-semantic content and called FISE (the Furtwangen IKS Semanticenhancement Engine). The FISE components of IKS focused on the aspect of semantic liftingwhich is clearly an important issue for CMS providers at present. It means adding functionalitythat will enable CMSs to add machine-readable meta-information (aka “knowledge” aka“semantic annotations”) to their primary content. This work was complemented by developmentwork on the knowledge management layer of IKS and, later in the year, work on the userinteraction components joined forces with a commercial development for a “semantic editor”.This is an important aspect of the community-building strength of IKSwhere we can report three successes in addition to the technicalwork: successful inclusion of an external development for an RDFbased CMS storage system called “Clerezza” - this group decided towork with IKS and became an Apache Incubator project in early2010; successful collaboration of IKS with a small company that hadstarted significant work on developing an HTML5 based semanticeditor called “Aloha”; and finally, at the end of 2010, the incubation ofthe IKS Alpha Stack itself, under the code name “Stanbol”. Thismeans that at the halfway stage, IKS has moved from idea tosustainable code base, which was the declared objective in theinterest of bringing semantics to CMS technology.Wernher BehrendtIKS Principal Investigator/Project ManagerPage 2 of 16
Table of ContentsSummary 2010 ------------------------------------- 2Important Areas of Work --------------------------- 4IKS Community “Hands on Workshops” ------------------------ 4IKS Early Adopters Coming on-board --------------------------- 7Semantic CMS Requirements ----------------------------------- 8IKS Semantic Stack Architecture ------------------------------ 10IKS Semantic Stack Components ------------------------------ 11Apache Standbol ------------------------------------ ---------- 12Future Work -------------------------------------- 13IKS Facts ------------------------------------------ 14Page 3 of 16
Important Areas of WorkIKS Community “Hands on WorkshopsThe IKS Community Workshops is anopen forum for principal developersfrom respective communities to join thedialogue and development process in IKS.In detail, the workshops are held every sixmonths to bring together CMS industryrepresentatives and experts to learn aboutand test the latest IKS results.potential early adopters, representing CMSproviders, integrators and tool providers, toinstall and experiment with, the first IKSstack component calledthe FISE engine, andcontribute to the IKSThe goals of the workshops are to raiseawareness within communities forinteroperability of semantic CMS stack,gather requirements, and support existingnetworks of open source semantic webcommunities.There are three major developmentcommunities that are addressed: The IKS RTD Team including the coreindustrial partners The "early adopter" CMS firms andtheir developers The wider open source communitieswhich will be connected with IKSrelated developments3rd IKS Workshop: IKS Early Adopters22-23 June 2010 Salzburg Austria,In 2010 the IKS Early Adopters workshopheld on 22-23 June 2010 in SalzburgAustria, launched the IKS Early Adoptersprogramme. In attendance were 25developmentroadmap. Theresult of theworkshop was thesignup of 9 CMS vendors and integrators asearly adopters. They are: QuinScape GmbH,Page 4 of 16
Important Areas of WorkIKS Community “Hands on WorkshopsGentics, Goss Interactive, Klein & Co, ZaiziLtd, SourceSense, Punkt.netservices, evo42communications, and SalsaDev. In the followup workshop most of the early adopterswere able to demonstrate their validationresults.4th IKS Workshop : "Unleashing thePower of Semantic Data - Today". 9-10December 2010, Amsterdam, TheNetherlandsThe IKS demonstrations were a mix of readyto install IKS software and moreexperimental advanced semanticapplications that show how your system canbenefit from more intelligent extraction andlinking of content services. The workshopalso provided the platform for thedemonstration of the experience and resultsfrom the first round of early adoptervalidation of IKS technology, in this case thecomponent FISE.IKS Components demonstrated:The 4th IKS Early Adopters Workshop washeld in Amsterdam at the Felix MeritisCenter (9-10 December, 2010) and wasattended by 40 participants from the CMSindustry and beyond. In this workshop wedemonstrated the value of using IKSsemantic enhancement tools in today'sContent Management Systems. Use of FISE semantic enhancementengine by Nuxeo DM within a newsdomain setting. Semantic Interaction Framework how user interactions and annotationscould be supported by semantictechnologies with the help of the AlohaHTML5 editor. How the component RICK can beapplied as an enterprise entitiy hub forreferencing, mapping and localcaching of linked data. Use of KReS FISE with Google richsnippets for better findability andsearch engine optimization of content.IKS early adopters demonstrated workingwith the IKS FISE component: Tommaso Teofili from Sourcesensepresented a plugin in Confluence,Page 5 of 16
Important Areas of WorkIKS Community “Hands on Workshopswhich they will make available as opensource. Stefane Gamard from Salsadev (asemantic tool provider) showed theirautomatic categorisation engine viathe FISE infrastructure. Aingaran Pillai from Zaizidemonstrated FISE integration andfuture plans for Alfresco ECM. Andreas Kuckartz from QuinScapepresented the current state of theintegration of FISE in the OpenSAGAWiki extension. It will be made availableunder an Open Source license. Jens Klein from Bluedynamicspresented how FISE is integrated intoPLONE via a python library.The second day was dedicated to hands-onintegration and planning future developmentfor the upcoming IKS components includingenhancement engines as well as thesemantic interaction framework.Page 6 of 16
Important Areas of WorkIKS Early Adopters Coming On-board« In only two years, the Interactive Knowledge Stack (IKS) project has released its firstworking demo of a semantic knowledge engine and is making quite a stir, as early adoptersbegin integrating it into their content management software. Recent events have also seenpart of the results acceptance as an Apache incubator projected named Stanbol »CMSWire Nov 30, 2010An important metric for the success ofIKS is the market validation of IKStechnology. This is performed under theauspices of the IKS Early AdoptersProgramme. But before we put thetechnology into the hands of our earlyadopter our industrial partners Nuxeo,Alkacon Software, TXT Polymedia, Pisano,Day Software and Nemein perform the firstphase of validation. We then invite CMSproviders/suppliers as early adopters toprovide the second phase of marketvalidation. The goal is to have 40 externalCMS providers/suppliers to validate the IKSStack by the end of 2012.The IKS Early Adoptersprogramme was launched in2010. In the first year 20 CMSproviders/suppliers signed upor are in the process offinalising their validationproposal. From this group 5were invited to present theirresults at the IKS Amsterdamworkshop in December 2010.First wave of early adotpers1.2.3.4.5.QuinScape GmbHGenticsGoss InteractiveKlein & CoZaizi Ltd6. SourceSense7. Punkt.netservices8. evo42 communications9. SalsaDev10. Jadu11. Jahia12. PAUX Technologies13. eZ Systems14. Sitecore15. OneHippo16. Ximdex17. Beorn Technologies18. Acuity Unlimited19. Quadra20. WYMeditorIKS in theSpotlightIKS is attracting a lotof attention in theCMS space.Subscribe to IKS News Feedwww.delicious.com/tag/ikspress-coveragePage 7 of 16
Important Areas of WorkSemantic CMS Requirements - and What the User Should Get« Be a Pal, Help IKS Bring Semantic Technologies to CMS Attention all CMS vendors, IKS(news, site) is inviting you to take part in a survey for evaluating their product's coverageof features, particularly with respect to semantic capabilities »CMSWire Jul 16, 2010Gathering requirements is still a difficultexercise, for any software developmentand the process of gathering requirementsfor large-scale technical innovations issubject to continuing debate – here is whatIKS did: we approached requirements fromthe perspectives of different stakeholders:the CMS vendors and developers, CMScustomers, researchers’ beliefs aboutfuture needs for “semantic CMS”, and actualuse cases ranging from well-understooddomains such as travel portals to complexdomains such as “Ambient Content in theHome of Tomorrow”. Managing the resultinglarge set of requirements was difficult, butwe were able to firstly, group them fromhigh-level to low-level for each of the layers ofthe Stack, and then created a mappingbetween the high-level requirements and theReference Architecture. In order tocommunicate the major objectives, wedeveloped the following conceptualframework: We declared the Alpha Versionas the “Developer’s IKS” whereas the BetaVersion should become the “User’s IKS”.In other words, the first prototype of IKSmust enable a developer to add newservices to the system, and to integrate IKScomponents into an existing CMS. Weachieved this by using so-called “RESTful”services and the OSGi standard for softwareintegration – both methods are well-knownand used in commercial softwaredevelopment, but OSGi is rarely used inacademic prototypes, because it requiressignificant software engineering experienceto make good use of it.The Beta prototype will be more ambitiousbecause it needs to demonstrate how thesemantic components actually add value tothe end user’s interaction capabilities withthe CMS. One of our first applications ofBeta-functionality is the project controllinguse case where we demonstrate howinformation from a project management toolgets combined into a web-based, semiautomatic report generator to assist aproject manager in producing a project auditreport. The idea behind the 4-by-4 grid isthat vertically, we map the layers of thesimplified Stack and horizontally, we map acontent usage chain that represents fourdistinct types of usage (1) authoring ofsemantically enriched content; (2) queryingof such semantic content; (3) consuming insome way, the results of a query over thesemantically enriched content, and; (4)giving the end consumer of the content theability to further interact with discreteelements of the retrieved, semantic content.An example of such further interactionwould be if we query for concerts of somefamous pianist in the coming year, consumeas retrieved content the list of concerts andare able to interact with each concert-pageor –site by placing orders for tickets, orbeing able to find information about accessPage 8 of 16
Important Areas of WorkSemantic CMS Requirements - and What the User Should GetFigure 1: The functionality scope of IKS “Beta” over the simplified Stackfor disabled persons, to theconcert venue. By contrast, if the knowledgedomain is project controlling then we mightwant to find all blog entries from staffmembers who were working in the in workpackage “Validation”. Being given thoseentries we may then ask for any Web linksthat were used by the authors of those blogentries. What this should demonstrate isthat semantic technology should enable usto move in a continuum from simpledocument management to highly structuredknowledge domains and we should be ableto interact with the information itemsavailable in these domains, in a natural,common-sense fashion. Semantictechnologies applied to contentmanagement are beginning to deliver goodresults, but the technology still needs tobecome easier to apply for softwaredevelopers and this is were IKS is making itscontribution.Page 9 of 16
Important Areas of WorkIKS Semantic Stack Architecture - The Top-down ViewIKS needs to resolve a tension that oftenin research projects, remainsunresolved or only partially addressed: thereis a high-level conceptual view of what the« Interactive Knowledge Stack » should looksuch a situation because it has set out tolower the barriers for adopting semantictechnologies. At this halfway stage, we wantto show you – the interested reader – howfar we are still removed from that target.The original eight-layerdiagram of the Stackin comparison withLAMP and JEE can befound at http://www.iks-project.eu/iks-story/approachFigure 2: The envisaged Reference Architecture for IKSlike. Then, there is a top-down architecturalview which is more accurate then the highlevel conceptualisation. Thirdly, there are theexisting technology stacks of each CMS thatis interested in re-using some of the IKScomponents. An finally, there are partiallyoverlapping research prototypes for corefunctionalities of the Stack and sincesignificant portions of these have beendeveloped over years, they do notnecessarily fit together as easily as the topdown design would like it. IKS cannot affordThe 4-by-4 matrix ofthe Beta-Version (seefigure above) is anattempt tocommunicate the kindof requirements weneed to fulfil. Thesetwo top-down viewswere translated into alayered software architecture,by University of Paderborn (see below).This layered architecture identifies a minimalset of software components needed tocover the functionality envisaged by IKS.Actual development of IKS software waspartly from scratch, partly ad-hoc and partlyusing pre-existing components that deviatedin part, from the target architecture, as weshall see in the next section.Page 10 of 16
Important Areas of WorkIKS Alpha Semantic Stack Components - the Bottom-up ViewThe major conceptual feature of the IKSStack is its attempt to clearly distinguishbetween interaction at the user level, itsknowledge-based representations in aninferencing layer, the ability to mediatebetween the knowledge base and externalsystems, and the ability to make content,knowledge and user interactions persistent.In order to achieve such a large-scalesystem, research partners were usingexisting components intheir respective areas,as starting points. Ascan be seen below, thecurrent Alpha Stackreflects therefore, thelayering as intended,but its internalstructure still needs refactoring to approachthe target architecture.The knowledgeinteraction componentis called “INTERPRET”. Itis connected viaRESTful services, withthe knowledgerepresentation andreasoning component “KReS” which dealswith ontology and rules management andwhich is able to connect to differentinference engines (“reasoners”). Currentlyshown at the same level of KReS is the IKSSemantic Enhancements Engine “FISE”which kick-started development of the AlphaStack by providing both a framework and aset of relatively easy-to-use components forsemantic lifting. Some of the FISEfunctionality can be seen asimplementations of services foreseen inKReS so the challenge here is how torefactor the two in order to end up with a“lean” reference implementation of thearchitecture. The bottom layer deals withFigure 3: The Architecture of the IKS “Alpha” Stackpersistence for the interactive knowledgestack. One of the concrete developmentshere is an implementation of the CMISinteroperation standard for IKS, dealing –amongst others – with triple stores as wellas relational databases and JCR.Page 11 of 16
Important Areas of WorkApache StanbolIKS has placed much emphasis ondeveloping a good following in relevantcommunities and one of the partners, DAYSoftware, has been very active incontributing to several Apache Open Sourceactivities. Having had favourable responsesto the early “FISE” semantic lifting modulesfrom the CMS community, with strongencouragement from one of the industrialsenior architects and with furtherencouragement from the EC, we decided toapply for Incubation at Apache in November2010 and were granted status as incubatorproject a few weeks later.component for dealing with local caches oflarge, external knowledge spaces. With thisearly move to Apache, we hope to not only,ensure sustainability of the project results,but also to be able to contribute significantlyto the building of a code base whichembraces as many of the advancedconcepts of IKS as possible.The code name of the incubation project is“stanbol” (http://incubator.apache.org/stanbol/) and it comprises the FISEmodules, parts of KReS and a newgoverned by work plans and contracts and adescription of work!The challenge of “going Apache” is of course,the tension between an eco-system(Apache) that is purely governed byindividuals and their willingness tocontribute, and another eco-system (the EUproject IKS with EC funding) that is stronglyPage 12 of 16
Future Work2011 and BeyondThe major development work of 2011 isthe « Beta « version of IKS with its focusshifting from developer-related to useroriented functionality. Also, in 2011 all of theIKS-based use cases need to be finished anddemonstrate how IKS can be used for thebuilding of semantics-based CMSapplications. In the final year (2012) theemphasis will be on demonstrating thebenefits of IKS via external show-cases. Wecan see a number of promising connectionpoints with related developments : several ofthe open source, natural languageprocessing tools could profit from thesimplicity of the FISE-approach thus makingseveral of these tools better used. Anotherpossible development is semanticenhancements to the CMIS standard. Finally,there has been a strong move towardsHTML5 as the WWW implementationlanguage of the future. We are workingtogether with other groups in order tofoster governance and convergence in webbased CMS applications. One such exampleis the « Aloha » Editor to which IKS iscontributing. Finally, there are severalApache projects that are complementary toIKS and we are seeking collaboration withthose. One early collaboration is withanother incubator project called « Clerezza »which is building an access layer to differentRDF triple stores. 2010 was a good year forIKS in terms of community building and forgetting known as a promising project that isaddressing the right questions. 2011 will bea hard year because we will need to showt
Architecture; from the architecture to the first implementation of the interactive knowledge stack, and finally to the early adoption of the IKS software through external CMS companies. . PLONE via a python library. The second day was dedicated to hands-on
We present the Internet Key Service (IKS), a distributed architecture for authenticated distribution of public keys, layered on Secure DNS (DNSSEC). Clients use DNSSEC to securely discover the identities of the relevant IKS servers, and send key lookup or management requests directly to these servers using a special-purpose protocol. Clients au-
T H E N AT I O N A L R E C O R D A L Theme heading insert SYSTEM IKS Policy (2004), National Research and Development Strategy, Ten-Year Innovation Plan (Bioeconomy Strategy), further endorsed by draft IKS Protection, Promotion, Development and Management Bill. The largest South African initiative that record, document, preserve and protect indigenous knowledge for the benefit of the .
a combination. Consultancy services from IKS ensure that the monitoring solution delivered will be the best and most cost-effective for your individual situation. Validation services from IKS mean that it will comply with all the appropriate qu
Surgical technique 4. Multimodal Pain Management 5. Rehab 6. Patient’s role. n 4014. Our experience n 2285 (Min 2 ans de recul) IKS Knee score 100. 16 %. No pain. 48 %. Our experience n 930 (Min 2 ans de recul) IKS Knee score
Dacron (USCI, Division of Bard International) and polyurethane (USCI Division of Bard Inter national and Cordis, Cordis Corporation) catheters are commonly used. Dacron catheters were used until they are technically unsuitable, such as uneven or softened texture, inappropriate configurations, poor torque.
carotid stent [Protege stent (n 9); Covidien, Xact stent (n 7); Abbott vascular and Precise stent (n 5); Cordis] was placed into the ocluded segment. ICA reconstruction was obtained with 5x20 mm balloons (Viatrac 14 Plus; Abbott vascular and Aviator Plus; Cordis) after the stenting. The filter was removed from the
Selective protein sensor based on Surface Plasmon Resonance and Surface Enhanced Raman Spectroscopy Eric Finot Nanomedecine 2010, Beijing- China October 2010 Plasmon nano-optics: towards novel nanotools for biomedicine Romain Quidant Passion for Knowledge, Donostia, Spa in September 2010 The numerical modelling of optical nanostructures
R&D projects, but there are doubts on how many innovations have effectively gone to the market. The mid-term evaluations show outputs and results coming out of collective actions and support to regional filières and clusters. 2011 is the first year with outputs in the field of
