Archive for October, 2007

Telecoms2.0

Paul gave me access to mojo at the end of last week, and since Norm Walsh is blogging about it, I assume I can too…

As one of the 20th Century telecoms monopolies, it’s good to see BT trying to adapt, and fun to imagine the battles Paul must have had to be allowed to expose call management function on the internet over a non ‘enterprise’ transport. etc, etc. I had programmatic access to an SMS gateway a few years ago when working on Extreme Blue, so I’ve thought of some of the possibilities before, but the RESTful HTTP api changes lots and I’m really looking forward to trying to integrate this with my current side project. I also see a facebook app coming on… I sort of ignored the Web21C stuff when it was first launched because it was (I think) .Net only, but now there’s Java APIs and Mojo so I’ll be taking a much closer look.

SemWeb

I’ve been sold on the idea of the Semantic Web for a while, but its because of descriptions like this (however tongue in cheek) that we’ll end up with something labelled Web 3.0.4.11!

all-encompassing ontological wonder of the Semantic Web

RFC5023

AtomPub is now RFC5023 which is very good news. I’ve been waiting for AtomPub and decent libraries for it for a while because it starts to answer one of the main criticisms I have of REST - that there’s no mechanism to build reusable infrastructure pieces. With Atom and AtomPub we finally have that (for the places its needed).

I’ve been playing around with Apache Abdera in the last week or so and while I think the API and samples could do with a bit of work, it’s functionally pretty good. Now, back to that AtomPub based project….

Next Page »


About

I’m David Illsley, I work in Web Services development at IBM Hursley, which involves work on the Apache WS Project, where I am a committer and PMC member. When not working with technology, I spend a lot of time on the backstage aspects of theatre, and a sadly decreasing amount of time reading.

a

Disclaimer

The postings on this site solely reflect the personal views of the author and do not necessarily represent the views, positions, strategies or opinions of IBM or IBM management.