** About 250 participants have already registered. Please note that the deadline for early registration will end tomorrow, July 31. **
From September 2 – 4, 2009 I-SEMANTICS brings together LOD aficionados in Graz/Austria. Chris Bizer (FU Berlin) will give an invited talk on “The Emerging Web of Linked Data” and the winners of theTriplification Challenge ‘09 will be honoured.
Submissions to the Triplification Challenge ‘09 are still possible till August 9, 2009. The descriptions should be submitted electronically via email to Michael Hausenblas with the subject Triplification Challenge.
Eric Tsui (The Hong Kong Polytechnic University, China)
Peter Kropsch (Austrian Press Agency, Austria)
Pragmatic Web Track
We are delighted to host the 4th AIS SigPrag International Pragmatic Web Conference Track at I-SEMANTICS. The special track is centered around the study of “pragmatics” in the Semantic Web. It draws attention to how communicative actions with a pragmatic context are performed via Web media and illuminates how mutual understanding and commitments to actions can evolve in conversations. For additional information see http://www.pragmaticweb.info/
International Cooperation Event
Due to the huge success in the last two years the Styrian Economy Funding Agency (SFG) in cooperation with the Enterprise Europe Network (EEN) again decided to organize an International Cooperation Event. You can sign up for the International Cooperation Event free of charge by registering on the official cooperation event website.
I-KNOW ‘09 – International Conference on Knowledge Management and Knowledge Technologies
I-SEMANTICS ‘09 will be held concurrently with I-KNOW ‘09. This special concept aims at bridging the gaps between the various communities and their technology fields. The overall program includes about 90 scientific presentations from all over the world. A German-speaking industry track offers about 30 industry presentations and an exhibition.
We look forward to welcoming you to Graz in September 2009!
Andreas Blumauer from Semantic Web Company (SWC) talked with Jamie Taylor, Minister of Information at Metaweb Technologies Inc. about Freebase & Linked Data and Google´s announcement to use RDFa.
Jamie: Since Freebase is a community writable semantic database, the addition of the RDF interface allows anyone to publish data into the LOD cloud. LOD Applications can access any Freebase Topic through the RDF interface by constructing a URI from the Freebase identifier. But perhaps more importantly, because entities in Freebase can be annotated with multiple identifiers, Freebase Topics can be retrieved by constructed URIs using the identifiers used by other systems and data sets.
For instance, the movie Blade Runner can be referred to as http://rdf.freebase.com/ns/en.blade_runner, but it can also be referenced as http://rdf.freebase.com/ns/authority.netflix.movie.70053131 using the Netflix identifier, http://rdf.freebase.com/ns/authority.imdb.title.tt0083658 using the IMDB identifier, or as http://rdf.freebase.com/ns/wikipedia.en.Dangerous_Days using a Wikipedia wikiword (which in this case is a Wikipedia redirect to the wikiword Blade_Runner).
Freebase also provides a user maintained mapping of how these identifiers can be used to address resources in other LOD systems. The sameas.freebase.com schema can tell an LOD user that the Freebase Blade Runner Topic can also be found in DBpedia using Wikipedia identifiers or how musical artists can be found at the BBC using Musicbrainz identifiers. In fact, the Freebase RDF interface uses the sameas.freebase.com schema to create the owl:sameAs links in the RDF output allowing the user community to expand the interconnections between Freebase and the LOD Cloud. Linked Data providers are also using the strong identifiers in Freebase to identify entities such as companies and locations in their own data sets. When they find an entity that is not represented in Freebase, they simply add the entity to Freebase and use the newly minted Freebase identifier. This permits anyone using their data to understand how their entities relates to any of the more than 5 million things interconnected within Freebase.
The RDF interface can also be used to reference the Freebase type system, giving LOD data set providers vocabularies across a wide range of subject areas. And because anyone can expand Freebase’s data model, data providers can use our schema development tools to build and extend these vocabularies to suite their needs.
Freebase was not designed for ephemeral or fast changing data, like weather conditions or stock ticks. But this type of information is well suited for publication as Linked Data. Freebase entities representing a location or company can be annotated with references to LOD services that provide these types of volatile data. Similarly, Linked Data provides a great way to disseminate very fined grained information that might be associated with a scientific study or financial report. Linked Data provides a seemless transition from Freebase, where a user (or application) can run a query with constraints that run across a wide range of types to find entities of interest along with the LOD services that provide access to temporal or high resolution data not available in Freebase.
We recently demonstrated MQL Extensions which allows the Metaweb Query Language to use data from other systems as a part of the query constraint and result set. While MQL Extensions are user extensible and work with a wide array of systems, this capability makes the connection between Freebase and the LOD Cloud even more transparent.
For example, because US companies that are registered with the SEC are annotated CIK code in Freebase and the sameas.freebase.com schema indicates that the CIK annotation can be used to create a URI that is dereferencable at rdfabout.com, it is possible to write a MQL query that asks who is on the board of financial services companies that trade on NASDAQ and are headquartered in California (and using another MQL Extension, you can ask for their stock price as well!)
SWC: Many organisations are very interested in Linking Open Data now but they are still not sure if they can benefit from publishing data on the web – what´s your experience so far?
Jamie: Linked Open Data provides a simple, standard way for organizations to distribute structured data. For most organizations, providing access to data is another important outlet to announce the availability of higher value services. For organizations involved in building or selling physical goods, the bits representing what they provide are not the goods themselves, but a way of attracting potential customers. Making catalogs and specification sheets available in electronic form, so other applications can connect buyers to their physical goods is simply an effective marketing system. Even for firms involved in electronic services, providing access to open structured data is generally a lead-in to value added services. For instance, if I ran a service collecting hard-to-find information about manufacturing relationships between medium sized businesses, I would publish open company profiles covering things like market size, industry, location for the medium-sized businesses I tracked, so potential users the premium data would know I had the coverage they were looking for.
SWC: Just recently Google has announced to use RDFa to enhance their search results. What do you think?
Jamie: We are excited about Google’s announcement. Yahoo’s use of RDFa for Search Monkey and Google’s announcement gives RDFa users tangible benefits. The Search Monkey team was very quick to realize that because users can create data models in Freebase, and because the elements of those models all have strong RDF identifiers, Freebase provides a large and user extensible vocabulary for RDF/RDFa (see the list of vocabularies). When a user wants to create a Search Monkey application that works with their film review site, they need not invent a new vocabulary (that will probably be used only once), they can use the Freebase Film Domain vocabulary which supports over 63,000 instances in Freebase alone.
Similarly, with over 5 Million well described Topics in Freebase and over 14,000,000 Named Objects (Topics, images, musical tracks and documents) when a user wants to unambiguously identify a subject or object in RDF/RDFa, Freebase has an extremely large collection of identifiers to draw from. These cover people, places, companies, movies, music, books and wide variety of other subjects. If Freebase doesn’t have the entity the user is looking for, they can of course add it themselves and make use of the identifier immediately. I think this is why Google used some Freebase identifiers in their examples. We hope that with Yahoo and Google’s support for RDFa the web will become a strongly annotated source of data which can support a wide range of user applications.
Linked Data is evolving fast. A huge amount of RDF data is available and ready for exciting new applications. Unfortunately, the bottleneck is still the availability of Semantic Web user front-ends which demonstrate the power of linked data. To a certain degree BBC Music beta is the first commercial platform which makes heavy use of linked data. With Parallax David Huynh has shown that one of the most interesting semantic web applications can be built around browse and search applications which offer tools for doing complex search queries.
Andreas Blumauer from Semantic Web Company (SWC) talked with David Huynh, “Interaction Scientist” at Metaweb, the company which developed Freebase, an “open, shared database of the world’s knowledge”.
SWC: David, you have been working for MIT´s Simile Project and now for Metaweb Technologies – two “building blocks” of the Semantic Web. Could you tell us a bit about your ongoing work at Metaweb?
David: My official title at Metaweb is “Interaction Scientist,” and so my main focus is coming up with novel interaction designs for Metaweb’s platform and products, and prototyping them to some extent to evaluate their effectiveness. Parallax was one such prototype that has gathered much excitement within Metaweb and the Semantic Web community at large. And the Freebase query editor 2.0 shows my interaction designs at the other end of the spectrum – targeting developers rather than just end-users.
I’ve also learned that data-centric user interfaces and interaction designs can only be as good as the data allows them to. So I am also dedicating some of my time toward analyzing the data we have and improving its quality so that I can design even better interactions.
SWC: With Parallax you have introduced a new way to search and explore data: Could you explain the “set-based browsing paradigm”?
David: In the browsing paradigm of the original Web, while looking at a web page, you can only click on one hyperlink to get to one other web page. But in a lot of cases, the hyperlinks on that web page can be grouped into different groups based on what they mean to the human reader: these are the links that lead to reviews, these are the links that lead to authors, these are the links that lead to vendors, etc.
Now if the computer actually knows what these links mean, then you can tell it to follow several of those links that mean the same thing: follow all the links that lead to authors. Think of it as powered browsing: the computer does the work of following several similar browsing paths at the same time – going from a set of things (web pages or data entries) to a similarly related set of things – and making all of that information available for your perusal in one shot. It is a paradigm shift compared to how we browse the Web today. And it’s only possible when the computer is capable of telling which link is similar to which other link. And that capability, in turn, will be made possible by the Data Web. (See this unpublished paper which goes into depth about this concept)
SWC: Linked Data is evolving fast. A huge amount of RDF data is available and ready for exciting new applications. Unfortunately, one bottleneck is still the availability of Semantic Web user front-ends which demonstrate the power of linked data. Do you think, that the Semantic Web is rather a server-technology than an end-user experience?
David: I have never thought of the Semantic Web as either a server technology or an end-user experience. I only care about usefulness, and then a matching amount of usability to make that usefulness accessible to people, especially those without Computer Science expertise.
I find that it’s so much easier to explain to people and get them excited about “immediate, personal, local benefits” of a particular technology than about “long-term, communal, global benefits” of a vision. For most people, the former must be experienced and felt often before the latter can appear vaguely appealing enough to call for actions. I’m lazy – I don’t like to spend efforts convincing people of visions; I only want entice people into using the tools that I have created. So if Parallax is considered a success, it is so not just because of its technologies and research contributions, but also because the accompanying screencast explained it in a way that people who cared nothing about the Semantic Web could understand why Parallax would be useful to them. This was achieved by pointing out limitations of existing web technologies as already experienced and understood by a lot of web users, and then illustrating concretely a possible solution enabled by data web technologies.
Perhaps I could venture further and say that the dichotomy of server technologies and end-user experience is what’s holding back Semantic Web user interface efforts. For those who don’t have expertise in design, it is a comfort to think that once the back-end technologies are solid, then it’s just a matter of putting on some polishes, a.k.a. user interfaces from their point of view, to make the whole package appealing. This approach is wrong. The user interface design must inform the back-end design. Otherwise, the user interface will almost always reflect the internal system model, and that’s usually very dissonant with how users think and behave. Recall all the Semantic Web interfaces you have seen that force users to think in terms of triples or of raw URIs. Those were made by starting from the data model, not from user needs.
SWC: Quite often I hear people saying: Where is the Semantic Web? – I still can´t “see” it! How could the linking open data community make use of such user interfaces like Exhibit, Piggy Bank or Parallax? Is the set-based browsing paradigm a universal way to browse linked data or just one possible way?
David: My research prototypes embody a number of UI ideas that are quite transferable to other platforms. Most of my code is open source, too. This, by the way, is rarer than it should be: research prototypes often fall apart as soon as, or even sooner than, the relevant research papers get presented at conferences, and research code rots rather than gets offered free for reuse. This is sad, because reusable data needs reusable code to proliferate even more widely, but there is no reward system for making research code reusable, or for keeping research prototypes running. So perhaps people can’t “see” the Semantic Web because research prototypes are not presented in appealing and comprehensible ways, and they break down and disappear too quickly.
Regarding the set-based browsing paradigm, it is most certainly not the only way to browse linked data. It is just the first good one that came to my mind, around 2005. But it’s not until 2008 that I actually got around to implement it for real. One of the factors so important in its feasibility is the quality of data in Freebase, compared to other data sources that I had access to. Even the simple fact that a lot of Freebase topics have images makes Parallax look a lot more interesting and useful. People like to see pictures rather than raw URIs. And the diversity of types of data helps illustrate the browsing paradigm of Parallax – that ability to shift focus from one set of things to another set of things, even across very seemingly unrelated domains of information, such as from politicians to their celebrity friends in the movie industry. So, perhaps one of the main challenges in adopting Parallax ideas on any arbitrary RDF data set is curating the data sufficiently for the purpose of presenting it. In fact, if you don’t know how some data is to be presented and used, there’s no way for you to determine if that data is of sufficient quality. User needs and interface designs drive back-end implementation and data curation, not the other way around. It’s a simple idea, really, but it can be hard to adopt if one is fixated on data alone.
SWC: Do you plan new versions of Parallax? When will it become part of Freebase or of even more Linked Data Sources?
David: I’ve done a few further experiments with the ideas in Parallax, but they are not ready for public use, yet. Freebase data makes my job much easier by allowing me to focus mostly on interaction designs rather than mostly on data quality, or rather, fighting the lack of data quality, for the purpose of presenting it. So I’ll start with Freebase data and we’ll see where it takes me.
SWC: What else are you working on at the moment?
David: As mentioned briefly earlier, reusable data needs reusable code to proliferate widely. That gives you a hint at an effort that I’m involved with.
The semantic web is suffering of data. Still. To get the network effects we expect to have with the use of the semantic web, there is still the need to open quality content to the semantic web world. One of the fields where such an opening to the RDF-world should happen, is cultural heritage. As works, people, history and references are distributed over various places, archives, libraries and holders of data, a semantic web approach seems to be perfect to resolve a lot of questions in making the world cultural heritage available.
Europeana is such a promising project. Europeana is funded by the European Commission under the eContent+ programme, as part of the i2010 policy. It is a partnership of 100 representatives of heritage and knowledge organisations and IT experts from throughout Europe. In the last two years Europeana’s prototype was done technically and in terms of connecting contents from various European museums, governmental organisations and art foundations. At Europeana two million books, maps, recordings, photographs, archival documents, and paintings can be found. This figure should be raised – with financial support of the European comission – up to 10 million entries until 2010. An effort which will take approximately 350 million euro.
Under the lead of Stefan Gradmann (University of Hamburg) semantic technologies within the framework and also to the outside semantic web are implemented. Even the now running beta version of Europeana focuses on traditional browsing and search algorithms, an additional semantic europeana prototype gives some insights into further developments of Europeana to a well intergrated semantic web service. So, hopefully we can expect a connection of big content networks to the LOD-cloud soon.
Projects like Europeana will go its way to a rich web of data. Hopefully this is not only a development which public institutions follow. Also commercial initiatives dealing with cultural heritage – say Google – should consider a connection of their harvested data into a bigger semantic web.
Today, the 18th WWW conference started in Madrid, Spain. In his opening talk, Tim Berners-Lee outlined the status quo of the current Web and focused on areas for ongoing research.
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.
The yearly organized Linking Open Data Triplification Challenge awards prizes to the most promising triplifications of existing Web applications, Websites and data sets. Chaired by Michael Hausenblas (DERI) and patroned by Tim Berners-Lee the challenge is open to anyone interested in applying Semantic Web and Linked Data technologies. This might include students, developers, researchers, and people from industry. Individual or group submissions are both acceptable.
Recently the SWC took a thorough look at Triplify, a tool for mapping the contents of a relational DB to RDF, in the course of which we could convince ourselves of Triplify’s ease of use and its potent capabilities.
We take this opportunity to given an account of the philosophy behind Triplify, how it is used and also had the chance to interview the creator Sören Auer.
A common objection from critics of the semantic web is that regular users or webmasters won’t go to the trouble of marking up their content or whole web sites with RDF.
While it is obvious that nobody is going to decorate their web pages with hand-carved RDF triples, it is also apparent that a lot of the current web’s pages are generated by transforming information from relational databases to HTML pages, which are perfectly suited for human consumption, but which suffer from a big loss of machine-readable semantics.
As the information in the relational databases is highly structured and contains rich semantics, it is only natural to also use the already existing structured data to generate RDF representations of the same information.
Triplify is all about this approach of bootstrapping data for the semantic web. It does this for web applications which are built on PHP and MySQL.
Triplify consists of a lightweight PHP script and a configuration file. The latter is used to do the mapping of the columns of an application’s relational database to appropriate RDF classes and properties.
In many cases a site administrator who wants to export her site’s content as RDF, only has to save Triplify with a premade configuration file for her site’s application into the right folder, as for many popular applications like Wordpress, Joomla! or phpBB all the work has already been done.
Once installed, Triplify can be used to generate a dump of the site’s complete RDF graph, or to generate Linked Data, as each of the site’s main concepts’ RDF graph is provided under its own URL, e.g. the semantic description of a user with the ID 123 can be accessed under http://yoursite.com/triplify/user/123.
If no configuration for an application exits, it is fairly easy to create one by yourself.
All one has to do is to look at the app’s database schema, find appropriate classes and properties from well known ontologies and create MySQL queries that grab the data from the relational database and map them to RDF classes or properties.
An example for a query that takes the data from a table describing the user of a CMS: "SELECT id, name AS 'foaf:name', url AS 'foaf:homepage', short_description AS 'dc:abstract' FROM user_table",
Triplify’s creator Sören Auer kindly gave us the opportunity for an interview:
Triplify is very easy to configure for web developers. For which scenarios would you recommend to use Triplify, and in which situations other approaches of semantifying your data might be more suitable?
As you already mentioned Triplify was primarily developed for Web applications developed in PHP. These usually have a relatively small and simple set of tables. Triplify creates complete RDF exports, Linked Data or JSON, but does not include SPARQL endpoint functionality. When SPARQL is required you are better off with D2R Server or Virtuosos RDF views.
Triplify creates semantic representations of the data in relational databases. Do you think there would also be benefit in the inverse approach i. e. creating an application that parses triples and writes it to a relational DB according to a mapping file?
In certain scenarios this might make sense, but for the most cases I think the database schema has to be developed separately. Database schemata contain more storage and retrieval oriented information, such as for example about data indexing. Vocabularies and ontologies on the other hand represent information on a conceptually higher level and are more flexible with regard to evolution of the information structures than databases.
Are there plans for further development of Triplify?
Sure. We want to add SPARQL support and possibly port Triplify to other scripting languages such as Ruby and Python.
Thank you Sören, we will stay tuned about the news from your great application and look forward to the Triplification Challenge 2009!
In a recent interview Prof. Chris Bizer from FU Berlin gave some insights into the commercial opportunities of linked data. In the short run he predicts three application areas:
I think we will see a growing number of applications that use data from the public Web as background knowledge to offer better search capabilities and to augment local content with additional content from the Web of Data.
[...]
Beside of the classic search engines, there might also be market opportunities for new search engines that specialize on Linked Data. [...] This will allow them to sell access to cleaned views on the Data Web and to become central components within Linked Data applications.
[...]
Within the corporate market, there is interest in using Linked Data as a lightweight, pay-as-you-go data integration technology.
Additionally Chris comments on the latest developments in the area of triple stores and D2RQ, and the necessity for more privacy awareness and information accountability in an increasingly interlinked world.
Since SWC is involved in a couple of semantic web projects in the media industry, I was watching for the BBC Music relaunch. Now the new platform is online – and from an enduser’s perspective the new system offers comfortable ways to navigate through the world of music: Bands, their members, biographies and outgoing links like to Wikipedia or MySpace are retrieved from MusicBrainz and mashed up with BBC blogs, playlists or reviews.
Matthew Shorter, interactive editor for music at the BBC, told silicon.com:
We’re kind of on a journey of moving from what’s effectively a magazine/print publication-based metaphor around web publishing…to a world where we recognise that that’s not the way that people use the web.
No doubt: Linked Data is a great deal for the end-users but what´s in for the providers, in this case for BBC?
reusing data from MusicBrainz and Wikipedia also provides better value for the licence payer as the BBC isn’t wasting resources reproducing data already in the public domain
from an SEO point of view, once we start generating a lot of meaningful links among our pages, then we’re going to improve the find-ability of our content via web search
by having as open a platform as we can, then our hope at least is that people will pick up that content and do things with it and we’ll benefit from incoming links as a result
This could be summarised as follows (by adding a fourth item):
re-use existing data
increase find-ability
extend your eco-system
understand users’ interests
By saying that linked data can help providers to understand their users in a more profound way which is based on the more granular way how information is offered in the linked data world (paradigm shift: page versus linked data) I´d like to ask a short, value-free question: Which side of the internet will drive the business in the future – the visible web or the deep web? Was linked data designed only for the visible web?
Those kind of applications should not be confused with “semantic web” end-user-applications like Google´s Wonderwheel or INTSPEI´sCloudlet: To add some semantics to existing user-interfaces can be helpful and obviously users are ready for such experiments, but of course this is NOT the innovation which the semantic web will bring but it is a very important step to be taken in parallel with the linked data initiative.
Let´s take a look at Cloudlet: This tool is an easy-to-use free Firefox extension that adds context-sensitive tag clouds to the most popular search engines and helps people more efficiently navigate through their search results. The previous version of Search Cloudlet worked with Google and Yahoo; the new version also works with Twitter. It adds Tag Clouds, Author Clouds, Recipient Clouds and Hashtag Clouds to Twitter search, Twitter user profiles and home pages. See some reviews on this popular tool.
Cloudlet is a child of the Web. INTSPEI has learned all lessons from Web 2.0 especially how to promote ideas using the blogosphere and how to identify market trends as early as possible, and it generates some added value for the users which is obvious. Sure, it doesn´t make use of linked data yet, but as a typical representative of the fast growing “semantic search evolution” it reminds me on Chris Welty´s famous insight: “In the Semantic Web, it is not the Semantic which is new, it is the Web which is new.”
Web 1.0 was the WWW without tons of network effects. Web 2.0 changed that a lot.
Linked Data is not the Semantic Web, it´s the basement for it. From a software developer´s and an IT archictect´s perspective it might seem as those two concepts were the same. But this community represents a very small percentage of all web-users.
So where is the User´s Web in the Linked Data architecture? If you´re looking at TimBL´s Linked Data principles one can clearly see that this is a “Web” for developers.
But things evolve. And some Web companies will jump on the bandwagon and will, for instance, improve their tagclouds, their semantic search, their recommender systems (Twine?) or their similarity search a lot by making use of linked data.
Like semantic search becomes mainstream (or call it “semantic search 2.0″) right now, then (in about three years, I guess) linked data will become part of a lot of mainstream applications. Linked data will generate tons of new network effects, maybe even new business models, it won´t be avant-garde anymore. It will be part of the Semantic Web.
Sweet Tools is a comprehensive collection of tools and applications for the Semantic Web. It is maintained by Mike Bergman with help from the Semantic Web Company. [more]
** About 250 participants have already registered. Please note that the deadline for early registration will end tomorrow, July 31. **
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=46c45d34-6d03-4b52-948a-638c993e5aad)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=06ca3434-b76d-4e36-8038-aacf447428b0)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=1f1b45ea-c2e5-42ca-b3da-842db7045c32)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=a57a19ba-ec60-4799-879c-58f927479170)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=0c8afbaf-2b14-4307-9a08-5990dbef9013)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=f64bbf00-499f-46b7-be3f-2bb13b58147c)
While some people work heavily on the extension of the semantic web infrastructure, like 
