Venue: Filmmuseum Wien
Date/time: 01.07.2010 / 6pm

More about this event in german and english.

RSVP to

Alex Wilhelm from The Next Web writes:

There is data outside of Facebook that the company wants to be brought in and made relevant inside of the Facebook platform. Enter the Open Graph protocol, Facebook’s way to say, in the common tongue ”all your graph are belong to Zuck.”

The product combines graphs, be they music graphs from Pandora or what have you, into the Facebook wider social graph. You can think of it has a “knit-up” with Facebook for other websites that are not Facebook affiliated.

Nick O’Neill from AllFacebook:

If HTML is the way developers get information into Google’s search engine, meta data is the way developers will get data into Facebook’s semantic search engine which will be based on the company’s “Open Graph”. Through the use of easy to implement plugins, Facebook is rapidly collecting structured data on every user. Facebook has also upgraded their API to make building on top of the Open Graph a much easier process. What’s pretty clear is that it’s an attempt to tackle the residing search giant.

[...] As Mark Zuckerberg said on stage an hour ago, by the end of the day Facebook should have more than 1 billion likes and that data will grow exponentially.

[...] There are a number of standards that have been created in the past as some developers have pointed out, microformats being the most widely accepted version, however the reduction of friction for implementation means that Facebook has a better shot at more quickly collecting the data. The race is on for building the semantic web and now that developers and website owners have the tools to implement this immediately.

Posted by John Klossner on Aug 03, 2009

For those of you, like me, who need a way to keep these things straight, I offer the following handy, wallet-sized program.

WEB 1.0 (browsers) – Users find data
WEB 2.0 (social networks) – Users find each other
WEB 3.0 (semantic Web) – Data find each other

Of course, a lifetime of science-fiction reading and viewing leads me to fear we can look forward to the following developments:

WEB 4.0 – Data create their own Facebook page, restrict friends.
WEB 5.0 – Data decide they can work without humans, create their own language.
WEB 6.0 –Human users realize that they no longer can find data unless invited by data.
WEB 7.0 – Data get cheaper cell phone rates.
WEB 8.0 – Data horde all the good YouTube videos, leaving human users with access to bad ’80′s music videos only.
WEB 9.0 – Data create and maintain own blogs, are more popular than human blogs.
WEB 10.0 – All episodes of Battlestar Gallactica will now be shown from the Cylons’ point of view.

According to Tim Berners-Lee the Web is still static and consists mostly of archived HTML and PDF documents. There is still a need for a read/write Web and the standards are still not used to a sufficient extend. Changes in the Web are the ‘move to mobile’ and the climb up of ‘advertizing to being a science’.

Beside the still existing challenges of the current Web, additional ones arrived. Web Applications as well as Open Social Networking and Open Linked Data count to the area of current interest.

Web Applications are supposed to become new computing platforms and need a serious clean trust system. In the future Web Applications could offer a decentralized modular installation like a webized Debian.

Open Social Networking has become a great application in the Web. Currently it suffers from the ‘Social Silo Problem’. Users have often accounts in several platforms like Facebook or MySpace. The platforms, however, are separated from each other like in a field of silos. The challenge of the Semantic Web Community is now to interconnect the silos via RDF, OWL, HTTP, and SPARQL. A further requirement of Tim Berners-Lee are to focus on a Secure Web id.

Open Linked Data attracted the attention of Tim Berners-Lee most of all. Being one of the chairs of the co-located workshop ‘Linked Data on the Web’ he stressed that “we need data on the Web to work better together” in government, enterprise, and science. Open Linked Data could be a wizard for users of existing relational database systems. As query language he proposed a federated/delegated SPARQL.

Finally, Tim Berners-Lee described the role of researchers in those challenges. Researchers should ‘build a platform for others that follow’. Thereby, one should not assume what people will use the platform for.

(Report by Christoph Wieser / Salzburg Research)

My colleague Tassilo Pellegrini gave some nice examples how some providers like Facebook explicitly state in their privacy policy that they are allowed to hand over all personal data to any other third party (“…our service providers may have access to your personal information for use for a limited time in connection with these business activities”).

