Difference between revisions of "hatom-parsing"

From Microformats Wiki
Jump to navigation Jump to search
(→‎References: adding link to test suite)
Line 62: Line 62:
== Informative References ==
== Informative References ==
* ...
* [http://hg.microformats.org/tests  test suite] - work in progress!

Revision as of 18:15, 1 June 2007

hAtom parsing

Work in progress!


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 classname hentry, the entire document should be treated as a feed

Extracting feed elements

Feed <category>

See hAtom: Feed Category

Extracting entry elements

Entry <link>

Use the first rel-design-pattern in the entry.

Entry <id>

Use the same value as the entry link.

Entry <title>

See hAtom: Entry Title

Entry <updated>

See hAtom: Entry Updated

Entry <published>

See hAtom: Entry Published

Extracting tag links

See rel-tag-parsing and hAtom: Entry Category.

@@TODO - how this maps to atom


Normative References

Informative References