Seeing Jon's post, I think I need to clarify something.  I'm a fan of automatic roadmap dispensers.  And as long as toolkits understand that the end result is a description of a message that you would accept, and not saying anything about what other messages you might also accept, then you can make use of  namespaces and named parameter associations to cope with change.

So when I saw David Bau's paper this morning, I made a note of it here and then fired off a message to soapbuilders to put it on the agenda for next month's meeting.

  3:35:50 PM    

Yesterday, Roller moves into SourceForge's cvs.  Meanwhile, DJ hacks a calendar into blosxom using SSI.  Then Ugo releases CocoBlog.  Meanwhile, the PyCS and PSS keep rolling [groan] along..

Most interesting to me is blagg.  The basic concept is that indendent of tool, workstation, or host, one should be able to produce an aggregated weblog that can be syndicated.

Perhaps it is time to build a community of open source weblog developers?  Perhaps we could even attract a trainedmonkey or two?

  12:13:20 PM    

Amusingly, when Joel writes his version of Sam Gentile's It's The Runtime Stupid, Sam calls Joel clueless in Colorado.  The central point of both essays is that, as Sam previously put it, is that The languages are just synatatic sugar.

What I find facinating is looking at the places where this assertion is not true.  Things like column major ordering or multiple inheritance or dynamic language support or zero based arrays or...  but I digress.

Back to Joel's real point.  If programming to a browser, what matters most is not whether the programming language is based on semicolons or indentation, but access to the browser's DOM.  I agree.

  11:11:09 AM    

Carnage4Life: Open Letter To Keith Ballinger and Simon Fell.  Dare notes that Simon use of words weren't precise.  Within minutes, the precision of Dare's own words were questioned.

In any case, it seems clear to me (particularly as Simon gave a full example) that Simon was referring to the namespace name, which is determined by the qualified name, either explicitly based on the namespace prefix or implicitly based on the default namespace.

What's more unfortunate is that the small gaffe obscured Keith's real question, which was how one determines the correct message definition associated with a given message.  The answer is that you can't.  A message may not have a definition.  It may also conform to multiple definitions.

What Object Does SOAP Access? covers this topic from another (non-WSDL) perspective.

  8:58:11 AM