The second post of the Problems of Linked Data series is about the problems regarding the concept of Linked Data:

In the Linked Data context, a node of the Web of data is redirected to the document containing its description. “Data” (or “datum”, if you’re pedantic) as the basic unit of this new Web of data, represents a new paradigm that needs to take over the role that the “document” had before. However, this idea is not fully elaborated, and documents still exist as data containers. In other words, the data structure is “glued” onto the (2D) document instead of being implemented via (3D) HTTP URIs.

Creating the Web of data is a challenge because an RDF graph and the Web graph are two different types of graphs. Arcs (links) in an RDF graph have names, while hyperlinks on the Web have only direction. Another problem is the fact that in an RDF graph, out of three types of nodes only URI references are identified by an URI. How to follow the idea of ​​Web documents and assign each “data” on the Web of data a URI, when blank nodes and literals have no URI? On the Web of documents, every document has a URI, there are no “blank documents” and “literal documents”.

read the whole post >

Stay tuned, more to come soon!


Check out the first post of the Problems of Linked Data series. The subject of the post is the identity of Linked Data:

In mid-2009 Paul Miller asked the question Does Linked Data need RDF?. He stated that the idea that Linked Data can only be Linked Data if expressed in RDF is a dogmatism that makes him „deeply uncomfortable“. A big debate questioning (once basic) assumptions of Linked Data began, and there is still no consensus today.

The problem arose because of the imprecise definition of the Linked Data rules that can be interpreted in different ways. The document that defines Linked Data and its rules is a personal note by Tim Berners-Lee and hasn’t been formally approved by the W3C. Even the term “Linked Data” itself is controversial and contributes to the confusion in the sense that the exact concept of “Linked Data” is conflated with the general idea of linking (any) data. Anyway, the third rule for publishing Linked Data has led to the most confusion and debate:

read the whole post >

Stay tuned, more to come soon!

Check out the new blog post on my new (personal) blog. It’s the first post of the series on the results of my recent research, regarding the realisation of the Web of data/the Semantic Web. The first part is about the problems of the RDF model and the subject of this post are blank nodes:

Nodes without a name represent a special kind of nodes called blank nodes (bNode). These nodes simply indicate the existence of a thing, without using, or saying anything about, the name of that thing. Therefore, they are referred to as existential variables of an RDF graph.

Due to the absence of a name (URI), manipulating data containing blank nodes is much harder – they make otherwise trivial operations far more complex. They complicate the lives of data consumers, especially if data changes in the future. Blank nodes add a lot of complexity to the standards built upon them, and the implementations consuming them. They are poorly understood and difficult for beginners.

read the whole post >

We are moving to the new server on Thursday, starting at 8 am EST. The site will be down for several hours.

We are very sorry for the inconvenience.

Thank you for your understanding,
Faviki team

W3C Semantic Web Activity logoWe are honored to have been invited to write a case study about Faviki and the idea behind semantic tags for the W3C Semantic Web Activity website.

The goal of W3C SW case studies is, primarily, to help the Web community at large understand and appreciate the advantages of possibly using Semantic Web technologies in real applications. It was a challenge to write a document that should convince (often skeptical) IT  managers and other technology people that there can be made some interesting applications based on SW technology.

I tried to show the benefits of  using the semantic tags and described how they are used in Faviki. The key idea of the case study is that the semantic tags, as an intersection point of Web 2.0 and the Semantic Web, have the potential to enable much faster evolution of the Web by providing a solid foundation from which the Semantic Web can grow soundly.

I already wrote on this blog about the need for a tag evolution back in May, so I was happy to present the idea, that has matured in the meantime, to a wider audience.

Many thanks to Ivan Herman for this opportunity and the comments which helped make the entry better.

Also, a big thank you to Maja, Sebastian and Rod for their suggestions.

Reblog this post [with Zemanta]

Today our friends and partners at Zemanta launched a public semantic API, as well as a front side SDK.

Zemanta API analyses unstructured documents/texts and returns five types of content objects:

  • machine readable static tags
  • general categories and custom taxonomies
  • named entities with links to objects from major online knowledge databases: Wikipedia, Amazon, IMDB, RottenTomatoes, CrunchBase,… and to selected pool of online media and blogs
  • pictures from Flickr, CC sources and professional agencies
  • articles from selected media sources and blogs

Zemanta API analyses unstructured documents and returns five types of content objects

This is the first API that returns disambiguated entities linked to DBPedia, Freebase, MusicBrainz, and Semantic Crunchbase. The data can be returned in the standard format of Semantic web – RDF.

There is the extensive developers documentation available, including architecture overview, code samples for most popular programming languages, frontside integration SDK, developers forum and application gallery.

API is free to use for up to 10.000 API calls per month, and for a subscription fee above that.

Zemanta API adds great value to Faviki, by analyzing the text from web pages that are saved by users and suggesting related DBpedia concepts. This makes Faviki users’ lives much easier, because now they can add semantic tags with a just one click.

Zemanta API is a powerful technology that has lots of potential. We can’t recommend it highly enough. Keep up the good work Zemanta 🙂

Reblog this post [with Zemanta]

ReadWriteWeb, a popular blog about web technology, has started publishing its annual list of “10 Semantic Web Apps to Watch” last year. This year, I’m happy to announce that Faviki made it to that list.

As the number of Semantic Web startups rapidly increases, I understand that editors at RWW consider this list to be a prediction of success in this brand new part of the market. I am very pleased that Faviki’s idea of semantic bookmarking quickly caught their eye.

I suggest you check out this list. You will find some very interesting and diverse projects, ranging from semantic search engines to resaurant review web sites.

Reblog this post [with Zemanta]