This document represents a draft microformat specification. Although drafts are somewhat mature in the development process, the stability of this document cannot be guaranteed, and implementers should be prepared to keep abreast of future developments and changes. Watch this wiki page, or follow discussions on the #microformats Freenode IRC channel to stay up-to-date.
hNews is a microformat for news content. hNews extends hAtom, introducing a number of fields that more completely describe a journalistic work. hNews also introduces another data format, rel-principles, a format that describes the journalistic principles upheld by the journalist or news organization that has published the news item. hNews will be one of several open standards.
- Stuart Myles (Associated Press)
- Martin Moore (Media Standards Trust)
- Mark Ng (Media Standards Trust)
- Todd B. Martin (Associated Press)
Per the public domain release on the authors' user pages (Jonathan Malek) this specification is released into the public domain.
Public Domain Contribution Requirement. Since the author(s) released this work into the public domain, in order to maintain this work's public domain status, all contributors to this page agree to release their contributions to this page to the public domain as well. Contributors may indicate their agreement by adding the public domain release template to their user page per the Voluntary Public Domain Declarations instructions. Unreleased contributions may be reverted/removed.
hNews is a microformat for identifying semantic information in news stories. It builds on hAtom, while adding a number of fields that more completely define a journalistic work. hNews can be thought of as inheriting from hAtom, since parsers and tools that do not understand the hNews extensions can still parse the hAtom content. However, those parsers and applications that understand hNews can enable a richer set of semantic actions on news stories.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
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.
<div>), or the appropriate contextual element (e.g. an
- 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
hNews extends hAtom. As the hAtom draft format notes, "Atom provides a lot more functionality than we need for a 'blog post' microformat, so we've taken the minimal number of elements needed." News stories typically introduce more fields (for instance, the publishing organization) than the current 0.1 draft of hAtom, and those fields are very important when reading or evaluating a news story. We focus on those fields that enable the development of semantic actions around news: license, principles, dateline (geo) and source organization.
The hNews schema consists of the following:
- hNews (
hentry. required. Using hAtom.
[*] Some required elements have defaults if missing, see below.
Field and Element Details
- an hNews story MUST be encoded as an hAtom
- if an hNews story cannot be parsed as an hAtom
hentry, it is invalid hNews.
- a Source Organization element is identified by the class name
- Source Organization represents the originating organization for the news story.
- a Source Organization MUST be encoded in an hCard.
- if the Source Organization is missing
- a dateline element is identified by the class name
- dateline represents the location where the news story was written or filed (see dateline for more details).
- a dateline element MAY be encoded with an adr, geo or hCard.
- a news story SHOULD have a dateline element.
- dateline sometimes also includes the publish date of the news story. In such cases, use the datetime-design-pattern to encode the date.
- a geo element is identified by the class name
- geo represents the geographic coordinates of relevant locations in the news story.
- a geo element should be encoded in a geo.
- in those cases where the latitude and longitude represent the dateline, a variant of geo should be used (see Geo Improvements for an example).
- a license element is identified by the rel value of
- a license element MUST be encoded as described in this license brainstorm proposal.
- a news story SHOULD include a license element.
- a principles element is identified by
- principles represents the statement of principles and ethics adhered to by the news organization and/or individual that produced the news story at the time of writing.
- a principles element MUST be encoded in rel-principles.
- a news story SHOULD include principles.
- principles SHOULD be linked to using the icons or .
<dl class="profile"> <dt>class</dt> <dd> <p><a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class"> HTML4 definition of the 'class' attribute.</a> This meta data profile defines some 'class' attribute values (class names) and their meanings as suggested by a <a href="http://www.w3.org/TR/WD-htmllink-970328#profile">draft of "Hypertext Links in HTML"</a>.</p> <dl> <dt>hnews</dt> <dd>Used to describe semantic information associated with news stories.</dd> <dt>source-org</dt> <dd>The originating organization for the news story.</dd> <dt>dateline</dt> <dd>Represents the location where the news story was filed.</dd> <dt>geo</dt> <dd>Represents geographic coordinates of relevant locations in the story.</dd> </dl> </dd> <dt>rel</dt> <dd> <dl> <dt>item-license</dt> <dd>Represents the license for the story.</dd> <dt>principles</dt> <dd>Represents the statement of principles and ethics used by the news organization that produced the news story.</dd> </dl> </dd> </dl>
Examples in the wild
- Readability parses and consumes hNews. See their Article Publishing Guidelines for details.
- Google also parses hAtom (e.g. it's supported by their Rich Snippets validator).
- XHTML 1.0
- item-license brainstorm
- RFC4287 (Atom 1.0)
- Other news efforts: see news-formats.
Work in progress
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added.
Version 0.1 was drafted August 2008.
- news-brainstorming: thoughts for improving hNews.
- hNews FAQ: if you have any questions about hNews, check here, and if you don't find answers, add your questions!
- hnews-issues: please add any issues with the specification to the issues page.
- news-formats: existing news and news management schemas.
- news-examples: examples of news formats on the web.
- hnews-examples: examples of how to implement hNews.