Many-to-Many: The Innovator's Lemma
text: Seyed: Some would say that if you have more than one ordered method (i.e. authoritative classification mechanisms which can conflict, such as Yahoo! Directory vs DMOZ) then you have chaos. I believe that it's this to which Clay is referring.
Jay: Yes, the current structure of folksonomy is only freeform within tightly-defined edges. However, it's worth remembering that the entire existing folksonomy structure is a flimsy web consisting of a handful of implementations (and a fair amount of consensus) on top of the existing structure of the WWW, just like Yahoo!, DMOZ, WebRings and a billion other organisational methods.
One of the beauties of the web is that if one particular style of organisation doesn't suit you, it's very easy to build another. I think this is the main lesson here: not that folksonomies rule (Clay's been consistently saying they don't) but that they're a prime example of the kind of agile, makeshift classification of which we'll be seeing much more.
One View to Rule Them All - The Daily WTF
_ctl0_MainContent__ctl0_PostForm_PostBodyRichText: Marcus:
Okay, you can't modify the app or the DB, but perhaps there's a way of
sticking a proxy in between the two which filters out the offending
query and replaces it with something sane?
I know very little about what you'd use in practice, but a service that
appears as an ODBC source which just passes the data back and forth
with a little filtering code in the middle... I believe there are
various bits of middleware you can buy to do this (it may even be
simple enough to write if you can find some decent ODBC libs) and it
wouldn't invalidate the warranty.
-- Yoz