It´s a shame that some fundamental rights regarding privacy have dissipated in just a few years.

Also today, I asked Chris Bizer, doubtlessly one of the key-players in the semantic web community, some questions for an interview. Among other things I was also wondering if he thinks that the Semantic Web could solve some privacy issues or if Linked Data will rather become a synonym for “transparent user” (Gläserner Mensch).

One of the many ways that the election of Barack Obama as president has echoed that of John F. Kennedy is his use of a new medium that will forever change politics. For Mr. Kennedy, it was television. For Mr. Obama, it is the Internet. Obama´s Internet Campaign Changed Politics. “Were it not for the Internet, Barack Obama would not be president. Were it not for the Internet, Barack Obama would not have been the nominee,” said Arianna Huffington, editor in chief of The Huffington Post.

America´s new president Barack Obama didn’t go out and recruit on facebook, they came to him at first. Did the internet make Obama’s natural “viralness” quicker and more transparent? Obama’s huge victory on Tuesday night was celebrated in Austria and Germany, as it was around the world: German Press on Obama Victory: “The Dream is Alive“. Der Spiegel‘s Gabor Steingart – who for months dismissed the notion that Obama had a real chance for the White House – writes about the Resurrection of the American Dream: “His base note is conciliatory, his overtone is exalted and the harmony is finely balanced. If anyone out there still doubted that the American dream was alive, he called out to his supporters in Chicago, “tonight is your answer.”

However things will happen or not and however the „Change has come to America“: The president´s new official website is online www.whitehouse.gov. And here users are really being involved. We all are involved. Obama means change. Let´s see in what ways this will concern the future of the internet.

One of Sun’s further assumptions is that users will migrate to KiWi neither immediately nor completely – and that’s an insight anyone developing yet another social platform should take to their heart. What was true in Field of Dreams – “If you build it, they will come” – does not quite apply here. The network effect works in favour of existing communities, and instead of striving to replace an existing platform, one might be better off with mashable contents and services.

The particular benefit of a semantic wiki is that it allows moving from unstructured to structured information (relatively) easily. For KiWi @ Sun (and in favour of mashed information), this means that what is relevant will be structured, both by people and by machines – a process that is going to extend beyond company boundaries. People will bring in structure by creating links from KiWi documents to external systems as well as by writing new facts (which the KiWi system will represent as triples) about external information. What is not relevant, won’t be structured – and will be forgotten. After all, it’s forgetting that makes you remember the important stuff.

One note about the users of KiWi at Sun: Since this use case focuses on knowledge management for software development, it can be taken for granted that users will have an above-average level of web savvyness. Primary users will be software designers (i.e. the people who design for the users of the final product) and developers – learn more about the different roles in a software development project at Sun here.

Consequently, the User Interface (UI) concept Josef introduced also comprises a social networking unit – things such as a ‘My Contacts’, ‘My Pages’ list, but most importantly an activity feed, which will help users to collaborate, participate, discover activities that others are currently working, develop a mental ‘social map’ of the community. Such an activity stream (similar to Facebook’s News Stream) would contain items such as:

• Szaby wrote a blog post
• Josef rated document XUI specs: five stars
• Peter created document ToDoList KiWi-UI
• Stephanie is now a contact of Marek
• Klara shared a document with Sebastian

Considering the target group, it is also planned that the UI will be extensible through widgets that users are able to write themselves.

*coffee break*

Above: The KiWi-Team, hailing (officially) from Austria, the Czech republic, Denmark and Germany

After the break, Andreas Blumauer (Semantic Web Company, Vienna) followed up with a talk entitled “Open Ontology Management & Linked Data” which explored the uses of the Web of Data for the Sun usecase.

