This is the outline for the CodeCon presentations on FeedParser I'm giving in February.
Outline
- Introduction
- Based on the NewsMonster parser infrastructure (XSLT)
- Designed for use within Rojo.
- Event based not DOM based
- Challenges with building a feed parser
- Too many standards
- RSS (0.9, 0.91, 0.92, 1.0, 2.0)
- Atom (0.3 and all draft specs)
- OPML
- FOAF
- Changes.xml
- RDF
- Modules (dc, aggregation, content, etc)
- Semantic confusion:
- rss:entry vs atom:item
- title issues across specifications (dc, rss, atom, etc)
- Encoding issues
- Invalid entity references
- XML prefix prior to <?xml?> (usually XML comments)
- Date encoding issues:
- RFC822 (RSS 2.0)
- ISO8601 (RSS 1.0 and Atom)
- Too many standards
- Feed Event Model
- FeedParserListener:
- init()
- onChannel( state, title, link description ): void
- onItem( state, title, link description ): void
- onItemEnd(): void
- FeedParserListener:
- HTTP issues (network API):
- Timeouts
- ETags (If-None-Modified)
- If-Modified-Since
- UserAgent
- Correct string support via Content-Type
- Problems with DOM models:
- Namespace matching doesn't line up correctly.
- Doesn't support ad-hoc schema updates with extenions
- Plugin API to pass events with vendor specific interfaces.
- mod_bigcompany
- BigCompanyEventListener
- Totally isolated development.
- Autodiscovery
- FeedLocator API
- Atom + RSS autodiscovery support
- Feed location via href
- URL fishing (disabled by default)
- Blog Profiles
- Flicker doesn't support HEAD
- Invalid autodiscovery implementations
- Avoid URL fishing
- Profile discovery support
- Feed Creation
- Same API can be used to create RSS feeds
- Same API can be used to create RSS feeds
- API
- FeedParsing:
- FeedParserListener (rss, atom)
- FeedParserListener (rss, atom)
- Directory Parsing
- FeedDirectoryParserListener (opml, foaf, changes.xml)
- FeedParsing:
-
- Content Parsing
- Tag Parsing
- Content Parsing
- Thanks
- Brad Neuberg
- Rojo Team!