intertwingly

I’d guess that she used some sort of MS Word based blogging tool (Blogger for Word?). The blogging tool used an MS Office XML namespace, but the tool didn’t add the proper namespace declaration to the XML and Blogger.com did not check that the post was valid XML.

The problem is probably in the publishing protocol. I wonder if Blogger for Word uses a Blogger API variant or some ancient pre-draft version of Atom protocol.

A colon is a legal NameChar in XML 1.0.

Whether your parser considers this feed to be well-formed or not may depend on how you set up your parser.

There are lots of interesting stories in this one case.

My first hint that the RIM 8700g API was written by people with a clue was the discovery of setAllowUndefinedNamespaces.......

I wILL CREATE aN ENTERTAINMENTINFRASTRUCTE they WILL LOG ON I WILL CONTROL THEM, I WILL RULE the woRLD!

Me thinks Dave is correct, but I’m confused why you are pointing to the RSV and not the FeedValidator? And why Google isn’t using an XML writer instead of a string writer?

I’m confused why you are pointing to the RSV and not the FeedValidator?

Because you asked me to.

OMG! Google is still serving 0.3?

[link]...

popurls.com | popular urls to the latest web buzz FeedBurner Ad Network - Select Channels Sam Ruby: UnREST The Odeo Blog: Podcasting Survival Guide Amazon Web Services Blog: Entrepreneur’s Perspective on Amazon S3 Bloggers Blog: Google Trend Search...

Today, I was wondering why Sam was pointing to the RSV (really simple validator). It turns out Google is still serving Atom 0.3 on their blogger platform. Yawn! Ass. Gear. I’m going to terminate support for Atom 0.3 in Rmail this month. Move on. RSS...

the sense of adsense: Google Sued Over Child Porn Sam Ruby: UnREST Bloggers Blog: Google Trend Search Shows Rising Blog Searches Scripting News: 5/10/2006...

Thanks for pointing out my Atom error.

I wanted to put a prettily formatted table into my post on WS-Convergence, so I cut and pasted the table from a Word document. It published just fine, but as Dave Johnson pointed out, Blogger didn’t bother to validate the XHTML.

It’s fixed now.

It’s fixed now.

What?  The tools?  The data?

What happens when you layer on more tools?

Sam,
I think she meant that she fixed XML. From now on, whenever you write XML, it’s automatically valid and the interpretation is left to the XML reader ;-)

I think she meant that she fixed XML.

She confirmed that on her blog.

My experience is that that’s rarely an option when “everything is automatically implemented behind the scenes”.

I happen to know Anne from my prior Web Services days.  For whatever reason, I have not been able to spark the discussion I wanted to have.  *sigh*

the sense of adsense: I (tags: amazon associates seo) the sense of adsense: Google Sued Over Child Porn (tags: google) the sense of adsense: Googlel Pack referrals become Firefox referrals outside the US (tags: adsense firefox seo) popurls.com...

The XML do work now.