hatom
hAtom
hAtom is a microformat for content that can be syndicated, primarily but not exclusively weblog postings. hAtom is a strongly based on a subset of the Atom syndication format; every concept in hAtom has a corresponding definition in Atom.
NOTE: the structure is in the process of being constructed, please give me a few days to get it in shape! DavidJanes
Draft Specification
Editor
Authors
Copyright
This specification is (C) 2004-2024 by the authors. However, the authors intend to submit (or already have submitted, see details in the spec) this specification to a standards body with a liberal copyright/licensing policy such as the GMPG, IETF, and/or W3C. Anyone wishing to contribute should read their copyright principles, policies and licenses (e.g. the GMPG Principles) and agree to them, including licensing of all contributions under all required licenses (e.g. CC-by 1.0 and later), before contributing.
Patents
This specification is subject to a royalty free patent policy, e.g. per the W3C Patent Policy, and IETF RFC3667 & RFC3668.
Introduction
Semantic XHTML Design Principles
Note: the Semantic XHTML Design Principles were written primarily within the context of developing hCard and hCalendar, thus it may be easier to understand these principles in the context of the hCard design methodology (i.e. read that first). Tantek
XHTML is built on XML, and thus XHTML based formats can be used not only for convenient display presentation, but also for general purpose data exchange. In many ways, XHTML based formats exemplify the best of both HTML and XML worlds. However, when building XHTML based formats, it helps to have a guiding set of principles.
- Reuse the schema (names, objects, properties, values, types, hierarchies, constraints) as much as possible from pre-existing, established, well-supported standards by reference. Avoid restating constraints expressed in the source standard. Informative mentions are ok.
- For types with multiple components, use nested elements with class names equivalent to the names of the components.
- Plural components are made singular, and thus multiple nested elements are used to represent multiple text values that are comma-delimited.
- Use the most accurately precise semantic XHTML building block for each object etc.
- Otherwise use a generic structural element (e.g.
<span>or<div>), or the appropriate contextual element (e.g. an<li>inside a<ul>or<ol>). - Use class names based on names from the original schema, unless the semantic XHTML building block precisely represents that part of the original schema. If names in the source schema are case-insensitive, then use an all lowercase equivalent. Components names implicit in prose (rather than explicit in the defined schema) should also use lowercase equivalents for ease of use. Spaces in component names become dash '-' characters.
- Finally, if the format of the data according to the original schema is too long and/or not human-friendly, use
<abbr>instead of a generic structural element, and place the literal data into the 'title' attribute (where abbr expansions go), and the more brief and human readable equivalent into the element itself. Further informative explanation of this use of<abbr>: Human vs. ISO8601 dates problem solved
Format
In General
Nomenclature
Schema elements are based on the Atom nomenclature and follow the microformat pattern of prefixing a unique identifier (in this case, atom) on the outermost container elements -- the EntryGroup or Entry. The parts of this microformat are based on analysis of many weblog, bulletin board and media posts and can be read here
| Concept | Atom Identifier | Microformat Idenitfier |
|---|---|---|
| EntryGroup | atom:feed
|
add class="atomfeed"
|
| EntryGroup Title | atom:title
|
Not defined in the first iteration of this proposal. |
| EntryGroup Permalink | atom:link@rel=alternate
|
Not defined in the first iteration of this proposal. |
| Entry | atom:entry
|
add class="atomentry"
|
| Entry Title | atom:title
|
use <h#> in block elements, or (non-preferentially) add class="title" in inline elements
|
| Entry Content | atom:content
|
add class="content"
|
| Entry Summary | atom:summary
|
add class="summary"
|
| Entry Permalink | atom:link
|
add class="link"
|
| Entry Created | atom:published
|
use <abbr class="published" title="YYYYMMYYThh:mm:ss">...</abbr>
|
| Entry Author | atom:author
|
use <address>...</address>
|
XMDP Profile
Parsing Details
Examples
This section is informative.
hAtom Sample
More Examples
See hatom-examples.
Examples in the wild
This section is informative.
Implementations
This section is informative.
References
Normative References
Informative References
Specifications That Use hAtom
Similar Work
Work in progress
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. There is a separate document where we are keeping our brainstorms and other explorations relating to hAtom:
Discussions
Q&A
- If you have any questions about hAtom, check the hAtom FAQ, and if you don't find answers, add your questions!
Issues
- Please add any issues with the specification to the separate hAtom issues document.
See Also
- hAtom - the draft proposal
- blog-post-brainstorming
- blog-post-formats
- blog-post-examples
- blog-description-format - how to describe a blog (as opposed to the individual entries, which is what we're doing here)