#iks-project

Pretty impressive list of participants. IKS is now on month 18 or 48, and there should already be some things to show to the CMS vendors.

Most LAMP content management systems have grown ad-hoc... you take a Linux server with Apache and MySQL, and then write lots of scripts in PHP or Java to make it run a website. But websites are getting more complicated.

Web content is not static any longer. It is part of some work process and users interact with it. Some of it comes from external sources, and some of it is published to systems outside your own CMS.

Semantic technologies could help with many aspects of that but the tools and conventions are not yet widely known in CMS circles. Can IKS change that?

Some more IKS stuff on Twitter: http://twitter.com/#search?q=%23iks

There has been lots of research in semantic technologies, but almost none of that has actually had an impact on the industry. We need better tools. And yeah, tools that are not in Java :-)

IKS targets both open and closed source CMS vendors. The IKS tools will obviously be open, but licensing will be done so that the closed guys can also use the results. The idea is to increase semantic capabilities of European CMS vendors after all regardless of their licensing model.

The CMS Watch Content Management network map is an interesting, clear presentation of where various systems and vendors sit. But where would IKS be? http://www.cmswatch.com/images/RealStoryGroup-vend...

Google's Rich Snippet testing tool shows what semantic information Google extracts from a web page. Quite a lot of data on my site! http://www.google.com/webmasters/tools/richsnippet...

The event venue is quite fancy: http://www.flickr.com/photos/bergie/4...

@bdelacretaz is talking about what IKS actually provides to CMSs. An example is FISE, an engine that CMSs can hook with to do semantical analysis on their content. You push textual content up, and get RDF triples back.

FISE's ambition is not limited to text analysis, though. There are also plans for picture recognition etc.

See slides: http://www.slideshare.net/bdelacretaz...

FISE already has a bunch of enhancement engines, including Zemanta tagging, language identification (would be useful for #Qaiku !), geolocation tagging, DBpedia entity tagging etc.

Engines will either work with RDF triples or the actual textual content. The engines can be chained up so first you extract entities using NLP, and then enhance the content by finding relations to the entities in the content.

There are packages of FISE available on the IKS wiki so users can play around with the current feature set: http://wiki.iks-project.eu/index.php/FISEgettingSt...

I gave an introduction to the IKS Semantic Editor initiative... building a modern web-based Rich Text Editor that makes inserting semantic content as easy as inserting an image or making text bold.

The basis will be Aloha Editor, an editor that works right in the page DOM instead of hacks involving forms or IFRAMEs.

yenzenz: talk about the new semantic editor: #iks produce it, every #cms vendor can use it. sounds good

michaelmarth: @bergie at #iks: "most CMSs treat HTML content as a black box" < we must change this

michaelmarth: @bergie at #iks: "forms are for governments, not for CMSs" < +1

scroisier: The concept of "web site" is becoming less important than the underlying content and its social propagation #iks

That is it for today. Next we go for a tour of the castle, and later for a dinner.

Going around the workshop participants. Seems most are interested in both FISE and the Semantic Editor. Now we just have to deliver on the expectations

The Turkish IKS team has written a tool that can be used for bridging JCR and CMIS repositories to OWL ontologies. There is then a REST API for accessing the ontologies.

IKS Early Adopters Program: 40 European CMS vendors can join and be sponsored for implementing IKS tools and specifications in their system:

• 2010 is the experimental stage, with FISE being the IKS tool available. 5-7 early adopters sought
• 2011 is still experimental, but with more tools and experience available. 10-12 early adopters
• 2012: the whole IKS stack should be stable and available. 25+ early adopters

Controversial view: "Facebook is a gigantic Content Management System with access control and semantic tagging". But privacy and information access is an issue.

Your data is in somebody else's hands

Access to information is skewed in favor of the service provider. Analyzing their data they can predict who you're going to be friends with, who you're falling in love with, what politicians are up to. And the service monopolizes your relation with your friends. If you change services, all connections with your friends have to be re-established, if you manage to convince them to follow you to another service at all.

This is different from how typical communications networks function. If you have a phone you can call any phone number. If you have email, you can email anybody. On the web you can get your own domain name and publish anything you want.

FOAF Me seeks to provide a service for syndicating profile and friend information so you can maintain your data once and have it available everywhere. But of course the big data silos like Facebook and Google are not interested in this kind of openness. They want to maintain their lock-in on the users.

FOAF+SSL is a secure authentication protocol that provides built-in transferability of your profile and contact lists. It has some advantages over the more widely adopted OpenID.

"CMSs say that they manage content. But usually this is a lie. What they manage is content containers"