hatom-parsing: Difference between revisions
Jump to navigation
Jump to search
GetmoNcnaa (talk | contribs) m (acelbocolo) |
m (Reverted edits by GetmoNcnaa (Talk) to last version by ScottReynen) |
||
(One intermediate revision by one other user not shown) | |||
Line 1: | Line 1: | ||
<h1>hAtom parsing</h1> | <h1>hAtom parsing</h1> | ||
Latest revision as of 19:21, 10 December 2008
hAtom parsing
Work in progress!
Editor/Author
URL handling
An hAtom parser may begin with a URL to retrieve.
If the URL lacks a fragment identifier, then the parser should parse the entire retrieved resource for hAtom feeds and hAtom entries.
If the URL has a fragment identifier, then the parser should parse only the node indicated by the fragment identifier and its descendants, looking for hAtom feeds and hAtom entries, starting with the indicated node, which may itself be a hAtom feed/entry.
Finding hAtom feeds/entries
- hAtom feeds are identified with the classname
hfeed
- hAtom entries are identified by the classname
hentry
- if the document does not contain an element with the class name
hfeed
, but does contain an element with the classnamehentry
, the entire document should be treated as a feed
Extracting feed elements
Feed <category>
Extracting entry elements
Entry <link>
Use the first rel-bookmark in the entry.
Entry <id>
Use the same value as the entry link.
Entry <title>
Entry <updated>
Entry <published>
Extracting tags
See rel-tag-parsing and hAtom: Entry Category.
References
Normative References
Informative References
- test suite - work in progress!
- parsing - general microformat parsing