Skip to content

raindropper

pouring…

Category Archives: RSS

This week, Google introduced OpenSocial API. It is a set of common interfaces for building social applications. Scobleizer’s blog post led me to more information about the OpenSocial API, here:

http://code.google.com/apis/opensocial/

I watched the Campfire One video – almost from beginning to end – and browsed through some Developer’s Guide docs. I appreciate Google’s simple and straightforward, hands-on approach. They have not created a “Meta-Reference Application Framework for Interfaces of Social Network Applications” and dozens of new acronyms. Instead, they show working code and the classic “Hello World!”, written with a vanilla text editor.

Why are Google and other companies allocating resources to social media? The way I see it, that is because their main revenue streams come from advertisers. Social applications are filled with data of people’s activities, interests, daily patterns, schedules, locations, networks etc. This data provides juice for building highly targeted marketing systems, which in turn generate happy advertisers.

The more data people put into the system, the better the system will serve the people. It’s a win-win for us all, don’t you think?

If you’re interested in anything Web 2.0, you should check the videos of the recent Web 2.0 Summit held in California.

Excellent roster. Excellent discussions. Some of the questions just splat on the faces of the interviewees, politely and with a smile, of course. John Battelle’s way of carrying the conversation is particularly good.

[Update 1.11.2007] Excellent? Nah, not all. What’s the reason for not showing the screens of the presenters? It’s not stimulating to watch a talking guy looking down at his laptop, enthusiastically giving a pitch for something that one can not see even a glimpse of.

Sig’s posts on Thingamy and RDF triples inspired me to “put the verb” back to this interlinked mass of documents we call the Web. In a simplified way. 

Here’s the official W3C recommendation and specification of links: 

http://www.w3.org/TR/html401/struct/links.html

If you go through it, you perhaps end up in the same conclusion with me: There’s no simple way to define a semantic relationship between web resources.

I propose that we extend the A HREF tag so that it carries more meaning with it. Let’s borrow the PREDICATE concept from RDF and add that to A HREF tag. 

Here’s an example. On nokia.com, there could be a link like this: 

<A HREF=”www.nseries.com” PRED=”produces, sells, markets”>Nseries</A>

So, what would we achieve with this? It would be a way to provide more precise information, more knowledge for the search engines, etc… We would be closer to the Internet Singularity