His argument was that content and topic-centred, open communities should have mechanisms at their disposal for relating content and activities to particular parts of a shared concept model, e.g. of an ontology. In particular in projects like NetBeans, where contents and related processes evolve over time, different NetBeans groups utilizing the KIWI system should be allowed to maintain and share their own concept models. The combination of bottom-up and top-down approaches would, for instance, come as the combination of free tagging (where people often use different labels to refer to the same, or the same label to refer to different things) and concept tagging.

Free concepts can be turned into controlled ones, too, by being inserted into an existing controlled vocabulary, as either a narrower or related concept of any existing controlled concept. Open Ontology Management done this way is a Learning system: Through the combination of a Free Extraction Model (FEM) and a Controlled Extraction Model (CEM), text extraction improves over time.

Andreas also revealed a first glimpse of a project currently in stealth mode, code name ‘PoolParty’, which is an Open Ontology Management System that can be used to enrich local knowledge with data from the web. PoolParty consumes Linked Data and provides Linked Data; in the context of the current use case, it will be able to communicate with the KiWi System. Please contact Andreas if you would like to be notified about the further development of PoolParty.

Alan Dix is a Professor at the Computing Department of Lancaster University, and author (with Janet Finlay, Gregory Abowd, and Russel Beale) of Human-Computer Interaction.

To start with, Alan pointed to the two sides of achieving the web of data: Firstly generating the web of data (a billion triples, as mighty as this may sound, is actually tiny, says Alan) and then, secondly, accessing the web of data.

With regard to generating the Web of Data, Alan distinguished between top down and bottom up approaches, counting to the former the creation of the web of data from legacy sources (i.e. where you take existing data and semantically lift them, e.g. from structured data) or web scraping such as DBpedia‘s extraction of data from Wikipedia.

N.B.: This notion of ‘top-down’ does not imply a hierarchical relationship, but rather means that there is already a plan for what is going to be put on the web of data (e.g. ‘all semi-structured information on Wikipedia’ or ‘dataset XY from project Z’). The bottom-up idea here implies that data is added as the result of an action, or interaction, as the user/s go, e.g. relationships are created as the user expands his or her social network. For instance on Amazon, user interaction is used to generate semantics: People do not tell Amazon what they like, they simply buy it.

Having relationships of course does not imply yet that these relationships are part of the Semantic Web. Or, as Alan put it, “why should I be RDFizing my online presence if none of my friends are?”

Please take a look at the PDF of the Alan’s slides (2,4 MB) – what I cannot reproduce here is a chart he developed, which was very useful for describing current scenarios on the web and which posed a twofold question:

Does a website/platform have the web of data implemented? YES/NO
Is the web of data on ta website/platform apparent to the user? YES/NO

The possible combinations (YES/YES, YES/NO, NO/YES, NO/NO) provide a good heuristic tool for describing what is currently available, with and without the Semantic Web. Take, for instance, the shiny interface of Talis’ Project Cenote: Cenote’s vision is to “make library data visible in many contexts, inside and outside of the library, making the data much more accessible and visible to a wider audience – benefiting current and potential users of library services wherever they are.” On Cenote, the user doesn’t see that it’s got the Web of Dat in it – it is actually implemented, but not in a way that is apparent to the user.

On the other end of the spectrum, you have a platform like Facebook: Alan referred to Facebook as “the user’s own web of data”, i.e. web of relationships: The user is aware of these relationships (they actually shape his interaction and communication with the site), and the (numerous!) apps on Facebook continually add relationships, but, regrettably, insulated from one another and not using RDF (and don’t you try to take data out of Facebook!).

Two examples of public data that Alan cited and that grow as people/institutions add data do them are Freebase (the “open database of the world’s information” – see previous posts on this blog about Freebase) and Swivel. Swivel allows people, institutions, anyone to upload and explore data, also featuring official data sources such as (links go to their Swivel pages): New York Federal Reserve Bank, UNESCO Institute for Statistics, DukeResearch or EUROSTAT. According to Alan, there is already more data on Swivel now than in the whole Linked Data cloud.

