Difference between revisions of "news-brainstorming"

From Microformats Wiki
Jump to navigation Jump to search
(→‎Open Issues: remove closed issues from open issues section)
(Moved issues to issues page)
(6 intermediate revisions by 3 users not shown)
Line 44: Line 44:
Please add new issues to the bottom of the [[news-brainstorming#Open_Issues|Open Issues]] section by copy and pasting the [[news-brainstorming#Issues_Template|Template]]. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.
Please see [[hnews-issues|hNews issues]].
See also [[hatom-issues|hAtom Issues]]
See also [[hatom-issues|hAtom Issues]] for questions about [[hAtom]].
=== Issues Template ===
=== Open Issues ===
=== Closed Issues ===
== Naming ==
== Naming ==
Line 63: Line 56:
= Proposal =  
= Proposal =  
hNews is a data format (similar to a microformat) for news content. hNews extends [http://microformats.org/wiki/hatom hAtom], introducing a number of fields that more completely describe a journalistic work. hNews also introduces another data format, [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ 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.
See the [[hnews]] draft.
== Introduction ==
hNews is a format (similar to 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.
== Format ==
=== In General ===
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.
=== Schema ===
The hNews schema consists of the following:
* (root) ('''<code>root</code>''') and '''<code>hentry</code>'''.  required. Using [[hAtom]].
** '''<code>source-org</code>'''. required. Using [[hCard]].[*]
** '''<code>dateline</code>'''. optional. Using text or [[hCard]].
** '''<code>geo</code>'''. optional. Using [[geo]].[*]
** '''<code>item-license</code>'''. required. Using a [http://microformats.org/wiki/licensing-brainstorming#item_as_container license brainstorm proposal].
** '''<code>principles</code>'''. recommended. Using the draft microformat. [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles].
[*] Some required elements have defaults if missing, see below.
=== Field and Element Details ===
===== Source Organization =====
* a Source Organization element is identified by the class name <code>source-org</code>.
* 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
** find the [[algorithm-nearest-in-parent]] element(s) with class name <code>source-org</code> and that is/are a valid [[hCard]]
** otherwise the entry is invalid hNews
===== Dateline =====
* a dateline element is identified by the class name <code>dateline</code>.
* dateline represents the location where the news story was written or filed (see [http://en.wikipedia.org/wiki/Dateline dateline] for more details).
* a dateline element {{may}} be encoded in an [[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.
===== Geo =====
* a geo element is identified by the class name <code>geo</code>
* 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 [http://microformats.org/wiki/geo-brainstorming#Geo_improvements Geo Improvements] for an example).
===== License =====
* a license element is identified by the class name <code>item-license</code>.
* a license element {{must}} be encoded as described in this [http://microformats.org/wiki/licensing-brainstorming#item_as_container license brainstorm proposal].
===== Principles =====
* a principles element is identified by <code>rel-principles</code>.
* principles represents the statement of principles and ethics used by the news organization that produced the news story.
* a principles element {{must}} be encoded in [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles].
* a news story {{should}} include principles.
* principles {{should}} be linked to using the icons [[image:principles-button-blue.png]] or [[image:principles-book-blue.png]].
=== XMDP Profile ===
<dl class="profile">
  <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>.
    Used to describe semantic information associated with news stories.
    The originating organization for the news story.
    Represents the location where the news story was filed.
    Represents geographic coordinates of relevant locations in the story.
    Represents the license for the story.
    Represents the statement of principles and ethics used by the news organization that produced the news story.

Latest revision as of 23:02, 14 October 2009

News Brainstorming

There have been several efforts to define data formats for news content. Almost all have focused on the interchange of news content between systems and organizations, and so contain dozens (if not hundreds) of fields that are targeted at "news management"--a mix of content management, metadata management, versioning and other operations undertaken by news organizations.

This page serves to document the brainstorming and ideas resulting from analysis of news examples from real world sites and systems for the design of a simple news microformat. - Jonathan Malek


  • Jonathan Malek
  • Stuart Myles
  • Martin Moore
  • Mark Ng
  • Todd Martin

See Also

The Problem

While there are dozens of formats used on thousands of news sites, there is no single standardized format for presentation of news on the web. Having a standardized news format for web publishing would significantly benefit readers, aggregators, search engines and researchers alike. With no standard format for news, search engines are forced to parse unstructured data, and errors can be costly (see Wired.com, 2008).

Thoughts on a Microformat for News

We found significant overlap with hAtom 0.1, and simplified an initial effort at a data format for news away from describing any fields already in hAtom 0.1, or the superset Atom, with the expectation that future versions of that draft specification would approach feature parity. Instead, we focused on those news fields not in hAtom 0.1.

In much the same way that one extends Atom, we are looking to extend hAtom 0.1 with the most vital news-specific fields.

The fields we've selected are a combination of the common fields from many of the news formats currently in use, and the introduction of one new field, principles.

Common News Fields

  • hAtom 0.1 fields: first and foremost, a news story is an hentry. If the news story cannot be parsed by an hAtom 0.1 parser, it is not a valid news format.
  • source-org: the source organization for this particular news story--should be considered different from the atom:source element because it does not represent the source feed, but rather the source organization (and so should use hCard 1.0). We're using source-org to avoid name conflict with hAtom 0.1 should the draft decide to include the atom:source element.
  • dateline: using text or hCard 1.0, not to be confused with date (see dateline for more information).
  • geo: using Geo, a simple way of providing the information necessary for services for readers around local news content. This field should be inherited from hAtom 0.1, but since it is not part of the format yet, we're including it here. See the hAtom and Geo discussion.
  • item-license: to express licensing around the item
  • principles: using the draft format rel-principles


Please see hNews issues.

See also hAtom Issues for questions about hAtom 0.1.


Here are candidate names for a news microformat:

  • hNews


See the hNews 0.1 draft.