For solving a host of vexing problems with quiet competence, and for doing it in ways that invite others to stand on their shoulders, I salute them all.
The idea that an application wears its state information on its sleeve, readily available for users to bookmark, modify, and trade, is an underappreciated strength of Web-based software. As the RIA bandwagon picks up steam, let's honor that idea and find a way to move it forward.
The way forward, Geer suggests, is not to abandon ACLs but rather to augment them with aggressive monitoring that holds people accountable for behaviors that can’t economically be permitted or denied.
A few months ago, key Microsoft architects were telling me that it would be impossible to decouple the Avalon presentation subsystem from the Longhorn OS.
...collaborative systems for building a shared database of items, developing a metadata vocabulary about the items, performing metadata-driven queries, and monitoring change in areas of interest.
Discussions about open source and innovation tend to cluster around two opposing memes. One says that open source can't innovate; the other that only open source can innovate. Both are wrong.
Bosworth's hunch is that a Web-style thin client, driven by a rich data model intelligently synchronized with the services cloud, could do most of what we really need -- both offline and online.
Here's a challenge: Let's improve the various functions performed by e-mail without multiplying the interfaces people must learn in order to use those functions.
Fault tolerance, service-level agreements, access control, and business activity monitoring are among the many things enabled by intermediaries that watch (and sometimes transform XML) message flows.
We need HCI (human/computer interface) guidelines more than ever. And we need them not only for Windows, OS X, GNOME, and Flash, but for the uber-platform that subsumes them all.
Clemens Vasters is cofounder and chief technology officer of newtelligence AG, a developer services company focusing on XML Web services and .NET enterprise technologies.
"His current technical interests include alternative transaction models, aspect-oriented programming, statistical modeling of distributed applications, and streaming XML"
"I'm short and I have the remnants of a southern accent," Paul says in a recent interview. Co-founder of Digital Creations, now Zope Corporation, Paul evangelizes the powerful Zope/Python combo.
CTO of Propylon, and previously co-founder of Digotome, Sean has served as an invited expert on W3C committees, and is a widely respected authority on XML.
It's been almost three years since I first wrote about the problem of RSS feed redirection. From time to time I'm reminded that it's still a problem, and today I noticed that two of the blogs I read were affected by it. I was subscribed to John Ludwig at www.theludwigs.com/index.rdf, and today's entry says "Feed moved -- pls check out www.theludwigs.com/index.xml." In fact he's got an index.xml and an atom.xml, and the latter seems to correspond to what's actually published on the blog, but either way the issue is that we've still yet to agree on a standard way for newsreaders to follow relocated feeds.
The second example comes from Kim Cameron, who lost track of Eric Norlin when he moved from here to here. Kim writes:
Note to community: We have work to do on making it less painful to change URLs when using RSS. Could there be a special tag we could put in the last posting at OLD-URL that tells peoples' blog readers to change their configuration to NEW-URL? Can Dave Winer devise such a thing - or is there some capability defined and I just don't have software that takes advantage of it?
It's been talked about for a long time. Back in 2002, Dave Winer noted a suggestion I made, and the next day Sam Ruby and I both pointed to this idea from Will Cox.
In April of 2003, I again noted the issue, and learned the next day from Dave Winer about an undocumented XML syntax that was supported by at least two newsreaders: Radio UserLand and NetNewsWire. I used the technique then, with some success, and haven't tried it since.
So far as I know, that's where things stand today. If you control your server, you can of course do an HTTP-level redirect. But your blog is hosted, you probably can't, in which case you need to use the feed itself to signal the redirect. There's no standard way to do this in RSS, and the Atom spec is apparently silent on the issue as well.
Kim Cameron is right. This really oughta get fixed, and in a way that works for all readers and all feed formats. Three years ago Dave Winer wrote:
This could be a first experience at really working together, with no flames. What do you think? Is it time??
Yes, it's time.
Update: James Robertson and Dare Obasanjo say that the solution is to Just Use HTTP and lean on the hosting services that don't. Fair enough. How many are there, and what kinds of evangelism and advocacy would be effective?