Paul Prescod has written a pretty interesting document on XML-RPC and REST.
Tantek , Scott Andrew and a few others wants to use XHTML instead of RSS. Sounds good.
I don’t think a BLOGPOST element should be used. The site summary are just another use of XHTML, the fact that something (any element) is a blogpost is a property. Setting a class fits very good.
Allright, who will define this format?
Microsoft don’t want to join the newly formed OASIS committee that aims to create a standard-format for office-applications. I hope they will change their mind.
More on the XML support in Office 11. If the XSLT support is both for open and save it’s looking interesting since you could define your own format for round-tripping your Office files.
FormsPlayer updates to support the XForms 1.0 CR format as well as adds some new functionality.
The SVG 1.1 implementation status page has an interesting little note: ” Note: interact-cursor-01-f was tested with Adobe ASV4 (unreleased), not ASV3″. I think that’s the first sign that Adobe is actually activly working on ASV4. Nice!
Also, cool to see that Nokia go an almost full SVG Tiny implementation. I wonder when we got that in our phones.
It’s interesting to see so many SVG implementations already. Lots of companies backing SVG. Now, let’s see who nails all tests first. My bet is on Batik but you never know.
“But Schmelzer, in response to Macromedia’s dismissive attitude toward SVG, said ‘denial is always the first stage.’”. Well, let’s see what will happen. With many of the big companies starting to back SVG, Macromedia might find themselves pretty lonely in a year or two.
The SVG working group at W3C sure has been busy. A few hours after releasing SVG 1.1 and SVG Mobile, they are now asking for feedback on SVG 1.2. My inital analysis to follow in a few days.