December 14th, 2007

It's nice when I can recycle concepts from many years ago for new releases of technology. Take, for instance, my concept of iron clouds and the release of Google's Knols.

An iron cloud is a cloud–a resource accessible by anyone, anywhere–that is seemingly open and accessible but has, as its core, a heart of iron: it's owned by a single entity. It is centralized by a single entity, regardless of its physical distribution. To me, there can be no true cloud when there's ownership.

Udi Manber introduces Knols with the following:

The web contains an enormous amount of information, and Google has helped to make that information more easily accessible by providing pretty good search facilities. But not everything is written nor is everything well organized to make it easily discoverable. There are millions of people who possess useful knowledge that they would love to share, and there are billions of people who can benefit from it. We believe that many do not share that knowledge today simply because it is not easy enough to do that. The challenge posed to us by Larry, Sergey and Eric was to find a way to help people share their knowledge. This is our main goal

We believe that many do not share that knowledge today simply because it is not easy enough to do that. This just isn't true, and a rather backhanded insult to another Google property, Blogger. If a person is comfortable enough with the Net, they have all they need to be able to start contributing to the Net, through Blogger, Typepad, Wordpress.com, and so on. There may be experts who refuse to put their material online until they're paid for it, but then again, we have sites like Huffington Post, which provides both payment and place in which the experts may dabble their little toes.

If this is a snide aside to Wikipedia's reliance on Wiki technology, I don't think any of us has seen that Wikipedia suffers heavily from too many people constrained from contributing. The problems at Wikipedia are based on organization and clannishness, not technology.

In fact, nothing about what Google is saying about Google Knols makes sense, and therefore one has to treat this new 'gift' with suspicion, and indeed, some alarm.

People have been saying that Knols are a way for Google to get back at Wikipedia, but in actuality, they're a way to get back at us. We have dirtied the pristine, perfect field of search, where only the cream floats to the top. We don't use NOFOLLOW on our links, and link indiscriminately, without a care or thought to how the search engine may suffer under our abuse. We toss our own half baked opinions out into the void and are linked, in turn, to further sully search results. Frankly, we're messy, and muck up the algorithms.

The whole point of RDF/OWL, first, and microformats and even HTML5, was so that we all could eventually annotate our material more properly, helping to make a better, more searchable knowledgebase that expands ever outward over time. We are the cloud. However, rather than trust us to form this knowledgebase on our own, Google has now taken matters into its own hands.

I feel like the time when I was a child, and sought to help my grandmother clean up after a holiday meal. I grabbed a dish towel and was reaching for one of the fine china plates, when my grandmother, reacting in horror, snatched it out of my grasp and told me to go play with the other children; before you break something going unspoken, but understood.

Danny Sullivan commenting on Knols, writes the following:

Why do Knol? Google vice president of engineering, Udi Manber, who heads the project, told me that is designed to help people put knowledge on the web that doesn't currently exist, which in turn should make search better, since there will be better information out there.

Of course, Google already offers other content creation tools, such as Blogger and Google Page Creator. In addition, there are non-Google tools people already use to publish content, not to mention collaborative tools such as those I named at the opening of this article. Why yet another tool?

Manber said that Knol has a special focus on authors and a collection of tools that Google thinks is unique, and which in turn should encourage both content creation and readership.

"Knol is all about the authors," he said. "We believe that knowing who wrote a knol will significantly help users make better use of web content."

I can feel the plate being snatched as I read these words.

Leaving aside the worrisome effect of 'knowledge' being centered in and controlled by Google, via its search engine and now Knols, Google is making the same calculated mistake with Knols, as Microsoft does with IE: rather than work with the community, using community tools and specifications, it goes its own proprietary path–using its considerable market presence to ensure it becomes a force regardless of the soundness, or rightness, of its approach.

Google also undercuts the more or less altruistic nature of the knowledge web in the past, with promises of remuneration for those who choose to contribute Knols (and not so coincidentally, profiting Google at the same time). It reminds me of what someone told me a year or so ago: that not having ads in my sidebar makes my site look amateurish. I guess the days when people shared knowledge just to share are over.

update

Best title: Google Runs Out of Content to Monetize; Wants You to Build More.

November 27th, 2007

Anne Van Kesteren:

A new survey reveals that at least Microsoft and IBM think the HTML charter does not cover the canvas element.

I have to wonder, when reading the survey results, how much the people who voted actually used either SVG or the Canvas element. I covered both SVG and the Canvas Element in the book, but I focused more on SVG. Comparing the two–SVG and Canvas–is like comparing the old FONT element with CSS.

The Canvas element requires scripting. The SVG element doesn't, even for animation if you use the animate elements. In addition, mistakes in SVG can be fun, as I found when I missed a parameter value in mistaken animation. A couple lines of markup. No script. Both Opera and Safari do an excellent job with the animation elements. I'm expecting Firefox to join this group in the next year.

If you use scripting, you can access each element in the SVG document as a separate element. You can't do that with Canvas.

I still don't think the Canvas element should be part of a new HTML 5, whatever the grand plans. However, since all but IE supports the Canvas element, it would be foolish to drop it. A better option would be to consider the Canvas element a bitmapped version of SVG and create a separate group to ensure it grows in a standard manner.

I did like what David Dailey wrote in the survey results:

I have considerable ambivalence about <canvas> as I have noted previously. If we were designing HTML 5 from the ground up , SVG and canvas ought to share syntax and ought not to duplicate so much functionality. <canvas> brings a few needed things with it, though it seems rather a bit of poor planning on the part of the advocates of <canvas> that has gotten us to this point. Those historically frustrated with W3C chose to ignore SVG and now seem to want W3C to ignore SVG in favor of a lesser technology. At the same time, <canvas> does enable client-side image analysis by giving the developer access to pixel values, and that alone allows for some tolerance of what otherwise seems to be a curious decoupling of reason from politics. Does it re-invent the wheel? — only about 95% of it is redundant with 20% of SVG.

As for all the discussion about semantic API…years ago I, and others, made a fight for a model and associated XML vocabulary, RDF, we said would stand the test of time and hold up under use. The road's been rough, and few people are going to defend reification, but RDF fuels the only truly open social graph in existence. Five years ago. That was about the time when everyone believed that all we'd need for semantics was RSS. Including Microsoft.