As I don’t have the time or the aspiration to write about all things happening right now in separate entries I wrap it all up into one. I’ve done such things before and I liked it. Not sure about you.
There was a lot of talk about RSS this week. For example, there now is a Longhorn Team RSS Blog. Microsoft seems to get the weblog thing. Now all they need is some standards advocate to prevent creating broken stuff. See also Simple List Questions and Longhorn and Standards from Sam Ruby. There was also a post Adriaan de J. (seriously, what’s up with the full name?). Personally I’m not so sure what’s different from Microsoft’s approach compared to that from Apple with the exception that you can de-install Safari if I’m told correctly. Hmm, maybe that’s it. But still, RSS can be perfectly both a desktop and browser feature.
Fortunately Microsoft is not alone. Apple — “we’re quite cool and refreshing, but sue you nonetheless” — released some Podcast (iTunes) specific RSS extensions. Sam Ruby has questions.
DOCTYPE on top and a text/html media type; what’s more accessible: <p>paragraph here or <span class="text">paragraph here</span>. Hah, I know, bad example. Be sure to read A principled argument from Matt May. You probably know that the WaSP has some accessibility task force with all high profile webloggers on it, right? I would like to know how many users are actually out there. What sites do they typically visit, in what visitor ‘categories’ can you place them in, et cetera. Are things like Jaws detectable, is there some server data? Those things.
rel=tag implies rel=nofollow. For now, just use rel="nofollow tag". Everything that doesn’t support that hasn’t got a conforming HTML 4.01 parser and should get one.
application/xhtml-voice+xml is also there — semi. For the Opera gang.
Finally, all my bookmarked posts in bloglines are cleared out. Time to start counting down at five; those who know will be quiet, me too.
I guess that has nothing to do with Dave Whiner having invented OPML.
No. It’s not that it needs replacing because it’s Winer’s spec, it’s that that it needs replacing because it’s a typical Winer spec.
Thanks Anne for the friendly note about our Info.nl Company Weblog.
A small correction however: Info.nl is no longer involved in creating (or designing) the Rabobank.nl website. We were heavily involved for quite a number of years, but alas, no longer. That being said, I myself was involved (for Info.nl) not too long ago for the Rabobank.nl project when they were developing their internet architecture. This is the period in which their stance on web standards, URI design, REST, etcetera was created. And also, we still do a bunch of other stuff for other Rabobank websites (they have quite a few).
But yes, you are right, before the end of this year we should see the end of the annoying browser warning at Rabobank.nl. Also see the Marc Cootjans interview on Emerce on the new Rabobank.nl initiative.
You forgot the www out of 'betaversion.org'.
Hey, if the Rabobank is going to use REST, does that mean we can script the banking interface? ;-)
Hey, if the Rabobank is going to use REST, does that mean we can script the banking interface? ;-)
We're even using SiFR (jojo2 is on our team) :-) The banking interface will take a bit more time but it's in the planning. In the meantime you can greasemonkey to your heart's content.
Cheers,
Meint
Meint, yeah, I heard about sIFR in Copenhagen. Even mailed with Ron when I found out jojo2's e-mail address was from the Rabobank. Well, I'm interested in seeing what you guys will do with it. Good luck!