Comments on: Folksonomizer: generic folksonomy service

By: Jason

Jason — Sat, 26 Aug 2006 12:35:01 +0000

“Any programmers out there with a lack for a pet project?”

…Im building a kind of generic folksonomy API for my organization’s intranet. Something kind of like IBM’s DogEar, but more generic. I’d be interested in collaborating on something public though.

By: How I’m becoming a techie… somewhat » Blog Archive TOAD for MySQL «

Fri, 25 Aug 2006 17:57:59 +0000

[...] … is a fabulous, bestest tool for fiddling around with MySQL. Even better than phpMyAdmin, yes. Been working on it all day, and love it. The make you fill out hajaar nonsense before you’re allowed to download it, and it’s bulit on .NET2.0 (snort), but it runs like a dream. It even has a nice graphical style SQL modeler which makes writing queries SUPER EASY. I’m using it right now to implement folksonomy on a wiki, and this made things much much simpler (along with this, this and this as references, in case you were interested in knowing how to do so). And so many so many so many features. Do ccheck it ou tif you’re n00bing you’re way around MySQL feeling all clueless. [...]

By: blog.forret.com » Blog Archive » Web-based web development

blog.forret.com » Blog Archive » Web-based web development — Wed, 22 Mar 2006 16:21:14 +0000

[...] photo tags/folksonomy: some future version of del.icio.us (see my Folksonomizer post) [...]

By: Jimbo

Jimbo — Sun, 06 Nov 2005 13:53:00 +0000

I`ve become fascinated with this whole culture.Where do you think the future of Folksonomy lies? Please take a look at my site and give critical feedback.
http://www.domeafavorbuddy.com/beta

much appreciated
James

By: leobard

leobard — Mon, 03 Oct 2005 01:15:00 +0000

one step backwards, two forwards:

the rusty old annotea project laid the grounds for adding tags to diverse webpages, including a protocol and user authorisation/identification etc.

Suppose that the protocl of annotea is weird and not as simple as REST, but its a good starter (and has implementations)

http://www.w3.org/2001/Annotea/

By: Gordon Luk

Gordon Luk — Wed, 20 Apr 2005 15:16:00 +0000

Interesting.

You could theoretically use something like Freetag to get started. I released it this past weekend so that it could get used to toss up tagging sytems for projects like Webjay in a matter of hours. It’s more of a basic system right now, but a RESTful API based upon my work for Upcoming.org is in the pipeline, as well as tag namespaces.

It’s geared more towards interoperability of multiple object repositories that run the same backend and communicate over the same framework, though. But I suppose you could implement it on a generalized directory of taggable services, and then use URI’s to manage everything. Or maybe I misunderstand your point?

I’d be happy to help extend Freetag somewhat towards new requirements – take a look at it and let me know if it might be suitable.

By: Pascal Van Hecke

Pascal Van Hecke — Fri, 11 Feb 2005 06:24:00 +0000

Peter and Peter,
I think you are working on the same thing…
http://poorbuthappy.com/ease/archives/2005/02/10/2508/
http://blog.forret.com/blog/2005/02/folksonomizer-generic-folksonomy.html
Pascal Van Hecke

By: Peter

Peter — Mon, 07 Feb 2005 23:11:00 +0000

Yes and no. It might be one way to implement it, but you cannot do public/private tags, plus the authorization for narrow folksonomies becomes tricky.

By: Anonymous

Anonymous — Mon, 07 Feb 2005 08:28:00 +0000

If every URI that belonged to a “service” had a tag associated with it that was the name of that service, wouldn’t that solve the problem?

So, for every URI to an MP3 on webjay (say http://www.grooveattack.com/mp3/non14_01.mp3) it has the tag “webjay” and whatever other descriptive tags (jazz, shank, etc.) you like. A “service” can really just be another tag.