Alan also mentioned the Social Graph API – o yesterday evening Luca Hammer (one of the web 2.0 people who had joined the Open Hacking Session) introduced me to the WordPress Plugin “Meet your commenters” – Meet you commenters uses Social Graph to find social relations on the web, and adds these data to the commenter profiles it creates in WordPress.

Image via WikipediaOn a different note: I took sometime today to explore Alan’s homepage and found the cute Christmas Cracker’s application which was first developed in 1999 and which is now also available on Facebook. As trivial as it may sound at first – sending virtual Christmas Crackers (with more than 5000 possible combinations!) is a good showcase for developing Human Interaction Scenarios, and a number of papers have been written about the application. Here is the casestudy which Alan recommends to begin with: Designing experience – virtual Christmas Crackers.

The abstract and a list of links to all websites and demos Alan discussed can be found here. Full reference: A. Dix and R. Cyganiak (2008). Using the Web of Data. Keynote at WOD-PD 2008 | Web of Data Practitioners Days, Vienna, Austria – Oct 22-23, 2008. http://www.hcibook.com/alan/papers/WOD-PD-2008/

Even if you have not met Richard Cyganiak in person, you have certainly come across one of his creations: The Linked Data Cloud. Richard is a research assistant at DERI Galway. In his demo, he gave us the opportunity to gain hands on experience, introducing a tool he dubbed Snorql, which is basically an easier to use version of a SPARQL-endpoint, as it already has the required prefixes ‘pre-installed’:

Using the Snorql interface, we could explore the dataset we had created collaboratively during Keith Alexander and Yves Raimond’s session. Writing SPARQL queries manually can be a challenge, but is next to impossible if you (like me) don’t know the syntax. But today we could just copy and paste all the queries from a website Richard had put up prior to his session – thanks a lot for the excellent preparation and demonstration!

Richard also showed a couple of RDF browsers in action, e.g. the Tabulator Plugin (“a Firefox extension which allows Firefox to handle data as well as documents”), or the Marbles Linked Data browser which is running right on beckr.org/marbles; enter, for instance http://api.talis.com/stores/wod-pd-sandbox/items/People/JanaHerwig (learn more about Marbles here).

Thank you, Alan and Richard – the combination of talk and demo was indeed a perfect intro towards using the Web of Data.

Related articles by Zemanta

• How will we interact with all this data?
• A New Constellation in the Linking Open Data (LOD) Sky

Q: What could be possible applications for the Semantic Web Community and how could the Linked Data Community benefit from zembly?

A: This is a great question! While social element is very key to us (social platforms provide identity services, social graphs, and distribution channels), zembly is also about building situational apps, which are often based on various data sources. zembly is great in accessing web APIs – it’s just a single JavaScript statement to access many of them.

When you combine aspects of common vocabulary and common access mechanisms of the semantic web on top of it, widgets and services suddenly become even more interoperable. So I think the Linked Data Community will benefit greatly. With zembly, it’s incredibly easy to create and host applications that leverage the data web. And we would like to make it easy to build providers for the data web too. The basic pieces are already in. Now it’s just a matter of putting them together.

Here is link to a service Jiri built for querying dbpedia: The service automatically extracts all of Sean Connery’s film partners and makes the triples available in JSON format (access only after login, so you’d need to get your beta invite first).

Zembly were also a sponsor at Facebook’s F8 conference, here’s a look back on the conference by Jiri on the zembly blog.

Related articles:

The full interview with Ryan Kennedy and Jiri Kopsa on our website
My first blog post about zembly from July 8 with a brief introduction for using it

But if you could write your own Facebook apps, you would avoid all those mistakes, right? Because you would write an application tailored especially to your needs and those of your friends.

If only you could write code…

Worry no longer! It seems as if the “Wiki for Code” has finally arrived with zembly, a web service currently in private beta where users, according to its claim, can “easily create and host social applications of all shapes and sizes, targeting the most popular social platforms on the web.”

Now this may sound too good to be true, yet it is: On the last day of your KiWi-meeting in Prague, I was able to attend a demo session of zembly given by Jiri Kopsa, one of the engineers in the developer organization connected to Sun Microsystems who are currently working on zembly.

