Author Archives: David Megginson

Tech Fashions: What's in a name?

Dare Obasanjo complains that new names like SOA, AJAX, and REST have more to do with fashion than software. He’s right, but his posting might be missing the point. There are two reasons that a fuzzy, general approach to things … Continue reading

Tagged , | Comments Off on Tech Fashions: What's in a name?

AJAX as a privacy solution

There’s a lot of noise about AJAX recently, ranging from positive to negative to what’s the big deal? It’s true that architecturally, AJAX is nothing new — basically, it’s just the old, pre-Web client-server model wrapped up in the browser … Continue reading

Tagged | 2 Comments

Canadian Flag in CSS

Via Anne van Kesteren (again), I have found a site with a pure-CSS rendition of the Canadian flag (the image here in my blog is a screenshot, not the live CSS). It’s a little squished, granted, but at least it’s … Continue reading

Tagged | 4 Comments

Attributes and Namespaces

Anne van Kesteren complains that the relationship between XML Namespaces and XML attributes bugs him, and I think that his annoyance might be justified. It’s been many years since we did the 1.0 Namespaces spec in the old XML working … Continue reading

Posted in General | 4 Comments

Big, public REST application: Seniors Canada Online

[Update: partial contact information at bottom.] Yesterday I found out about a major government XML+HTTP (i.e. REST) web application that has been open to the general public since October 2004 but was never formally announced — I’m posting about it … Continue reading

Tagged | Comments Off on Big, public REST application: Seniors Canada Online

Cascading RSS

The idea of Cascading RSS (or aggregation aggregation) is so obvious that it has probably already been blogged to death or even implemented by well-known web sites; unfortunately, my short attention span ran out before I think up the right … Continue reading

Tagged | 1 Comment

Business requirements: the weakest link?

Nobody, or at least, almost nobody in the software engineering world believes in the waterfall design model any more. Like Santa Claus, waterfall sounded like a great idea (old guy comes down chimney and leaves free stuff in living room; … Continue reading

Posted in General | Comments Off on Business requirements: the weakest link?

REST design question #5: the "C" word (content)

The other posts in this series of REST design questions has danced around the edge of the content problem dipping in its toes with issues like identification and linking, but now that the design questions are coming to a close, … Continue reading

Posted in General | 5 Comments

REST design question #4: how much normalization?

[Update: why this has to do with REST] Here is the fourth in a series of REST design questions: how much should the XML data files returned by a REST web application be normalized into separate XML files? For example, … Continue reading

Tagged | 3 Comments

REST design question #3: meaning of a link

This is the third in a series of REST design questions. The first design question asked about keeping track of location and identification information after you have downloaded an XML file; the second design question asked about discovering resources and … Continue reading

Tagged | 5 Comments