2011-12-27

After seven years

In the spirit of the previous post, some oldies goodies of the first year of this blog.
  • Subject Identity (2004-08-17) on difficulty of subject identification. The reference thread on topic map list is one year older. Just replace "topic map" by "triple store" or "RDF graph", and "topics" by "resources", and see that this critical question is still largely open.
    The core requirement for semantic interoperability of [topic map] applications is interagreement on subject identification mechanisms, enabling both humans and applications to establish when and how different topics, either from the same topic map or different ones, should be interpreted as representing the same subject and processed accordingly.
  • Identification as an experimental protocol (2004-08-29) ... have we made any progress on this topic? Meanwile astronomers still prepare the GAIA mission, due to lift off in 2013.
  • Wikipedia URLs as Subject codes (2005-02-03) ... Jack Park anticipation, two years before DBpedia first release.
    Wikipedia appears popular enough that its URLs might serve at least one important aspect of the subject identity issue ...
     Indeed, more than the volatile and questionable content of DBpedia descriptions, it's the permanence and reliability of DBpedia URIs as subject indicators which makes them a core component of the Semantic Web.

A Web of unfinished weavings

The Web is full of enthusiastic beginnings. Regular and steady follow-up, such as Astronomy Picture of The Day, of which daily archives are available since 1995, are harder to find. The statistics of this blog, and many more of the same, provide typical examples, but unfinished weaving is unfortunately not limited to personal looms, it's also undermining greater collective endeavors. I was looking today at the state of some Wikipedia articles I'd been seriously contributing to, five years ago, such as the one about  SKOS, and figured they need to be seriously updated. But if it's a lot of fun starting a new article, it's quite a boring task to go through it five years after, cleaning and updating it. And since it's a collaborative task, someone else could care after all. Many interpretations have been given to the fact that many people have given up editing Wikipedia, such as growing complexity, bureaucracy, edit wars etc. But people can cope with all this, as long as there is fun, and as long as there is something new every day. Wikipedia is now more than ten years old. It started in the previous century. At Web time scale, it's a very old-fashioned thing.
I see a similar trend undermining the Semantic Web. One could think that vocabularies used by linked data, since more and more people and application rely upon them, would be maintained and curated like precious assets. Actually after a year or so of exploration of this ecosystem, trying to federate the community around its crucial importance, I'm surprised that many of those vocabularies just sit there on a Web shelf, letting to everyone's guess if they're here to stay, if they have been or will be updated, if their publishers have any roadmap for their future evolution, or even if they still remember them.
Weaving the Web? If the weavers seem to be attracted every day by the next trendy loom, and forget to finish what's up on the old ones, the tapestry will always look like an unfinished patchwork. Is this the knowledge we want to build?

2010-11-05

Making Sense of Ambiguity

Paper presented by David Booth at Semantic Technology Conference in San Francisco, 25 June 2010. Just do read it and try to make sense of it. The best analysis of the issue I've read so far.

2010-07-13

Coreference using substitution rules

Note : This is mostly copied/adapted from a message I posted last week in yet another conversation about the identity issue on W3C Library Linked Data Incubator Group internal mailing list.

2010-07-01

What 'mean' means

I've been working for a couple of months now with Gerard de Melo at Lexvo.org. The first objective was to make an example of Linked Data both social and technical good practice. If you have published a set of URIs, and find out afterwards that another set for the same resources has better quality, and moreover you have not the bandwidth or resources to maintain your dataset, what should you do? The example at hand was to redirect the work I've been doing at lingvoj.org towards the data at Lexvo.org which are far more complete, and moreover integrated in a general approach which I found extremely interesting.
The neat result of this work so far is that URIs for languages at lingvoj.org are now redirecting seamlessly to matching lexvo.org URIs, see e.g., http://www.lingvoj.org/lang/fr.

2010-06-17

Looking for the stranger next door

Back in 2002 I was involved in the building of a knowledge model for drug discovery, intended to be used by a knowledge portal of a major pharmaceutical group. Not sure it ever was implemented, but the work was great food for thought. Asking a leading scientist there what were his main functional requirements for a knowledge portal, I was stunned by the obvious simplicity of his answer. In short:
I want the system to stop pushing to me things I already know, such as my own publications, or those of my students and colleagues. What is of interest to me lies just behind this, one click away over the edge of my current knowledge. What I want to be pushed to me by the system should be different enough to question my current knowledge and make it move forward, but close enough to be easily connected to it.
I've met this requirement over and over since, made more or less explicit by all kinds of users. In a nutshell the interesting knowledge is both close to mine and different. It's the stranger living next door. But actually I've not seen yet any application meeting this requirement.
Indeed many applications push stuff based on user profile, social recommendations etc. But most of the time what they push to the user is something (or someone, in the case of social network recommendations) possibly unknown, but close and similar. The basic mechanism is Amazon's "if you like this, you should probably like that", or LinkedIn's "meet a friend of your friends". Very often the recommended stuff or person is not that unknown, and when it is, most of the time it's just adding a layer to your current knowledge or social cocoon. To find out something or someone both new and challenging, the best way is still to-date random browsing and serendipity. That's basically how I found out about PDF 2010 conference, through an excellent report by Marcia Stepanek and Ethan Zuckerman's post about Eli Pariser and Filter Bubbles, both providing excellent background reading for what I'm pushing here.

But how does one spot the stranger next door? Well, she's somehow different. Maybe the emergent social-semantic web tools can help to find out this. Imagine an interface where users would pick data and people making together a comfort zone representative of their current knowledge and network. First the system would check if this choice is globally consistent, and if yes search the edge of this comfort zone by any convenient follow-your-nose algorithms, and discover assertions related to, but not consistent with the user's current view of the world. So instead of like-minded folks and similar readings comforting my knowledge cocoon, I would see popping up on my dashboard "John Bar, which you might know, has a different view about topic Foo. Do you want to discuss this now?", along with a cool visualization based on the inconsistent triples.

Now that would be an exciting way to explore the social-semantic edges, avoiding the pitfalls of both cocooning and random serendipity. Did you say killer app?

2010-04-08

Coreference as a Service

Yahoo! releases Concordance as part of GeoPlanet API. The aim of this service is to provide equivalence between identifiers for geo entities defined in different namespaces. Quoting Gary Gale on Yahoo! Geo Technologies Blog.

We’ve collected these identifiers and namespaces as a single object, a concordance, which empowers a user to reference each source. You can think of it as a mapping of an identifier in a namespace to its equivalent in another namespace. But it’s not a joining of information; we’re only enumerating the identifiers, not the back-end data or attributes that they describe.
The last sentence is important. The service is agnostic on the data model or ontologies used by the various identifiers publishers. Ontological emptiness makes the service useful.

Another striking example is provided by Ellerdale, reconciliating Wikipedia or Freebase topics with Twitter hashtags to build amazing dynamic pages.

Let's guess that many more of the same will emerge in the months to come.