the ryan king

The other day I posted a link to hCalendar-creator, javascript program that will help you build hCalendars. I now present to you the hReview-creator.

This page will help you to build the markup for an hReview. The idea is to provide a tool that will help you get the basic markup right. You can then copy and paste the output into your blog or other authoring tool and tweak the markup and layout however you see fit.

As always, let me know [ryan at this domain] if you have any problems or suggestions.

Ericka Menchen says she has a problem with the term folksonomy in
The trouble with folksonomy (the term):

The trouble is that folksonomy is used to describe systems that allow users to tag their own content, and systems that allow users to tag the content of others (i.e. delicious).

I’ve told several people that I think author-tagging and reader-tagging are really two different things. I usually just get blank stares when I say this, so I’m glad someone else agrees with me.

Part of the reason reader-created folksonomies is that the terms used to describe the work are in the vocabulary of the reader, not the writer. Authors could never fully imagine how their readers will view their work. For this reason, reader-created folksonomies have a distinct advantage over author-created folksonomies.

I’d be interested to see if there are different patterns in tagging behavior between author-tagging and reader-tagging. I’d suspect that author-tagging tends to be more conservative, using fewer and more established terms, rather than invented or compound terms.

In response to some bullshit by IBM, Ryan Tomayko says: IBM poop heads say LAMP users need to “grow up”?:

The need for complex systems in the enterprise was and still is greatly overestimated. The trick isn’t to make PHP more complex, it’s to make the enterprise less complex. You need to equate complex requirements with complex systems less and start asking “do we really need this?“? more.

He really has some great points about why middlewhere is not neccessary.

Via Scott Raymond’s delicous links.

Phil Jones has a long piece in response to Danny Ayers‘ (and others‘) rebuttals to critics of the Semantic Web. He says:

This is just one of many examples why, in the final analysis, the W3C’s implementation of the SW smells so bad. And why programmers with a sense of design aesthetics run a mile when they see it. RDF is pitched as some extremely high-level meta-language which can describe almost anything, yet in practice it’s riddled with premature implementation commitments : to web-protocols, to XML standards etc. It’s this mismatch between the claims for generality, and these awkward, intrusive implementation details that looks ugly and is so off-putting.

Its a long piece, but worth the read (or at least a skim).

(Via Danny Ayers.)

You’ve probably heard about Open Search, A9’s format which allows anyone to be a search source for A9.com. Despite the name of the technology, the registry of sources is not open to the public, only to A9. A few of my fellow students have changed this by creating the ChorroSearch Open Search Registry. One of my professors, David Wolber explains:

Chris Fraschetti and Deniz Efendioglu, two students in my Internet Systems Research course, developed this metasearch tool based on A9’s Open Search protocol. It displays results in a column-based manner similar to A9’s client. It also allows information sources to register and immediately have their data searchable to ChorroSearch or any other client that uses ChorroSearch’s open registry (as far as I know, A9 doesn’t provide an open xml-based list of registered opensearch sources). The guys also developed ‘Got Chorro?’ which allows an ordinary user to create a search engine from documents on their desktop, register as an opensearch source, and automatically become a producer of information as well as a consumer (a prosumer).

(Via The Absent-Minded Professor.)