X040703A: Atom Encoding Incoherence

Status	Date	Description




	2004-07-25	Clean up X040703B 0.10 to say the right thing about lair-atom.xml and how the snapshot now shows up invalid also. This means we are even more clueless about what the web site is really saying and how the validator handles it.
	2004-07-25	To work on the encoding incoherence further, it is necessary to see what the web server coughs up for the XML feeds. I will need to do a sniffer capture of the actual XML transfer.
done	2004-07-25	After copying snapshots of the feeds for each blog, check the buttons and adjust as needed depending on whether any of them show the encoding incoherence or not. Update the demonstration page as needed and close these items.
	2004-07-25	Cite this <http://www.dehora.net/journal/2004/07/incoherence.html> Bill de hÓra entry on Incoherence between HTTP, MIME, and XML. The ASCII solution is a problem for me, because not everything does have a character entity and using the absolute numbers is, well, icky. Also, I am not sure how to cajole blogger into switching the encoding style. So there are even more complex incoherence cases to deal with.
done 2004-07-25	2004-07-24	See if any of the clu-atom.xml and pn-atom.xml will copy in a way that remains invalidAtom. Do this before anything else is done to the feed. Success!!
done	2004-07-24	Record the demonstration as unstable with more to be figured out
done	2004-07-24	Refer to the actual lair-atom.xml site feed, because the copy doesn't show up as invalid!
done	2004-07-24	In the valid case on wing-atom.xml, reissue that one with a copy of the valid feed also.
~~done~~	2004-07-24	~~Refer to a copy of the invalid feed so that the experience can be confirmed~~ [doesn't work]
done	20004-07-23	Create a new entry that indicates the Atom Feed is not valid and links to this incident.
done	2004-07-23	Connect the example to an abbreviated feed that still demonstrates the example.
done	2004-07-23	Start the incident report with basic demonstration and a summary