news-brainstorming: Difference between revisions
(Moved issues to issues page) |
|||
| (26 intermediate revisions by 5 users not shown) | |||
| Line 34: | Line 34: | ||
=== Common News Fields === | === Common News Fields === | ||
* [[hAtom]] fields | * [[hAtom]] fields: first and foremost, a news story is an [[hatom#Entry|hentry]]. If the news story cannot be parsed by an [[hAtom]] parser, it is not a valid news format. | ||
* '''source-org''': the source organization for this particular news story--should be considered different from the [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#element.source atom:source element] because it does not represent the source feed, but rather the source organization (and so should use [[hCard]]). We're using ''source-org'' to avoid name conflict with [[hAtom]] should the draft decide to include the ''atom:source'' element. | * '''source-org''': the source organization for this particular news story--should be considered different from the [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#element.source atom:source element] because it does not represent the source feed, but rather the source organization (and so should use [[hCard]]). We're using ''source-org'' to avoid name conflict with [[hAtom]] should the draft decide to include the ''atom:source'' element. | ||
* '''dateline''': using text or [[hCard]], not to be confused with date (see [http://en.wikipedia.org/wiki/Dateline dateline] for more information). | * '''dateline''': using text or [[hCard]], not to be confused with date (see [http://en.wikipedia.org/wiki/Dateline 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]], but since it is not part of the format yet, we're including it here. See the [[hatom-issues#Geo|hAtom and Geo]] discussion. | |||
* '''geo''': using [[geo]], a simple way of providing the information necessary for services for readers around local news content | |||
* '''item-license''': to express licensing around the item | * '''item-license''': to express licensing around the item | ||
* '''principles''': using the draft format [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles] | * '''principles''': using the draft format [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles] | ||
== Issues == | |||
Please see [[hnews-issues|hNews issues]]. | |||
See also [[hatom-issues|hAtom Issues]] for questions about [[hAtom]]. | |||
== Naming == | == Naming == | ||
| Line 50: | Line 54: | ||
* hNews | * hNews | ||
= Proposal = | |||
See the [[hnews]] draft. | |||
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
Contributors
- 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, and simplified an initial effort at a data format for news away from describing any fields already in hAtom, 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.
In much the same way that one extends Atom, we are looking to extend hAtom 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 fields: first and foremost, a news story is an hentry. If the news story cannot be parsed by an hAtom 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). We're using source-org to avoid name conflict with hAtom should the draft decide to include the atom:source element.
- dateline: using text or hCard, 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, 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
Issues
Please see hNews issues.
See also hAtom Issues for questions about hAtom.
Naming
Here are candidate names for a news microformat:
- hNews
Proposal
See the hnews draft.