No additional software needs to be installed – using just their browser, users can develop applications for several popular social platforms, including Facebook, Meebo, OpenSocial, build apps for their iPhone or other embeddable widgets.

In the demo we were given, Jiri showed us how create a widget that automatically requests the latest Flickr picture. We then deployed the widget on iGoogle as an automatically updating image widget – all that done in considerably less than five minutes.

In technical terms (Jiri clued me up on this), we created a live editable REST service on zembly – no professional coding skills required, you just have to know how to use a mouse. The widget we created calls up the Flickr API in a single JavaScript statement, as Flickr’s API is already integrated in zembly.

The same convenience applies to the development cycle for Facebook applications on zembly – no endless repetitions of editing, FTP uploads, testing, editing, uploading, etc. is required. Just edit the code on zembly and then preview the results on Facebook.

Here are the links to the Picture of the Day service and widget mentioned above (alternatively, search for PictureOfTheDay in zembly after the login)

Putting zembly to the test: When online editors start building widgets

Myself, being at the level of an online editor, technically speaking, I know my fair share of HTML and CSS, but abandoned the idea of entering a career as a developer back in 2001, when I realized that I just cannot even get my head around basic programming tasks such as writing a JavaScript instruction. Nonetheless, I thought I’d give zembly a go and started playing with their beta invitation widget. To do so, I first cloned zembly’s own back-end service to be able to send my own, customized invitation message. Then I cloned the invitation widget itself and began editing.

Zembly offers three types of editing panels: You can edit the (X)HTML, the CSS and JavaScript – I customized the text in the HTML, adjusted the CSS to make the widget fit our browser side bar and blog font, and connected the widget with my service in the Javascript (with the help of the instructions on the zembly blog). Save, preview, done – it was quite a satisfying experience to see the results of my editing generated and displayed on the screen so swiftly. Eventually, I published the whole thing which generated an iFrame that I could easily copy and embed in our blog – you can finf the modified widget (created by myself, the non-coder!) in our right side-bar now. It’s live and working – request your beta invite right away, Jiri put some in my account:-)

Open Content in zembly

Regarding hosting: Applications that are built in zembly are, very conveniently, hosted for free on zembly’s servers – which are, in effect, Sun Microsystems’ servers and which therefore hold the promise of full scalability.

Those who are more immediately interested in applications for the Semantic Web might want to have a look at the service Jiri built for querying dbpedia: The service automatically extracts all of Sean Connery’s film partners and makes the triples available in JSON format. Access it here or search for dbpediaSeanConneryPartners (it’s only accessible after login, so get your beta invite first).

The probably most interesting aspect of zembly seems to me tha you don’t have to start from scratch, if you want to build an app or widget. But there’s more to it than simply cloning widgets: “The whole point of zembly is to reuse and combine not just what other people at zembly create,” they write on their website, “but to rely on the APIs and data from anywhere on the web.”

Some of the web API providers that are currently already integrated into zembly are Amazon webservices, del.icio-ous, Facebook platform, flickr, Google Maps, Yahoo! developer network and YouTube.

What this means in effect is that, for instance, users can use Dapper to create RSS feeds from content they find on a website, and immediately reuse them in a widget they build on zembly and publish it on Facebook. Let the widgeting begin, I say!

And more practically speaking: Zembly is something that we could also use in the KiWi-project, e.g. to enhance our showcases with content widgets or to establish ourselves in Facebook. One of the issues yet to be addressed is, however, whether zembly is going to go open source or not. “It would be nice”, as Jesper Andersen wrote in a guest post on O’Reilly Radar, “to see an open source approach, or a mechanism that would produce a complete runtime for your application that you could run on your own servers.” That would make zembly even more interesting for the IkeWiki-based KiWi. Let’s just wait a little and see – zembly sounds like something definitely worth following up on!

Related articles by Zemanta

• Sun sponsors social apps platform
• Video: Zembly ‘Wikipedia For Social Apps’
• zembly Provides Social Context for Web Development