[
Lists Home |
Date Index |
Thread Index
]
At 10:19 AM -0500 1/15/04, James Robertson wrote:
>There's a practical problem with this idea - most aggregators
>already deal with RSS, and have started adding support for the early
>Atom formats. As an aggregator author, I can tell you that using a
>separate framework for dealing with Atom is not a likely scenario;
>I'm using the same code to deal with Atom that I use to deal with
>RSS. As such, it has leniency for things (like illegal characters)
>for both RSS and Atom. I suspect that other aggregator authors
>either are or will be in the same boat; asking people to maintain
>different sets of rules for the two formats will seem odd to end
>users, and require some level of extra work on the part of authors.
>This is a 'facts on the ground' problem - what do you suggest as a
>solution?
>
I suggest using one of the many high quality, open source XML parsers
to process Atom feeds. (Hell, I suggest doing it for RSS.) This is
minimal extra work on your part. Take the data produced by the XML
parser and feed that into the part of your processing chain that
handles the structures rather than using your custom built RSS
parser. If your process does not cleanly separate the parsing from
the data strcuture building, then you may need to add an additional
step where the parse results are morphed into the same internal data
structure you use.
The only reason aggregator authors needed to write custom RSS parsers
in the first place was because they were trying to parse non-XML
documents. If Atom feeds are XML, then use an XML parser.
--
Elliotte Rusty Harold
elharo@metalab.unc.edu
Effective XML (Addison-Wesley, 2003)
http://www.cafeconleche.org/books/effectivexml
http://www.amazon.com/exec/obidos/ISBN%3D0321150406/ref%3Dnosim/cafeaulaitA
|
