It’s just data
why the lucky stiff: Now, I'll tell you upfront. This match is rigged. The deck is stacked against XML. I just threw together an Atom2YAML converter. Atom = 12 MB. YAML = 6 MB. I only have to do 50% of the work. And these are awful YAML documents. Give me an afternoon and we'll be down to 5MB with some fragrance.
The goal is to support these queries. It will be interesting to see how _why handles the second one given that he is currently cheating on the content element. ;-)
Oh, this is juicy. That second one is a real pomegranate. Looks like you have an advantage there. Good play, good play. (Rummaging around: Where is my secret weapon?!)
So I either have to convert the content to YAML or use XPath on the content. This is one of those fun checkmates that happens early in the game. I love it when someone checkmates me early. It's like: how cute!
Ok, so I convert the content to YAML. No, that's no good. YAML ain't markup. I go down that route and you'll have home court advantage.
So can I allow querying of the content and keep it in XML? Be right back.
Posted by why the lucky stiff atSam Ruby has a post about an Atom2Yaml conversion and comparison between Atom in XML and YAML. YAML looks neat and is something I will consider using for the iCite net....
[more]
Trackback from the iCite net development blog
Indeed The latest Ruby snapshot is loading the YAML feeds in 1.5 secs. (Compare against speeds in the previous post.) I'm just now compiling Python 2.3.2 and libxml2 to get a comparison. So, things are going swimmingly on just the parsing...
Excerpt from whytheluckystiff.net at