DISQUS

I appreciate the honesty in this interview.

I just soft-launched my rails-based video tracker and I am using the caching all over the place. It is easy to do and every rails developer should put it in before launching.

The language is amazingly cool to develop in, and rails saves a lot of time even if the data modelling approach is somewhat simplistic. But I can definitely see a performance difference between ruby and languages such as perl, php, and even java.

As with everything in engineering, you have to deal with difficult trade-offs. With Memecat, I chose to pay for coding happiness with more processor heat and server memory.

I am working on perl/java project to be hosted on a domain name having some take on "dat", and so I reserved "tagdat.com". This naming convention is part of an idea I had of making data munging more appealing to wider web audiences.

Putting "dat" at the end of a verb adds a bit of MTV / hip-hop culture to the semantic web. So "dat" just might be the next "tag" :)

I can transfer "tagdat.com" to you if you want it. Also, you might consider these other "dats" for what you're working on:

aggdat
knowdat
brewdat
blendat
feedat
savedat

- Jamie

This is exactly where the tag-fad need to be heading (not to mention the next generation of wikis). Congrats!

This conversation definitely needed to get started. I have been thinking about this one ever since I started sketching out how to present the data I have been processing to general web users, semantic users, and to the google machine.

Ultimately, there will be separate presentations of the same data for human consumption and for machine consumption.

In designing a better human-readable assertion language, we need to understand our priorities. One important design goal beyond readability is speakability.

I am thinking of a very formal sort of writing which, while somewhat repetitive, achieves the fluidity of the spoken word. The assertions would have to be translatable into rdf without (m)any errors. That won't be easy.

What I want to do right now is present my semantic data about finance in a way which will encourage mortal contributors to refer to assertions and even add their own. I cannot expect people to use rdf to interact with a web service, nor perform a lot of gui interaction.