mediaSpace came together today. it's basically a new framework based upon gallerySpace. i've copied a lot of ideas from other systems. at least in form. i love the tagging system from delicious. i want to make sure all the media (images and files) are able to be tagged and served up with that tagging system. what this gives me is a clear framework to develop any kind of content and tag it and offer it up based upon tags, collections (formal orderings) or directly. and what media is, at this point, i don't care. please, don't be offended. i like content. really. i just don't seem to be producing much lately. i'm too caught up in systems design and that...
so i just found out about the xml conference in the united states - this time it's in georgia in november. i would like to submit my abstract again on open systems design. but of course, this time, i'll mention xml. that was a slight oversight for an abstract for an xml conference. anyway, i'm understanding better how to express the system. essentially, i think there is lots of room for systems designers to sync up content producers with the individual fragments to xml which can be used within a website. i've been working hard lately to change how i conduct my business. i begin every project now by demanding that the client start to use deli.icio.us. this allows me...
here's a way we can improve the URI scheme: every KO would have these URI options [path/p] koId=#### state=view|edit view=[mod specific interfaces / processes] subview=[subprocesses] all of them could be converted into a single path, so we wouldn't have to do the mod_rewrite /MyHouse/MyWorkShop/234/Edit/Content/Details/ or /MyHouse/MyWorkShop/234/View/Question1/ what this does is treat our URIs as true objects. we change some of the language so that we can treat it as a noun (no verbs - view is a state). this would reinforce certain ideas about the atomic nature of these KOs. they can all be called directly or within a context (ie. Room/XHTML). they can all be called in certain 'states' which will either render a different interface for the object...
i've been working on a content management system for the last two years, while at the same time i've been studying xml. at the beginning of the project, there was little hope of using xml because i simply didn't know enough. half way through, i was ready to begin using it, so i started to employ a few xml fragments - most of them stored in a mysql database. but the main uses of xml which i wanted to try, i couldn't. we couldn't even rely on xslt or xpath. all my xml was very basic. i was pretty frustrated about this. but we should never let frustration stand in the way of doing something. i kept building the system...
i am still amazed at the simplicity of the problem of spam. lots of people are suggesting interesting technological solutions to fighting spam. many people have implemented strong filter systems, but these systems still permit spam to exist and in a way, we are still required to occasionally check out junk box, just in case. so spam has won. i have read that spam represents 70% of all email traffic. this is crazy. why can we not find a true solution to spam? well, i think the reason is that we're looking in the wrong place. we want to find a technology to save us from spam. but the problem, spam is not a technological problem. it's actually a social...
1000camels went and checked out the Interior Design Show in toronto today. i wasn't expecting much, since i am so narrow when it comes to so much design. but there was some nice stuff there. ald's exhibit was great. it was a massive wall of extruded plastic, white with ripples. we forgot our camera, so there's nothing to show. a nice testament to their new materials lab. we primarily went to see Winy Maas talk. he was quite good. i liked the way he spoke and many of his designs were quite engaging. however, i still walked about cursing architects. i can't help it. i guess i'm very defensive of melissa's work, and her field. i just think architects are...