http://microformats.org/wiki/api.php?action=feedcontributions&user=JonathanMalek&feedformat=atomMicroformats Wiki - User contributions [en]2024-03-28T14:16:01ZUser contributionsMediaWiki 1.38.4http://microformats.org/wiki/index.php?title=hnews-issues&diff=43413hnews-issues2010-12-28T21:33:20Z<p>JonathanMalek: Clarifying principles question raised by TobyInk on 14 November 2010.</p>
<hr />
<div><h1> hNews issues </h1><br />
<br />
__TOC__<br />
<br />
These are externally raised issues about [[hnews|hNews]] with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the draft. <br />
<br />
'''IMPORTANT''': Please read the [[hnews-faq|hNews FAQ]] before giving any feedback or raising any issues as your feedback/issues may already be resolved/answered.<br />
<br />
Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — [http://tantek.com/ Tantek]<br />
<br />
Please add new issues to the '''top''' of the list. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.<br />
<br />
See related [[hatom-issues]] and [[hcard-issues]].<br />
<br />
== Template ==<br />
<br />
{{issues-format}}<br />
<br />
<br />
== Issues ==<br />
=== Open Issues ===<br />
<br />
<div class="hentry"><br />
{{OpenIssue}} <span class="entry-summary author vcard"><span class="published">2010-03-29</span> raised by <span class="fn">[[User:Trondhuso|Trond Husø]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Add lead class/tag</strong>. An article consists of a title, lead and the body content. I would very much like to see the lead attribute/tag being added. I see two possible usages: 1) In a world of AJAX you could show the content related to the lead-part + Click here for more. When you click the link the rest of the article becomes visible. Or it can be used in parts where you load to a title/lead carousel. 2) In RSS/Atom the Lead-part is what you would like to see in the description part of the feed.<br />
** Trond, I really like the idea. I suggest taking a look at using [http://microformats.org/wiki/hAtom#Entry_Summary hAtom entry-summary] for this purpose. I feel the lead paragraph of the typical upside-pyramid-style news story is an ideal value for the [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#element.summary atom:summary] element. And, by re-using the hAtom conventions in this way, your news item will be semantically available to software focusing on both hAtom and hNews. The Associated Press interpreted Atom in this way, as illustrated by one of [http://hosted.ap.org/lineups/TOPHEADS-atom_0.3.xml?SITE=CAANG&SECTION=HOME AP's public Atom feeds]. [[User:gut1975|Guthrie Collin]] 14:25, 01 April 2010 (UTC)<br />
</div><br />
</div><br />
<br />
<div class="hentry"><br />
{{OpenIssue}} <span class="entry-summary author vcard"><span class="published">2009-11-16</span> raised by <span class="fn">[[User:gut1975|Guthrie Collin]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Allowable number of item-licenses?</strong>. In the news world, different news companies sometimes share the copyright on specific works, and this arrangement results in two copyright statements appearing for one piece of content. Modeling this relationship in the hNews world would result in two or more "item-license" elements, with each item-license element potentially linking to a separate license for each news company. Hence, I think the hNews format should explicitly allow more than one item-license for each "hnews hentry" container. Thoughts?<br />
** If as you say "In the news world, different news companies sometimes share the copyright on specific works, and this arrangement results in two copyright statements appearing for one piece of content" then please provide URLs to real world examples that demonstrate as such. Absent any such examples, we must not change hNews for an otherwise assumed to be theoretical example, per microformats [[process]] and [[principles]]. [[User:Tantek|Tantek]] 23:51, 16 November 2009 (UTC)<br />
** Some examples are:<blockquote><p>[http://sports.yahoo.com/nhl/preview?gid=2006122911 Capitals-Devils Preview on Yahoo!] which was created under a joint arrangement between AP and STATS, Inc (scroll to page bottom).</p><p>[http://www.kcbd.com/global/story.asp?s=11520396 Colo. medical pot & taxes on KCBD 11 in Lubbock, TX] which was an AP story but since AP and some of its customers have special copyright arrangements, KCBD and its parent company also share copyright on the content (see bottom of page).</p></blockquote>As you can see, it's somewhat inefficient to have the license separate from the content in this way, and I think the hNews schema should permit multiple item-license elements for these situations. [[User:gut1975|Guthrie Collin]] 16:21, 17 November 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<div class="hentry"><br />
{{OpenIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-20</span> raised by <span class="fn">[[User:MilesD|Miles De Feyter]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">News, Commentary, and Opinion pieces as they relate to hNews</strong>. An interesting comment came up today when looking at how to use hNews on other AOL properties outside of our main news site, and that is, some of our sites are both news and commentary. Let's take our sports site for example http://www.fanhouse.com/ <br />
<br />
This site reports on sports news with article headlines such as: <br />
[http://www.fanhouse.com/news/nfl/big-ben-tops-pass-rankings/723353 Big Ben tops pass rankings]<br />
<br />
But fanhouse.com also has some obvious opinion pieces such as:<br />
[http://kevin-blackistone.fanhouse.com/2009/10/19/ail-to-the-redskins-worst-run-franchise-on-the-planet/ Fail to the Redskins: Worst-Run Franchise on the Planet]<br />
<br />
Currently we have one publishing system for all of our content within Fanhouse whether it be feed driven, in house publisher, news content, or commentary. So at the moment if one thing gets hNews it all does. <br />
<br />
Have you given this situation thought? My initial thinking is that perhaps this is where a principles statement specific to Fanhouse could account for the different types of content being labeled hNews. <br />
** Very glad you brought this up. We've given this alot of thought. I think your initial thinking is right. Right now the place to distinguish differences such as these (e.g. reporting from opinion) is within the principles statement. But this is something I think would benefit significantly from further development (i.e. the development of additional hNews criteria) [[User:Martinjemoore|Martin Moore]]<br />
** I believe that hNews is applicable to many types of news, ranging from reporting facts, to analysis pieces, opinion and columns. It is not unusual for a given piece of news to be a mix of two or three "types". Really, the purpose of hNews is allow for the common structural components of news to be more clearly marked up. The exact content is less important than the form. However, I also see that there is also value for a publisher of hNews to be able to self-classify the "type" of content. One way to do this would be to use rel-tag to indicate how the publisher would like to describe the hNews-encoded content (as commentary, opinion, analysis, interview, satire or whatever). [[User:Smyles|Stuart Myles]]<br />
</div><br />
</div><br />
<br />
=== Resolved Issues ===<br />
<br />
<div class="hentry"><br />
{{ResolvedIssue}} <span class="entry-summary author vcard"> <span class="published">2010-11-14</span> raised by <span class="fn">[[User:TobyInk|TobyInk]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Meaning of rel=principles</strong>. It's currently defined as "represents the statement of principles and ethics used by the news organization that produced the news story" - but are those the principles the ones used by the organisation at the time the article was written, or are they the principles that are being used by the organisation currently? If the latter, this property might be better as an extension to hCard. Either way, I think it should be clarified.<br />
** An interesting distinction, and not one I think that was discussed at any point, as far as I can see in my notes. I agree, clarification is needed. I have a feeling that the second option (the principles that are being used by the organization currently) is much simpler, and so more likely to be used. I also agree in part with your point about extending hCard in that case, as the principles apply to the [http://microformats.org/wiki/hnews#Additional_Fields source-org], rather than to the article itself. However, what about those cases where the source organization applies different principles for different types of content? For instance, an opinion piece? [[User:JonathanMalek|JonathanMalek]] 04:45, 15 November 2010 (UTC)<br />
** Good question Toby. The underlying basis of rel-principles has always been 'the principles that apply to this article'. Therefore if the article was written and published under certain principles then it should link to those principles even if the principles of the organisation subsequently change. The purpose of this is so that the reader can always tell under what principles a particular item of news was produced. Therefore rel-principles has to remain flexible by article rather than by author. For this reason I think it is better that it remain part of hNews rather than as an extension to hCard [[User:Martinjemoore|Martin Moore]] 16 November 2010<br />
*** This was the interpretation I'd always assumed, and hoped was the case as it seems most useful. Could somebody update the [[hnews]] page on the wiki to clarify the definition? [[User:TobyInk|TobyInk]] 10:34, 30 November 2010 (UTC)<br />
*** So the proposal as it stands is to change: <blockquote><p>* principles represents the statement of principles and ethics used by the news organization that produced the news story.</p></blockquote> to:<blockquote><p>* 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''.</p></blockquote> I will let this sit for a bit, and if there are no objections, I will update the [[hnews]] page. [[User:JonathanMalek|JonathanMalek]] 15:23, 5 December 2010 (UTC)<br />
*** +1 on JonathanMalek's proposed resolution and changes. - [[User:Tantek|Tantek]] 22:23, 5 December 2010 (UTC)<br />
** ACCEPTED SPEC UPDATE. CLARIFIED: 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. [[User:JonathanMalek|JonathanMalek]] 21:33, 28 December 2010 (UTC)<br />
</div><br />
</div><br />
<br />
<div class="hentry"><br />
{{ResolvedIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-14</span> raised by <span class="fn">[[User:MarkNg|MarkNg]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">adr for dateline</strong>. From [http://twitter.com/pigsonthewing/status/4831500605 Andy Mabbett on Twitter] : hNews microformat spec "dateline. optional. Using text or hCard" should read "dateline. optional. Using text, adr or hCard".<br />
** Seems like a useful extra to me, any objections ? [[User:MarkNg|MarkNg]]<br />
** Agreed, makes sense. --[[User:JonathanMalek|JonathanMalek]] 00:57, 15 October 2009 (UTC)<br />
** +1 to addition of optional "adr" markup of "dateline", but should also allow "geo" markup of "dateline" as well. i.e. change: <blockquote><p>* a dateline element MAY be encoded in an hCard.</p></blockquote> to <blockquote><p>* a dateline element MAY be encoded with an [[adr]], [[geo]], or [[hCard]] on the same element.</p></blockquote> [[User:Tantek|Tantek]] 19:57, 15 October 2009 (UTC)<br />
** ACCEPTED SPEC UPDATE. ADDED: [[User:Tantek|Tantek]]'s recommendation from 15 October 2009. [[User:JonathanMalek|JonathanMalek]] 21:33, 28 December 2010 (UTC)<br />
</div><br />
</div><br />
<br />
<div class="hentry"><br />
{{ResolvedIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-15</span> raised by <span class="fn">[[User:TobyInk|TobyInk]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">XMDP defines 'principles' incorrectly.</strong> The XMDP for hNews defines 'principles' as a class, whereas the rest of the draft refers to it as a link type (i.e. 'rel' value).<br />
** ACCEPTED SPEC UPDATE. FIXED: thanks for pointing that out. I believe the updated profile reflects that correctly now. --[[User:JonathanMalek|JonathanMalek]] 15:37, 15 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<div class="hentry"><br />
{{ResolvedIssue}} <span class="entry-summary author vcard"><span class="published">2009-11-13</span> raised by <span class="fn">[[User:gut1975|Guthrie Collin]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">The item-license element is incorrectly described as a class</strong>. The XMDP profile and element description for item-license in hNews describes the element as a class attribute value, however, the [http://microformats.org/wiki/licensing-brainstorming#item_as_container Licensing Brainstorming] proposal describes this field as a link type. In addition, the hNews examples purport item-license as a link type. Which item-license description is correct? <br />
** ACCEPTED SPEC UPDATE. FIXED: the correct description is as a link (rel). The profile has been updated to reflect that correctly. --[[User:JonathanMalek|JonathanMalek]] 18:44, 13 November 2009 (UTC)<br />
</div><br />
</div><br />
<br />
=== Closed Issues ===<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-09</span> raised by <span class="fn">Miles De Feyter</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Implementation of item-license as it relates to hNews</strong>. Reading through the item-license brainstorm it seems to indicate that "item-license" would need to be nested within something with the class of "item". So as this relates to hNews is the suggestion to then have an articles containing div have the three class names of "hnews hentry item"?<br />
** At this point, Miles, that is correct (following the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] concept and guidance). I expect we'll see changes around item-license (it's still just brainstorming), but for the time being, the third class name "item" is needed. --[[User:JonathanMalek|JonathanMalek]] 16:25, 12 October 2009 (UTC)<br />
** Added to [[hnews-faq]] --[[User:JonathanMalek|JonathanMalek]] 02:19, 14 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">2009-09-28</span> raised by <span class="fn">[[User:MilesD|Miles De Feyter]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Principles as a requirement</strong>. Working for a publishing company that owns and operates a large number of different organizations I'd love to incorporate hNews within our publishing system. The hNews requirement for a principles statement could pose a problem though or at least make rolling out hNews a more involved process then it would be otherwise. The issue is, I would now have to go to each product owner and ask then to provide this principles statement to link to. So my concern is now rather then just making a change to the publishing system to support hNews there is this requirement for some supporting content. And due to the nature of the content I can only assume our legal dep. would need to sign off as well, further complicating the adoption of hNews.<br />
** +1 I agree that the "principles" property (and probably all other others) should be optional. [[User:Tantek|Tantek]] 18:29, 29 September 2009 (UTC)<br />
*** I think it's important to explain why principles is a requirement. hnews is essentially a specialization of hAtom. Its purpose is to distinguish news on the web. Hence the description of source organisation, license and principles. Of these, principles is the only one which consistently distinguishes news on the web from other content (eg. commercial, government). In the future it should be distinguished further by making the principles themselves machine readable (but that is for a later date). Most professional news organisations adhere to a Statement of Principles (e.g. see http://en.wikipedia.org/wiki/Journalism_ethics_and_standards and http://www.journalism.org/resources/ethics_codes). If a site wants to mark up its content but does not want to distinguish it as news, then wouldn't it be easiest to use hAtom? [[User:martinjemoore|Martin Moore]] 9:00, 20 September 2009 (UTC)<br />
*** Having discussed this issue at length outside this brainstorming, we understand some of the concerns of the microformat community regarding 'must', but are still convinced of the criticality of principles to hNews - therefore recommend downgrading from 'must' to 'should'. [[User:martinjemoore|Martin Moore]] 14:00, 7 October 2009 (UTC)<br />
**** Accepted and implemented in 0.1. In keeping with the general direction here, we've changed <code>item-license</code> as well, and would consider adopting the same with <code>source-org</code> as well, if it proves to present the same problems. --[[User:JonathanMalek|JonathanMalek]] 00:53, 15 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">hCalendar instead of dateline?</strong> Would an [[hCalendar]] event (which can contain an hCard location) make sense for a dateline, or is the 'date' part more often omitted?<br />
** Confusingly, the journalistic term "dateline" isn't anything to do with a date or time. It is the location from which a report is filed and is generally the main location associated with a story. Generally, a dateline consists of a city (e.g. "Rome") but could be the name of a ship at sea or even a space station. [[User:Stuart Myles|Stuart Myles]] 21:12, 24 August 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">hCard instead of geo?</strong> Is geo really in use here, or would using an hCard (that can contain geo) be a better way of representing locations referred to in the story, as more human readable?<br />
** The reason for geo being highlighted (as an optional field) is to promote at least one location identifier in the story--preferably the most appropriate single location on a map for that particular story. Geo does not have to be related to dateline, but in some [http://labs.ap.org/wiki/hNews examples] we've worked on, we show the two collapsed into a single field. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)<br />
** For locations referred to in the story, I agree--publishers should be using [[hCard]] with the contained geo to markup the locations themselves. One of the concepts I've struggled with is drawing an admittedly arbitrary line between the metadata ''about'' a story from the metadata ''within'' a story. For the former, we've focused on simplicity and minimalism, primarily as a means to encourage adoption. That has meant preferring [[rel-tag]] over in-line entity extraction and markup using compound microformats. For the latter, we feel that the field is open: use whatever microformat fits your purpose, however you can--the more, the better. This lets publishers with minimal technology capabilities at least get started by tweaking a few templates in their CMS, while those more technically inclined aren't limited by the simplicity of the format to a paucity of data. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)<br />
** Also, dateline can be text or [[hCard]], as noted in the [[news-brainstorming#Common_News_Fields|Common News Fields]] section. --[[User:JonathanMalek|JonathanMalek]] 18:17, 24 September 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">What is item-license?</strong> Using [[rel-license]] presumably?<br />
** We're working off the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] discussions for this. Our concern with [[rel-license]] was its definition as applying to an entire page, rather than an item within a page. The current discussions around licensing definitely address that. --[[User:JonathanMalek|JonathanMalek]] 00:02, 25 August 2009 (UTC)<br />
*** +1 using item-license for news-brainstorming makes sense. [[User:Tantek|Tantek]] 22:32, 27 August 2009 (UTC)<br />
</div><br />
</div></div>JonathanMalekhttp://microformats.org/wiki/index.php?title=hnews&diff=43412hnews2010-12-28T21:32:14Z<p>JonathanMalek: Accepted clarifying language on definition of principles, based on Martinjemoore's clarifications, with input from JonathanMalek and Tantek.</p>
<hr />
<div><entry-title>hNews 0.1</entry-title><br />
{{Template:DraftSpecification}}<br />
<br />
hNews is 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, [[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.<br />
__TOC__<br />
== Draft Specification ==<br />
<br />
;Editor/Author<br />
:[[:User:JonathanMalek|Jonathan Malek]] ([http://www.ap.org Associated Press])<br />
<br />
;Contributors<br />
:[[:User:Smyles|Stuart Myles]] ([http://www.ap.org Associated Press]) <br />
:[[:User:Martinjemoore|Martin Moore]] ([http://mediastandardstrust.org Media Standards Trust])<br />
:[[:User:MarkNg|Mark Ng]] ([http://mediastandardstrust.org Media Standards Trust])<br />
:[[:User:Tbmartinwiki|Todd B. Martin]] ([http://www.ap.org Associated Press])<br />
<br />
=== Copyright ===<br />
Per the public domain release on the authors' user pages ([[:User:JonathanMalek|Jonathan Malek]]) this specification is released into the public domain. <br />
<br />
{{MicroFormatPublicDomainContributionStatement}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Introduction ==<br />
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.<br />
<br />
{{rfc-2119-intro}}<br />
<br />
== Semantic XHTML Design Principles ==<br />
{{semantic-xhtml-design-principles}}<br />
<br />
== Format ==<br />
=== In General ===<br />
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.<br />
<br />
=== Schema ===<br />
The hNews schema consists of the following: <br />
<br />
* hNews ('''<code>hnews</code>''') and '''<code>hentry</code>'''. required. Using [[hAtom]].<br />
** '''<code>source-org</code>'''. required. Using [[hCard]].[*]<br />
** '''<code>dateline</code>'''. optional. Using text or [[hCard]].<br />
** '''<code>geo</code>'''. optional. Using [[geo]].[*]<br />
** '''<code>item-license</code>'''. recommended. Using a [[licensing-brainstorming#item_as_container|brainstorm proposal]].<br />
** '''<code>principles</code>'''. recommended. Using the draft microformat [[principles-brainstorming#rel-principles_specification|rel-principles]].<br />
<br />
[*] Some required elements have defaults if missing, see below.<br />
<br />
=== Field and Element Details ===<br />
<br />
==== hAtom Fields ====<br />
<br />
===== Entry =====<br />
* an hNews story {{must}} be encoded as an [[hAtom]] <code>hentry</code>.<br />
* if an hNews story cannot be parsed as an [[hAtom]] <code>hentry</code>, it is invalid hNews.<br />
<br />
==== Additional Fields ====<br />
<br />
===== Source Organization =====<br />
* a Source Organization element is identified by the class name <code>source-org</code>.<br />
* Source Organization represents the originating organization for the news story.<br />
* a Source Organization {{must}} be encoded in an [[hCard]].<br />
* if the Source Organization is missing <br />
** find the [[algorithm-nearest-in-parent]] element(s) with class name <code>source-org</code> and that is/are a valid [[hCard]]<br />
** otherwise the entry is invalid hNews<br />
<br />
===== Dateline =====<br />
* a dateline element is identified by the class name <code>dateline</code>.<br />
* dateline represents the location where the news story was written or filed (see [http://en.wikipedia.org/wiki/Dateline dateline] for more details).<br />
* a dateline element {{may}} be encoded with an [[adr]], [[geo]] or [[hCard]].<br />
* a news story {{should}} have a dateline element.<br />
* dateline sometimes also includes the publish date of the news story. In such cases, use the [[datetime-design-pattern]] to encode the date.<br />
<br />
===== Geo =====<br />
* a geo element is identified by the class name <code>geo</code><br />
* geo represents the geographic coordinates of relevant locations in the news story.<br />
* a geo element should be encoded in a [[geo]].<br />
* 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).<br />
<br />
===== License =====<br />
* a license element is identified by the rel value of <code>item-license</code>.<br />
* a license element {{must}} be encoded as described in this [http://microformats.org/wiki/licensing-brainstorming#item_as_container license brainstorm proposal].<br />
* a news story {{should}} include a license element.<br />
<br />
===== Principles =====<br />
* a principles element is identified by <code>rel-principles</code>.<br />
* 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.<br />
* a principles element {{must}} be encoded in [[principles-brainstorming#rel-principles_specification|rel-principles]].<br />
* a news story {{should}} include principles.<br />
* principles {{should}} be linked to using the icons http://labs.ap.org/principles-button-blue.png or http://labs.ap.org/principles-book-blue.png.<br />
<br />
=== XMDP Profile ===<br />
<source lang=html4strict><br />
<dl class="profile"><br />
<br />
<dt>class</dt><br />
<dd><br />
<p><a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class"><br />
HTML4 definition of the 'class' attribute.</a><br />
This meta data profile defines some 'class' attribute values (class names) <br />
and their meanings as suggested by a <br />
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">draft of<br />
"Hypertext Links in HTML"</a>.</p><br />
<dl><br />
<br />
<dt>hnews</dt><br />
<dd>Used to describe semantic information associated with news stories.</dd><br />
<br />
<dt>source-org</dt><br />
<dd>The originating organization for the news story.</dd><br />
<br />
<dt>dateline</dt><br />
<dd>Represents the location where the news story was filed.</dd><br />
<br />
<dt>geo</dt><br />
<dd>Represents geographic coordinates of relevant locations in the story.</dd><br />
<br />
</dl><br />
</dd><br />
<br />
<dt>rel</dt><br />
<dd><br />
<dl><br />
<br />
<dt>item-license</dt><br />
<dd>Represents the license for the story.</dd><br />
<br />
<dt>principles</dt><br />
<dd>Represents the statement of principles and ethics used by the news organization that produced the news story.</dd><br />
<br />
</dl><br />
</dd><br />
<br />
</dl><br />
</source><br />
<br />
== Examples ==<br />
<br />
See [[hnews-examples]].<br />
<br />
=== Examples in the wild ===<br />
<br />
See [[hnews-examples-in-wild]].<br />
<br />
== Implementations ==<br />
<br />
== References ==<br />
<br />
=== Normative References ===<br />
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0]<br />
* [[hatom|hAtom]]<br />
* [[hcard|hCard]]<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [[rel-tag]]<br />
* [[geo]]<br />
* [[licensing-brainstorming#item_as_container_license|item-license brainstorm]]<br />
* [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles]<br />
* [http://www.ietf.org/rfc/rfc2119.txt RFC2119]<br />
* [http://www.ietf.org/rfc/rfc4287.txt RFC4287] (Atom 1.0)<br />
<br />
=== Informative References ===<br />
* Other news efforts: see [[news-formats]].<br />
<br />
== Work in progress ==<br />
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. <br />
<br />
=== Version 0.1 ===<br />
<br />
Version 0.1 was drafted August 2008.<br />
<br />
== Further Reading ==<br />
* See [http://www.technorati.com/cosmos/referer.html blogs discussing this page].<br />
<br />
== Related Pages ==<br />
* hnews<br />
* [[news-brainstorming]]: thoughts for improving hNews. <br />
* [[hnews-faq|hNews FAQ]]: if you have any questions about hNews, check here, and if you don't find answers, add your questions!<br />
* [[hnews-issues]]: please add any issues with the specification to the issues page.<br />
* [[news-formats]]: existing news and news management schemas.<br />
* [[news-examples]]: examples of news formats on the web.<br />
** [[hnews-examples]]: examples of how to implement hNews.<br />
<br />
[[Category:Draft Specifications]]<br />
[[Category:hNews]]</div>JonathanMalekhttp://microformats.org/wiki/index.php?title=hnews-issues&diff=43411hnews-issues2010-12-28T21:23:46Z<p>JonathanMalek: Updated MarkNg's open issue from 14 October 2009, to resolved.</p>
<hr />
<div><h1> hNews issues </h1><br />
<br />
__TOC__<br />
<br />
These are externally raised issues about [[hnews|hNews]] with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the draft. <br />
<br />
'''IMPORTANT''': Please read the [[hnews-faq|hNews FAQ]] before giving any feedback or raising any issues as your feedback/issues may already be resolved/answered.<br />
<br />
Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — [http://tantek.com/ Tantek]<br />
<br />
Please add new issues to the '''top''' of the list. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.<br />
<br />
See related [[hatom-issues]] and [[hcard-issues]].<br />
<br />
== Template ==<br />
<br />
{{issues-format}}<br />
<br />
<br />
== Issues ==<br />
=== Open Issues ===<br />
<br />
<div class="hentry"><br />
{{OpenIssue}} <span class="entry-summary author vcard"> <span class="published">2010-11-14</span> raised by <span class="fn">[[User:TobyInk|TobyInk]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Meaning of rel=principles</strong>. It's currently defined as "represents the statement of principles and ethics used by the news organization that produced the news story" - but are those the principles the ones used by the organisation at the time the article was written, or are they the principles that are being used by the organisation currently? If the latter, this property might be better as an extension to hCard. Either way, I think it should be clarified.<br />
** An interesting distinction, and not one I think that was discussed at any point, as far as I can see in my notes. I agree, clarification is needed. I have a feeling that the second option (the principles that are being used by the organization currently) is much simpler, and so more likely to be used. I also agree in part with your point about extending hCard in that case, as the principles apply to the [http://microformats.org/wiki/hnews#Additional_Fields source-org], rather than to the article itself. However, what about those cases where the source organization applies different principles for different types of content? For instance, an opinion piece? [[User:JonathanMalek|JonathanMalek]] 04:45, 15 November 2010 (UTC)<br />
** Good question Toby. The underlying basis of rel-principles has always been 'the principles that apply to this article'. Therefore if the article was written and published under certain principles then it should link to those principles even if the principles of the organisation subsequently change. The purpose of this is so that the reader can always tell under what principles a particular item of news was produced. Therefore rel-principles has to remain flexible by article rather than by author. For this reason I think it is better that it remain part of hNews rather than as an extension to hCard [[User:Martinjemoore|Martin Moore]] 16 November 2010<br />
*** This was the interpretation I'd always assumed, and hoped was the case as it seems most useful. Could somebody update the [[hnews]] page on the wiki to clarify the definition? [[User:TobyInk|TobyInk]] 10:34, 30 November 2010 (UTC)<br />
*** So the proposal as it stands is to change: <blockquote><p>* principles represents the statement of principles and ethics used by the news organization that produced the news story.</p></blockquote> to:<blockquote><p>* 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''.</p></blockquote> I will let this sit for a bit, and if there are no objections, I will update the [[hnews]] page. [[User:JonathanMalek|JonathanMalek]] 15:23, 5 December 2010 (UTC)<br />
*** +1 on JonathanMalek's proposed resolution and changes. - [[User:Tantek|Tantek]] 22:23, 5 December 2010 (UTC)<br />
</div><br />
</div><br />
<div class="hentry"><br />
{{OpenIssue}} <span class="entry-summary author vcard"><span class="published">2010-03-29</span> raised by <span class="fn">[[User:Trondhuso|Trond Husø]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Add lead class/tag</strong>. An article consists of a title, lead and the body content. I would very much like to see the lead attribute/tag being added. I see two possible usages: 1) In a world of AJAX you could show the content related to the lead-part + Click here for more. When you click the link the rest of the article becomes visible. Or it can be used in parts where you load to a title/lead carousel. 2) In RSS/Atom the Lead-part is what you would like to see in the description part of the feed.<br />
** Trond, I really like the idea. I suggest taking a look at using [http://microformats.org/wiki/hAtom#Entry_Summary hAtom entry-summary] for this purpose. I feel the lead paragraph of the typical upside-pyramid-style news story is an ideal value for the [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#element.summary atom:summary] element. And, by re-using the hAtom conventions in this way, your news item will be semantically available to software focusing on both hAtom and hNews. The Associated Press interpreted Atom in this way, as illustrated by one of [http://hosted.ap.org/lineups/TOPHEADS-atom_0.3.xml?SITE=CAANG&SECTION=HOME AP's public Atom feeds]. [[User:gut1975|Guthrie Collin]] 14:25, 01 April 2010 (UTC)<br />
</div><br />
</div><br />
<br />
<div class="hentry"><br />
{{OpenIssue}} <span class="entry-summary author vcard"><span class="published">2009-11-16</span> raised by <span class="fn">[[User:gut1975|Guthrie Collin]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Allowable number of item-licenses?</strong>. In the news world, different news companies sometimes share the copyright on specific works, and this arrangement results in two copyright statements appearing for one piece of content. Modeling this relationship in the hNews world would result in two or more "item-license" elements, with each item-license element potentially linking to a separate license for each news company. Hence, I think the hNews format should explicitly allow more than one item-license for each "hnews hentry" container. Thoughts?<br />
** If as you say "In the news world, different news companies sometimes share the copyright on specific works, and this arrangement results in two copyright statements appearing for one piece of content" then please provide URLs to real world examples that demonstrate as such. Absent any such examples, we must not change hNews for an otherwise assumed to be theoretical example, per microformats [[process]] and [[principles]]. [[User:Tantek|Tantek]] 23:51, 16 November 2009 (UTC)<br />
** Some examples are:<blockquote><p>[http://sports.yahoo.com/nhl/preview?gid=2006122911 Capitals-Devils Preview on Yahoo!] which was created under a joint arrangement between AP and STATS, Inc (scroll to page bottom).</p><p>[http://www.kcbd.com/global/story.asp?s=11520396 Colo. medical pot & taxes on KCBD 11 in Lubbock, TX] which was an AP story but since AP and some of its customers have special copyright arrangements, KCBD and its parent company also share copyright on the content (see bottom of page).</p></blockquote>As you can see, it's somewhat inefficient to have the license separate from the content in this way, and I think the hNews schema should permit multiple item-license elements for these situations. [[User:gut1975|Guthrie Collin]] 16:21, 17 November 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<div class="hentry"><br />
{{OpenIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-20</span> raised by <span class="fn">[[User:MilesD|Miles De Feyter]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">News, Commentary, and Opinion pieces as they relate to hNews</strong>. An interesting comment came up today when looking at how to use hNews on other AOL properties outside of our main news site, and that is, some of our sites are both news and commentary. Let's take our sports site for example http://www.fanhouse.com/ <br />
<br />
This site reports on sports news with article headlines such as: <br />
[http://www.fanhouse.com/news/nfl/big-ben-tops-pass-rankings/723353 Big Ben tops pass rankings]<br />
<br />
But fanhouse.com also has some obvious opinion pieces such as:<br />
[http://kevin-blackistone.fanhouse.com/2009/10/19/ail-to-the-redskins-worst-run-franchise-on-the-planet/ Fail to the Redskins: Worst-Run Franchise on the Planet]<br />
<br />
Currently we have one publishing system for all of our content within Fanhouse whether it be feed driven, in house publisher, news content, or commentary. So at the moment if one thing gets hNews it all does. <br />
<br />
Have you given this situation thought? My initial thinking is that perhaps this is where a principles statement specific to Fanhouse could account for the different types of content being labeled hNews. <br />
** Very glad you brought this up. We've given this alot of thought. I think your initial thinking is right. Right now the place to distinguish differences such as these (e.g. reporting from opinion) is within the principles statement. But this is something I think would benefit significantly from further development (i.e. the development of additional hNews criteria) [[User:Martinjemoore|Martin Moore]]<br />
** I believe that hNews is applicable to many types of news, ranging from reporting facts, to analysis pieces, opinion and columns. It is not unusual for a given piece of news to be a mix of two or three "types". Really, the purpose of hNews is allow for the common structural components of news to be more clearly marked up. The exact content is less important than the form. However, I also see that there is also value for a publisher of hNews to be able to self-classify the "type" of content. One way to do this would be to use rel-tag to indicate how the publisher would like to describe the hNews-encoded content (as commentary, opinion, analysis, interview, satire or whatever). [[User:Smyles|Stuart Myles]]<br />
</div><br />
</div><br />
<br />
=== Resolved Issues ===<br />
<br />
<div class="hentry"><br />
{{ResolvedIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-14</span> raised by <span class="fn">[[User:MarkNg|MarkNg]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">adr for dateline</strong>. From [http://twitter.com/pigsonthewing/status/4831500605 Andy Mabbett on Twitter] : hNews microformat spec "dateline. optional. Using text or hCard" should read "dateline. optional. Using text, adr or hCard".<br />
** Seems like a useful extra to me, any objections ? [[User:MarkNg|MarkNg]]<br />
** Agreed, makes sense. --[[User:JonathanMalek|JonathanMalek]] 00:57, 15 October 2009 (UTC)<br />
** +1 to addition of optional "adr" markup of "dateline", but should also allow "geo" markup of "dateline" as well. i.e. change: <blockquote><p>* a dateline element MAY be encoded in an hCard.</p></blockquote> to <blockquote><p>* a dateline element MAY be encoded with an [[adr]], [[geo]], or [[hCard]] on the same element.</p></blockquote> [[User:Tantek|Tantek]] 19:57, 15 October 2009 (UTC)<br />
** ACCEPTED SPEC UPDATE. ADDED: [[User:Tantek|Tantek]]'s recommendation from 15 October 2009.<br />
</div><br />
</div><br />
<br />
<div class="hentry"><br />
{{ResolvedIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-15</span> raised by <span class="fn">[[User:TobyInk|TobyInk]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">XMDP defines 'principles' incorrectly.</strong> The XMDP for hNews defines 'principles' as a class, whereas the rest of the draft refers to it as a link type (i.e. 'rel' value).<br />
** ACCEPTED SPEC UPDATE. FIXED: thanks for pointing that out. I believe the updated profile reflects that correctly now. --[[User:JonathanMalek|JonathanMalek]] 15:37, 15 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<div class="hentry"><br />
{{ResolvedIssue}} <span class="entry-summary author vcard"><span class="published">2009-11-13</span> raised by <span class="fn">[[User:gut1975|Guthrie Collin]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">The item-license element is incorrectly described as a class</strong>. The XMDP profile and element description for item-license in hNews describes the element as a class attribute value, however, the [http://microformats.org/wiki/licensing-brainstorming#item_as_container Licensing Brainstorming] proposal describes this field as a link type. In addition, the hNews examples purport item-license as a link type. Which item-license description is correct? <br />
** ACCEPTED SPEC UPDATE. FIXED: the correct description is as a link (rel). The profile has been updated to reflect that correctly. --[[User:JonathanMalek|JonathanMalek]] 18:44, 13 November 2009 (UTC)<br />
</div><br />
</div><br />
<br />
=== Closed Issues ===<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-09</span> raised by <span class="fn">Miles De Feyter</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Implementation of item-license as it relates to hNews</strong>. Reading through the item-license brainstorm it seems to indicate that "item-license" would need to be nested within something with the class of "item". So as this relates to hNews is the suggestion to then have an articles containing div have the three class names of "hnews hentry item"?<br />
** At this point, Miles, that is correct (following the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] concept and guidance). I expect we'll see changes around item-license (it's still just brainstorming), but for the time being, the third class name "item" is needed. --[[User:JonathanMalek|JonathanMalek]] 16:25, 12 October 2009 (UTC)<br />
** Added to [[hnews-faq]] --[[User:JonathanMalek|JonathanMalek]] 02:19, 14 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">2009-09-28</span> raised by <span class="fn">[[User:MilesD|Miles De Feyter]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Principles as a requirement</strong>. Working for a publishing company that owns and operates a large number of different organizations I'd love to incorporate hNews within our publishing system. The hNews requirement for a principles statement could pose a problem though or at least make rolling out hNews a more involved process then it would be otherwise. The issue is, I would now have to go to each product owner and ask then to provide this principles statement to link to. So my concern is now rather then just making a change to the publishing system to support hNews there is this requirement for some supporting content. And due to the nature of the content I can only assume our legal dep. would need to sign off as well, further complicating the adoption of hNews.<br />
** +1 I agree that the "principles" property (and probably all other others) should be optional. [[User:Tantek|Tantek]] 18:29, 29 September 2009 (UTC)<br />
*** I think it's important to explain why principles is a requirement. hnews is essentially a specialization of hAtom. Its purpose is to distinguish news on the web. Hence the description of source organisation, license and principles. Of these, principles is the only one which consistently distinguishes news on the web from other content (eg. commercial, government). In the future it should be distinguished further by making the principles themselves machine readable (but that is for a later date). Most professional news organisations adhere to a Statement of Principles (e.g. see http://en.wikipedia.org/wiki/Journalism_ethics_and_standards and http://www.journalism.org/resources/ethics_codes). If a site wants to mark up its content but does not want to distinguish it as news, then wouldn't it be easiest to use hAtom? [[User:martinjemoore|Martin Moore]] 9:00, 20 September 2009 (UTC)<br />
*** Having discussed this issue at length outside this brainstorming, we understand some of the concerns of the microformat community regarding 'must', but are still convinced of the criticality of principles to hNews - therefore recommend downgrading from 'must' to 'should'. [[User:martinjemoore|Martin Moore]] 14:00, 7 October 2009 (UTC)<br />
**** Accepted and implemented in 0.1. In keeping with the general direction here, we've changed <code>item-license</code> as well, and would consider adopting the same with <code>source-org</code> as well, if it proves to present the same problems. --[[User:JonathanMalek|JonathanMalek]] 00:53, 15 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">hCalendar instead of dateline?</strong> Would an [[hCalendar]] event (which can contain an hCard location) make sense for a dateline, or is the 'date' part more often omitted?<br />
** Confusingly, the journalistic term "dateline" isn't anything to do with a date or time. It is the location from which a report is filed and is generally the main location associated with a story. Generally, a dateline consists of a city (e.g. "Rome") but could be the name of a ship at sea or even a space station. [[User:Stuart Myles|Stuart Myles]] 21:12, 24 August 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">hCard instead of geo?</strong> Is geo really in use here, or would using an hCard (that can contain geo) be a better way of representing locations referred to in the story, as more human readable?<br />
** The reason for geo being highlighted (as an optional field) is to promote at least one location identifier in the story--preferably the most appropriate single location on a map for that particular story. Geo does not have to be related to dateline, but in some [http://labs.ap.org/wiki/hNews examples] we've worked on, we show the two collapsed into a single field. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)<br />
** For locations referred to in the story, I agree--publishers should be using [[hCard]] with the contained geo to markup the locations themselves. One of the concepts I've struggled with is drawing an admittedly arbitrary line between the metadata ''about'' a story from the metadata ''within'' a story. For the former, we've focused on simplicity and minimalism, primarily as a means to encourage adoption. That has meant preferring [[rel-tag]] over in-line entity extraction and markup using compound microformats. For the latter, we feel that the field is open: use whatever microformat fits your purpose, however you can--the more, the better. This lets publishers with minimal technology capabilities at least get started by tweaking a few templates in their CMS, while those more technically inclined aren't limited by the simplicity of the format to a paucity of data. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)<br />
** Also, dateline can be text or [[hCard]], as noted in the [[news-brainstorming#Common_News_Fields|Common News Fields]] section. --[[User:JonathanMalek|JonathanMalek]] 18:17, 24 September 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">What is item-license?</strong> Using [[rel-license]] presumably?<br />
** We're working off the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] discussions for this. Our concern with [[rel-license]] was its definition as applying to an entire page, rather than an item within a page. The current discussions around licensing definitely address that. --[[User:JonathanMalek|JonathanMalek]] 00:02, 25 August 2009 (UTC)<br />
*** +1 using item-license for news-brainstorming makes sense. [[User:Tantek|Tantek]] 22:32, 27 August 2009 (UTC)<br />
</div><br />
</div></div>JonathanMalekhttp://microformats.org/wiki/index.php?title=hnews&diff=43410hnews2010-12-28T21:15:48Z<p>JonathanMalek: Accepted "adr for dateline", raised 2009-10-04 on hnews-issues by MarkNg, with contributions from Tantek.</p>
<hr />
<div><entry-title>hNews 0.1</entry-title><br />
{{Template:DraftSpecification}}<br />
<br />
hNews is 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, [[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.<br />
__TOC__<br />
== Draft Specification ==<br />
<br />
;Editor/Author<br />
:[[:User:JonathanMalek|Jonathan Malek]] ([http://www.ap.org Associated Press])<br />
<br />
;Contributors<br />
:[[:User:Smyles|Stuart Myles]] ([http://www.ap.org Associated Press]) <br />
:[[:User:Martinjemoore|Martin Moore]] ([http://mediastandardstrust.org Media Standards Trust])<br />
:[[:User:MarkNg|Mark Ng]] ([http://mediastandardstrust.org Media Standards Trust])<br />
:[[:User:Tbmartinwiki|Todd B. Martin]] ([http://www.ap.org Associated Press])<br />
<br />
=== Copyright ===<br />
Per the public domain release on the authors' user pages ([[:User:JonathanMalek|Jonathan Malek]]) this specification is released into the public domain. <br />
<br />
{{MicroFormatPublicDomainContributionStatement}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Introduction ==<br />
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.<br />
<br />
{{rfc-2119-intro}}<br />
<br />
== Semantic XHTML Design Principles ==<br />
{{semantic-xhtml-design-principles}}<br />
<br />
== Format ==<br />
=== In General ===<br />
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.<br />
<br />
=== Schema ===<br />
The hNews schema consists of the following: <br />
<br />
* hNews ('''<code>hnews</code>''') and '''<code>hentry</code>'''. required. Using [[hAtom]].<br />
** '''<code>source-org</code>'''. required. Using [[hCard]].[*]<br />
** '''<code>dateline</code>'''. optional. Using text or [[hCard]].<br />
** '''<code>geo</code>'''. optional. Using [[geo]].[*]<br />
** '''<code>item-license</code>'''. recommended. Using a [[licensing-brainstorming#item_as_container|brainstorm proposal]].<br />
** '''<code>principles</code>'''. recommended. Using the draft microformat [[principles-brainstorming#rel-principles_specification|rel-principles]].<br />
<br />
[*] Some required elements have defaults if missing, see below.<br />
<br />
=== Field and Element Details ===<br />
<br />
==== hAtom Fields ====<br />
<br />
===== Entry =====<br />
* an hNews story {{must}} be encoded as an [[hAtom]] <code>hentry</code>.<br />
* if an hNews story cannot be parsed as an [[hAtom]] <code>hentry</code>, it is invalid hNews.<br />
<br />
==== Additional Fields ====<br />
<br />
===== Source Organization =====<br />
* a Source Organization element is identified by the class name <code>source-org</code>.<br />
* Source Organization represents the originating organization for the news story.<br />
* a Source Organization {{must}} be encoded in an [[hCard]].<br />
* if the Source Organization is missing <br />
** find the [[algorithm-nearest-in-parent]] element(s) with class name <code>source-org</code> and that is/are a valid [[hCard]]<br />
** otherwise the entry is invalid hNews<br />
<br />
===== Dateline =====<br />
* a dateline element is identified by the class name <code>dateline</code>.<br />
* dateline represents the location where the news story was written or filed (see [http://en.wikipedia.org/wiki/Dateline dateline] for more details).<br />
* a dateline element {{may}} be encoded with an [[adr]], [[geo]] or [[hCard]].<br />
* a news story {{should}} have a dateline element.<br />
* dateline sometimes also includes the publish date of the news story. In such cases, use the [[datetime-design-pattern]] to encode the date.<br />
<br />
===== Geo =====<br />
* a geo element is identified by the class name <code>geo</code><br />
* geo represents the geographic coordinates of relevant locations in the news story.<br />
* a geo element should be encoded in a [[geo]].<br />
* 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).<br />
<br />
===== License =====<br />
* a license element is identified by the rel value of <code>item-license</code>.<br />
* a license element {{must}} be encoded as described in this [http://microformats.org/wiki/licensing-brainstorming#item_as_container license brainstorm proposal].<br />
* a news story {{should}} include a license element.<br />
<br />
===== Principles =====<br />
* a principles element is identified by <code>rel-principles</code>.<br />
* principles represents the statement of principles and ethics used by the news organization that produced the news story.<br />
* a principles element {{must}} be encoded in [[principles-brainstorming#rel-principles_specification|rel-principles]].<br />
* a news story {{should}} include principles.<br />
* principles {{should}} be linked to using the icons http://labs.ap.org/principles-button-blue.png or http://labs.ap.org/principles-book-blue.png.<br />
<br />
=== XMDP Profile ===<br />
<source lang=html4strict><br />
<dl class="profile"><br />
<br />
<dt>class</dt><br />
<dd><br />
<p><a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class"><br />
HTML4 definition of the 'class' attribute.</a><br />
This meta data profile defines some 'class' attribute values (class names) <br />
and their meanings as suggested by a <br />
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">draft of<br />
"Hypertext Links in HTML"</a>.</p><br />
<dl><br />
<br />
<dt>hnews</dt><br />
<dd>Used to describe semantic information associated with news stories.</dd><br />
<br />
<dt>source-org</dt><br />
<dd>The originating organization for the news story.</dd><br />
<br />
<dt>dateline</dt><br />
<dd>Represents the location where the news story was filed.</dd><br />
<br />
<dt>geo</dt><br />
<dd>Represents geographic coordinates of relevant locations in the story.</dd><br />
<br />
</dl><br />
</dd><br />
<br />
<dt>rel</dt><br />
<dd><br />
<dl><br />
<br />
<dt>item-license</dt><br />
<dd>Represents the license for the story.</dd><br />
<br />
<dt>principles</dt><br />
<dd>Represents the statement of principles and ethics used by the news organization that produced the news story.</dd><br />
<br />
</dl><br />
</dd><br />
<br />
</dl><br />
</source><br />
<br />
== Examples ==<br />
<br />
See [[hnews-examples]].<br />
<br />
=== Examples in the wild ===<br />
<br />
See [[hnews-examples-in-wild]].<br />
<br />
== Implementations ==<br />
<br />
== References ==<br />
<br />
=== Normative References ===<br />
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0]<br />
* [[hatom|hAtom]]<br />
* [[hcard|hCard]]<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [[rel-tag]]<br />
* [[geo]]<br />
* [[licensing-brainstorming#item_as_container_license|item-license brainstorm]]<br />
* [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles]<br />
* [http://www.ietf.org/rfc/rfc2119.txt RFC2119]<br />
* [http://www.ietf.org/rfc/rfc4287.txt RFC4287] (Atom 1.0)<br />
<br />
=== Informative References ===<br />
* Other news efforts: see [[news-formats]].<br />
<br />
== Work in progress ==<br />
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. <br />
<br />
=== Version 0.1 ===<br />
<br />
Version 0.1 was drafted August 2008.<br />
<br />
== Further Reading ==<br />
* See [http://www.technorati.com/cosmos/referer.html blogs discussing this page].<br />
<br />
== Related Pages ==<br />
* hnews<br />
* [[news-brainstorming]]: thoughts for improving hNews. <br />
* [[hnews-faq|hNews FAQ]]: if you have any questions about hNews, check here, and if you don't find answers, add your questions!<br />
* [[hnews-issues]]: please add any issues with the specification to the issues page.<br />
* [[news-formats]]: existing news and news management schemas.<br />
* [[news-examples]]: examples of news formats on the web.<br />
** [[hnews-examples]]: examples of how to implement hNews.<br />
<br />
[[Category:Draft Specifications]]<br />
[[Category:hNews]]</div>JonathanMalekhttp://microformats.org/wiki/index.php?title=hnews-issues&diff=43365hnews-issues2010-12-05T15:23:59Z<p>JonathanMalek: Using language for Martin Moore to clarify principles definition (proposal)</p>
<hr />
<div><h1> hNews issues </h1><br />
<br />
__TOC__<br />
<br />
These are externally raised issues about [[hnews|hNews]] with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the draft. <br />
<br />
'''IMPORTANT''': Please read the [[hnews-faq|hNews FAQ]] before giving any feedback or raising any issues as your feedback/issues may already be resolved/answered.<br />
<br />
Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — [http://tantek.com/ Tantek]<br />
<br />
Please add new issues to the '''top''' of the list. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.<br />
<br />
See related [[hatom-issues]] and [[hcard-issues]].<br />
<br />
== Template ==<br />
<br />
{{issues-format}}<br />
<br />
<br />
== Issues ==<br />
=== Open Issues ===<br />
<br />
<div class="hentry"><br />
{{OpenIssue}} <span class="entry-summary author vcard"> <span class="published">2010-11-14</span> raised by <span class="fn">[[User:TobyInk|TobyInk]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Meaning of rel=principles</strong>. It's currently defined as "represents the statement of principles and ethics used by the news organization that produced the news story" - but are those the principles the ones used by the organisation at the time the article was written, or are they the principles that are being used by the organisation currently? If the latter, this property might be better as an extension to hCard. Either way, I think it should be clarified.<br />
** An interesting distinction, and not one I think that was discussed at any point, as far as I can see in my notes. I agree, clarification is needed. I have a feeling that the second option (the principles that are being used by the organization currently) is much simpler, and so more likely to be used. I also agree in part with your point about extending hCard in that case, as the principles apply to the [http://microformats.org/wiki/hnews#Additional_Fields source-org], rather than to the article itself. However, what about those cases where the source organization applies different principles for different types of content? For instance, an opinion piece? [[User:JonathanMalek|JonathanMalek]] 04:45, 15 November 2010 (UTC)<br />
** Good question Toby. The underlying basis of rel-principles has always been 'the principles that apply to this article'. Therefore if the article was written and published under certain principles then it should link to those principles even if the principles of the organisation subsequently change. The purpose of this is so that the reader can always tell under what principles a particular item of news was produced. Therefore rel-principles has to remain flexible by article rather than by author. For this reason I think it is better that it remain part of hNews rather than as an extension to hCard [[User:Martinjemoore|Martin Moore]] 16 November 2010<br />
*** This was the interpretation I'd always assumed, and hoped was the case as it seems most useful. Could somebody update the [[hnews]] page on the wiki to clarify the definition? [[User:TobyInk|TobyInk]] 10:34, 30 November 2010 (UTC)<br />
*** So the proposal as it stands is to change: <blockquote><p>* principles represents the statement of principles and ethics used by the news organization that produced the news story.</p></blockquote> to:<blockquote><p>* 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''.</p></blockquote> I will let this sit for a bit, and if there are no objections, I will update the [[hnews]] page. [[User:JonathanMalek|JonathanMalek]] 15:23, 5 December 2010 (UTC)<br />
</div><br />
</div><br />
<div class="hentry"><br />
{{OpenIssue}} <span class="entry-summary author vcard"><span class="published">2010-03-29</span> raised by <span class="fn">[[User:Trondhuso|Trond Husø]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Add lead class/tag</strong>. An article consists of a title, lead and the body content. I would very much like to see the lead attribute/tag being added. I see two possible usages: 1) In a world of AJAX you could show the content related to the lead-part + Click here for more. When you click the link the rest of the article becomes visible. Or it can be used in parts where you load to a title/lead carousel. 2) In RSS/Atom the Lead-part is what you would like to see in the description part of the feed.<br />
** Trond, I really like the idea. I suggest taking a look at using [http://microformats.org/wiki/hAtom#Entry_Summary hAtom entry-summary] for this purpose. I feel the lead paragraph of the typical upside-pyramid-style news story is an ideal value for the [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#element.summary atom:summary] element. And, by re-using the hAtom conventions in this way, your news item will be semantically available to software focusing on both hAtom and hNews. The Associated Press interpreted Atom in this way, as illustrated by one of [http://hosted.ap.org/lineups/TOPHEADS-atom_0.3.xml?SITE=CAANG&SECTION=HOME AP's public Atom feeds]. [[User:gut1975|Guthrie Collin]] 14:25, 01 April 2010 (UTC)<br />
</div><br />
</div><br />
<br />
<div class="hentry"><br />
{{OpenIssue}} <span class="entry-summary author vcard"><span class="published">2009-11-16</span> raised by <span class="fn">[[User:gut1975|Guthrie Collin]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Allowable number of item-licenses?</strong>. In the news world, different news companies sometimes share the copyright on specific works, and this arrangement results in two copyright statements appearing for one piece of content. Modeling this relationship in the hNews world would result in two or more "item-license" elements, with each item-license element potentially linking to a separate license for each news company. Hence, I think the hNews format should explicitly allow more than one item-license for each "hnews hentry" container. Thoughts?<br />
** If as you say "In the news world, different news companies sometimes share the copyright on specific works, and this arrangement results in two copyright statements appearing for one piece of content" then please provide URLs to real world examples that demonstrate as such. Absent any such examples, we must not change hNews for an otherwise assumed to be theoretical example, per microformats [[process]] and [[principles]]. [[User:Tantek|Tantek]] 23:51, 16 November 2009 (UTC)<br />
** Some examples are:<blockquote><p>[http://sports.yahoo.com/nhl/preview?gid=2006122911 Capitals-Devils Preview on Yahoo!] which was created under a joint arrangement between AP and STATS, Inc (scroll to page bottom).</p><p>[http://www.kcbd.com/global/story.asp?s=11520396 Colo. medical pot & taxes on KCBD 11 in Lubbock, TX] which was an AP story but since AP and some of its customers have special copyright arrangements, KCBD and its parent company also share copyright on the content (see bottom of page).</p></blockquote>As you can see, it's somewhat inefficient to have the license separate from the content in this way, and I think the hNews schema should permit multiple item-license elements for these situations. [[User:gut1975|Guthrie Collin]] 16:21, 17 November 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<div class="hentry"><br />
{{OpenIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-20</span> raised by <span class="fn">[[User:MilesD|Miles De Feyter]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">News, Commentary, and Opinion pieces as they relate to hNews</strong>. An interesting comment came up today when looking at how to use hNews on other AOL properties outside of our main news site, and that is, some of our sites are both news and commentary. Let's take our sports site for example http://www.fanhouse.com/ <br />
<br />
This site reports on sports news with article headlines such as: <br />
[http://www.fanhouse.com/news/nfl/big-ben-tops-pass-rankings/723353 Big Ben tops pass rankings]<br />
<br />
But fanhouse.com also has some obvious opinion pieces such as:<br />
[http://kevin-blackistone.fanhouse.com/2009/10/19/ail-to-the-redskins-worst-run-franchise-on-the-planet/ Fail to the Redskins: Worst-Run Franchise on the Planet]<br />
<br />
Currently we have one publishing system for all of our content within Fanhouse whether it be feed driven, in house publisher, news content, or commentary. So at the moment if one thing gets hNews it all does. <br />
<br />
Have you given this situation thought? My initial thinking is that perhaps this is where a principles statement specific to Fanhouse could account for the different types of content being labeled hNews. <br />
** Very glad you brought this up. We've given this alot of thought. I think your initial thinking is right. Right now the place to distinguish differences such as these (e.g. reporting from opinion) is within the principles statement. But this is something I think would benefit significantly from further development (i.e. the development of additional hNews criteria) [[User:Martinjemoore|Martin Moore]]<br />
** I believe that hNews is applicable to many types of news, ranging from reporting facts, to analysis pieces, opinion and columns. It is not unusual for a given piece of news to be a mix of two or three "types". Really, the purpose of hNews is allow for the common structural components of news to be more clearly marked up. The exact content is less important than the form. However, I also see that there is also value for a publisher of hNews to be able to self-classify the "type" of content. One way to do this would be to use rel-tag to indicate how the publisher would like to describe the hNews-encoded content (as commentary, opinion, analysis, interview, satire or whatever). [[User:Smyles|Stuart Myles]]<br />
</div><br />
</div><br />
<br />
<div class="hentry"><br />
{{OpenIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-14</span> raised by <span class="fn">[[User:MarkNg|MarkNg]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">adr for dateline</strong>. From [http://twitter.com/pigsonthewing/status/4831500605 Andy Mabbett on Twitter] : hNews microformat spec "dateline. optional. Using text or hCard" should read "dateline. optional. Using text, adr or hCard".<br />
** Seems like a useful extra to me, any objections ? [[User:MarkNg|MarkNg]]<br />
** Agreed, makes sense. --[[User:JonathanMalek|JonathanMalek]] 00:57, 15 October 2009 (UTC)<br />
** +1 to addition of optional "adr" markup of "dateline", but should also allow "geo" markup of "dateline" as well. i.e. change: <blockquote><p>* a dateline element MAY be encoded in an hCard.</p></blockquote> to <blockquote><p>* a dateline element MAY be encoded with an [[adr]], [[geo]], or [[hCard]] on the same element.</p></blockquote> [[User:Tantek|Tantek]] 19:57, 15 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
=== Resolved Issues ===<br />
<br />
<div class="hentry"><br />
{{ResolvedIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-15</span> raised by <span class="fn">[[User:TobyInk|TobyInk]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">XMDP defines 'principles' incorrectly.</strong> The XMDP for hNews defines 'principles' as a class, whereas the rest of the draft refers to it as a link type (i.e. 'rel' value).<br />
** ACCEPTED SPEC UPDATE. FIXED: thanks for pointing that out. I believe the updated profile reflects that correctly now. --[[User:JonathanMalek|JonathanMalek]] 15:37, 15 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<div class="hentry"><br />
{{ResolvedIssue}} <span class="entry-summary author vcard"><span class="published">2009-11-13</span> raised by <span class="fn">[[User:gut1975|Guthrie Collin]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">The item-license element is incorrectly described as a class</strong>. The XMDP profile and element description for item-license in hNews describes the element as a class attribute value, however, the [http://microformats.org/wiki/licensing-brainstorming#item_as_container Licensing Brainstorming] proposal describes this field as a link type. In addition, the hNews examples purport item-license as a link type. Which item-license description is correct? <br />
** ACCEPTED SPEC UPDATE. FIXED: the correct description is as a link (rel). The profile has been updated to reflect that correctly. --[[User:JonathanMalek|JonathanMalek]] 18:44, 13 November 2009 (UTC)<br />
</div><br />
</div><br />
<br />
=== Closed Issues ===<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-09</span> raised by <span class="fn">Miles De Feyter</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Implementation of item-license as it relates to hNews</strong>. Reading through the item-license brainstorm it seems to indicate that "item-license" would need to be nested within something with the class of "item". So as this relates to hNews is the suggestion to then have an articles containing div have the three class names of "hnews hentry item"?<br />
** At this point, Miles, that is correct (following the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] concept and guidance). I expect we'll see changes around item-license (it's still just brainstorming), but for the time being, the third class name "item" is needed. --[[User:JonathanMalek|JonathanMalek]] 16:25, 12 October 2009 (UTC)<br />
** Added to [[hnews-faq]] --[[User:JonathanMalek|JonathanMalek]] 02:19, 14 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">2009-09-28</span> raised by <span class="fn">[[User:MilesD|Miles De Feyter]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Principles as a requirement</strong>. Working for a publishing company that owns and operates a large number of different organizations I'd love to incorporate hNews within our publishing system. The hNews requirement for a principles statement could pose a problem though or at least make rolling out hNews a more involved process then it would be otherwise. The issue is, I would now have to go to each product owner and ask then to provide this principles statement to link to. So my concern is now rather then just making a change to the publishing system to support hNews there is this requirement for some supporting content. And due to the nature of the content I can only assume our legal dep. would need to sign off as well, further complicating the adoption of hNews.<br />
** +1 I agree that the "principles" property (and probably all other others) should be optional. [[User:Tantek|Tantek]] 18:29, 29 September 2009 (UTC)<br />
*** I think it's important to explain why principles is a requirement. hnews is essentially a specialization of hAtom. Its purpose is to distinguish news on the web. Hence the description of source organisation, license and principles. Of these, principles is the only one which consistently distinguishes news on the web from other content (eg. commercial, government). In the future it should be distinguished further by making the principles themselves machine readable (but that is for a later date). Most professional news organisations adhere to a Statement of Principles (e.g. see http://en.wikipedia.org/wiki/Journalism_ethics_and_standards and http://www.journalism.org/resources/ethics_codes). If a site wants to mark up its content but does not want to distinguish it as news, then wouldn't it be easiest to use hAtom? [[User:martinjemoore|Martin Moore]] 9:00, 20 September 2009 (UTC)<br />
*** Having discussed this issue at length outside this brainstorming, we understand some of the concerns of the microformat community regarding 'must', but are still convinced of the criticality of principles to hNews - therefore recommend downgrading from 'must' to 'should'. [[User:martinjemoore|Martin Moore]] 14:00, 7 October 2009 (UTC)<br />
**** Accepted and implemented in 0.1. In keeping with the general direction here, we've changed <code>item-license</code> as well, and would consider adopting the same with <code>source-org</code> as well, if it proves to present the same problems. --[[User:JonathanMalek|JonathanMalek]] 00:53, 15 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">hCalendar instead of dateline?</strong> Would an [[hCalendar]] event (which can contain an hCard location) make sense for a dateline, or is the 'date' part more often omitted?<br />
** Confusingly, the journalistic term "dateline" isn't anything to do with a date or time. It is the location from which a report is filed and is generally the main location associated with a story. Generally, a dateline consists of a city (e.g. "Rome") but could be the name of a ship at sea or even a space station. [[User:Stuart Myles|Stuart Myles]] 21:12, 24 August 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">hCard instead of geo?</strong> Is geo really in use here, or would using an hCard (that can contain geo) be a better way of representing locations referred to in the story, as more human readable?<br />
** The reason for geo being highlighted (as an optional field) is to promote at least one location identifier in the story--preferably the most appropriate single location on a map for that particular story. Geo does not have to be related to dateline, but in some [http://labs.ap.org/wiki/hNews examples] we've worked on, we show the two collapsed into a single field. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)<br />
** For locations referred to in the story, I agree--publishers should be using [[hCard]] with the contained geo to markup the locations themselves. One of the concepts I've struggled with is drawing an admittedly arbitrary line between the metadata ''about'' a story from the metadata ''within'' a story. For the former, we've focused on simplicity and minimalism, primarily as a means to encourage adoption. That has meant preferring [[rel-tag]] over in-line entity extraction and markup using compound microformats. For the latter, we feel that the field is open: use whatever microformat fits your purpose, however you can--the more, the better. This lets publishers with minimal technology capabilities at least get started by tweaking a few templates in their CMS, while those more technically inclined aren't limited by the simplicity of the format to a paucity of data. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)<br />
** Also, dateline can be text or [[hCard]], as noted in the [[news-brainstorming#Common_News_Fields|Common News Fields]] section. --[[User:JonathanMalek|JonathanMalek]] 18:17, 24 September 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">What is item-license?</strong> Using [[rel-license]] presumably?<br />
** We're working off the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] discussions for this. Our concern with [[rel-license]] was its definition as applying to an entire page, rather than an item within a page. The current discussions around licensing definitely address that. --[[User:JonathanMalek|JonathanMalek]] 00:02, 25 August 2009 (UTC)<br />
*** +1 using item-license for news-brainstorming makes sense. [[User:Tantek|Tantek]] 22:32, 27 August 2009 (UTC)<br />
</div><br />
</div></div>JonathanMalekhttp://microformats.org/wiki/index.php?title=hnews-issues&diff=43273hnews-issues2010-11-15T04:46:23Z<p>JonathanMalek: minor clean-ups</p>
<hr />
<div><h1> hNews issues </h1><br />
<br />
__TOC__<br />
<br />
These are externally raised issues about [[hnews|hNews]] with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the draft. <br />
<br />
'''IMPORTANT''': Please read the [[hnews-faq|hNews FAQ]] before giving any feedback or raising any issues as your feedback/issues may already be resolved/answered.<br />
<br />
Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — [http://tantek.com/ Tantek]<br />
<br />
Please add new issues to the '''top''' of the list. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.<br />
<br />
See related [[hatom-issues]] and [[hcard-issues]].<br />
<br />
== Template ==<br />
<br />
{{issues-format}}<br />
<br />
<br />
== Issues ==<br />
=== Open Issues ===<br />
<br />
<div class="hentry"><br />
{{OpenIssue}} <span class="entry-summary author vcard"> <span class="published">2010-11-14</span> raised by <span class="fn">[[User:TobyInk|TobyInk]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Meaning of rel=principles</strong>. It's currently defined as "represents the statement of principles and ethics used by the news organization that produced the news story" - but are those the principles the ones used by the organisation at the time the article was written, or are they the principles that are being used by the organisation currently? If the latter, this property might be better as an extension to hCard. Either way, I think it should be clarified.<br />
** An interesting distinction, and not one I think that was discussed at any point, as far as I can see in my notes. I agree, clarification is needed. I have a feeling that the second option (the principles that are being used by the organization currently) is much simpler, and so more likely to be used. I also agree in part with your point about extending hCard in that case, as the principles apply to the [http://microformats.org/wiki/hnews#Additional_Fields source-org], rather than to the article itself. However, what about those cases where the source organization applies different principles for different types of content? For instance, an opinion piece? [[User:JonathanMalek|JonathanMalek]] 04:45, 15 November 2010 (UTC)<br />
</div><br />
</div><br />
<div class="hentry"><br />
{{OpenIssue}} <span class="entry-summary author vcard"><span class="published">2010-03-29</span> raised by <span class="fn">[[User:Trondhuso|Trond Husø]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Add lead class/tag</strong>. An article consists of a title, lead and the body content. I would very much like to see the lead attribute/tag being added. I see two possible usages: 1) In a world of AJAX you could show the content related to the lead-part + Click here for more. When you click the link the rest of the article becomes visible. Or it can be used in parts where you load to a title/lead carousel. 2) In RSS/Atom the Lead-part is what you would like to see in the description part of the feed.<br />
** Trond, I really like the idea. I suggest taking a look at using [http://microformats.org/wiki/hAtom#Entry_Summary hAtom entry-summary] for this purpose. I feel the lead paragraph of the typical upside-pyramid-style news story is an ideal value for the [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#element.summary atom:summary] element. And, by re-using the hAtom conventions in this way, your news item will be semantically available to software focusing on both hAtom and hNews. The Associated Press interpreted Atom in this way, as illustrated by one of [http://hosted.ap.org/lineups/TOPHEADS-atom_0.3.xml?SITE=CAANG&SECTION=HOME AP's public Atom feeds]. [[User:gut1975|Guthrie Collin]] 14:25, 01 April 2010 (UTC)<br />
</div><br />
</div><br />
<br />
<div class="hentry"><br />
{{OpenIssue}} <span class="entry-summary author vcard"><span class="published">2009-11-16</span> raised by <span class="fn">[[User:gut1975|Guthrie Collin]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Allowable number of item-licenses?</strong>. In the news world, different news companies sometimes share the copyright on specific works, and this arrangement results in two copyright statements appearing for one piece of content. Modeling this relationship in the hNews world would result in two or more "item-license" elements, with each item-license element potentially linking to a separate license for each news company. Hence, I think the hNews format should explicitly allow more than one item-license for each "hnews hentry" container. Thoughts?<br />
** If as you say "In the news world, different news companies sometimes share the copyright on specific works, and this arrangement results in two copyright statements appearing for one piece of content" then please provide URLs to real world examples that demonstrate as such. Absent any such examples, we must not change hNews for an otherwise assumed to be theoretical example, per microformats [[process]] and [[principles]]. [[User:Tantek|Tantek]] 23:51, 16 November 2009 (UTC)<br />
** Some examples are:<blockquote><p>[http://sports.yahoo.com/nhl/preview?gid=2006122911 Capitals-Devils Preview on Yahoo!] which was created under a joint arrangement between AP and STATS, Inc (scroll to page bottom).</p><p>[http://www.kcbd.com/global/story.asp?s=11520396 Colo. medical pot & taxes on KCBD 11 in Lubbock, TX] which was an AP story but since AP and some of its customers have special copyright arrangements, KCBD and its parent company also share copyright on the content (see bottom of page).</p></blockquote>As you can see, it's somewhat inefficient to have the license separate from the content in this way, and I think the hNews schema should permit multiple item-license elements for these situations. [[User:gut1975|Guthrie Collin]] 16:21, 17 November 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<div class="hentry"><br />
{{OpenIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-20</span> raised by <span class="fn">[[User:MilesD|Miles De Feyter]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">News, Commentary, and Opinion pieces as they relate to hNews</strong>. An interesting comment came up today when looking at how to use hNews on other AOL properties outside of our main news site, and that is, some of our sites are both news and commentary. Let's take our sports site for example http://www.fanhouse.com/ <br />
<br />
This site reports on sports news with article headlines such as: <br />
[http://www.fanhouse.com/news/nfl/big-ben-tops-pass-rankings/723353 Big Ben tops pass rankings]<br />
<br />
But fanhouse.com also has some obvious opinion pieces such as:<br />
[http://kevin-blackistone.fanhouse.com/2009/10/19/ail-to-the-redskins-worst-run-franchise-on-the-planet/ Fail to the Redskins: Worst-Run Franchise on the Planet]<br />
<br />
Currently we have one publishing system for all of our content within Fanhouse whether it be feed driven, in house publisher, news content, or commentary. So at the moment if one thing gets hNews it all does. <br />
<br />
Have you given this situation thought? My initial thinking is that perhaps this is where a principles statement specific to Fanhouse could account for the different types of content being labeled hNews. <br />
** Very glad you brought this up. We've given this alot of thought. I think your initial thinking is right. Right now the place to distinguish differences such as these (e.g. reporting from opinion) is within the principles statement. But this is something I think would benefit significantly from further development (i.e. the development of additional hNews criteria) [[User:Martinjemoore|Martin Moore]]<br />
** I believe that hNews is applicable to many types of news, ranging from reporting facts, to analysis pieces, opinion and columns. It is not unusual for a given piece of news to be a mix of two or three "types". Really, the purpose of hNews is allow for the common structural components of news to be more clearly marked up. The exact content is less important than the form. However, I also see that there is also value for a publisher of hNews to be able to self-classify the "type" of content. One way to do this would be to use rel-tag to indicate how the publisher would like to describe the hNews-encoded content (as commentary, opinion, analysis, interview, satire or whatever). [[User:Smyles|Stuart Myles]]<br />
</div><br />
</div><br />
<br />
<div class="hentry"><br />
{{OpenIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-14</span> raised by <span class="fn">[[User:MarkNg|MarkNg]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">adr for dateline</strong>. From [http://twitter.com/pigsonthewing/status/4831500605 Andy Mabbett on Twitter] : hNews microformat spec "dateline. optional. Using text or hCard" should read "dateline. optional. Using text, adr or hCard".<br />
** Seems like a useful extra to me, any objections ? [[User:MarkNg|MarkNg]]<br />
** Agreed, makes sense. --[[User:JonathanMalek|JonathanMalek]] 00:57, 15 October 2009 (UTC)<br />
** +1 to addition of optional "adr" markup of "dateline", but should also allow "geo" markup of "dateline" as well. i.e. change: <blockquote><p>* a dateline element MAY be encoded in an hCard.</p></blockquote> to <blockquote><p>* a dateline element MAY be encoded with an [[adr]], [[geo]], or [[hCard]] on the same element.</p></blockquote> [[User:Tantek|Tantek]] 19:57, 15 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
=== Resolved Issues ===<br />
<br />
<div class="hentry"><br />
{{ResolvedIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-15</span> raised by <span class="fn">[[User:TobyInk|TobyInk]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">XMDP defines 'principles' incorrectly.</strong> The XMDP for hNews defines 'principles' as a class, whereas the rest of the draft refers to it as a link type (i.e. 'rel' value).<br />
** ACCEPTED SPEC UPDATE. FIXED: thanks for pointing that out. I believe the updated profile reflects that correctly now. --[[User:JonathanMalek|JonathanMalek]] 15:37, 15 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<div class="hentry"><br />
{{ResolvedIssue}} <span class="entry-summary author vcard"><span class="published">2009-11-13</span> raised by <span class="fn">[[User:gut1975|Guthrie Collin]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">The item-license element is incorrectly described as a class</strong>. The XMDP profile and element description for item-license in hNews describes the element as a class attribute value, however, the [http://microformats.org/wiki/licensing-brainstorming#item_as_container Licensing Brainstorming] proposal describes this field as a link type. In addition, the hNews examples purport item-license as a link type. Which item-license description is correct? <br />
** ACCEPTED SPEC UPDATE. FIXED: the correct description is as a link (rel). The profile has been updated to reflect that correctly. --[[User:JonathanMalek|JonathanMalek]] 18:44, 13 November 2009 (UTC)<br />
</div><br />
</div><br />
<br />
=== Closed Issues ===<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-09</span> raised by <span class="fn">Miles De Feyter</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Implementation of item-license as it relates to hNews</strong>. Reading through the item-license brainstorm it seems to indicate that "item-license" would need to be nested within something with the class of "item". So as this relates to hNews is the suggestion to then have an articles containing div have the three class names of "hnews hentry item"?<br />
** At this point, Miles, that is correct (following the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] concept and guidance). I expect we'll see changes around item-license (it's still just brainstorming), but for the time being, the third class name "item" is needed. --[[User:JonathanMalek|JonathanMalek]] 16:25, 12 October 2009 (UTC)<br />
** Added to [[hnews-faq]] --[[User:JonathanMalek|JonathanMalek]] 02:19, 14 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">2009-09-28</span> raised by <span class="fn">[[User:MilesD|Miles De Feyter]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Principles as a requirement</strong>. Working for a publishing company that owns and operates a large number of different organizations I'd love to incorporate hNews within our publishing system. The hNews requirement for a principles statement could pose a problem though or at least make rolling out hNews a more involved process then it would be otherwise. The issue is, I would now have to go to each product owner and ask then to provide this principles statement to link to. So my concern is now rather then just making a change to the publishing system to support hNews there is this requirement for some supporting content. And due to the nature of the content I can only assume our legal dep. would need to sign off as well, further complicating the adoption of hNews.<br />
** +1 I agree that the "principles" property (and probably all other others) should be optional. [[User:Tantek|Tantek]] 18:29, 29 September 2009 (UTC)<br />
*** I think it's important to explain why principles is a requirement. hnews is essentially a specialization of hAtom. Its purpose is to distinguish news on the web. Hence the description of source organisation, license and principles. Of these, principles is the only one which consistently distinguishes news on the web from other content (eg. commercial, government). In the future it should be distinguished further by making the principles themselves machine readable (but that is for a later date). Most professional news organisations adhere to a Statement of Principles (e.g. see http://en.wikipedia.org/wiki/Journalism_ethics_and_standards and http://www.journalism.org/resources/ethics_codes). If a site wants to mark up its content but does not want to distinguish it as news, then wouldn't it be easiest to use hAtom? [[User:martinjemoore|Martin Moore]] 9:00, 20 September 2009 (UTC)<br />
*** Having discussed this issue at length outside this brainstorming, we understand some of the concerns of the microformat community regarding 'must', but are still convinced of the criticality of principles to hNews - therefore recommend downgrading from 'must' to 'should'. [[User:martinjemoore|Martin Moore]] 14:00, 7 October 2009 (UTC)<br />
**** Accepted and implemented in 0.1. In keeping with the general direction here, we've changed <code>item-license</code> as well, and would consider adopting the same with <code>source-org</code> as well, if it proves to present the same problems. --[[User:JonathanMalek|JonathanMalek]] 00:53, 15 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">hCalendar instead of dateline?</strong> Would an [[hCalendar]] event (which can contain an hCard location) make sense for a dateline, or is the 'date' part more often omitted?<br />
** Confusingly, the journalistic term "dateline" isn't anything to do with a date or time. It is the location from which a report is filed and is generally the main location associated with a story. Generally, a dateline consists of a city (e.g. "Rome") but could be the name of a ship at sea or even a space station. [[User:Stuart Myles|Stuart Myles]] 21:12, 24 August 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">hCard instead of geo?</strong> Is geo really in use here, or would using an hCard (that can contain geo) be a better way of representing locations referred to in the story, as more human readable?<br />
** The reason for geo being highlighted (as an optional field) is to promote at least one location identifier in the story--preferably the most appropriate single location on a map for that particular story. Geo does not have to be related to dateline, but in some [http://labs.ap.org/wiki/hNews examples] we've worked on, we show the two collapsed into a single field. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)<br />
** For locations referred to in the story, I agree--publishers should be using [[hCard]] with the contained geo to markup the locations themselves. One of the concepts I've struggled with is drawing an admittedly arbitrary line between the metadata ''about'' a story from the metadata ''within'' a story. For the former, we've focused on simplicity and minimalism, primarily as a means to encourage adoption. That has meant preferring [[rel-tag]] over in-line entity extraction and markup using compound microformats. For the latter, we feel that the field is open: use whatever microformat fits your purpose, however you can--the more, the better. This lets publishers with minimal technology capabilities at least get started by tweaking a few templates in their CMS, while those more technically inclined aren't limited by the simplicity of the format to a paucity of data. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)<br />
** Also, dateline can be text or [[hCard]], as noted in the [[news-brainstorming#Common_News_Fields|Common News Fields]] section. --[[User:JonathanMalek|JonathanMalek]] 18:17, 24 September 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">What is item-license?</strong> Using [[rel-license]] presumably?<br />
** We're working off the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] discussions for this. Our concern with [[rel-license]] was its definition as applying to an entire page, rather than an item within a page. The current discussions around licensing definitely address that. --[[User:JonathanMalek|JonathanMalek]] 00:02, 25 August 2009 (UTC)<br />
*** +1 using item-license for news-brainstorming makes sense. [[User:Tantek|Tantek]] 22:32, 27 August 2009 (UTC)<br />
</div><br />
</div></div>JonathanMalekhttp://microformats.org/wiki/index.php?title=hnews-issues&diff=43272hnews-issues2010-11-15T04:45:42Z<p>JonathanMalek: Response to "meaning of rel-principles"</p>
<hr />
<div><h1> hNews issues </h1><br />
<br />
__TOC__<br />
<br />
These are externally raised issues about [[hnews|hNews]] with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the draft. <br />
<br />
'''IMPORTANT''': Please read the [[hnews-faq|hNews FAQ]] before giving any feedback or raising any issues as your feedback/issues may already be resolved/answered.<br />
<br />
Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — [http://tantek.com/ Tantek]<br />
<br />
Please add new issues to the '''top''' of the list. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.<br />
<br />
See related [[hatom-issues]] and [[hcard-issues]].<br />
<br />
== Template ==<br />
<br />
{{issues-format}}<br />
<br />
<br />
== Issues ==<br />
=== Open Issues ===<br />
<br />
<div class="hentry"><br />
{{OpenIssue}} <span class="entry-summary author vcard"> <span class="published">2010-11-14</span> raised by <span class="fn">[[User:TobyInk|TobyInk]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Meaning of rel=principles</strong>. It's currently defined as "represents the statement of principles and ethics used by the news organization that produced the news story" - but are those the principles the ones used by the organisation at the time the article was written, or are they the principles that are being used by the organisation currently? If the latter, this property might be better as an extension to hCard. Either way, I think it should be clarified.</dd><br />
** An interesting distinction, and not one I think that was discussed at any point, as far as I can see in my notes. I agree, clarification is needed. I have a feeling that the second option (the principles that are being used by the organization currently) is much simpler, and so more likely to be used. I also agree in part with your point about extending hCard in that case, as the principles apply to the [http://microformats.org/wiki/hnews#Additional_Fields source-org], rather than to the article itself. However, what about those cases where the source organization applies different principles for different types of content? For instance, an opinion piece? [[User:JonathanMalek|JonathanMalek]] 04:45, 15 November 2010 (UTC)<br />
</div><br />
</div><br />
<div class="hentry"><br />
{{OpenIssue}} <span class="entry-summary author vcard"><span class="published">2010-03-29</span> raised by <span class="fn">[[User:Trondhuso|Trond Husø]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Add lead class/tag</strong>. An article consists of a title, lead and the body content. I would very much like to see the lead attribute/tag being added. I see two possible usages: 1) In a world of AJAX you could show the content related to the lead-part + Click here for more. When you click the link the rest of the article becomes visible. Or it can be used in parts where you load to a title/lead carousel. 2) In RSS/Atom the Lead-part is what you would like to see in the description part of the feed.<br />
** Trond, I really like the idea. I suggest taking a look at using [http://microformats.org/wiki/hAtom#Entry_Summary hAtom entry-summary] for this purpose. I feel the lead paragraph of the typical upside-pyramid-style news story is an ideal value for the [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#element.summary atom:summary] element. And, by re-using the hAtom conventions in this way, your news item will be semantically available to software focusing on both hAtom and hNews. The Associated Press interpreted Atom in this way, as illustrated by one of [http://hosted.ap.org/lineups/TOPHEADS-atom_0.3.xml?SITE=CAANG&SECTION=HOME AP's public Atom feeds]. [[User:gut1975|Guthrie Collin]] 14:25, 01 April 2010 (UTC)<br />
** Follow-up comment #2<br />
</div><br />
</div><br />
<br />
<div class="hentry"><br />
{{OpenIssue}} <span class="entry-summary author vcard"><span class="published">2009-11-16</span> raised by <span class="fn">[[User:gut1975|Guthrie Collin]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Allowable number of item-licenses?</strong>. In the news world, different news companies sometimes share the copyright on specific works, and this arrangement results in two copyright statements appearing for one piece of content. Modeling this relationship in the hNews world would result in two or more "item-license" elements, with each item-license element potentially linking to a separate license for each news company. Hence, I think the hNews format should explicitly allow more than one item-license for each "hnews hentry" container. Thoughts?<br />
** If as you say "In the news world, different news companies sometimes share the copyright on specific works, and this arrangement results in two copyright statements appearing for one piece of content" then please provide URLs to real world examples that demonstrate as such. Absent any such examples, we must not change hNews for an otherwise assumed to be theoretical example, per microformats [[process]] and [[principles]]. [[User:Tantek|Tantek]] 23:51, 16 November 2009 (UTC)<br />
** Some examples are:<blockquote><p>[http://sports.yahoo.com/nhl/preview?gid=2006122911 Capitals-Devils Preview on Yahoo!] which was created under a joint arrangement between AP and STATS, Inc (scroll to page bottom).</p><p>[http://www.kcbd.com/global/story.asp?s=11520396 Colo. medical pot & taxes on KCBD 11 in Lubbock, TX] which was an AP story but since AP and some of its customers have special copyright arrangements, KCBD and its parent company also share copyright on the content (see bottom of page).</p></blockquote>As you can see, it's somewhat inefficient to have the license separate from the content in this way, and I think the hNews schema should permit multiple item-license elements for these situations. [[User:gut1975|Guthrie Collin]] 16:21, 17 November 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<div class="hentry"><br />
{{OpenIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-20</span> raised by <span class="fn">[[User:MilesD|Miles De Feyter]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">News, Commentary, and Opinion pieces as they relate to hNews</strong>. An interesting comment came up today when looking at how to use hNews on other AOL properties outside of our main news site, and that is, some of our sites are both news and commentary. Let's take our sports site for example http://www.fanhouse.com/ <br />
<br />
This site reports on sports news with article headlines such as: <br />
[http://www.fanhouse.com/news/nfl/big-ben-tops-pass-rankings/723353 Big Ben tops pass rankings]<br />
<br />
But fanhouse.com also has some obvious opinion pieces such as:<br />
[http://kevin-blackistone.fanhouse.com/2009/10/19/ail-to-the-redskins-worst-run-franchise-on-the-planet/ Fail to the Redskins: Worst-Run Franchise on the Planet]<br />
<br />
Currently we have one publishing system for all of our content within Fanhouse whether it be feed driven, in house publisher, news content, or commentary. So at the moment if one thing gets hNews it all does. <br />
<br />
Have you given this situation thought? My initial thinking is that perhaps this is where a principles statement specific to Fanhouse could account for the different types of content being labeled hNews. <br />
** Very glad you brought this up. We've given this alot of thought. I think your initial thinking is right. Right now the place to distinguish differences such as these (e.g. reporting from opinion) is within the principles statement. But this is something I think would benefit significantly from further development (i.e. the development of additional hNews criteria) [[User:Martinjemoore|Martin Moore]]<br />
** I believe that hNews is applicable to many types of news, ranging from reporting facts, to analysis pieces, opinion and columns. It is not unusual for a given piece of news to be a mix of two or three "types". Really, the purpose of hNews is allow for the common structural components of news to be more clearly marked up. The exact content is less important than the form. However, I also see that there is also value for a publisher of hNews to be able to self-classify the "type" of content. One way to do this would be to use rel-tag to indicate how the publisher would like to describe the hNews-encoded content (as commentary, opinion, analysis, interview, satire or whatever). [[User:Smyles|Stuart Myles]]<br />
</div><br />
</div><br />
<br />
<div class="hentry"><br />
{{OpenIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-14</span> raised by <span class="fn">[[User:MarkNg|MarkNg]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">adr for dateline</strong>. From [http://twitter.com/pigsonthewing/status/4831500605 Andy Mabbett on Twitter] : hNews microformat spec "dateline. optional. Using text or hCard" should read "dateline. optional. Using text, adr or hCard".<br />
** Seems like a useful extra to me, any objections ? [[User:MarkNg|MarkNg]]<br />
** Agreed, makes sense. --[[User:JonathanMalek|JonathanMalek]] 00:57, 15 October 2009 (UTC)<br />
** +1 to addition of optional "adr" markup of "dateline", but should also allow "geo" markup of "dateline" as well. i.e. change: <blockquote><p>* a dateline element MAY be encoded in an hCard.</p></blockquote> to <blockquote><p>* a dateline element MAY be encoded with an [[adr]], [[geo]], or [[hCard]] on the same element.</p></blockquote> [[User:Tantek|Tantek]] 19:57, 15 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
=== Resolved Issues ===<br />
<br />
<div class="hentry"><br />
{{ResolvedIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-15</span> raised by <span class="fn">[[User:TobyInk|TobyInk]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">XMDP defines 'principles' incorrectly.</strong> The XMDP for hNews defines 'principles' as a class, whereas the rest of the draft refers to it as a link type (i.e. 'rel' value).<br />
** ACCEPTED SPEC UPDATE. FIXED: thanks for pointing that out. I believe the updated profile reflects that correctly now. --[[User:JonathanMalek|JonathanMalek]] 15:37, 15 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<div class="hentry"><br />
{{ResolvedIssue}} <span class="entry-summary author vcard"><span class="published">2009-11-13</span> raised by <span class="fn">[[User:gut1975|Guthrie Collin]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">The item-license element is incorrectly described as a class</strong>. The XMDP profile and element description for item-license in hNews describes the element as a class attribute value, however, the [http://microformats.org/wiki/licensing-brainstorming#item_as_container Licensing Brainstorming] proposal describes this field as a link type. In addition, the hNews examples purport item-license as a link type. Which item-license description is correct? <br />
** ACCEPTED SPEC UPDATE. FIXED: the correct description is as a link (rel). The profile has been updated to reflect that correctly. --[[User:JonathanMalek|JonathanMalek]] 18:44, 13 November 2009 (UTC)<br />
</div><br />
</div><br />
<br />
=== Closed Issues ===<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-09</span> raised by <span class="fn">Miles De Feyter</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Implementation of item-license as it relates to hNews</strong>. Reading through the item-license brainstorm it seems to indicate that "item-license" would need to be nested within something with the class of "item". So as this relates to hNews is the suggestion to then have an articles containing div have the three class names of "hnews hentry item"?<br />
** At this point, Miles, that is correct (following the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] concept and guidance). I expect we'll see changes around item-license (it's still just brainstorming), but for the time being, the third class name "item" is needed. --[[User:JonathanMalek|JonathanMalek]] 16:25, 12 October 2009 (UTC)<br />
** Added to [[hnews-faq]] --[[User:JonathanMalek|JonathanMalek]] 02:19, 14 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">2009-09-28</span> raised by <span class="fn">[[User:MilesD|Miles De Feyter]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Principles as a requirement</strong>. Working for a publishing company that owns and operates a large number of different organizations I'd love to incorporate hNews within our publishing system. The hNews requirement for a principles statement could pose a problem though or at least make rolling out hNews a more involved process then it would be otherwise. The issue is, I would now have to go to each product owner and ask then to provide this principles statement to link to. So my concern is now rather then just making a change to the publishing system to support hNews there is this requirement for some supporting content. And due to the nature of the content I can only assume our legal dep. would need to sign off as well, further complicating the adoption of hNews.<br />
** +1 I agree that the "principles" property (and probably all other others) should be optional. [[User:Tantek|Tantek]] 18:29, 29 September 2009 (UTC)<br />
*** I think it's important to explain why principles is a requirement. hnews is essentially a specialization of hAtom. Its purpose is to distinguish news on the web. Hence the description of source organisation, license and principles. Of these, principles is the only one which consistently distinguishes news on the web from other content (eg. commercial, government). In the future it should be distinguished further by making the principles themselves machine readable (but that is for a later date). Most professional news organisations adhere to a Statement of Principles (e.g. see http://en.wikipedia.org/wiki/Journalism_ethics_and_standards and http://www.journalism.org/resources/ethics_codes). If a site wants to mark up its content but does not want to distinguish it as news, then wouldn't it be easiest to use hAtom? [[User:martinjemoore|Martin Moore]] 9:00, 20 September 2009 (UTC)<br />
*** Having discussed this issue at length outside this brainstorming, we understand some of the concerns of the microformat community regarding 'must', but are still convinced of the criticality of principles to hNews - therefore recommend downgrading from 'must' to 'should'. [[User:martinjemoore|Martin Moore]] 14:00, 7 October 2009 (UTC)<br />
**** Accepted and implemented in 0.1. In keeping with the general direction here, we've changed <code>item-license</code> as well, and would consider adopting the same with <code>source-org</code> as well, if it proves to present the same problems. --[[User:JonathanMalek|JonathanMalek]] 00:53, 15 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">hCalendar instead of dateline?</strong> Would an [[hCalendar]] event (which can contain an hCard location) make sense for a dateline, or is the 'date' part more often omitted?<br />
** Confusingly, the journalistic term "dateline" isn't anything to do with a date or time. It is the location from which a report is filed and is generally the main location associated with a story. Generally, a dateline consists of a city (e.g. "Rome") but could be the name of a ship at sea or even a space station. [[User:Stuart Myles|Stuart Myles]] 21:12, 24 August 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">hCard instead of geo?</strong> Is geo really in use here, or would using an hCard (that can contain geo) be a better way of representing locations referred to in the story, as more human readable?<br />
** The reason for geo being highlighted (as an optional field) is to promote at least one location identifier in the story--preferably the most appropriate single location on a map for that particular story. Geo does not have to be related to dateline, but in some [http://labs.ap.org/wiki/hNews examples] we've worked on, we show the two collapsed into a single field. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)<br />
** For locations referred to in the story, I agree--publishers should be using [[hCard]] with the contained geo to markup the locations themselves. One of the concepts I've struggled with is drawing an admittedly arbitrary line between the metadata ''about'' a story from the metadata ''within'' a story. For the former, we've focused on simplicity and minimalism, primarily as a means to encourage adoption. That has meant preferring [[rel-tag]] over in-line entity extraction and markup using compound microformats. For the latter, we feel that the field is open: use whatever microformat fits your purpose, however you can--the more, the better. This lets publishers with minimal technology capabilities at least get started by tweaking a few templates in their CMS, while those more technically inclined aren't limited by the simplicity of the format to a paucity of data. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)<br />
** Also, dateline can be text or [[hCard]], as noted in the [[news-brainstorming#Common_News_Fields|Common News Fields]] section. --[[User:JonathanMalek|JonathanMalek]] 18:17, 24 September 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">What is item-license?</strong> Using [[rel-license]] presumably?<br />
** We're working off the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] discussions for this. Our concern with [[rel-license]] was its definition as applying to an entire page, rather than an item within a page. The current discussions around licensing definitely address that. --[[User:JonathanMalek|JonathanMalek]] 00:02, 25 August 2009 (UTC)<br />
*** +1 using item-license for news-brainstorming makes sense. [[User:Tantek|Tantek]] 22:32, 27 August 2009 (UTC)<br />
</div><br />
</div></div>JonathanMalekhttp://microformats.org/wiki/index.php?title=hnews-issues&diff=41379hnews-issues2009-11-13T18:45:22Z<p>JonathanMalek: /* Open Issues */ fixing missing close div on issue.</p>
<hr />
<div><h1> hNews issues </h1><br />
<br />
__TOC__<br />
<br />
These are externally raised issues about [[hnews|hNews]] with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the draft. <br />
<br />
'''IMPORTANT''': Please read the [[hnews-faq|hNews FAQ]] before giving any feedback or raising any issues as your feedback/issues may already be resolved/answered.<br />
<br />
Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — [http://tantek.com/ Tantek]<br />
<br />
Please add new issues to the '''top''' of the list. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.<br />
<br />
See related [[hatom-issues]] and [[hcard-issues]].<br />
<br />
== Template ==<br />
<br />
{{issues-format}}<br />
<br />
<br />
== Issues ==<br />
=== Open Issues ===<br />
<div class="hentry"><br />
{{OpenIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-20</span> raised by <span class="fn">[[User:MilesD|Miles De Feyter]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">News, Commentary, and Opinion pieces as they relate to hNews</strong>. An interesting comment came up today when looking at how to use hNews on other AOL properties outside of our main news site, and that is, some of our sites are both news and commentary. Let's take our sports site for example http://www.fanhouse.com/ <br />
<br />
This site reports on sports news with article headlines such as: <br />
[http://www.fanhouse.com/news/nfl/big-ben-tops-pass-rankings/723353 Big Ben tops pass rankings]<br />
<br />
But fanhouse.com also has some obvious opinion pieces such as:<br />
[http://kevin-blackistone.fanhouse.com/2009/10/19/ail-to-the-redskins-worst-run-franchise-on-the-planet/ Fail to the Redskins: Worst-Run Franchise on the Planet]<br />
<br />
Currently we have one publishing system for all of our content within Fanhouse whether it be feed driven, in house publisher, news content, or commentary. So at the moment if one thing gets hNews it all does. <br />
<br />
Have you given this situation thought? My initial thinking is that perhaps this is where a principles statement specific to Fanhouse could account for the different types of content being labeled hNews. <br />
** Very glad you brought this up. We've given this alot of thought. I think your initial thinking is right. Right now the place to distinguish differences such as these (e.g. reporting from opinion) is within the principles statement. But this is something I think would benefit significantly from further development (i.e. the development of additional hNews criteria) [[User:Martinjemoore|Martin Moore]]<br />
</div><br />
</div><br />
<br />
<div class="hentry"><br />
{{OpenIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-14</span> raised by <span class="fn">[[User:MarkNg|MarkNg]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">adr for dateline</strong>. From [http://twitter.com/pigsonthewing/status/4831500605 Andy Mabbett on Twitter] : hNews microformat spec "dateline. optional. Using text or hCard" should read "dateline. optional. Using text, adr or hCard".<br />
** Seems like a useful extra to me, any objections ? [[User:MarkNg|MarkNg]]<br />
** Agreed, makes sense. --[[User:JonathanMalek|JonathanMalek]] 00:57, 15 October 2009 (UTC)<br />
** +1 to addition of optional "adr" markup of "dateline", but should also allow "geo" markup of "dateline" as well. i.e. change: <blockquote><p>* a dateline element MAY be encoded in an hCard.</p></blockquote> to <blockquote><p>* a dateline element MAY be encoded with an [[adr]], [[geo]], or [[hCard]] on the same element.</p></blockquote> [[User:Tantek|Tantek]] 19:57, 15 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
=== Resolved Issues ===<br />
<br />
<div class="hentry"><br />
{{ResolvedIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-15</span> raised by <span class="fn">[[User:TobyInk|TobyInk]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">XMDP defines 'principles' incorrectly.</strong> The XMDP for hNews defines 'principles' as a class, whereas the rest of the draft refers to it as a link type (i.e. 'rel' value).<br />
** ACCEPTED SPEC UPDATE. FIXED: thanks for pointing that out. I believe the updated profile reflects that correctly now. --[[User:JonathanMalek|JonathanMalek]] 15:37, 15 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<div class="hentry"><br />
{{ResolvedIssue}} <span class="entry-summary author vcard"><span class="published">2009-11-13</span> raised by <span class="fn">[[User:gut1975|Guthrie Collin]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">The item-license element is incorrectly described as a class</strong>. The XMDP profile and element description for item-license in hNews describes the element as a class attribute value, however, the [http://microformats.org/wiki/licensing-brainstorming#item_as_container Licensing Brainstorming] proposal describes this field as a link type. In addition, the hNews examples purport item-license as a link type. Which item-license description is correct? <br />
** ACCEPTED SPEC UPDATE. FIXED: the correct description is as a link (rel). The profile has been updated to reflect that correctly. --[[User:JonathanMalek|JonathanMalek]] 18:44, 13 November 2009 (UTC)<br />
</div><br />
</div><br />
<br />
=== Closed Issues ===<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-09</span> raised by <span class="fn">Miles De Feyter</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Implementation of item-license as it relates to hNews</strong>. Reading through the item-license brainstorm it seems to indicate that "item-license" would need to be nested within something with the class of "item". So as this relates to hNews is the suggestion to then have an articles containing div have the three class names of "hnews hentry item"?<br />
** At this point, Miles, that is correct (following the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] concept and guidance). I expect we'll see changes around item-license (it's still just brainstorming), but for the time being, the third class name "item" is needed. --[[User:JonathanMalek|JonathanMalek]] 16:25, 12 October 2009 (UTC)<br />
** Added to [[hnews-faq]] --[[User:JonathanMalek|JonathanMalek]] 02:19, 14 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">2009-09-28</span> raised by <span class="fn">[[User:MilesD|Miles De Feyter]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Principles as a requirement</strong>. Working for a publishing company that owns and operates a large number of different organizations I'd love to incorporate hNews within our publishing system. The hNews requirement for a principles statement could pose a problem though or at least make rolling out hNews a more involved process then it would be otherwise. The issue is, I would now have to go to each product owner and ask then to provide this principles statement to link to. So my concern is now rather then just making a change to the publishing system to support hNews there is this requirement for some supporting content. And due to the nature of the content I can only assume our legal dep. would need to sign off as well, further complicating the adoption of hNews.<br />
** +1 I agree that the "principles" property (and probably all other others) should be optional. [[User:Tantek|Tantek]] 18:29, 29 September 2009 (UTC)<br />
*** I think it's important to explain why principles is a requirement. hnews is essentially a specialization of hAtom. Its purpose is to distinguish news on the web. Hence the description of source organisation, license and principles. Of these, principles is the only one which consistently distinguishes news on the web from other content (eg. commercial, government). In the future it should be distinguished further by making the principles themselves machine readable (but that is for a later date). Most professional news organisations adhere to a Statement of Principles (e.g. see http://en.wikipedia.org/wiki/Journalism_ethics_and_standards and http://www.journalism.org/resources/ethics_codes). If a site wants to mark up its content but does not want to distinguish it as news, then wouldn't it be easiest to use hAtom? [[User:martinjemoore|Martin Moore]] 9:00, 20 September 2009 (UTC)<br />
*** Having discussed this issue at length outside this brainstorming, we understand some of the concerns of the microformat community regarding 'must', but are still convinced of the criticality of principles to hNews - therefore recommend downgrading from 'must' to 'should'. [[User:martinjemoore|Martin Moore]] 14:00, 7 October 2009 (UTC)<br />
**** Accepted and implemented in 0.1. In keeping with the general direction here, we've changed <code>item-license</code> as well, and would consider adopting the same with <code>source-org</code> as well, if it proves to present the same problems. --[[User:JonathanMalek|JonathanMalek]] 00:53, 15 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">hCalendar instead of dateline?</strong> Would an [[hCalendar]] event (which can contain an hCard location) make sense for a dateline, or is the 'date' part more often omitted?<br />
** Confusingly, the journalistic term "dateline" isn't anything to do with a date or time. It is the location from which a report is filed and is generally the main location associated with a story. Generally, a dateline consists of a city (e.g. "Rome") but could be the name of a ship at sea or even a space station. [[User:Stuart Myles|Stuart Myles]] 21:12, 24 August 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">hCard instead of geo?</strong> Is geo really in use here, or would using an hCard (that can contain geo) be a better way of representing locations referred to in the story, as more human readable?<br />
** The reason for geo being highlighted (as an optional field) is to promote at least one location identifier in the story--preferably the most appropriate single location on a map for that particular story. Geo does not have to be related to dateline, but in some [http://labs.ap.org/wiki/hNews examples] we've worked on, we show the two collapsed into a single field. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)<br />
** For locations referred to in the story, I agree--publishers should be using [[hCard]] with the contained geo to markup the locations themselves. One of the concepts I've struggled with is drawing an admittedly arbitrary line between the metadata ''about'' a story from the metadata ''within'' a story. For the former, we've focused on simplicity and minimalism, primarily as a means to encourage adoption. That has meant preferring [[rel-tag]] over in-line entity extraction and markup using compound microformats. For the latter, we feel that the field is open: use whatever microformat fits your purpose, however you can--the more, the better. This lets publishers with minimal technology capabilities at least get started by tweaking a few templates in their CMS, while those more technically inclined aren't limited by the simplicity of the format to a paucity of data. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)<br />
** Also, dateline can be text or [[hCard]], as noted in the [[news-brainstorming#Common_News_Fields|Common News Fields]] section. --[[User:JonathanMalek|JonathanMalek]] 18:17, 24 September 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">What is item-license?</strong> Using [[rel-license]] presumably?<br />
** We're working off the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] discussions for this. Our concern with [[rel-license]] was its definition as applying to an entire page, rather than an item within a page. The current discussions around licensing definitely address that. --[[User:JonathanMalek|JonathanMalek]] 00:02, 25 August 2009 (UTC)<br />
*** +1 using item-license for news-brainstorming makes sense. [[User:Tantek|Tantek]] 22:32, 27 August 2009 (UTC)<br />
</div><br />
</div></div>JonathanMalekhttp://microformats.org/wiki/index.php?title=hnews-issues&diff=41378hnews-issues2009-11-13T18:44:16Z<p>JonathanMalek: /* Resolved Issues */ Marking itemlicense is a class or link as resolved.</p>
<hr />
<div><h1> hNews issues </h1><br />
<br />
__TOC__<br />
<br />
These are externally raised issues about [[hnews|hNews]] with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the draft. <br />
<br />
'''IMPORTANT''': Please read the [[hnews-faq|hNews FAQ]] before giving any feedback or raising any issues as your feedback/issues may already be resolved/answered.<br />
<br />
Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — [http://tantek.com/ Tantek]<br />
<br />
Please add new issues to the '''top''' of the list. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.<br />
<br />
See related [[hatom-issues]] and [[hcard-issues]].<br />
<br />
== Template ==<br />
<br />
{{issues-format}}<br />
<br />
<br />
== Issues ==<br />
=== Open Issues ===<br />
<div class="hentry"><br />
{{OpenIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-20</span> raised by <span class="fn">[[User:MilesD|Miles De Feyter]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">News, Commentary, and Opinion pieces as they relate to hNews</strong>. An interesting comment came up today when looking at how to use hNews on other AOL properties outside of our main news site, and that is, some of our sites are both news and commentary. Let's take our sports site for example http://www.fanhouse.com/ <br />
<br />
This site reports on sports news with article headlines such as: <br />
[http://www.fanhouse.com/news/nfl/big-ben-tops-pass-rankings/723353 Big Ben tops pass rankings]<br />
<br />
But fanhouse.com also has some obvious opinion pieces such as:<br />
[http://kevin-blackistone.fanhouse.com/2009/10/19/ail-to-the-redskins-worst-run-franchise-on-the-planet/ Fail to the Redskins: Worst-Run Franchise on the Planet]<br />
<br />
Currently we have one publishing system for all of our content within Fanhouse whether it be feed driven, in house publisher, news content, or commentary. So at the moment if one thing gets hNews it all does. <br />
<br />
Have you given this situation thought? My initial thinking is that perhaps this is where a principles statement specific to Fanhouse could account for the different types of content being labeled hNews. <br />
** Very glad you brought this up. We've given this alot of thought. I think your initial thinking is right. Right now the place to distinguish differences such as these (e.g. reporting from opinion) is within the principles statement. But this is something I think would benefit significantly from further development (i.e. the development of additional hNews criteria) [[User:Martinjemoore|Martin Moore]]<br />
</div><br />
<br />
<div class="hentry"><br />
{{OpenIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-14</span> raised by <span class="fn">[[User:MarkNg|MarkNg]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">adr for dateline</strong>. From [http://twitter.com/pigsonthewing/status/4831500605 Andy Mabbett on Twitter] : hNews microformat spec "dateline. optional. Using text or hCard" should read "dateline. optional. Using text, adr or hCard".<br />
** Seems like a useful extra to me, any objections ? [[User:MarkNg|MarkNg]]<br />
** Agreed, makes sense. --[[User:JonathanMalek|JonathanMalek]] 00:57, 15 October 2009 (UTC)<br />
** +1 to addition of optional "adr" markup of "dateline", but should also allow "geo" markup of "dateline" as well. i.e. change: <blockquote><p>* a dateline element MAY be encoded in an hCard.</p></blockquote> to <blockquote><p>* a dateline element MAY be encoded with an [[adr]], [[geo]], or [[hCard]] on the same element.</p></blockquote> [[User:Tantek|Tantek]] 19:57, 15 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
=== Resolved Issues ===<br />
<br />
<div class="hentry"><br />
{{ResolvedIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-15</span> raised by <span class="fn">[[User:TobyInk|TobyInk]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">XMDP defines 'principles' incorrectly.</strong> The XMDP for hNews defines 'principles' as a class, whereas the rest of the draft refers to it as a link type (i.e. 'rel' value).<br />
** ACCEPTED SPEC UPDATE. FIXED: thanks for pointing that out. I believe the updated profile reflects that correctly now. --[[User:JonathanMalek|JonathanMalek]] 15:37, 15 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<div class="hentry"><br />
{{ResolvedIssue}} <span class="entry-summary author vcard"><span class="published">2009-11-13</span> raised by <span class="fn">[[User:gut1975|Guthrie Collin]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">The item-license element is incorrectly described as a class</strong>. The XMDP profile and element description for item-license in hNews describes the element as a class attribute value, however, the [http://microformats.org/wiki/licensing-brainstorming#item_as_container Licensing Brainstorming] proposal describes this field as a link type. In addition, the hNews examples purport item-license as a link type. Which item-license description is correct? <br />
** ACCEPTED SPEC UPDATE. FIXED: the correct description is as a link (rel). The profile has been updated to reflect that correctly. --[[User:JonathanMalek|JonathanMalek]] 18:44, 13 November 2009 (UTC)<br />
</div><br />
</div><br />
<br />
=== Closed Issues ===<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-09</span> raised by <span class="fn">Miles De Feyter</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Implementation of item-license as it relates to hNews</strong>. Reading through the item-license brainstorm it seems to indicate that "item-license" would need to be nested within something with the class of "item". So as this relates to hNews is the suggestion to then have an articles containing div have the three class names of "hnews hentry item"?<br />
** At this point, Miles, that is correct (following the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] concept and guidance). I expect we'll see changes around item-license (it's still just brainstorming), but for the time being, the third class name "item" is needed. --[[User:JonathanMalek|JonathanMalek]] 16:25, 12 October 2009 (UTC)<br />
** Added to [[hnews-faq]] --[[User:JonathanMalek|JonathanMalek]] 02:19, 14 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">2009-09-28</span> raised by <span class="fn">[[User:MilesD|Miles De Feyter]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Principles as a requirement</strong>. Working for a publishing company that owns and operates a large number of different organizations I'd love to incorporate hNews within our publishing system. The hNews requirement for a principles statement could pose a problem though or at least make rolling out hNews a more involved process then it would be otherwise. The issue is, I would now have to go to each product owner and ask then to provide this principles statement to link to. So my concern is now rather then just making a change to the publishing system to support hNews there is this requirement for some supporting content. And due to the nature of the content I can only assume our legal dep. would need to sign off as well, further complicating the adoption of hNews.<br />
** +1 I agree that the "principles" property (and probably all other others) should be optional. [[User:Tantek|Tantek]] 18:29, 29 September 2009 (UTC)<br />
*** I think it's important to explain why principles is a requirement. hnews is essentially a specialization of hAtom. Its purpose is to distinguish news on the web. Hence the description of source organisation, license and principles. Of these, principles is the only one which consistently distinguishes news on the web from other content (eg. commercial, government). In the future it should be distinguished further by making the principles themselves machine readable (but that is for a later date). Most professional news organisations adhere to a Statement of Principles (e.g. see http://en.wikipedia.org/wiki/Journalism_ethics_and_standards and http://www.journalism.org/resources/ethics_codes). If a site wants to mark up its content but does not want to distinguish it as news, then wouldn't it be easiest to use hAtom? [[User:martinjemoore|Martin Moore]] 9:00, 20 September 2009 (UTC)<br />
*** Having discussed this issue at length outside this brainstorming, we understand some of the concerns of the microformat community regarding 'must', but are still convinced of the criticality of principles to hNews - therefore recommend downgrading from 'must' to 'should'. [[User:martinjemoore|Martin Moore]] 14:00, 7 October 2009 (UTC)<br />
**** Accepted and implemented in 0.1. In keeping with the general direction here, we've changed <code>item-license</code> as well, and would consider adopting the same with <code>source-org</code> as well, if it proves to present the same problems. --[[User:JonathanMalek|JonathanMalek]] 00:53, 15 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">hCalendar instead of dateline?</strong> Would an [[hCalendar]] event (which can contain an hCard location) make sense for a dateline, or is the 'date' part more often omitted?<br />
** Confusingly, the journalistic term "dateline" isn't anything to do with a date or time. It is the location from which a report is filed and is generally the main location associated with a story. Generally, a dateline consists of a city (e.g. "Rome") but could be the name of a ship at sea or even a space station. [[User:Stuart Myles|Stuart Myles]] 21:12, 24 August 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">hCard instead of geo?</strong> Is geo really in use here, or would using an hCard (that can contain geo) be a better way of representing locations referred to in the story, as more human readable?<br />
** The reason for geo being highlighted (as an optional field) is to promote at least one location identifier in the story--preferably the most appropriate single location on a map for that particular story. Geo does not have to be related to dateline, but in some [http://labs.ap.org/wiki/hNews examples] we've worked on, we show the two collapsed into a single field. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)<br />
** For locations referred to in the story, I agree--publishers should be using [[hCard]] with the contained geo to markup the locations themselves. One of the concepts I've struggled with is drawing an admittedly arbitrary line between the metadata ''about'' a story from the metadata ''within'' a story. For the former, we've focused on simplicity and minimalism, primarily as a means to encourage adoption. That has meant preferring [[rel-tag]] over in-line entity extraction and markup using compound microformats. For the latter, we feel that the field is open: use whatever microformat fits your purpose, however you can--the more, the better. This lets publishers with minimal technology capabilities at least get started by tweaking a few templates in their CMS, while those more technically inclined aren't limited by the simplicity of the format to a paucity of data. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)<br />
** Also, dateline can be text or [[hCard]], as noted in the [[news-brainstorming#Common_News_Fields|Common News Fields]] section. --[[User:JonathanMalek|JonathanMalek]] 18:17, 24 September 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">What is item-license?</strong> Using [[rel-license]] presumably?<br />
** We're working off the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] discussions for this. Our concern with [[rel-license]] was its definition as applying to an entire page, rather than an item within a page. The current discussions around licensing definitely address that. --[[User:JonathanMalek|JonathanMalek]] 00:02, 25 August 2009 (UTC)<br />
*** +1 using item-license for news-brainstorming makes sense. [[User:Tantek|Tantek]] 22:32, 27 August 2009 (UTC)<br />
</div><br />
</div></div>JonathanMalekhttp://microformats.org/wiki/index.php?title=hnews-issues&diff=41377hnews-issues2009-11-13T18:40:46Z<p>JonathanMalek: /* Open Issues */ Moving "itemlicense is rel or class" question from Guthrie Collin to resolved.</p>
<hr />
<div><h1> hNews issues </h1><br />
<br />
__TOC__<br />
<br />
These are externally raised issues about [[hnews|hNews]] with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the draft. <br />
<br />
'''IMPORTANT''': Please read the [[hnews-faq|hNews FAQ]] before giving any feedback or raising any issues as your feedback/issues may already be resolved/answered.<br />
<br />
Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — [http://tantek.com/ Tantek]<br />
<br />
Please add new issues to the '''top''' of the list. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.<br />
<br />
See related [[hatom-issues]] and [[hcard-issues]].<br />
<br />
== Template ==<br />
<br />
{{issues-format}}<br />
<br />
<br />
== Issues ==<br />
=== Open Issues ===<br />
<div class="hentry"><br />
{{OpenIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-20</span> raised by <span class="fn">[[User:MilesD|Miles De Feyter]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">News, Commentary, and Opinion pieces as they relate to hNews</strong>. An interesting comment came up today when looking at how to use hNews on other AOL properties outside of our main news site, and that is, some of our sites are both news and commentary. Let's take our sports site for example http://www.fanhouse.com/ <br />
<br />
This site reports on sports news with article headlines such as: <br />
[http://www.fanhouse.com/news/nfl/big-ben-tops-pass-rankings/723353 Big Ben tops pass rankings]<br />
<br />
But fanhouse.com also has some obvious opinion pieces such as:<br />
[http://kevin-blackistone.fanhouse.com/2009/10/19/ail-to-the-redskins-worst-run-franchise-on-the-planet/ Fail to the Redskins: Worst-Run Franchise on the Planet]<br />
<br />
Currently we have one publishing system for all of our content within Fanhouse whether it be feed driven, in house publisher, news content, or commentary. So at the moment if one thing gets hNews it all does. <br />
<br />
Have you given this situation thought? My initial thinking is that perhaps this is where a principles statement specific to Fanhouse could account for the different types of content being labeled hNews. <br />
** Very glad you brought this up. We've given this alot of thought. I think your initial thinking is right. Right now the place to distinguish differences such as these (e.g. reporting from opinion) is within the principles statement. But this is something I think would benefit significantly from further development (i.e. the development of additional hNews criteria) [[User:Martinjemoore|Martin Moore]]<br />
</div><br />
<br />
<div class="hentry"><br />
{{OpenIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-14</span> raised by <span class="fn">[[User:MarkNg|MarkNg]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">adr for dateline</strong>. From [http://twitter.com/pigsonthewing/status/4831500605 Andy Mabbett on Twitter] : hNews microformat spec "dateline. optional. Using text or hCard" should read "dateline. optional. Using text, adr or hCard".<br />
** Seems like a useful extra to me, any objections ? [[User:MarkNg|MarkNg]]<br />
** Agreed, makes sense. --[[User:JonathanMalek|JonathanMalek]] 00:57, 15 October 2009 (UTC)<br />
** +1 to addition of optional "adr" markup of "dateline", but should also allow "geo" markup of "dateline" as well. i.e. change: <blockquote><p>* a dateline element MAY be encoded in an hCard.</p></blockquote> to <blockquote><p>* a dateline element MAY be encoded with an [[adr]], [[geo]], or [[hCard]] on the same element.</p></blockquote> [[User:Tantek|Tantek]] 19:57, 15 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
=== Resolved Issues ===<br />
<br />
<div class="hentry"><br />
{{ResolvedIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-15</span> raised by <span class="fn">[[User:TobyInk|TobyInk]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">XMDP defines 'principles' incorrectly.</strong> The XMDP for hNews defines 'principles' as a class, whereas the rest of the draft refers to it as a link type (i.e. 'rel' value).<br />
** ACCEPTED SPEC UPDATE. FIXED: thanks for pointing that out. I believe the updated profile reflects that correctly now. --[[User:JonathanMalek|JonathanMalek]] 15:37, 15 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
=== Closed Issues ===<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-09</span> raised by <span class="fn">Miles De Feyter</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Implementation of item-license as it relates to hNews</strong>. Reading through the item-license brainstorm it seems to indicate that "item-license" would need to be nested within something with the class of "item". So as this relates to hNews is the suggestion to then have an articles containing div have the three class names of "hnews hentry item"?<br />
** At this point, Miles, that is correct (following the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] concept and guidance). I expect we'll see changes around item-license (it's still just brainstorming), but for the time being, the third class name "item" is needed. --[[User:JonathanMalek|JonathanMalek]] 16:25, 12 October 2009 (UTC)<br />
** Added to [[hnews-faq]] --[[User:JonathanMalek|JonathanMalek]] 02:19, 14 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">2009-09-28</span> raised by <span class="fn">[[User:MilesD|Miles De Feyter]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Principles as a requirement</strong>. Working for a publishing company that owns and operates a large number of different organizations I'd love to incorporate hNews within our publishing system. The hNews requirement for a principles statement could pose a problem though or at least make rolling out hNews a more involved process then it would be otherwise. The issue is, I would now have to go to each product owner and ask then to provide this principles statement to link to. So my concern is now rather then just making a change to the publishing system to support hNews there is this requirement for some supporting content. And due to the nature of the content I can only assume our legal dep. would need to sign off as well, further complicating the adoption of hNews.<br />
** +1 I agree that the "principles" property (and probably all other others) should be optional. [[User:Tantek|Tantek]] 18:29, 29 September 2009 (UTC)<br />
*** I think it's important to explain why principles is a requirement. hnews is essentially a specialization of hAtom. Its purpose is to distinguish news on the web. Hence the description of source organisation, license and principles. Of these, principles is the only one which consistently distinguishes news on the web from other content (eg. commercial, government). In the future it should be distinguished further by making the principles themselves machine readable (but that is for a later date). Most professional news organisations adhere to a Statement of Principles (e.g. see http://en.wikipedia.org/wiki/Journalism_ethics_and_standards and http://www.journalism.org/resources/ethics_codes). If a site wants to mark up its content but does not want to distinguish it as news, then wouldn't it be easiest to use hAtom? [[User:martinjemoore|Martin Moore]] 9:00, 20 September 2009 (UTC)<br />
*** Having discussed this issue at length outside this brainstorming, we understand some of the concerns of the microformat community regarding 'must', but are still convinced of the criticality of principles to hNews - therefore recommend downgrading from 'must' to 'should'. [[User:martinjemoore|Martin Moore]] 14:00, 7 October 2009 (UTC)<br />
**** Accepted and implemented in 0.1. In keeping with the general direction here, we've changed <code>item-license</code> as well, and would consider adopting the same with <code>source-org</code> as well, if it proves to present the same problems. --[[User:JonathanMalek|JonathanMalek]] 00:53, 15 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">hCalendar instead of dateline?</strong> Would an [[hCalendar]] event (which can contain an hCard location) make sense for a dateline, or is the 'date' part more often omitted?<br />
** Confusingly, the journalistic term "dateline" isn't anything to do with a date or time. It is the location from which a report is filed and is generally the main location associated with a story. Generally, a dateline consists of a city (e.g. "Rome") but could be the name of a ship at sea or even a space station. [[User:Stuart Myles|Stuart Myles]] 21:12, 24 August 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">hCard instead of geo?</strong> Is geo really in use here, or would using an hCard (that can contain geo) be a better way of representing locations referred to in the story, as more human readable?<br />
** The reason for geo being highlighted (as an optional field) is to promote at least one location identifier in the story--preferably the most appropriate single location on a map for that particular story. Geo does not have to be related to dateline, but in some [http://labs.ap.org/wiki/hNews examples] we've worked on, we show the two collapsed into a single field. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)<br />
** For locations referred to in the story, I agree--publishers should be using [[hCard]] with the contained geo to markup the locations themselves. One of the concepts I've struggled with is drawing an admittedly arbitrary line between the metadata ''about'' a story from the metadata ''within'' a story. For the former, we've focused on simplicity and minimalism, primarily as a means to encourage adoption. That has meant preferring [[rel-tag]] over in-line entity extraction and markup using compound microformats. For the latter, we feel that the field is open: use whatever microformat fits your purpose, however you can--the more, the better. This lets publishers with minimal technology capabilities at least get started by tweaking a few templates in their CMS, while those more technically inclined aren't limited by the simplicity of the format to a paucity of data. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)<br />
** Also, dateline can be text or [[hCard]], as noted in the [[news-brainstorming#Common_News_Fields|Common News Fields]] section. --[[User:JonathanMalek|JonathanMalek]] 18:17, 24 September 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">What is item-license?</strong> Using [[rel-license]] presumably?<br />
** We're working off the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] discussions for this. Our concern with [[rel-license]] was its definition as applying to an entire page, rather than an item within a page. The current discussions around licensing definitely address that. --[[User:JonathanMalek|JonathanMalek]] 00:02, 25 August 2009 (UTC)<br />
*** +1 using item-license for news-brainstorming makes sense. [[User:Tantek|Tantek]] 22:32, 27 August 2009 (UTC)<br />
</div><br />
</div></div>JonathanMalekhttp://microformats.org/wiki/index.php?title=hnews&diff=41376hnews2009-11-13T18:38:42Z<p>JonathanMalek: Fixing the rel-itemlicense section of the XMDP profile per issue by Guthrie Collin</p>
<hr />
<div><entry-title>hNews 0.1</entry-title><br />
{{Template:DraftSpecification}}<br />
<br />
hNews is 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, [[principles-brainstorming#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.<br />
__TOC__<br />
== Draft Specification ==<br />
<br />
;Editor/Author<br />
:[[:User:JonathanMalek|Jonathan Malek]] ([http://www.ap.org Associated Press])<br />
<br />
;Contributors<br />
:[[:User:Smyles|Stuart Myles]] ([http://www.ap.org Associated Press]) <br />
:[[:User:Martinjemoore|Martin Moore]] ([http://mediastandardstrust.org Media Standards Trust])<br />
:[[:User:MarkNg|Mark Ng]] ([http://mediastandardstrust.org Media Standards Trust])<br />
:[[:User:Tbmartinwiki|Todd B. Martin]] ([http://www.ap.org Associated Press])<br />
<br />
=== Copyright ===<br />
Per the public domain release on the authors' user pages ([[:User:JonathanMalek|Jonathan Malek]]) this specification is released into the public domain. <br />
<br />
{{MicroFormatPublicDomainContributionStatement}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Introduction ==<br />
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.<br />
<br />
{{rfc-2119-intro}}<br />
<br />
== Semantic XHTML Design Principles ==<br />
{{semantic-xhtml-design-principles}}<br />
<br />
== Format ==<br />
=== In General ===<br />
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.<br />
<br />
=== Schema ===<br />
The hNews schema consists of the following: <br />
<br />
* hNews ('''<code>hnews</code>''') and '''<code>hentry</code>'''. required. Using [[hAtom]].<br />
** '''<code>source-org</code>'''. required. Using [[hCard]].[*]<br />
** '''<code>dateline</code>'''. optional. Using text or [[hCard]].<br />
** '''<code>geo</code>'''. optional. Using [[geo]].[*]<br />
** '''<code>item-license</code>'''. recommended. Using a [[licensing-brainstorming#item_as_container license|brainstorm proposal]].<br />
** '''<code>principles</code>'''. recommended. Using the draft microformat [[principles-brainstorming#rel-principles_specification|rel-principles]].<br />
<br />
[*] Some required elements have defaults if missing, see below.<br />
<br />
=== Field and Element Details ===<br />
<br />
==== hAtom Fields ====<br />
<br />
===== Entry =====<br />
* an hNews story {{must}} be encoded as an [[hAtom]] <code>hentry</code>.<br />
* if an hNews story cannot be parsed as an [[hAtom]] <code>hentry</code>, it is invalid hNews.<br />
<br />
==== Additional Fields ====<br />
<br />
===== Source Organization =====<br />
* a Source Organization element is identified by the class name <code>source-org</code>.<br />
* Source Organization represents the originating organization for the news story.<br />
* a Source Organization {{must}} be encoded in an [[hCard]].<br />
* if the Source Organization is missing <br />
** find the [[algorithm-nearest-in-parent]] element(s) with class name <code>source-org</code> and that is/are a valid [[hCard]]<br />
** otherwise the entry is invalid hNews<br />
<br />
===== Dateline =====<br />
* a dateline element is identified by the class name <code>dateline</code>.<br />
* dateline represents the location where the news story was written or filed (see [http://en.wikipedia.org/wiki/Dateline dateline] for more details).<br />
* a dateline element {{may}} be encoded in an [[hCard]].<br />
* a news story {{should}} have a dateline element.<br />
* dateline sometimes also includes the publish date of the news story. In such cases, use the [[datetime-design-pattern]] to encode the date.<br />
<br />
===== Geo =====<br />
* a geo element is identified by the class name <code>geo</code><br />
* geo represents the geographic coordinates of relevant locations in the news story.<br />
* a geo element should be encoded in a [[geo]].<br />
* 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).<br />
<br />
===== License =====<br />
* a license element is identified by the class name <code>item-license</code>.<br />
* a license element {{must}} be encoded as described in this [http://microformats.org/wiki/licensing-brainstorming#item_as_container license brainstorm proposal].<br />
* a news story {{should}} include a license element.<br />
<br />
===== Principles =====<br />
* a principles element is identified by <code>rel-principles</code>.<br />
* principles represents the statement of principles and ethics used by the news organization that produced the news story.<br />
* a principles element {{must}} be encoded in [[principles-brainstorming#rel-principles_specification|rel-principles]].<br />
* a news story {{should}} include principles.<br />
* principles {{should}} be linked to using the icons http://labs.ap.org/principles-button-blue.png or http://labs.ap.org/principles-book-blue.png.<br />
<br />
=== XMDP Profile ===<br />
<pre><br />
<dl class="profile"><br />
<dt>class</dt><br />
<dd><p><br />
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class"><br />
HTML4 definition of the 'class' attribute.</a><br />
This meta data profile defines some 'class' attribute values (class names) <br />
and their meanings as suggested by a <br />
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile"><br />
draft of "Hypertext Links in HTML"</a>.<br />
<dl><br />
<br />
<dt>hnews</dt><br />
<dd><br />
Used to describe semantic information associated with news stories.<br />
</dd><br />
<br />
<dt>source-org</dt><br />
<dd><br />
The originating organization for the news story.<br />
</dd><br />
<br />
<dt>dateline</dt><br />
<dd><br />
Represents the location where the news story was filed.<br />
</dd><br />
<br />
<dt>geo</dt><br />
<dd><br />
Represents geographic coordinates of relevant locations in the story.<br />
</dd><br />
<br />
<dt>rel</dt><br />
<dd><br />
<dl><br />
<dt>item-license</dt><br />
<dd><br />
Represents the license for the story.<br />
</dd><br />
</dl><br />
</dd><br />
<br />
<dt>rel</dt><br />
<dd><br />
<dl><br />
<dt>principles</dt><br />
<dd><br />
Represents the statement of principles and ethics used by the news organization that produced the news story.<br />
</dd><br />
</dl><br />
</dd><br />
<br />
</dl><br />
</dd><br />
</dl><br />
</pre><br />
<br />
== Examples ==<br />
<br />
See [[hnews-examples]].<br />
<br />
=== Examples in the wild ===<br />
<br />
See [[hnews-examples-in-wild]].<br />
<br />
== Implementations ==<br />
<br />
== References ==<br />
<br />
=== Normative References ===<br />
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0]<br />
* [[hatom|hAtom]]<br />
* [[hcard|hCard]]<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [[rel-tag]]<br />
* [[geo]]<br />
* [[licensing-brainstorming#item_as_container_license|item-license brainstorm]]<br />
* [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles]<br />
* [http://www.ietf.org/rfc/rfc2119.txt RFC2119]<br />
* [http://www.ietf.org/rfc/rfc4287.txt RFC4287] (Atom 1.0)<br />
<br />
=== Informative References ===<br />
* Other news efforts: see [[news-formats]].<br />
<br />
== Work in progress ==<br />
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. <br />
<br />
=== Version 0.1 ===<br />
<br />
Version 0.1 was drafted August 2008.<br />
<br />
== Further Reading ==<br />
* See [http://www.technorati.com/cosmos/referer.html blogs discussing this page].<br />
<br />
== Related Pages ==<br />
* hnews<br />
* [[news-brainstorming]]: thoughts for improving hNews. <br />
* [[hnews-faq|hNews FAQ]]: if you have any questions about hNews, check here, and if you don't find answers, add your questions!<br />
* [[hnews-issues]]: please add any issues with the specification to the issues page.<br />
* [[news-formats]]: existing news and news management schemas.<br />
* [[news-examples]]: examples of news formats on the web.<br />
** [[hnews-examples]]: examples of how to implement hNews.<br />
<br />
[[Category:Draft Specifications]]<br />
[[Category:hNews]]</div>JonathanMalekhttp://microformats.org/wiki/index.php?title=hnews-issues&diff=41368hnews-issues2009-11-13T04:40:20Z<p>JonathanMalek: /* Open Issues */ Cleaning up principles issue and response</p>
<hr />
<div><h1> hNews issues </h1><br />
<br />
__TOC__<br />
<br />
These are externally raised issues about [[hnews|hNews]] with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the draft. <br />
<br />
'''IMPORTANT''': Please read the [[hnews-faq|hNews FAQ]] before giving any feedback or raising any issues as your feedback/issues may already be resolved/answered.<br />
<br />
Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — [http://tantek.com/ Tantek]<br />
<br />
Please add new issues to the '''top''' of the list. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.<br />
<br />
See related [[hatom-issues]] and [[hcard-issues]].<br />
<br />
== Template ==<br />
<br />
{{issues-format}}<br />
<br />
<br />
== Issues ==<br />
=== Open Issues ===<br />
<br />
<div class="hentry"><br />
{{OpenIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-20</span> raised by <span class="fn">[[User:MilesD|Miles De Feyter]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">News, Commentary, and Opinion pieces as they relate to hNews</strong>. An interesting comment came up today when looking at how to use hNews on other AOL properties outside of our main news site, and that is, some of our sites are both news and commentary. Let's take our sports site for example http://www.fanhouse.com/ <br />
<br />
This site reports on sports news with article headlines such as: <br />
[http://www.fanhouse.com/news/nfl/big-ben-tops-pass-rankings/723353 Big Ben tops pass rankings]<br />
<br />
But fanhouse.com also has some obvious opinion pieces such as:<br />
[http://kevin-blackistone.fanhouse.com/2009/10/19/ail-to-the-redskins-worst-run-franchise-on-the-planet/ Fail to the Redskins: Worst-Run Franchise on the Planet]<br />
<br />
Currently we have one publishing system for all of our content within Fanhouse whether it be feed driven, in house publisher, news content, or commentary. So at the moment if one thing gets hNews it all does. <br />
<br />
Have you given this situation thought? My initial thinking is that perhaps this is where a principles statement specific to Fanhouse could account for the different types of content being labeled hNews. <br />
** Very glad you brought this up. We've given this alot of thought. I think your initial thinking is right. Right now the place to distinguish differences such as these (e.g. reporting from opinion) is within the principles statement. But this is something I think would benefit significantly from further development (i.e. the development of additional hNews criteria) [[User:Martinjemoore|Martin Moore]]<br />
</div><br />
<br />
<div class="hentry"><br />
{{OpenIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-14</span> raised by <span class="fn">[[User:MarkNg|MarkNg]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">adr for dateline</strong>. From [http://twitter.com/pigsonthewing/status/4831500605 Andy Mabbett on Twitter] : hNews microformat spec "dateline. optional. Using text or hCard" should read "dateline. optional. Using text, adr or hCard".<br />
** Seems like a useful extra to me, any objections ? [[User:MarkNg|MarkNg]]<br />
** Agreed, makes sense. --[[User:JonathanMalek|JonathanMalek]] 00:57, 15 October 2009 (UTC)<br />
** +1 to addition of optional "adr" markup of "dateline", but should also allow "geo" markup of "dateline" as well. i.e. change: <blockquote><p>* a dateline element MAY be encoded in an hCard.</p></blockquote> to <blockquote><p>* a dateline element MAY be encoded with an [[adr]], [[geo]], or [[hCard]] on the same element.</p></blockquote> [[User:Tantek|Tantek]] 19:57, 15 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
=== Resolved Issues ===<br />
<br />
<div class="hentry"><br />
{{ResolvedIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-15</span> raised by <span class="fn">[[User:TobyInk|TobyInk]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">XMDP defines 'principles' incorrectly.</strong> The XMDP for hNews defines 'principles' as a class, whereas the rest of the draft refers to it as a link type (i.e. 'rel' value).<br />
** ACCEPTED SPEC UPDATE. FIXED: thanks for pointing that out. I believe the updated profile reflects that correctly now. --[[User:JonathanMalek|JonathanMalek]] 15:37, 15 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
=== Closed Issues ===<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-09</span> raised by <span class="fn">Miles De Feyter</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Implementation of item-license as it relates to hNews</strong>. Reading through the item-license brainstorm it seems to indicate that "item-license" would need to be nested within something with the class of "item". So as this relates to hNews is the suggestion to then have an articles containing div have the three class names of "hnews hentry item"?<br />
** At this point, Miles, that is correct (following the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] concept and guidance). I expect we'll see changes around item-license (it's still just brainstorming), but for the time being, the third class name "item" is needed. --[[User:JonathanMalek|JonathanMalek]] 16:25, 12 October 2009 (UTC)<br />
** Added to [[hnews-faq]] --[[User:JonathanMalek|JonathanMalek]] 02:19, 14 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">2009-09-28</span> raised by <span class="fn">[[User:MilesD|Miles De Feyter]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Principles as a requirement</strong>. Working for a publishing company that owns and operates a large number of different organizations I'd love to incorporate hNews within our publishing system. The hNews requirement for a principles statement could pose a problem though or at least make rolling out hNews a more involved process then it would be otherwise. The issue is, I would now have to go to each product owner and ask then to provide this principles statement to link to. So my concern is now rather then just making a change to the publishing system to support hNews there is this requirement for some supporting content. And due to the nature of the content I can only assume our legal dep. would need to sign off as well, further complicating the adoption of hNews.<br />
** +1 I agree that the "principles" property (and probably all other others) should be optional. [[User:Tantek|Tantek]] 18:29, 29 September 2009 (UTC)<br />
*** I think it's important to explain why principles is a requirement. hnews is essentially a specialization of hAtom. Its purpose is to distinguish news on the web. Hence the description of source organisation, license and principles. Of these, principles is the only one which consistently distinguishes news on the web from other content (eg. commercial, government). In the future it should be distinguished further by making the principles themselves machine readable (but that is for a later date). Most professional news organisations adhere to a Statement of Principles (e.g. see http://en.wikipedia.org/wiki/Journalism_ethics_and_standards and http://www.journalism.org/resources/ethics_codes). If a site wants to mark up its content but does not want to distinguish it as news, then wouldn't it be easiest to use hAtom? [[User:martinjemoore|Martin Moore]] 9:00, 20 September 2009 (UTC)<br />
*** Having discussed this issue at length outside this brainstorming, we understand some of the concerns of the microformat community regarding 'must', but are still convinced of the criticality of principles to hNews - therefore recommend downgrading from 'must' to 'should'. [[User:martinjemoore|Martin Moore]] 14:00, 7 October 2009 (UTC)<br />
**** Accepted and implemented in 0.1. In keeping with the general direction here, we've changed <code>item-license</code> as well, and would consider adopting the same with <code>source-org</code> as well, if it proves to present the same problems. --[[User:JonathanMalek|JonathanMalek]] 00:53, 15 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">hCalendar instead of dateline?</strong> Would an [[hCalendar]] event (which can contain an hCard location) make sense for a dateline, or is the 'date' part more often omitted?<br />
** Confusingly, the journalistic term "dateline" isn't anything to do with a date or time. It is the location from which a report is filed and is generally the main location associated with a story. Generally, a dateline consists of a city (e.g. "Rome") but could be the name of a ship at sea or even a space station. [[User:Stuart Myles|Stuart Myles]] 21:12, 24 August 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">hCard instead of geo?</strong> Is geo really in use here, or would using an hCard (that can contain geo) be a better way of representing locations referred to in the story, as more human readable?<br />
** The reason for geo being highlighted (as an optional field) is to promote at least one location identifier in the story--preferably the most appropriate single location on a map for that particular story. Geo does not have to be related to dateline, but in some [http://labs.ap.org/wiki/hNews examples] we've worked on, we show the two collapsed into a single field. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)<br />
** For locations referred to in the story, I agree--publishers should be using [[hCard]] with the contained geo to markup the locations themselves. One of the concepts I've struggled with is drawing an admittedly arbitrary line between the metadata ''about'' a story from the metadata ''within'' a story. For the former, we've focused on simplicity and minimalism, primarily as a means to encourage adoption. That has meant preferring [[rel-tag]] over in-line entity extraction and markup using compound microformats. For the latter, we feel that the field is open: use whatever microformat fits your purpose, however you can--the more, the better. This lets publishers with minimal technology capabilities at least get started by tweaking a few templates in their CMS, while those more technically inclined aren't limited by the simplicity of the format to a paucity of data. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)<br />
** Also, dateline can be text or [[hCard]], as noted in the [[news-brainstorming#Common_News_Fields|Common News Fields]] section. --[[User:JonathanMalek|JonathanMalek]] 18:17, 24 September 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">What is item-license?</strong> Using [[rel-license]] presumably?<br />
** We're working off the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] discussions for this. Our concern with [[rel-license]] was its definition as applying to an entire page, rather than an item within a page. The current discussions around licensing definitely address that. --[[User:JonathanMalek|JonathanMalek]] 00:02, 25 August 2009 (UTC)<br />
*** +1 using item-license for news-brainstorming makes sense. [[User:Tantek|Tantek]] 22:32, 27 August 2009 (UTC)<br />
</div><br />
</div></div>JonathanMalekhttp://microformats.org/wiki/index.php?title=hnews-examples-in-wild&diff=41131hnews-examples-in-wild2009-10-20T15:52:21Z<p>JonathanMalek: fixing typo</p>
<hr />
<div><h1>hNews Examples in the wild </h1><br />
This page is an '''informative''' section of the [[hnews|hNews]] specification.<br />
<br />
The following sites have published [[hnews|hNews]], and thus are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc. <br />
<br />
If you publish hNews on your own site, feel free to add it to the '''top''' of this list. Please be sure to include at least one URL to a page on your site that includes actual [[hnews|hNews]] markup. Examples added without a URL to a page with hNews markup may be removed. <br />
<br />
<br />
== New Examples ==</div>JonathanMalekhttp://microformats.org/wiki/index.php?title=hnews-examples-in-wild&diff=41130hnews-examples-in-wild2009-10-20T15:33:14Z<p>JonathanMalek: creating examples in wild for hnews page</p>
<hr />
<div><h1>hReview Examples in the wild </h1><br />
This page is an '''informative''' section of the [[hnews|hNews]] specification.<br />
<br />
The following sites have published [[hnews|hNews]], and thus are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc. <br />
<br />
If you publish hNews on your own site, feel free to add it to the '''top''' of this list. Please be sure to include at least one URL to a page on your site that includes actual [[hnews|hNews]] markup. Examples added without a URL to a page with hNews markup may be removed. <br />
<br />
<br />
== New Examples ==</div>JonathanMalekhttp://microformats.org/wiki/index.php?title=hnews-issues&diff=41128hnews-issues2009-10-20T14:09:18Z<p>JonathanMalek: Moving TOC to top</p>
<hr />
<div><h1> hNews issues </h1><br />
<br />
__TOC__<br />
<br />
These are externally raised issues about [[hnews|hNews]] with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the draft. <br />
<br />
'''IMPORTANT''': Please read the [[hnews-faq|hNews FAQ]] before giving any feedback or raising any issues as your feedback/issues may already be resolved/answered.<br />
<br />
Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — [http://tantek.com/ Tantek]<br />
<br />
Please add new issues to the '''top''' of the list. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.<br />
<br />
See related [[hatom-issues]] and [[hcard-issues]].<br />
<br />
== Template ==<br />
<br />
{{issues-format}}<br />
<br />
<br />
== Issues ==<br />
=== Open Issues ===<br />
<br />
<div class="hentry"><br />
{{OpenIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-20</span> raised by <span class="fn">[[User:MilesD|Miles De Feyter]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">News, Commentary, and Opinion pieces as they relate to hNews</strong>. An interesting comment came up today when looking at how to use hNews on other AOL properties outside of our main news site, and that is, some of our sites are both news and commentary. Let's take our sports site for example http://www.fanhouse.com/ <br />
<br />
This site reports on sports news with article headlines such as: <br />
[http://www.fanhouse.com/news/nfl/big-ben-tops-pass-rankings/723353 Big Ben tops pass rankings]<br />
<br />
But fanhouse.com also has some obvious opinion pieces such as:<br />
[http://kevin-blackistone.fanhouse.com/2009/10/19/ail-to-the-redskins-worst-run-franchise-on-the-planet/ Fail to the Redskins: Worst-Run Franchise on the Planet]<br />
<br />
Currently we have one publishing system for all of our content within Fanhouse whether it be feed driven, in house publisher, news content, or commentary. So at the moment if one thing gets hNews it all does. <br />
<br />
Have you given this situation thought? My initial thinking is that perhaps this is where a principles statement specific to Fanhouse could account for the different types of content being labeled hNews. <br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{OpenIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-14</span> raised by <span class="fn">[[User:MarkNg|MarkNg]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">adr for dateline</strong>. From [http://twitter.com/pigsonthewing/status/4831500605 Andy Mabbett on Twitter] : hNews microformat spec "dateline. optional. Using text or hCard" should read "dateline. optional. Using text, adr or hCard".<br />
** Seems like a useful extra to me, any objections ? [[User:MarkNg|MarkNg]]<br />
** Agreed, makes sense. --[[User:JonathanMalek|JonathanMalek]] 00:57, 15 October 2009 (UTC)<br />
** +1 to addition of optional "adr" markup of "dateline", but should also allow "geo" markup of "dateline" as well. i.e. change: <blockquote><p>* a dateline element MAY be encoded in an hCard.</p></blockquote> to <blockquote><p>* a dateline element MAY be encoded with an [[adr]], [[geo]], or [[hCard]] on the same element.</p></blockquote> [[User:Tantek|Tantek]] 19:57, 15 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
=== Resolved Issues ===<br />
<br />
<div class="hentry"><br />
{{ResolvedIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-15</span> raised by <span class="fn">[[User:TobyInk|TobyInk]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">XMDP defines 'principles' incorrectly.</strong> The XMDP for hNews defines 'principles' as a class, whereas the rest of the draft refers to it as a link type (i.e. 'rel' value).<br />
** ACCEPTED SPEC UPDATE. FIXED: thanks for pointing that out. I believe the updated profile reflects that correctly now. --[[User:JonathanMalek|JonathanMalek]] 15:37, 15 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
=== Closed Issues ===<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-09</span> raised by <span class="fn">Miles De Feyter</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Implementation of item-license as it relates to hNews</strong>. Reading through the item-license brainstorm it seems to indicate that "item-license" would need to be nested within something with the class of "item". So as this relates to hNews is the suggestion to then have an articles containing div have the three class names of "hnews hentry item"?<br />
** At this point, Miles, that is correct (following the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] concept and guidance). I expect we'll see changes around item-license (it's still just brainstorming), but for the time being, the third class name "item" is needed. --[[User:JonathanMalek|JonathanMalek]] 16:25, 12 October 2009 (UTC)<br />
** Added to [[hnews-faq]] --[[User:JonathanMalek|JonathanMalek]] 02:19, 14 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">2009-09-28</span> raised by <span class="fn">[[User:MilesD|Miles De Feyter]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Principles as a requirement</strong>. Working for a publishing company that owns and operates a large number of different organizations I'd love to incorporate hNews within our publishing system. The hNews requirement for a principles statement could pose a problem though or at least make rolling out hNews a more involved process then it would be otherwise. The issue is, I would now have to go to each product owner and ask then to provide this principles statement to link to. So my concern is now rather then just making a change to the publishing system to support hNews there is this requirement for some supporting content. And due to the nature of the content I can only assume our legal dep. would need to sign off as well, further complicating the adoption of hNews.<br />
** +1 I agree that the "principles" property (and probably all other others) should be optional. [[User:Tantek|Tantek]] 18:29, 29 September 2009 (UTC)<br />
*** I think it's important to explain why principles is a requirement. hnews is essentially a specialization of hAtom. Its purpose is to distinguish news on the web. Hence the description of source organisation, license and principles. Of these, principles is the only one which consistently distinguishes news on the web from other content (eg. commercial, government). In the future it should be distinguished further by making the principles themselves machine readable (but that is for a later date). Most professional news organisations adhere to a Statement of Principles (e.g. see http://en.wikipedia.org/wiki/Journalism_ethics_and_standards and http://www.journalism.org/resources/ethics_codes). If a site wants to mark up its content but does not want to distinguish it as news, then wouldn't it be easiest to use hAtom? [[User:martinjemoore|Martin Moore]] 9:00, 20 September 2009 (UTC)<br />
*** Having discussed this issue at length outside this brainstorming, we understand some of the concerns of the microformat community regarding 'must', but are still convinced of the criticality of principles to hNews - therefore recommend downgrading from 'must' to 'should'. [[User:martinjemoore|Martin Moore]] 14:00, 7 October 2009 (UTC)<br />
**** Accepted and implemented in 0.1. In keeping with the general direction here, we've changed <code>item-license</code> as well, and would consider adopting the same with <code>source-org</code> as well, if it proves to present the same problems. --[[User:JonathanMalek|JonathanMalek]] 00:53, 15 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">hCalendar instead of dateline?</strong> Would an [[hCalendar]] event (which can contain an hCard location) make sense for a dateline, or is the 'date' part more often omitted?<br />
** Confusingly, the journalistic term "dateline" isn't anything to do with a date or time. It is the location from which a report is filed and is generally the main location associated with a story. Generally, a dateline consists of a city (e.g. "Rome") but could be the name of a ship at sea or even a space station. [[User:Stuart Myles|Stuart Myles]] 21:12, 24 August 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">hCard instead of geo?</strong> Is geo really in use here, or would using an hCard (that can contain geo) be a better way of representing locations referred to in the story, as more human readable?<br />
** The reason for geo being highlighted (as an optional field) is to promote at least one location identifier in the story--preferably the most appropriate single location on a map for that particular story. Geo does not have to be related to dateline, but in some [http://labs.ap.org/wiki/hNews examples] we've worked on, we show the two collapsed into a single field. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)<br />
** For locations referred to in the story, I agree--publishers should be using [[hCard]] with the contained geo to markup the locations themselves. One of the concepts I've struggled with is drawing an admittedly arbitrary line between the metadata ''about'' a story from the metadata ''within'' a story. For the former, we've focused on simplicity and minimalism, primarily as a means to encourage adoption. That has meant preferring [[rel-tag]] over in-line entity extraction and markup using compound microformats. For the latter, we feel that the field is open: use whatever microformat fits your purpose, however you can--the more, the better. This lets publishers with minimal technology capabilities at least get started by tweaking a few templates in their CMS, while those more technically inclined aren't limited by the simplicity of the format to a paucity of data. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)<br />
** Also, dateline can be text or [[hCard]], as noted in the [[news-brainstorming#Common_News_Fields|Common News Fields]] section. --[[User:JonathanMalek|JonathanMalek]] 18:17, 24 September 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">What is item-license?</strong> Using [[rel-license]] presumably?<br />
** We're working off the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] discussions for this. Our concern with [[rel-license]] was its definition as applying to an entire page, rather than an item within a page. The current discussions around licensing definitely address that. --[[User:JonathanMalek|JonathanMalek]] 00:02, 25 August 2009 (UTC)<br />
*** +1 using item-license for news-brainstorming makes sense. [[User:Tantek|Tantek]] 22:32, 27 August 2009 (UTC)<br />
</div><br />
</div></div>JonathanMalekhttp://microformats.org/wiki/index.php?title=hnews-issues&diff=41127hnews-issues2009-10-20T14:08:26Z<p>JonathanMalek: /* Issues */ : Creating resolved issues section, more whitespace</p>
<hr />
<div><h1> hNews issues </h1><br />
<br />
These are externally raised issues about [[hnews|hNews]] with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the draft. <br />
<br />
'''IMPORTANT''': Please read the [[hnews-faq|hNews FAQ]] before giving any feedback or raising any issues as your feedback/issues may already be resolved/answered.<br />
<br />
Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — [http://tantek.com/ Tantek]<br />
<br />
Please add new issues to the '''top''' of the list. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.<br />
<br />
See related [[hatom-issues]] and [[hcard-issues]].<br />
<br />
== Template ==<br />
<br />
{{issues-format}}<br />
<br />
__TOC__<br />
<br />
== Issues ==<br />
=== Open Issues ===<br />
<br />
<div class="hentry"><br />
{{OpenIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-20</span> raised by <span class="fn">[[User:MilesD|Miles De Feyter]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">News, Commentary, and Opinion pieces as they relate to hNews</strong>. An interesting comment came up today when looking at how to use hNews on other AOL properties outside of our main news site, and that is, some of our sites are both news and commentary. Let's take our sports site for example http://www.fanhouse.com/ <br />
<br />
This site reports on sports news with article headlines such as: <br />
[http://www.fanhouse.com/news/nfl/big-ben-tops-pass-rankings/723353 Big Ben tops pass rankings]<br />
<br />
But fanhouse.com also has some obvious opinion pieces such as:<br />
[http://kevin-blackistone.fanhouse.com/2009/10/19/ail-to-the-redskins-worst-run-franchise-on-the-planet/ Fail to the Redskins: Worst-Run Franchise on the Planet]<br />
<br />
Currently we have one publishing system for all of our content within Fanhouse whether it be feed driven, in house publisher, news content, or commentary. So at the moment if one thing gets hNews it all does. <br />
<br />
Have you given this situation thought? My initial thinking is that perhaps this is where a principles statement specific to Fanhouse could account for the different types of content being labeled hNews. <br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{OpenIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-14</span> raised by <span class="fn">[[User:MarkNg|MarkNg]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">adr for dateline</strong>. From [http://twitter.com/pigsonthewing/status/4831500605 Andy Mabbett on Twitter] : hNews microformat spec "dateline. optional. Using text or hCard" should read "dateline. optional. Using text, adr or hCard".<br />
** Seems like a useful extra to me, any objections ? [[User:MarkNg|MarkNg]]<br />
** Agreed, makes sense. --[[User:JonathanMalek|JonathanMalek]] 00:57, 15 October 2009 (UTC)<br />
** +1 to addition of optional "adr" markup of "dateline", but should also allow "geo" markup of "dateline" as well. i.e. change: <blockquote><p>* a dateline element MAY be encoded in an hCard.</p></blockquote> to <blockquote><p>* a dateline element MAY be encoded with an [[adr]], [[geo]], or [[hCard]] on the same element.</p></blockquote> [[User:Tantek|Tantek]] 19:57, 15 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
=== Resolved Issues ===<br />
<br />
<div class="hentry"><br />
{{ResolvedIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-15</span> raised by <span class="fn">[[User:TobyInk|TobyInk]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">XMDP defines 'principles' incorrectly.</strong> The XMDP for hNews defines 'principles' as a class, whereas the rest of the draft refers to it as a link type (i.e. 'rel' value).<br />
** ACCEPTED SPEC UPDATE. FIXED: thanks for pointing that out. I believe the updated profile reflects that correctly now. --[[User:JonathanMalek|JonathanMalek]] 15:37, 15 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
=== Closed Issues ===<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-09</span> raised by <span class="fn">Miles De Feyter</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Implementation of item-license as it relates to hNews</strong>. Reading through the item-license brainstorm it seems to indicate that "item-license" would need to be nested within something with the class of "item". So as this relates to hNews is the suggestion to then have an articles containing div have the three class names of "hnews hentry item"?<br />
** At this point, Miles, that is correct (following the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] concept and guidance). I expect we'll see changes around item-license (it's still just brainstorming), but for the time being, the third class name "item" is needed. --[[User:JonathanMalek|JonathanMalek]] 16:25, 12 October 2009 (UTC)<br />
** Added to [[hnews-faq]] --[[User:JonathanMalek|JonathanMalek]] 02:19, 14 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">2009-09-28</span> raised by <span class="fn">[[User:MilesD|Miles De Feyter]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Principles as a requirement</strong>. Working for a publishing company that owns and operates a large number of different organizations I'd love to incorporate hNews within our publishing system. The hNews requirement for a principles statement could pose a problem though or at least make rolling out hNews a more involved process then it would be otherwise. The issue is, I would now have to go to each product owner and ask then to provide this principles statement to link to. So my concern is now rather then just making a change to the publishing system to support hNews there is this requirement for some supporting content. And due to the nature of the content I can only assume our legal dep. would need to sign off as well, further complicating the adoption of hNews.<br />
** +1 I agree that the "principles" property (and probably all other others) should be optional. [[User:Tantek|Tantek]] 18:29, 29 September 2009 (UTC)<br />
*** I think it's important to explain why principles is a requirement. hnews is essentially a specialization of hAtom. Its purpose is to distinguish news on the web. Hence the description of source organisation, license and principles. Of these, principles is the only one which consistently distinguishes news on the web from other content (eg. commercial, government). In the future it should be distinguished further by making the principles themselves machine readable (but that is for a later date). Most professional news organisations adhere to a Statement of Principles (e.g. see http://en.wikipedia.org/wiki/Journalism_ethics_and_standards and http://www.journalism.org/resources/ethics_codes). If a site wants to mark up its content but does not want to distinguish it as news, then wouldn't it be easiest to use hAtom? [[User:martinjemoore|Martin Moore]] 9:00, 20 September 2009 (UTC)<br />
*** Having discussed this issue at length outside this brainstorming, we understand some of the concerns of the microformat community regarding 'must', but are still convinced of the criticality of principles to hNews - therefore recommend downgrading from 'must' to 'should'. [[User:martinjemoore|Martin Moore]] 14:00, 7 October 2009 (UTC)<br />
**** Accepted and implemented in 0.1. In keeping with the general direction here, we've changed <code>item-license</code> as well, and would consider adopting the same with <code>source-org</code> as well, if it proves to present the same problems. --[[User:JonathanMalek|JonathanMalek]] 00:53, 15 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">hCalendar instead of dateline?</strong> Would an [[hCalendar]] event (which can contain an hCard location) make sense for a dateline, or is the 'date' part more often omitted?<br />
** Confusingly, the journalistic term "dateline" isn't anything to do with a date or time. It is the location from which a report is filed and is generally the main location associated with a story. Generally, a dateline consists of a city (e.g. "Rome") but could be the name of a ship at sea or even a space station. [[User:Stuart Myles|Stuart Myles]] 21:12, 24 August 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">hCard instead of geo?</strong> Is geo really in use here, or would using an hCard (that can contain geo) be a better way of representing locations referred to in the story, as more human readable?<br />
** The reason for geo being highlighted (as an optional field) is to promote at least one location identifier in the story--preferably the most appropriate single location on a map for that particular story. Geo does not have to be related to dateline, but in some [http://labs.ap.org/wiki/hNews examples] we've worked on, we show the two collapsed into a single field. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)<br />
** For locations referred to in the story, I agree--publishers should be using [[hCard]] with the contained geo to markup the locations themselves. One of the concepts I've struggled with is drawing an admittedly arbitrary line between the metadata ''about'' a story from the metadata ''within'' a story. For the former, we've focused on simplicity and minimalism, primarily as a means to encourage adoption. That has meant preferring [[rel-tag]] over in-line entity extraction and markup using compound microformats. For the latter, we feel that the field is open: use whatever microformat fits your purpose, however you can--the more, the better. This lets publishers with minimal technology capabilities at least get started by tweaking a few templates in their CMS, while those more technically inclined aren't limited by the simplicity of the format to a paucity of data. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)<br />
** Also, dateline can be text or [[hCard]], as noted in the [[news-brainstorming#Common_News_Fields|Common News Fields]] section. --[[User:JonathanMalek|JonathanMalek]] 18:17, 24 September 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">What is item-license?</strong> Using [[rel-license]] presumably?<br />
** We're working off the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] discussions for this. Our concern with [[rel-license]] was its definition as applying to an entire page, rather than an item within a page. The current discussions around licensing definitely address that. --[[User:JonathanMalek|JonathanMalek]] 00:02, 25 August 2009 (UTC)<br />
*** +1 using item-license for news-brainstorming makes sense. [[User:Tantek|Tantek]] 22:32, 27 August 2009 (UTC)<br />
</div><br />
</div></div>JonathanMalekhttp://microformats.org/wiki/index.php?title=hnews-issues&diff=41126hnews-issues2009-10-20T14:06:34Z<p>JonathanMalek: /* Open Issues */ : moving resolved issue</p>
<hr />
<div><h1> hNews issues </h1><br />
<br />
These are externally raised issues about [[hnews|hNews]] with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the draft. <br />
<br />
'''IMPORTANT''': Please read the [[hnews-faq|hNews FAQ]] before giving any feedback or raising any issues as your feedback/issues may already be resolved/answered.<br />
<br />
Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — [http://tantek.com/ Tantek]<br />
<br />
Please add new issues to the '''top''' of the list. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.<br />
<br />
See related [[hatom-issues]] and [[hcard-issues]].<br />
<br />
== Template ==<br />
<br />
{{issues-format}}<br />
<br />
__TOC__<br />
<br />
== Issues ==<br />
=== Open Issues ===<br />
<br />
<div class="hentry"><br />
{{OpenIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-20</span> raised by <span class="fn">[[User:MilesD|Miles De Feyter]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">News, Commentary, and Opinion pieces as they relate to hNews</strong>. An interesting comment came up today when looking at how to use hNews on other AOL properties outside of our main news site, and that is, some of our sites are both news and commentary. Let's take our sports site for example http://www.fanhouse.com/ <br />
<br />
This site reports on sports news with article headlines such as: <br />
[http://www.fanhouse.com/news/nfl/big-ben-tops-pass-rankings/723353 Big Ben tops pass rankings]<br />
<br />
But fanhouse.com also has some obvious opinion pieces such as:<br />
[http://kevin-blackistone.fanhouse.com/2009/10/19/ail-to-the-redskins-worst-run-franchise-on-the-planet/ Fail to the Redskins: Worst-Run Franchise on the Planet]<br />
<br />
Currently we have one publishing system for all of our content within Fanhouse whether it be feed driven, in house publisher, news content, or commentary. So at the moment if one thing gets hNews it all does. <br />
<br />
Have you given this situation thought? My initial thinking is that perhaps this is where a principles statement specific to Fanhouse could account for the different types of content being labeled hNews. <br />
</div><br />
<br />
<div class="hentry"><br />
{{OpenIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-14</span> raised by <span class="fn">[[User:MarkNg|MarkNg]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">adr for dateline</strong>. From [http://twitter.com/pigsonthewing/status/4831500605 Andy Mabbett on Twitter] : hNews microformat spec "dateline. optional. Using text or hCard" should read "dateline. optional. Using text, adr or hCard".<br />
** Seems like a useful extra to me, any objections ? [[User:MarkNg|MarkNg]]<br />
** Agreed, makes sense. --[[User:JonathanMalek|JonathanMalek]] 00:57, 15 October 2009 (UTC)<br />
** +1 to addition of optional "adr" markup of "dateline", but should also allow "geo" markup of "dateline" as well. i.e. change: <blockquote><p>* a dateline element MAY be encoded in an hCard.</p></blockquote> to <blockquote><p>* a dateline element MAY be encoded with an [[adr]], [[geo]], or [[hCard]] on the same element.</p></blockquote> [[User:Tantek|Tantek]] 19:57, 15 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
=== Closed Issues ===<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-09</span> raised by <span class="fn">Miles De Feyter</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Implementation of item-license as it relates to hNews</strong>. Reading through the item-license brainstorm it seems to indicate that "item-license" would need to be nested within something with the class of "item". So as this relates to hNews is the suggestion to then have an articles containing div have the three class names of "hnews hentry item"?<br />
** At this point, Miles, that is correct (following the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] concept and guidance). I expect we'll see changes around item-license (it's still just brainstorming), but for the time being, the third class name "item" is needed. --[[User:JonathanMalek|JonathanMalek]] 16:25, 12 October 2009 (UTC)<br />
** Added to [[hnews-faq]] --[[User:JonathanMalek|JonathanMalek]] 02:19, 14 October 2009 (UTC)<br />
</div><br />
</div><br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">2009-09-28</span> raised by <span class="fn">[[User:MilesD|Miles De Feyter]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Principles as a requirement</strong>. Working for a publishing company that owns and operates a large number of different organizations I'd love to incorporate hNews within our publishing system. The hNews requirement for a principles statement could pose a problem though or at least make rolling out hNews a more involved process then it would be otherwise. The issue is, I would now have to go to each product owner and ask then to provide this principles statement to link to. So my concern is now rather then just making a change to the publishing system to support hNews there is this requirement for some supporting content. And due to the nature of the content I can only assume our legal dep. would need to sign off as well, further complicating the adoption of hNews.<br />
** +1 I agree that the "principles" property (and probably all other others) should be optional. [[User:Tantek|Tantek]] 18:29, 29 September 2009 (UTC)<br />
*** I think it's important to explain why principles is a requirement. hnews is essentially a specialization of hAtom. Its purpose is to distinguish news on the web. Hence the description of source organisation, license and principles. Of these, principles is the only one which consistently distinguishes news on the web from other content (eg. commercial, government). In the future it should be distinguished further by making the principles themselves machine readable (but that is for a later date). Most professional news organisations adhere to a Statement of Principles (e.g. see http://en.wikipedia.org/wiki/Journalism_ethics_and_standards and http://www.journalism.org/resources/ethics_codes). If a site wants to mark up its content but does not want to distinguish it as news, then wouldn't it be easiest to use hAtom? [[User:martinjemoore|Martin Moore]] 9:00, 20 September 2009 (UTC)<br />
*** Having discussed this issue at length outside this brainstorming, we understand some of the concerns of the microformat community regarding 'must', but are still convinced of the criticality of principles to hNews - therefore recommend downgrading from 'must' to 'should'. [[User:martinjemoore|Martin Moore]] 14:00, 7 October 2009 (UTC)<br />
**** Accepted and implemented in 0.1. In keeping with the general direction here, we've changed <code>item-license</code> as well, and would consider adopting the same with <code>source-org</code> as well, if it proves to present the same problems. --[[User:JonathanMalek|JonathanMalek]] 00:53, 15 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">hCalendar instead of dateline?</strong> Would an [[hCalendar]] event (which can contain an hCard location) make sense for a dateline, or is the 'date' part more often omitted?<br />
** Confusingly, the journalistic term "dateline" isn't anything to do with a date or time. It is the location from which a report is filed and is generally the main location associated with a story. Generally, a dateline consists of a city (e.g. "Rome") but could be the name of a ship at sea or even a space station. [[User:Stuart Myles|Stuart Myles]] 21:12, 24 August 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">hCard instead of geo?</strong> Is geo really in use here, or would using an hCard (that can contain geo) be a better way of representing locations referred to in the story, as more human readable?<br />
** The reason for geo being highlighted (as an optional field) is to promote at least one location identifier in the story--preferably the most appropriate single location on a map for that particular story. Geo does not have to be related to dateline, but in some [http://labs.ap.org/wiki/hNews examples] we've worked on, we show the two collapsed into a single field. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)<br />
** For locations referred to in the story, I agree--publishers should be using [[hCard]] with the contained geo to markup the locations themselves. One of the concepts I've struggled with is drawing an admittedly arbitrary line between the metadata ''about'' a story from the metadata ''within'' a story. For the former, we've focused on simplicity and minimalism, primarily as a means to encourage adoption. That has meant preferring [[rel-tag]] over in-line entity extraction and markup using compound microformats. For the latter, we feel that the field is open: use whatever microformat fits your purpose, however you can--the more, the better. This lets publishers with minimal technology capabilities at least get started by tweaking a few templates in their CMS, while those more technically inclined aren't limited by the simplicity of the format to a paucity of data. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)<br />
** Also, dateline can be text or [[hCard]], as noted in the [[news-brainstorming#Common_News_Fields|Common News Fields]] section. --[[User:JonathanMalek|JonathanMalek]] 18:17, 24 September 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">What is item-license?</strong> Using [[rel-license]] presumably?<br />
** We're working off the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] discussions for this. Our concern with [[rel-license]] was its definition as applying to an entire page, rather than an item within a page. The current discussions around licensing definitely address that. --[[User:JonathanMalek|JonathanMalek]] 00:02, 25 August 2009 (UTC)<br />
*** +1 using item-license for news-brainstorming makes sense. [[User:Tantek|Tantek]] 22:32, 27 August 2009 (UTC)<br />
</div><br />
</div></div>JonathanMalekhttp://microformats.org/wiki/index.php?title=Main_Page&diff=41116Main Page2009-10-19T00:31:16Z<p>JonathanMalek: /* Drafts */ : adding hNews to drafts list</p>
<hr />
<div><entry-title>Welcome to the microformats wiki!</entry-title><br />
__TOC__<br />
Please start with the [[introduction]] page and read [[how-to-play]] before making any edits.<br />
<br />
==Introduction==<br />
This wiki is the central resource of the microformats community. You'll find current versions of published microformat specifications, specification drafts and publishing patterns. The wiki also hosts development resources, such as brainstorming pages for new formats and issue tracking pages for all current and in-development microformats.<br />
<br />
== Get Started==<br />
To get started with microformats:<br />
<br />
* First, be familiar writing your pages and applications with semantically rich, descriptive, ‘[[posh|<abbr title="Plain Old Semantic HTML">POSH</abbr>]]’ <abbr title="HyperText Mark-up Language">HTML</abbr>.<br />
* Learn about microformats from the [http://microformats.org/about/ about page], [http://microformats.org/ blog], [[press]], [[presentations]], [[books]], [[podcasts]], & [[screencasts]] pages.<br />
* Take a look at established specifications such as [[hcard|hCard]] and [[hcalendar|hCalendar]], and follow the [[hcard-examples|examples]] to start publishing microformats.<br />
* Have questions? Read the [[faq|frequently asked questions]] and see the [[glossary]] for terms and definitions. You can also post to the {{MicroformatsMailingList}}.<br />
* Want to learn more in person? Check out microformats [[events]].<br />
<br />
==Definition==<br />
Microformats are small patterns of HTML to represent commonly published things like [[hcard|people]], [[hcalendar|events]], [[hatom|blog posts]], [[hreview|reviews]] and [[rel-tag|tags]] in web pages.<br />
<br />
Microformats enable the publishing of higher fidelity information on the Web; the fastest and simplest way to provide feeds and APIs for the information in your website.<br />
<br />
* Read more explanations of [[what-are-microformats|what microformats are]], and [[what-can-you-do-with-microformats|what you can do with them]].<br />
<br />
== How to contribute ==<br />
Do you want to help take microformats to the next level? You can:<br />
<br />
* [[get-started|Get started]] by adding microformats to your website, services, and products.<br />
* [[advocacy|Advocate]] the use of microformats on other web sites, especially those you use.<br />
* Write a [[testimonial]].<br />
* Do something on the [[to-do|to do list]].<br />
* Join the [[irc|IRC Channel]] and [[mail|mailing lists]] to learn and help answer questions (read the [[mailing-lists#General_guidelines|general guidelines]] before posting).<br />
* [[Main_Page#microformats_wiki_translations|Translate this microformats wiki into other languages]] to make microformats more accessible to readers of languages around the world.<br />
* Before proposing any new microformats, make sure your website is [[POSH]], [[get-started|uses existing microformats]], and then read the [[process]].<br />
<br />
This wiki has a number of enhancements to assist development and contributions to microformats. Before you start editing, see the [[wiki-2|wiki introduction page]] for instructions.<br />
<br />
== Specifications ==<br />
The list of current, stable [[microformats|Microformats]] open standard specifications.<br />
<br />
* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hCalendar creator]<br />
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hCard creator]<br />
* [[rel-license]]<br />
* [[rel-nofollow]]<br />
* [[rel-tag]]<br />
* [[vote-links|VoteLinks]]<br />
* [[XFN]] - [http://gmpg.org/xfn/creator XFN creator]<br />
* [[XMDP]]<br />
* [[xoxo|XOXO]]<br />
<br />
''If you're tempted to try your hand at writing a microformat please read '''[[process|the process]]''' page first!''<br />
<br />
== Drafts ==<br />
Drafts are newer microformats, for which the specifications haven't been completed yet. Drafts are somewhat mature in the development [[process]] (see [[exploratory-discussions]] for additional efforts that are not as far along in the process). The stability of these documents cannot be guaranteed, and implementers should be prepared to keep abreast of future developments and changes. Please watch the wiki pages for updates.<br />
<br />
* [[adr|adr]] - for marking up address information<br />
* [[geo|geo]] - for marking up [http://en.wikipedia.org/wiki/WGS84 WGS84] geographic coordinates (latitude; longitude)<br />
* [[hatom|hAtom]] - syndicating episodic content (e.g. weblog postings)<br />
* [[haudio|hAudio]]<br />
* [[hmedia|hMedia]] - A single media publishing format that relates to Images, Video and Audio. <br />
* [[hnews|hNews]]<br />
* [[hproduct|hProduct]]<br />
* [[hrecipe|hRecipe]] - for cooking+baking recipes<br />
* [[hresume|hResume]] - for publishing resumes and CVs<br />
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hReview creator]<br />
* [[rel-directory]] - to indicate that the destination of a hyperlink is a directory listing containing an entry for the current page<br />
* [[rel-enclosure]] - for indicating attachments (e.g. files) to download and cache<br />
* [[rel-home]] - indicate a hyperlink to the homepage of the site<br />
* [[rel-payment]] - indicate a payment mechanism<br />
* [[robots-exclusion|robots exclusion]]<br />
* [[xfolk|xFolk]]<br />
<br />
== Design Patterns ==<br />
{{design_patterns}} <!-- this can be edited in /wiki/Template:design_patterns --><br />
<br />
== Exploratory Discussions ==<br />
See: [[exploratory-discussions]] for details of research and analysis of real-world [[examples]], existing formats, and brainstorming of possible new microformats, per the microformats [[process]].<br />
<br />
== Examples ==<br />
* [[examples-in-the-wild]]<br />
* [[implementations]]<br />
* [[zen-garden]]<br />
<br />
== Resources ==<br />
See [[resources]].<br />
<br />
== User centric development ==<br />
*[[user-interface]]<br />
*[[data-portability]]<br />
*[[social-network-portability]]<br />
<br />
== Shared work areas ==<br />
* [[to-do]]<br />
* [[templates]]<br />
* [http://microformats.org/wiki/delete pages for deletion] <!-- keep as external link; removes from "what links here" --><br />
* [[Special:Specialpages|"Special" wiki pages]]<br />
* [[year-in-review]]<br />
<br />
== Tools, test cases, additional research ==<br />
The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting [[tools|tools and services]] that need to process more than one microformat. That section is intended for editors, [[parsers]], [[validators]], test cases, and other information relevant across multiple microformats.<br />
<br />
== Microformats wiki translations ==<br />
<span id="microformats_wiki_translations_in_other_languages">You may read and edit microformats articles in many other languages:</span><br />
<br />
* languages with over 100 articles<br />
** [[Main_Page-fr|<span lang="fr">Français</span> (French)]] <span lang="fr">{{UpdateMarker-fr}}</span><br />
* languages with over 10 articles<br />
** [[Main_Page-pt-br|<span lang="pt-br">Português</span> (Brazilian Portuguese)]]<br />
** [[Main_Page-ja|<span lang="ja">日本語</span> (Japanese)]]<br />
** [[Main_Page-ru|<span lang="ru">Русский</span> (Russian)]]<br />
* languages with over 2 articles<br />
** [[Main_Page-cs|<span lang="cs">Česky</span> (Czech)]] {{NewMarker}}<br />
** [[Main_Page-de|<span lang="de">Deutsch</span> (German)]]<br />
** [[Main_Page-es|<span lang="es">Español</span> (Spanish)]]<br />
** [[Main_Page-gl|<span lang="gl">Galego</span> (Galician)]] {{NewMarker}}<br />
** [[Main_Page-pl|<span lang="pl">Polski</span> (Polish)]]<br />
** [[Main_Page-ro|<span lang="ro">Română</span> (Romanian)]] {{NewMarker}}<br />
** [[Main_Page-zh|<span lang="zh">汉语</span> (Chinese)]]<br />
** [[Main_Page-id|<span lang="id">Indonesia</span> (Bahasa Indonesia)]] {{NewMarker}}<br />
* languages just started<br />
** [[Main_Page-ar|<span lang="ar">العربية</span> (Arabic)]]<br />
** [[Main_Page-th|<span lang="th">ภาษาไทย</span> (Thai)]]<br />
** [[Main_Page-it|<span lang="it">Italiano</span> (Italian)]] {{NewMarker}}<br />
** [[Main_Page-ko|<span lang="ko">한국어</span> (Korean)]] {{NewMarker}}<br />
* elsewhere<br />
**[http://en.wikipedia.org/wiki/Microformat Wikipedia's article on microformats] has been translated into a number of languages.<br />
<br />
See also [[other-languages]], and [[how-to-start-new-translation|how-to-start-a-new-translation]].</div>JonathanMalekhttp://microformats.org/wiki/index.php?title=exploratory-discussions&diff=41115exploratory-discussions2009-10-19T00:29:53Z<p>JonathanMalek: /* active */ : removing news from the active exploratory discussions</p>
<hr />
<div><h1>Exploratory Discussions</h1><br />
{{TOC-right}}<br />
Per the microformats [[process]]: research and analysis of real-world [[examples]], existing formats, and brainstorming to motivate the microformat. Please check [[rejected-formats]] before making additions.<br />
<br />
Sort each section alphabetically. Group similar efforts.<br />
<br />
==active==<br />
The following exploratory discussions are being actively pursued, generally, edited in the last month, and/or being utilized/experimented with by multiple sites in the wild.<br />
<br />
* [[activity-streams]]<br />
* [[citation]]: [[citation-examples|citation examples]], [[citation-formats|citation formats]], [[citation-brainstorming|citation brainstorming]], [[citation-strawman-01|h3988 proposal]] and [[citation-faq|citation FAQ]]<br />
* [[comment]] ([[comment-problem|comment problem]], [[comment-examples|comment examples]], [[comments-formats|comment formats]], and [[comment-brainstorming|comment brainstorming]]{{NewMarker}} (Some stuff needs to be extracted from [[comments-formats]], [[hcomment]] and [[mfcomment]]))<br />
* figures [[figure]], [[figure-examples|figure examples]], [[figure-formats]], [[figure-brainstorming|figure brainstorming]]<br />
* [[group]]: [[group-examples|group examples]], [[group-formats]], [[group-brainstorming|group brainstorming]] <br />
* listing / hListing [[hlisting-proposal|hListing proposal]], and [[hlisting-feedback|hListing feedback]] <br />
** based on listing [[listing-examples|examples]], [[listing-formats|formats]], and [[listing-brainstorming|brainstorming]]<br />
* measures and measurement units [[measure]], [[measure-examples]], [[measure-formats]]<br />
* [[mfo]]: [[mfo-examples]]<br />
* [[product]] - [[product-examples]], [[product-formats]], [[product-brainstorming]].<br />
* [[project|project]]{{NewMarker}}, [[project-examples|project examples]]{{NewMarker}}, [[project-formats|project formats]]{{NewMarker}}, [[project-brainstorming|project brainstorming]]{{NewMarker}}<br />
* [[recipe]] [[recipe-examples|recipe examples]], [[recipe-formats]], [[recipe-brainstorming]]<br />
* [[representative-hcard]] - see also [[uid]]<br />
* [[rel-shortlink]] {{NewMarker}}<br />
<br />
=== media related ===<br />
Media related efforts are very active in the microformats community and thus have been grouped here for convenience<br />
* [[audio-info]] ([[audio-info-examples|examples]], [[audio-info-formats|formats]], [[audio-info-brainstorming|brainstorming]], [[audio-info-proposal|proposal]], [[audio-info-issues|issues]], [[haudio|specification]]{{NewMarker}}) - Marking up information and metadata related to audio (speech, music, and sound in general).<br />
** music [[music-examples|music examples]]<br />
* audio-album (see [[audio-info]] pages for examples, formats, brainstorming. [[audio-album-proposal]], [[audio-album-issues]]) - Marking up information and metadata related to audio albums/collections.<br />
* broadcast: Internet Radio & TV: [[broadcast-examples]], [[broadcast-brainstorming]]<br />
* [[media-info]] ([[media-info-examples|media-info examples]], [[media-info-formats|media-info formats]], [[media-info-brainstorming|media-info brainstorming]], [[media-info-proposal| media-info Proposal]])<br />
* photo note [[photo-note-examples|photo note examples]]<br />
* video-info ([[video-info-examples|examples]], [[video-info-formats|formats]], [[video-info-brainstorming|brainstorming]], [[video-info-proposal|proposal]], [[video-info-issues|issues]]) - Marking up information and metadata related to video (video clips, movies, television, and video multimedia presentation in general).<br />
<br />
== other ==<br />
The following explorations are fairly inactive, though they may just be waiting for folks with sufficient interest and use cases to help further their development. Some of them could probably be consolidated, or even rejected with suggestions of re-using existing microformats.<br />
<br />
* [[alternates]] ([[alternates-examples|alternates examples]], [[alternates-formats]], [[alternates-brainstorming|alternates brainstorming]])<br />
*[[attention]]<br />
* book [[book-examples|book examples]], [[book-formats|book formats]], and [[book-brainstorming|book brainstorming]]<br />
* chat [[chat-examples|chat examples]], [[chat-formats|chat formats]], and [[chat-brainstorming|chat brainstorming]]<br />
* code [[code-examples|code examples]], [[code-formats]], [[code-brainstorming|code brainstorming]]<br />
* [[collection-description|collection description]] - for describing collections in libraries <br />
* [[definition-examples]]<br />
* [[depend-examples]]: examples of dependency graphs, especially as they relate to software <br />
* [[digital-signatures]]: incorporation of digital signatures in Microformatted data; ([[digitalsignature-examples|digital-signature examples]], [[digitalsignature-formats]], [[digitalsignature-brainstorming|digital-signatures brainstorming]]) <br />
* directions [[directions-examples|directions examples]] <br />
* [[downloads]] [[downloads-examples|downloads examples]], [[downloads-formats|downloads formats]], [[downloads-brainstorming|downloads brainstorming]] <br />
* [[error-message]] [[error-message-examples|error message examples]], [[error-message-formats]], [[error-message-brainstorming|error message brainstorming]]<br />
* file-format ([[file-format-examples|examples]], formats, brainstorming) - for the mark-up of file format information (size, type, codecs, bitrate, etc.) - should this be merged with [[downloads]] ?<br />
* forms [[forms-examples|forms examples]]<br />
* genealogy [[genealogy-examples]], [[genealogy-formats|genealogy formats]]<br />
* grouping ([[grouping-examples|examples]], [[grouping-formats|formats]], [[grouping-brainstorming|brainstorming]], [[grouping-proposal|proposal]]) - Metadata markup of items that should be grouped together. <br />
* hash [[hash-examples|hash examples]] (see also [[downloads]])<br />
* items [[items-examples|items examples]], [[items-formats]], [[items-brainstorming|items brainstorming]]<br />
* [[journal-brainstorming]]<br />
* last modified [[last-modified-examples|last modified examples]], [[last-modified-formats|last modified formats]], and [[last-modified-brainstorming|last modified brainstorming]]<br />
* metalink [[metalink-examples|metalink examples]] <br />
* [[operating-hours]]: [[operating-hours-examples]] ..of stores, restaurants, etc.<br />
* [[page-summary]] [[page-summary-examples]], [[page-summary-formats]]<br />
* [[payment]]<br />
* [[question-answer]], [[question-answer-examples]], [[question-answer-formats]], [[question-answer-brainstorming]] <br />
* requirements testing [[requirements-testing|requirements testing overview]], and [[requirements-testing-examples|requirements testing examples]]<br />
* [[rest-examples|REST examples]] (see also [[rest]])<br />
* search results [[search-results-example|search results example]]<br />
* [[species]] - for the marking up of the scientific names of living things: [[species-examples]], [[species-formats]], [[species-brainstorming]]<br />
* table [[table-examples|examples]]<br />
* transit table [[transit-table-examples|transit table examples]]<br />
* [[widget]], [[widget-examples|widget examples]], [[widget-formats]], [[widget-brainstorming|widget brainstorming]]<br />
* [[wiki-formats|wiki formats]]<br />
* work of art [[work-of-art|work of art overview]], [[workofart-examples|work of art examples]], [[workofart-formats|work of art formats]], and [[workofart-brainstorming|work of art brainstorming]]<br />
* [[xpn-examples]] - proposal to extend (or replicate) XFN for business (or professional - hence X'''P'''N) relationships <br />
<br />
=== blogging related ===<br />
* blog description [[blog-description-examples|blog description examples]]<br />
* blog info [[blog-info-examples|blog info examples]]<br />
* distributed conversation [[distributed-conversation|distributed conversation overview]], [[distributed-conversation-examples|distributed conversation examples]], [[distributed-conversation-formats|distributed conversation formats]], [[distributed-conversation-brainstorming|distributed conversation brainstorming]]<br />
* tagspeak [[tagspeak-examples|tagspeak examples]]<br />
* tagcloud [[tagcloud-examples|tagcloud examples]], [[tagcloud-formats]], and [[tagcloud-brainstorming|tagcloud brainstorming]].<br />
<br />
=== education related ===<br />
* higher education academic information<br />
** [[hied-course-examples]], [[hied-course-formats]], [[hied-course-brainstorming]] - an academic course activity<br />
** [[course-catalog]]; [[course-catalog-examples]] <br />
* learning ([[learning-examples|examples]], [[learning-formats|formats]], [[learning-brainstorming|brainstorming]], [[learning-people|people]], [[learning-proposal|proposal]], [[learning-issues|issues]]) - a microformat for microlearning<br />
<br />
=== productivity related ===<br />
* task [[htask|task effort]], [[task-examples|task examples]], [[task-formats|task formats]], [[task-brainstorming|task brainstorming]], and [[task-faq|task FAQ]]<br />
* [[to-do-examples]]<br />
* meeting minutes [[meeting-minutes-examples|meeting minutes examples]], [[meeting-minutes-formats|meeting minutes formats]], and [[meeting-minutes-brainstorming|meeting minutes brainstorming]]<br />
** meetings usually aren't very productive, yet, hopefully if meeting minutes are captured, meetings aren't a complete waste of time.<br />
<br />
=== commerce products listings related ===<br />
* bank account [[bankaccount-brainstorming]], [[bankaccount-examples]]<br />
* [[currency]]; [[currency-examples]]; [[currency-formats]]; [[currency-brainstorming]]; [[currency-proposal]]; [[currency-issues]]<br />
* job listing [[job-listing-examples|job listing examples]], [[job-listing-formats]], [[job-listing-brainstorming|job listing brainstorming]]<br />
* receipt ([[receipt-examples|examples]], [[receipt-formats|formats]], [[receipt-brainstorming|brainstorming]], [[receipt-proposal|proposal]]) - Marking up information and metadata related to purchase receipts.<br />
* [[wishlist]], [[wishlist-examples]]<br />
* [[hService_Proposal|proposal for selling commercial services]]<br />
<br />
== completed ==<br />
The following exploratory discussions resulted in a microformat.<br />
<br />
* blog post [[blog-post-examples|examples]], [[blog-post-formats|blog post formats]], and [[blog-post-brainstorming|blog post brainstorming]] (yielded the [[hatom|hAtom]] draft)<br />
* directory inclusion [[directory-inclusion-examples|directory inclusion examples]], [[directory-inclusion-formats|directory inclusion formats]]. (yielded the [[rel-directory]] microformat)<br />
* location [[location-examples]], [[location-formats|location formats]]. (see also [[adr]], [[geo]], [[hcard|hCard]])<br />
* resume [[resume-examples]], [[resume-formats|resume formats]], [[resume-brainstorming|resume brainstorming]] yielded the [[hresume|hResume]] draft.<br />
* review [[review-examples|review examples]], and [[review-formats|review formats]] yielded the [[hreview|hReview]] draft<br />
<br />
<br />
== solo pursuits ==<br />
The following are primarily pursued by a single individual and thus have not generated widespread interest in the community yet. In general, solo pursuits are discouraged. <br />
<br />
The goal of a format is to help human communication, the exchange of information between two people. Thus if only one community member is really interested in pursuing it (enough to work on it in the community), it's not important as a format. While a list of contributors or supporters helps demonstrate some broader interest, it is still insufficient if a format is only really being worked on in the community by a single individual.<br />
<br />
* geo extensions ([[User:AndyMabbett|Andy Mabbett]])<br />
** [[geo-elevation-examples]], [[geo-elevation-formats]] - extend geo for representing altitude <br />
** [[geo-waypoint-examples]], [[geo-waypoint-formats]] - extend geo for representing routes and boundaries, using waypoints <br />
** [[geo-extension-examples]], [[geo-extension-formats]], [[geo-extension-brainstorming]], [[geo-extension-strawman]] - extend geo for moons, other planets, etc.<br />
* [[off|OFF]]<br />
* [[hJoke]] a microformat used to delineate jokes/humor<br />
* [[itinerary]] ([[User:Lfbn|Luís Nóbrega]]), [[itinerary-examples]].<br />
<br />
== failed to follow process ==<br />
All too often it seems people propose a new microformat without following the [[process]] (most often not even reading apparently), nor creating the proper research pages first (and doing the research), nor sometimes even reading the [[introduction]] and [[how-to-play]] pages. Such proposals are relegated to this section to make it clear that they are worse than mere solo pursuits, they are (most of the time) solo pursuits by people who haven't even read the [[process]] page!<br />
<br />
In short, if you, the proposer, don't even bother to spend the time reading and attempting to use existing microformats (as the [[Main_Page]], [[introduction]], AND [[process]] page ask you to do so), how can you expect anyone else to bother to read and consider your proposal?<br />
<br />
* [[directory-proposal]]<br />
* [[realestate-propertydetail]], [[realestate-propertydetail-examples]], [[realestate-propertydetail-formats]], [[realestate-propertydetail brainstorming]]<br />
* show [[show-examples]], [[show-formats]], [[show-brainstorming|show brainstorming]]<br />
* showroll [[showroll-examples]], [[showroll-formats]], [[showroll-brainstorming]]<br />
* syllabus [[syllabus-examples]], [[syllabus-formats]], [[syllabus-brainstorming]]<br />
* [[web-page]]<br />
<br />
=== did not read main page ===<br />
Even worse, proposals by people who apparently didn't even bother to read the rest of the [[Main_Page]]!<br />
These are proposals that failed to follow the process and were added by the author to the [[Main_Page]] where it explicitly says to follow the process (often right next to where they added the link to their brainstorm proposal).<br />
<br />
* [[hwiki|hWiki]]<br />
* [[rel-ecolabel]]</div>JonathanMalekhttp://microformats.org/wiki/index.php?title=hnews-issues&diff=41083hnews-issues2009-10-15T15:37:43Z<p>JonathanMalek: XMDP rel-principles issue: updated</p>
<hr />
<div><h1> hNews issues </h1><br />
<br />
These are externally raised issues about [[hnews|hNews]] with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the draft. <br />
<br />
'''IMPORTANT''': Please read the [[hnews-faq|hNews FAQ]] before giving any feedback or raising any issues as your feedback/issues may already be resolved/answered.<br />
<br />
Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — [http://tantek.com/ Tantek]<br />
<br />
Please add new issues to the '''top''' of the list. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.<br />
<br />
See related [[hatom-issues]] and [[hcard-issues]].<br />
<br />
== Template ==<br />
<br />
{{issues-format}}<br />
<br />
__TOC__<br />
<br />
== Issues ==<br />
=== Open Issues ===<br />
<br />
<div class="hentry"><br />
{{OpenIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-15</span> raised by <span class="fn">[[User:TobyInk|TobyInk]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">XMDP defines 'principles' incorrectly.</strong> The XMDP for hNews defines 'principles' as a class, whereas the rest of the draft refers to it as a link type (i.e. 'rel' value).<br />
** FIXED: thanks for pointing that out. I believe the updated profile reflects that correctly now. --[[User:JonathanMalek|JonathanMalek]] 15:37, 15 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<div class="hentry"><br />
{{OpenIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-14</span> raised by <span class="fn">[[User:MarkNg|MarkNg]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">adr for dateline</strong>. From [[http://twitter.com/pigsonthewing/status/4831500605 Andy Mabbett on Twitter]] : hNews microformat spec "dateline. optional. Using text or hCard" should read "dateline. optional. Using text, adr or hCard".<br />
** Seems like a useful extra to me, any objections ? [[User:MarkNg|MarkNg]]<br />
** Agreed, makes sense. --[[User:JonathanMalek|JonathanMalek]] 00:57, 15 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
=== Closed Issues ===<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-09</span> raised by <span class="fn">Miles De Feyter</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Implementation of item-license as it relates to hNews</strong>. Reading through the item-license brainstorm it seems to indicate that "item-license" would need to be nested within something with the class of "item". So as this relates to hNews is the suggestion to then have an articles containing div have the three class names of "hnews hentry item"?<br />
** At this point, Miles, that is correct (following the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] concept and guidance). I expect we'll see changes around item-license (it's still just brainstorming), but for the time being, the third class name "item" is needed. --[[User:JonathanMalek|JonathanMalek]] 16:25, 12 October 2009 (UTC)<br />
** Added to [[hnews-faq]] --[[User:JonathanMalek|JonathanMalek]] 02:19, 14 October 2009 (UTC)<br />
</div><br />
</div><br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">2009-09-28</span> raised by <span class="fn">[[User:MilesD|Miles De Feyter]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Principles as a requirement</strong>. Working for a publishing company that owns and operates a large number of different organizations I'd love to incorporate hNews within our publishing system. The hNews requirement for a principles statement could pose a problem though or at least make rolling out hNews a more involved process then it would be otherwise. The issue is, I would now have to go to each product owner and ask then to provide this principles statement to link to. So my concern is now rather then just making a change to the publishing system to support hNews there is this requirement for some supporting content. And due to the nature of the content I can only assume our legal dep. would need to sign off as well, further complicating the adoption of hNews.<br />
** +1 I agree that the "principles" property (and probably all other others) should be optional. [[User:Tantek|Tantek]] 18:29, 29 September 2009 (UTC)<br />
*** I think it's important to explain why principles is a requirement. hnews is essentially a specialization of hAtom. Its purpose is to distinguish news on the web. Hence the description of source organisation, license and principles. Of these, principles is the only one which consistently distinguishes news on the web from other content (eg. commercial, government). In the future it should be distinguished further by making the principles themselves machine readable (but that is for a later date). Most professional news organisations adhere to a Statement of Principles (e.g. see http://en.wikipedia.org/wiki/Journalism_ethics_and_standards and http://www.journalism.org/resources/ethics_codes). If a site wants to mark up its content but does not want to distinguish it as news, then wouldn't it be easiest to use hAtom? [[User:martinjemoore|Martin Moore]] 9:00, 20 September 2009 (UTC)<br />
*** Having discussed this issue at length outside this brainstorming, we understand some of the concerns of the microformat community regarding 'must', but are still convinced of the criticality of principles to hNews - therefore recommend downgrading from 'must' to 'should'. [[User:martinjemoore|Martin Moore]] 14:00, 7 October 2009 (UTC)<br />
**** Accepted and implemented in 0.1. In keeping with the general direction here, we've changed <code>item-license</code> as well, and would consider adopting the same with <code>source-org</code> as well, if it proves to present the same problems. --[[User:JonathanMalek|JonathanMalek]] 00:53, 15 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">hCalendar instead of dateline?</strong> Would an [[hCalendar]] event (which can contain an hCard location) make sense for a dateline, or is the 'date' part more often omitted?<br />
** Confusingly, the journalistic term "dateline" isn't anything to do with a date or time. It is the location from which a report is filed and is generally the main location associated with a story. Generally, a dateline consists of a city (e.g. "Rome") but could be the name of a ship at sea or even a space station. [[User:Stuart Myles|Stuart Myles]] 21:12, 24 August 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">hCard instead of geo?</strong> Is geo really in use here, or would using an hCard (that can contain geo) be a better way of representing locations referred to in the story, as more human readable?<br />
** The reason for geo being highlighted (as an optional field) is to promote at least one location identifier in the story--preferably the most appropriate single location on a map for that particular story. Geo does not have to be related to dateline, but in some [http://labs.ap.org/wiki/hNews examples] we've worked on, we show the two collapsed into a single field. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)<br />
** For locations referred to in the story, I agree--publishers should be using [[hCard]] with the contained geo to markup the locations themselves. One of the concepts I've struggled with is drawing an admittedly arbitrary line between the metadata ''about'' a story from the metadata ''within'' a story. For the former, we've focused on simplicity and minimalism, primarily as a means to encourage adoption. That has meant preferring [[rel-tag]] over in-line entity extraction and markup using compound microformats. For the latter, we feel that the field is open: use whatever microformat fits your purpose, however you can--the more, the better. This lets publishers with minimal technology capabilities at least get started by tweaking a few templates in their CMS, while those more technically inclined aren't limited by the simplicity of the format to a paucity of data. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)<br />
** Also, dateline can be text or [[hCard]], as noted in the [[news-brainstorming#Common_News_Fields|Common News Fields]] section. --[[User:JonathanMalek|JonathanMalek]] 18:17, 24 September 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">What is item-license?</strong> Using [[rel-license]] presumably?<br />
** We're working off the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] discussions for this. Our concern with [[rel-license]] was its definition as applying to an entire page, rather than an item within a page. The current discussions around licensing definitely address that. --[[User:JonathanMalek|JonathanMalek]] 00:02, 25 August 2009 (UTC)<br />
*** +1 using item-license for news-brainstorming makes sense. [[User:Tantek|Tantek]] 22:32, 27 August 2009 (UTC)<br />
</div><br />
</div></div>JonathanMalekhttp://microformats.org/wiki/index.php?title=hnews&diff=41082hnews2009-10-15T15:31:33Z<p>JonathanMalek: FIX: root name, and correcting rel-principles in XMDP.</p>
<hr />
<div><entry-title>hNews 0.1</entry-title><br />
{{Template:DraftSpecification}}<br />
<br />
hNews is 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.<br />
__TOC__<br />
== Draft Specification ==<br />
<br />
;Editor/Author<br />
:[[:User:JonathanMalek|Jonathan Malek]] ([http://www.ap.org Associated Press])<br />
<br />
;Contributors<br />
:[[:User:Smyles|Stuart Myles]] ([http://www.ap.org Associated Press]) <br />
:[[:User:Martinjemoore|Martin Moore]] ([http://mediastandardstrust.org Media Standards Trust])<br />
:[[:User:MarkNg|Mark Ng]] ([http://mediastandardstrust.org Media Standards Trust])<br />
:[[:User:Tbmartinwiki|Todd B. Martin]] ([http://www.ap.org Associated Press])<br />
<br />
=== Copyright ===<br />
Per the public domain release on the authors' user pages ([[:User:JonathanMalek|Jonathan Malek]]) this specification is released into the public domain. <br />
<br />
{{MicroFormatPublicDomainContributionStatement}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Introduction ==<br />
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.<br />
<br />
{{rfc-2119-intro}}<br />
<br />
== Semantic XHTML Design Principles ==<br />
{{semantic-xhtml-design-principles}}<br />
<br />
== Format ==<br />
=== In General ===<br />
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.<br />
<br />
=== Schema ===<br />
The hNews schema consists of the following: <br />
<br />
* hNews ('''<code>hnews</code>''') and '''<code>hentry</code>'''. required. Using [[hAtom]].<br />
** '''<code>source-org</code>'''. required. Using [[hCard]].[*]<br />
** '''<code>dateline</code>'''. optional. Using text or [[hCard]].<br />
** '''<code>geo</code>'''. optional. Using [[geo]].[*]<br />
** '''<code>item-license</code>'''. recommended. Using a [[licensing-brainstorming#item_as_container license|brainstorm proposal]].<br />
** '''<code>principles</code>'''. recommended. Using the draft microformat [[principles-brainstorming#rel-principles_specification|rel-principles]].<br />
<br />
[*] Some required elements have defaults if missing, see below.<br />
<br />
=== Field and Element Details ===<br />
<br />
==== hAtom Fields ====<br />
<br />
===== Entry =====<br />
* an hNews story {{must}} be encoded as an [[hAtom]] <code>hentry</code>.<br />
* if an hNews story cannot be parsed as an [[hAtom]] <code>hentry</code>, it is invalid hNews.<br />
<br />
==== Additional Fields ====<br />
<br />
===== Source Organization =====<br />
* a Source Organization element is identified by the class name <code>source-org</code>.<br />
* Source Organization represents the originating organization for the news story.<br />
* a Source Organization {{must}} be encoded in an [[hCard]].<br />
* if the Source Organization is missing <br />
** find the [[algorithm-nearest-in-parent]] element(s) with class name <code>source-org</code> and that is/are a valid [[hCard]]<br />
** otherwise the entry is invalid hNews<br />
<br />
===== Dateline =====<br />
* a dateline element is identified by the class name <code>dateline</code>.<br />
* dateline represents the location where the news story was written or filed (see [http://en.wikipedia.org/wiki/Dateline dateline] for more details).<br />
* a dateline element {{may}} be encoded in an [[hCard]].<br />
* a news story {{should}} have a dateline element.<br />
* dateline sometimes also includes the publish date of the news story. In such cases, use the [[datetime-design-pattern]] to encode the date.<br />
<br />
===== Geo =====<br />
* a geo element is identified by the class name <code>geo</code><br />
* geo represents the geographic coordinates of relevant locations in the news story.<br />
* a geo element should be encoded in a [[geo]].<br />
* 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).<br />
<br />
===== License =====<br />
* a license element is identified by the class name <code>item-license</code>.<br />
* a license element {{must}} be encoded as described in this [http://microformats.org/wiki/licensing-brainstorming#item_as_container license brainstorm proposal].<br />
* a news story {{should}} include a license element.<br />
<br />
===== Principles =====<br />
* a principles element is identified by <code>rel-principles</code>.<br />
* principles represents the statement of principles and ethics used by the news organization that produced the news story.<br />
* a principles element {{must}} be encoded in [[principles-brainstorming#rel-principles_specification|rel-principles]].<br />
* a news story {{should}} include principles.<br />
* principles {{should}} be linked to using the icons http://labs.ap.org/principles-button-blue.png or http://labs.ap.org/principles-book-blue.png.<br />
<br />
=== XMDP Profile ===<br />
<pre><br />
<dl class="profile"><br />
<dt>class</dt><br />
<dd><p><br />
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class"><br />
HTML4 definition of the 'class' attribute.</a><br />
This meta data profile defines some 'class' attribute values (class names) <br />
and their meanings as suggested by a <br />
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile"><br />
draft of "Hypertext Links in HTML"</a>.<br />
<dl><br />
<br />
<dt>hnews</dt><br />
<dd><br />
Used to describe semantic information associated with news stories.<br />
</dd><br />
<br />
<dt>source-org</dt><br />
<dd><br />
The originating organization for the news story.<br />
</dd><br />
<br />
<dt>dateline</dt><br />
<dd><br />
Represents the location where the news story was filed.<br />
</dd><br />
<br />
<dt>geo</dt><br />
<dd><br />
Represents geographic coordinates of relevant locations in the story.<br />
</dd><br />
<br />
<dt>item-license</dt><br />
<dd><br />
Represents the license for the story.<br />
</dd><br />
<br />
<dt>rel</dt><br />
<dd><br />
<dl><br />
<dt>principles</dt><br />
<dd><br />
Represents the statement of principles and ethics used by the news organization that produced the news story.<br />
</dd><br />
</dl><br />
</dd><br />
<br />
</dl><br />
</dd><br />
</dl><br />
</pre><br />
<br />
== Examples ==<br />
<br />
See [[hnews-examples]].<br />
<br />
=== Examples in the wild ===<br />
<br />
See [[hnews-examples-in-wild]].<br />
<br />
== Implementations ==<br />
<br />
== References ==<br />
<br />
=== Normative References ===<br />
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0]<br />
* [[hatom|hAtom]]<br />
* [[hcard|hCard]]<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [[rel-tag]]<br />
* [[geo]]<br />
* [[licensing-brainstorming#item_as_container_license|item-license brainstorm]]<br />
* [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles]<br />
* [http://www.ietf.org/rfc/rfc2119.txt RFC2119]<br />
* [http://www.ietf.org/rfc/rfc4287.txt RFC4287] (Atom 1.0)<br />
<br />
=== Informative References ===<br />
* Other news efforts: see [[news-formats]].<br />
<br />
== Work in progress ==<br />
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. <br />
<br />
=== Version 0.1 ===<br />
<br />
Version 0.1 was drafted August 2008.<br />
<br />
== Further Reading ==<br />
* See [http://www.technorati.com/cosmos/referer.html blogs discussing this page].<br />
<br />
== Related Pages ==<br />
* hnews<br />
* [[news-brainstorming]]: thoughts for improving hNews. <br />
* [[hnews-faq|hNews FAQ]]: if you have any questions about hNews, check here, and if you don't find answers, add your questions!<br />
* [[hnews-issues]]: please add any issues with the specification to the issues page.<br />
* [[news-formats]]: existing news and news management schemas.<br />
* [[news-examples]]: examples of news formats on the web.<br />
** [[hnews-examples]]: examples of how to implement hNews.<br />
<br />
[[Category:Draft Specifications]]<br />
[[Category:hNews]]</div>JonathanMalekhttp://microformats.org/wiki/index.php?title=hnews-issues&diff=41080hnews-issues2009-10-15T00:57:38Z<p>JonathanMalek: +1 on adding adr for dateline to hnews.</p>
<hr />
<div><h1> hNews issues </h1><br />
<br />
These are externally raised issues about [[hnews|hNews]] with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the draft. <br />
<br />
'''IMPORTANT''': Please read the [[hnews-faq|hNews FAQ]] before giving any feedback or raising any issues as your feedback/issues may already be resolved/answered.<br />
<br />
Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — [http://tantek.com/ Tantek]<br />
<br />
Please add new issues to the '''top''' of the list. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.<br />
<br />
See related [[hatom-issues]] and [[hcard-issues]].<br />
<br />
== Template ==<br />
<br />
{{issues-format}}<br />
<br />
__TOC__<br />
<br />
== Issues ==<br />
=== Open Issues ===<br />
<div class="hentry"><br />
{{OpenIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-14</span> raised by <span class="fn">[[User:MarkNg|MarkNg]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">adr for dateline</strong>. From [[http://twitter.com/pigsonthewing/status/4831500605 Andy Mabbett on Twitter]] : hNews microformat spec "dateline. optional. Using text or hCard" should read "dateline. optional. Using text, adr or hCard".<br />
** Seems like a useful extra to me, any objections ? [[User:MarkNg|MarkNg]]<br />
** Agreed, makes sense. --[[User:JonathanMalek|JonathanMalek]] 00:57, 15 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
=== Closed Issues ===<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-09</span> raised by <span class="fn">Miles De Feyter</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Implementation of item-license as it relates to hNews</strong>. Reading through the item-license brainstorm it seems to indicate that "item-license" would need to be nested within something with the class of "item". So as this relates to hNews is the suggestion to then have an articles containing div have the three class names of "hnews hentry item"?<br />
** At this point, Miles, that is correct (following the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] concept and guidance). I expect we'll see changes around item-license (it's still just brainstorming), but for the time being, the third class name "item" is needed. --[[User:JonathanMalek|JonathanMalek]] 16:25, 12 October 2009 (UTC)<br />
** Added to [[hnews-faq]] --[[User:JonathanMalek|JonathanMalek]] 02:19, 14 October 2009 (UTC)<br />
</div><br />
</div><br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">2009-09-28</span> raised by <span class="fn">[[User:MilesD|Miles De Feyter]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Principles as a requirement</strong>. Working for a publishing company that owns and operates a large number of different organizations I'd love to incorporate hNews within our publishing system. The hNews requirement for a principles statement could pose a problem though or at least make rolling out hNews a more involved process then it would be otherwise. The issue is, I would now have to go to each product owner and ask then to provide this principles statement to link to. So my concern is now rather then just making a change to the publishing system to support hNews there is this requirement for some supporting content. And due to the nature of the content I can only assume our legal dep. would need to sign off as well, further complicating the adoption of hNews.<br />
** +1 I agree that the "principles" property (and probably all other others) should be optional. [[User:Tantek|Tantek]] 18:29, 29 September 2009 (UTC)<br />
*** I think it's important to explain why principles is a requirement. hnews is essentially a specialization of hAtom. Its purpose is to distinguish news on the web. Hence the description of source organisation, license and principles. Of these, principles is the only one which consistently distinguishes news on the web from other content (eg. commercial, government). In the future it should be distinguished further by making the principles themselves machine readable (but that is for a later date). Most professional news organisations adhere to a Statement of Principles (e.g. see http://en.wikipedia.org/wiki/Journalism_ethics_and_standards and http://www.journalism.org/resources/ethics_codes). If a site wants to mark up its content but does not want to distinguish it as news, then wouldn't it be easiest to use hAtom? [[User:martinjemoore|Martin Moore]] 9:00, 20 September 2009 (UTC)<br />
*** Having discussed this issue at length outside this brainstorming, we understand some of the concerns of the microformat community regarding 'must', but are still convinced of the criticality of principles to hNews - therefore recommend downgrading from 'must' to 'should'. [[User:martinjemoore|Martin Moore]] 14:00, 7 October 2009 (UTC)<br />
**** Accepted and implemented in 0.1. In keeping with the general direction here, we've changed <code>item-license</code> as well, and would consider adopting the same with <code>source-org</code> as well, if it proves to present the same problems. --[[User:JonathanMalek|JonathanMalek]] 00:53, 15 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">hCalendar instead of dateline?</strong> Would an [[hCalendar]] event (which can contain an hCard location) make sense for a dateline, or is the 'date' part more often omitted?<br />
** Confusingly, the journalistic term "dateline" isn't anything to do with a date or time. It is the location from which a report is filed and is generally the main location associated with a story. Generally, a dateline consists of a city (e.g. "Rome") but could be the name of a ship at sea or even a space station. [[User:Stuart Myles|Stuart Myles]] 21:12, 24 August 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">hCard instead of geo?</strong> Is geo really in use here, or would using an hCard (that can contain geo) be a better way of representing locations referred to in the story, as more human readable?<br />
** The reason for geo being highlighted (as an optional field) is to promote at least one location identifier in the story--preferably the most appropriate single location on a map for that particular story. Geo does not have to be related to dateline, but in some [http://labs.ap.org/wiki/hNews examples] we've worked on, we show the two collapsed into a single field. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)<br />
** For locations referred to in the story, I agree--publishers should be using [[hCard]] with the contained geo to markup the locations themselves. One of the concepts I've struggled with is drawing an admittedly arbitrary line between the metadata ''about'' a story from the metadata ''within'' a story. For the former, we've focused on simplicity and minimalism, primarily as a means to encourage adoption. That has meant preferring [[rel-tag]] over in-line entity extraction and markup using compound microformats. For the latter, we feel that the field is open: use whatever microformat fits your purpose, however you can--the more, the better. This lets publishers with minimal technology capabilities at least get started by tweaking a few templates in their CMS, while those more technically inclined aren't limited by the simplicity of the format to a paucity of data. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)<br />
** Also, dateline can be text or [[hCard]], as noted in the [[news-brainstorming#Common_News_Fields|Common News Fields]] section. --[[User:JonathanMalek|JonathanMalek]] 18:17, 24 September 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">What is item-license?</strong> Using [[rel-license]] presumably?<br />
** We're working off the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] discussions for this. Our concern with [[rel-license]] was its definition as applying to an entire page, rather than an item within a page. The current discussions around licensing definitely address that. --[[User:JonathanMalek|JonathanMalek]] 00:02, 25 August 2009 (UTC)<br />
*** +1 using item-license for news-brainstorming makes sense. [[User:Tantek|Tantek]] 22:32, 27 August 2009 (UTC)<br />
</div><br />
</div></div>JonathanMalekhttp://microformats.org/wiki/index.php?title=hnews-issues&diff=41079hnews-issues2009-10-15T00:53:36Z<p>JonathanMalek: Accepted "should" for principles, changed item-license to "should" in 0.1</p>
<hr />
<div><h1> hNews issues </h1><br />
<br />
These are externally raised issues about [[hnews|hNews]] with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the draft. <br />
<br />
'''IMPORTANT''': Please read the [[hnews-faq|hNews FAQ]] before giving any feedback or raising any issues as your feedback/issues may already be resolved/answered.<br />
<br />
Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — [http://tantek.com/ Tantek]<br />
<br />
Please add new issues to the '''top''' of the list. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.<br />
<br />
See related [[hatom-issues]] and [[hcard-issues]].<br />
<br />
== Template ==<br />
<br />
{{issues-format}}<br />
<br />
__TOC__<br />
<br />
== Issues ==<br />
=== Open Issues ===<br />
<div class="hentry"><br />
{{OpenIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-14</span> raised by <span class="fn">[[User:MarkNg|MarkNg]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">adr for dateline</strong>. From [[http://twitter.com/pigsonthewing/status/4831500605 Andy Mabbett on Twitter]] : hNews microformat spec "dateline. optional. Using text or hCard" should read "dateline. optional. Using text, adr or hCard".<br />
** Seems like a useful extra to me, any objections ? [[User:MarkNg|MarkNg]]<br />
</div><br />
</div><br />
<br />
=== Closed Issues ===<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-09</span> raised by <span class="fn">Miles De Feyter</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Implementation of item-license as it relates to hNews</strong>. Reading through the item-license brainstorm it seems to indicate that "item-license" would need to be nested within something with the class of "item". So as this relates to hNews is the suggestion to then have an articles containing div have the three class names of "hnews hentry item"?<br />
** At this point, Miles, that is correct (following the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] concept and guidance). I expect we'll see changes around item-license (it's still just brainstorming), but for the time being, the third class name "item" is needed. --[[User:JonathanMalek|JonathanMalek]] 16:25, 12 October 2009 (UTC)<br />
** Added to [[hnews-faq]] --[[User:JonathanMalek|JonathanMalek]] 02:19, 14 October 2009 (UTC)<br />
</div><br />
</div><br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">2009-09-28</span> raised by <span class="fn">[[User:MilesD|Miles De Feyter]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Principles as a requirement</strong>. Working for a publishing company that owns and operates a large number of different organizations I'd love to incorporate hNews within our publishing system. The hNews requirement for a principles statement could pose a problem though or at least make rolling out hNews a more involved process then it would be otherwise. The issue is, I would now have to go to each product owner and ask then to provide this principles statement to link to. So my concern is now rather then just making a change to the publishing system to support hNews there is this requirement for some supporting content. And due to the nature of the content I can only assume our legal dep. would need to sign off as well, further complicating the adoption of hNews.<br />
** +1 I agree that the "principles" property (and probably all other others) should be optional. [[User:Tantek|Tantek]] 18:29, 29 September 2009 (UTC)<br />
*** I think it's important to explain why principles is a requirement. hnews is essentially a specialization of hAtom. Its purpose is to distinguish news on the web. Hence the description of source organisation, license and principles. Of these, principles is the only one which consistently distinguishes news on the web from other content (eg. commercial, government). In the future it should be distinguished further by making the principles themselves machine readable (but that is for a later date). Most professional news organisations adhere to a Statement of Principles (e.g. see http://en.wikipedia.org/wiki/Journalism_ethics_and_standards and http://www.journalism.org/resources/ethics_codes). If a site wants to mark up its content but does not want to distinguish it as news, then wouldn't it be easiest to use hAtom? [[User:martinjemoore|Martin Moore]] 9:00, 20 September 2009 (UTC)<br />
*** Having discussed this issue at length outside this brainstorming, we understand some of the concerns of the microformat community regarding 'must', but are still convinced of the criticality of principles to hNews - therefore recommend downgrading from 'must' to 'should'. [[User:martinjemoore|Martin Moore]] 14:00, 7 October 2009 (UTC)<br />
**** Accepted and implemented in 0.1. In keeping with the general direction here, we've changed <code>item-license</code> as well, and would consider adopting the same with <code>source-org</code> as well, if it proves to present the same problems. --[[User:JonathanMalek|JonathanMalek]] 00:53, 15 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">hCalendar instead of dateline?</strong> Would an [[hCalendar]] event (which can contain an hCard location) make sense for a dateline, or is the 'date' part more often omitted?<br />
** Confusingly, the journalistic term "dateline" isn't anything to do with a date or time. It is the location from which a report is filed and is generally the main location associated with a story. Generally, a dateline consists of a city (e.g. "Rome") but could be the name of a ship at sea or even a space station. [[User:Stuart Myles|Stuart Myles]] 21:12, 24 August 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">hCard instead of geo?</strong> Is geo really in use here, or would using an hCard (that can contain geo) be a better way of representing locations referred to in the story, as more human readable?<br />
** The reason for geo being highlighted (as an optional field) is to promote at least one location identifier in the story--preferably the most appropriate single location on a map for that particular story. Geo does not have to be related to dateline, but in some [http://labs.ap.org/wiki/hNews examples] we've worked on, we show the two collapsed into a single field. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)<br />
** For locations referred to in the story, I agree--publishers should be using [[hCard]] with the contained geo to markup the locations themselves. One of the concepts I've struggled with is drawing an admittedly arbitrary line between the metadata ''about'' a story from the metadata ''within'' a story. For the former, we've focused on simplicity and minimalism, primarily as a means to encourage adoption. That has meant preferring [[rel-tag]] over in-line entity extraction and markup using compound microformats. For the latter, we feel that the field is open: use whatever microformat fits your purpose, however you can--the more, the better. This lets publishers with minimal technology capabilities at least get started by tweaking a few templates in their CMS, while those more technically inclined aren't limited by the simplicity of the format to a paucity of data. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)<br />
** Also, dateline can be text or [[hCard]], as noted in the [[news-brainstorming#Common_News_Fields|Common News Fields]] section. --[[User:JonathanMalek|JonathanMalek]] 18:17, 24 September 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">What is item-license?</strong> Using [[rel-license]] presumably?<br />
** We're working off the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] discussions for this. Our concern with [[rel-license]] was its definition as applying to an entire page, rather than an item within a page. The current discussions around licensing definitely address that. --[[User:JonathanMalek|JonathanMalek]] 00:02, 25 August 2009 (UTC)<br />
*** +1 using item-license for news-brainstorming makes sense. [[User:Tantek|Tantek]] 22:32, 27 August 2009 (UTC)<br />
</div><br />
</div></div>JonathanMalekhttp://microformats.org/wiki/index.php?title=hnews-issues&diff=41067hnews-issues2009-10-14T19:16:04Z<p>JonathanMalek: creating issues page</p>
<hr />
<div><h1> hNews issues </h1><br />
<br />
These are externally raised issues about [[hnews|hNews]] with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the draft. <br />
<br />
'''IMPORTANT''': Please read the [[hnews-faq|hNews FAQ]] before giving any feedback or raising any issues as your feedback/issues may already be resolved/answered.<br />
<br />
Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — [http://tantek.com/ Tantek]<br />
<br />
Please add new issues to the '''top''' of the list. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.<br />
<br />
See related [[hatom-issues]] and [[hcard-issues]].<br />
<br />
== Template ==<br />
<br />
{{issues-format}}<br />
<br />
__TOC__<br />
<br />
== Issues ==</div>JonathanMalekhttp://microformats.org/wiki/index.php?title=news-brainstorming&diff=41065news-brainstorming2009-10-14T02:19:07Z<p>JonathanMalek: closing issue "implementation of item-license as it relates to hNews"</p>
<hr />
<div>= News Brainstorming =<br />
<br />
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.<br />
<br />
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]]. - [[User:JonathanMalek|Jonathan Malek]] <br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* Jonathan Malek<br />
* Stuart Myles<br />
* Martin Moore<br />
* Mark Ng<br />
* Todd Martin<br />
<br />
== See Also ==<br />
<br />
* [[news-examples]]<br />
* [[news-formats]]<br />
<br />
== The Problem ==<br />
<br />
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 ''[http://www.wired.com/threatlevel/2008/09/six-year-old-st/ Wired.com], 2008'').<br />
<br />
== Thoughts on a Microformat for News ==<br />
<br />
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 [http://www.atomenabled.org/ 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]].<br />
<br />
In much the same way that one extends [http://www.atomenabled.org/ Atom], we are looking to extend [[hAtom]] with the most vital news-specific fields.<br />
<br />
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'''.<br />
<br />
=== Common News Fields ===<br />
<br />
* [[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.<br />
* '''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.<br />
* '''dateline''': using text or [[hCard]], not to be confused with date (see [http://en.wikipedia.org/wiki/Dateline dateline] for more information).<br />
* '''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.<br />
* '''item-license''': to express licensing around the item<br />
* '''principles''': using the draft format [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles]<br />
<br />
== Issues ==<br />
<br />
<br />
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.<br />
<br />
See also [[hatom-issues|hAtom Issues]] for questions about [[hAtom]].<br />
<br />
=== Issues Template ===<br />
<br />
{{issues-format}}<br />
<br />
=== Open Issues ===<br />
<br />
<br />
=== Closed Issues ===<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-09</span> raised by <span class="fn">Miles De Feyter</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Implementation of item-license as it relates to hNews</strong>. Reading through the item-license brainstorm it seems to indicate that "item-license" would need to be nested within something with the class of "item". So as this relates to hNews is the suggestion to then have an articles containing div have the three class names of "hnews hentry item"?<br />
** At this point, Miles, that is correct (following the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] concept and guidance). I expect we'll see changes around item-license (it's still just brainstorming), but for the time being, the third class name "item" is needed. --[[User:JonathanMalek|JonathanMalek]] 16:25, 12 October 2009 (UTC)<br />
** Added to [[hnews-faq]] --[[User:JonathanMalek|JonathanMalek]] 02:19, 14 October 2009 (UTC)<br />
</div><br />
</div><br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">2009-09-28</span> raised by <span class="fn">[[User:MilesD|Miles De Feyter]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Principles as a requirement</strong>. Working for a publishing company that owns and operates a large number of different organizations I'd love to incorporate hNews within our publishing system. The hNews requirement for a principles statement could pose a problem though or at least make rolling out hNews a more involved process then it would be otherwise. The issue is, I would now have to go to each product owner and ask then to provide this principles statement to link to. So my concern is now rather then just making a change to the publishing system to support hNews there is this requirement for some supporting content. And due to the nature of the content I can only assume our legal dep. would need to sign off as well, further complicating the adoption of hNews.<br />
** +1 I agree that the "principles" property (and probably all other others) should be optional. [[User:Tantek|Tantek]] 18:29, 29 September 2009 (UTC)<br />
*** I think it's important to explain why principles is a requirement. hnews is essentially a specialization of hAtom. Its purpose is to distinguish news on the web. Hence the description of source organisation, license and principles. Of these, principles is the only one which consistently distinguishes news on the web from other content (eg. commercial, government). In the future it should be distinguished further by making the principles themselves machine readable (but that is for a later date). Most professional news organisations adhere to a Statement of Principles (e.g. see http://en.wikipedia.org/wiki/Journalism_ethics_and_standards and http://www.journalism.org/resources/ethics_codes). If a site wants to mark up its content but does not want to distinguish it as news, then wouldn't it be easiest to use hAtom? [[User:martinjemoore|Martin Moore]] 9:00, 20 September 2009 (UTC)<br />
*** Having discussed this issue at length outside this brainstorming, we understand some of the concerns of the microformat community regarding 'must', but are still convinced of the criticality of principles to hNews - therefore recommend downgrading from 'must' to 'should'. [[User:martinjemoore|Martin Moore]] 14:00, 7 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">hCalendar instead of dateline?</strong> Would an [[hCalendar]] event (which can contain an hCard location) make sense for a dateline, or is the 'date' part more often omitted?<br />
** Confusingly, the journalistic term "dateline" isn't anything to do with a date or time. It is the location from which a report is filed and is generally the main location associated with a story. Generally, a dateline consists of a city (e.g. "Rome") but could be the name of a ship at sea or even a space station. [[User:Stuart Myles|Stuart Myles]] 21:12, 24 August 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">hCard instead of geo?</strong> Is geo really in use here, or would using an hCard (that can contain geo) be a better way of representing locations referred to in the story, as more human readable?<br />
** The reason for geo being highlighted (as an optional field) is to promote at least one location identifier in the story--preferably the most appropriate single location on a map for that particular story. Geo does not have to be related to dateline, but in some [http://labs.ap.org/wiki/hNews examples] we've worked on, we show the two collapsed into a single field. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)<br />
** For locations referred to in the story, I agree--publishers should be using [[hCard]] with the contained geo to markup the locations themselves. One of the concepts I've struggled with is drawing an admittedly arbitrary line between the metadata ''about'' a story from the metadata ''within'' a story. For the former, we've focused on simplicity and minimalism, primarily as a means to encourage adoption. That has meant preferring [[rel-tag]] over in-line entity extraction and markup using compound microformats. For the latter, we feel that the field is open: use whatever microformat fits your purpose, however you can--the more, the better. This lets publishers with minimal technology capabilities at least get started by tweaking a few templates in their CMS, while those more technically inclined aren't limited by the simplicity of the format to a paucity of data. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)<br />
** Also, dateline can be text or [[hCard]], as noted in the [[news-brainstorming#Common_News_Fields|Common News Fields]] section. --[[User:JonathanMalek|JonathanMalek]] 18:17, 24 September 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">What is item-license?</strong> Using [[rel-license]] presumably?<br />
** We're working off the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] discussions for this. Our concern with [[rel-license]] was its definition as applying to an entire page, rather than an item within a page. The current discussions around licensing definitely address that. --[[User:JonathanMalek|JonathanMalek]] 00:02, 25 August 2009 (UTC)<br />
*** +1 using item-license for news-brainstorming makes sense. [[User:Tantek|Tantek]] 22:32, 27 August 2009 (UTC)<br />
</div><br />
</div><br />
<br />
== Naming ==<br />
<br />
Here are candidate names for a news microformat:<br />
<br />
* hNews<br />
<br />
= Proposal = <br />
See the [[hnews]] draft.</div>JonathanMalekhttp://microformats.org/wiki/index.php?title=hnews-faq&diff=41064hnews-faq2009-10-14T02:15:34Z<p>JonathanMalek: Updating Q&A section (following hReview guidance), answering question about item-license root.</p>
<hr />
<div>= hNews FAQ =<br />
<br />
This page is for documenting Q&A about [[hnews|hNews]]. <br />
<br />
== Q&A ==<br />
<br />
# In order to use <code>item-license</code> in an hNews entry, should the root contain three class names of "hnews hentry item"? -- paraphrased from [[User:MilesD|Miles De Feyter]] 09 October, 2009<br />
#* At this point, that is correct (following the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] concept and guidance). I expect we'll see changes around item-license (it's still just brainstorming), but for the time being, the third class name "item" is needed.<br />
<br />
<br />
== Additional Topics ==<br />
''(moved from the discussion page at http://labs.ap.org/wiki/Talk:hNews)''<br />
<br />
=== Where can I read the current draft for hNews? ===<br />
It can be found [[hNews|here]].<br />
<br />
=== Does hNews replace NewsML, NewsML-G2, ATOM or RSS? ===<br />
No. -- [[User:Smyles|Stuart Myles]]<br />
<br />
=== OK, So How Does hNews relate to NewsML, NewsML-G2, ATOM and RSS? ===<br />
The idea with hNews is to add some machine-readable news-specific semantics to display-ready HTML. I see NewsML [http://www.iptc.org/cms/site/index.html?channel=CH0106], NewsML-G2 [http://www.iptc.org/cms/site/index.html?channel=CH0111], ATOM [http://tools.ietf.org/html/rfc4287] and RSS [http://en.wikipedia.org/wiki/RSS_(file_format)] as ways of enveloping content, to provide structure and metadata. (Each has its own merits and drawbacks). They can all be used to convey HTML and therefore any of them would be an ideal way to deliver hNews. There may be some overlap in the news metadata that is marked up (e.g. you can indicate a headline in NewsML and within hNews). -- [[User:Smyles|Stuart Myles]]<br />
<br />
=== Does hNews Replace NITF? ===<br />
NITF (News Industry Text Format [http://www.nitf.org]) is an XML format for defining the content and structure of articles. Whereas hNews is ready-for-display, NITF needs to be translated into a display format (e.g. HTML, XHTML, WML, PDF, etc.). This is one of NITF's strengths - you can turn it into virtually any other display format (including print!). NITF also has a much richer set of metadata fields that can be expressed [http://www.iptc.org/std/NITF/3.4/documentation/nitf-documentation.html]. AP plans to continue to use NITF (alongside a number of other formats), even as we roll out hNews. -- [[User:Smyles|Stuart Myles]] (In the interests of full disclosure - I represent AP to the IPTC and am the chairman of the IPTC's NITF Working Group).<br />
<br />
=== Why not RDFa? ===<br />
A couple of people have asked me whether the goals of hNews be met using RDFa [http://www.w3.org/TR/rdfa-syntax/] instead? RDFa is "a thin layer of markup you can add to your web pages that makes them understandable for machines as well as people... By adding it, browsers, search engines, and other software can understand more about the pages, and in so doing offer more services or better results for the user." (quote from [http://www.w3.org/MarkUp/2009/rdfa-for-html-authors]).<br />
<br />
I agree that RDFa would be another, equally valid way to add the hNews metadata into an (X)HTML page. I'm not an RDFa expert, but I wonder if it would be possible to use both hNews and RDFa at the same time? If anyone has done something similar to hNews with RDFa, then please let us know. -- [[User:Smyles|Stuart Myles]]<br />
<br />
Teams at the BBC are currently considering marking up their news content as RDF available as a seperate resource, rather than in the pages themselves. It might prove sensible to do some work with GRDDL to make it possible to exchange hNews content into whatever ontology they end up working with. -- [[User:MarkNg|Mark Ng]]<br />
<br />
=== Why not use microdata ? ===<br />
The WHATWG is considering introducing a "microdata" syntax into HTML 5 [http://www.whatwg.org/specs/web-apps/current-work/multipage/microdata.html]. This would seem to be a valid way of achieving something similar to hNews - although not without controversy. See, for example the discussions at [http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2009Aug/thread.html]. We look forward to a bit more clarity around this, including whether microdata will only work in HTML 5 onwards or will it be possible to retrofit it into current web pages. -- [[User:Smyles|Stuart Myles]]<br />
<br />
=== Where is the tracking piece in hNews? ===<br />
hNews is a way to add some machine-readable news semantics to HTML. If you want to follow the hNews spec, you are not required to - or prevented from - adding any kind of tracking device, such as a "web bug" [http://en.wikipedia.org/wiki/Web_bug]. -- [[User:Smyles|Stuart Myles]]<br />
<br />
=== Is hNews a microformat? ===<br />
[[User:Adactio|Adactio]] proposed that this was erroneously asserted, and modified the draft. In fact, our intent is to submit this as a microformat draft on the microformat site (as should be evident from the use of microformat.org/wiki templates, to facilitate a quick move), assuming that it is acceptable to the community as such. If it is not, then at that time we will modify the language appropriately. -- [[User:JonathanMalek|Jonathan Malek]]<br />
<br />
But until a format has been through the microformats process, it is *not* a microformat. It does you no favours to mis-label a markup pattern as a microformat prematurely ...if anything, doing so will damage your standing with the microformats community who may view it as opportunistic coattail-grabbing. -- [[User:Adactio|Adactio]]<br />
<br />
I completely agree, Jeremy. I was happy to see the changes to the http://en.wikipedia.org/wiki/HNews that you made, and I think those make sense. I'd like to keep this draft intact in terms of intent, namely to submit this as a draft on the microformat site. -- [[User:JonathanMalek|Jonathan Malek]]<br />
<br />
But even if this were on the microformats wiki, you still wouldn't refer to hNews as a microformat until it has passed the microformats process. If this document is supposed to be a draft text for a page on the microformats wiki, then I don't understand why it has been published at a public URL. As long it *is* a public URL, it shouldn't contain any misleading falsehoods.<br />
<br />
I would encourage you to try the microformats process; namely to propose a format for syndicating news content, look at existing patterns and discussg what to do next. Creating an entire spec and *then* bringing it to the microformats community is putting the cart before the horse. State the problem case, not the solution. That way, others can help you in drafting a format. -- [[User:Adactio|Adactio]]<br />
<br />
Jeremy, I went through the process steps back in May of last year, and worked through what I could within the constraints I have. Be assured that we will faithfully pursue the microformats process, now that this effort has seen the light of day. I would point you to numerous other pages on the web that have done the same thing, and then let you consider whether you should revert your changes. For example: http://www.jodcast.net/avm/microformat.html, http://developer.iamalpha.com/profile, just to name a few. -- [[User:JonathanMalek|Jonathan Malek]]<br />
<br />
Yes, those examples you point to are examples of formats *incorrectly* labelling formats as microformats. There are some others out there as well. -- [[User:Adactio|Adactio]]<br />
<br />
I had a chance to speak with Tantek at the microformatsdevcamp about retrofitting some of the work from hnews into hatom and/or a specific news microformat. I'll be carrying that work out on the hatom-brainstorming page. I'm not sure how we best move the current work across to the microformats wiki wholesale. -- [[User:MarkNg|Mark Ng]]</div>JonathanMalekhttp://microformats.org/wiki/index.php?title=hnews&diff=41061hnews2009-10-14T00:17:12Z<p>JonathanMalek: linking to the updated principles page</p>
<hr />
<div><entry-title>hNews 0.1</entry-title><br />
{{Template:DraftSpecification}}<br />
<br />
hNews is 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.<br />
__TOC__<br />
== Draft Specification ==<br />
<br />
;Editor/Author<br />
:[[:User:JonathanMalek|Jonathan Malek]] ([http://www.ap.org Associated Press])<br />
<br />
;Contributors<br />
:[[:User:Smyles|Stuart Myles]] ([http://www.ap.org Associated Press]) <br />
:[[:User:Martinjemoore|Martin Moore]] ([http://mediastandardstrust.org Media Standards Trust])<br />
:[[:User:MarkNg|Mark Ng]] ([http://mediastandardstrust.org Media Standards Trust])<br />
:[[:User:Tbmartinwiki|Todd B. Martin]] ([http://www.ap.org Associated Press])<br />
<br />
=== Copyright ===<br />
Per the public domain release on the authors' user pages ([[:User:JonathanMalek|Jonathan Malek]]) this specification is released into the public domain. <br />
<br />
{{MicroFormatPublicDomainContributionStatement}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Introduction ==<br />
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.<br />
<br />
{{rfc-2119-intro}}<br />
<br />
== Semantic XHTML Design Principles ==<br />
{{semantic-xhtml-design-principles}}<br />
<br />
== Format ==<br />
=== In General ===<br />
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.<br />
<br />
=== Schema ===<br />
The hNews schema consists of the following: <br />
<br />
* hNews ('''<code>hnews</code>''') and '''<code>hentry</code>'''. required. Using [[hAtom]].<br />
** '''<code>source-org</code>'''. required. Using [[hCard]].[*]<br />
** '''<code>dateline</code>'''. optional. Using text or [[hCard]].<br />
** '''<code>geo</code>'''. optional. Using [[geo]].[*]<br />
** '''<code>item-license</code>'''. recommended. Using a [[licensing-brainstorming#item_as_container license|brainstorm proposal]].<br />
** '''<code>principles</code>'''. recommended. Using the draft microformat [[principles-brainstorming#rel-principles_specification|rel-principles]].<br />
<br />
[*] Some required elements have defaults if missing, see below.<br />
<br />
=== Field and Element Details ===<br />
<br />
==== hAtom Fields ====<br />
<br />
===== Entry =====<br />
* an hNews story {{must}} be encoded as an [[hAtom]] <code>hentry</code>.<br />
* if an hNews story cannot be parsed as an [[hAtom]] <code>hentry</code>, it is invalid hNews.<br />
<br />
==== Additional Fields ====<br />
<br />
===== Source Organization =====<br />
* a Source Organization element is identified by the class name <code>source-org</code>.<br />
* Source Organization represents the originating organization for the news story.<br />
* a Source Organization {{must}} be encoded in an [[hCard]].<br />
* if the Source Organization is missing <br />
** find the [[algorithm-nearest-in-parent]] element(s) with class name <code>source-org</code> and that is/are a valid [[hCard]]<br />
** otherwise the entry is invalid hNews<br />
<br />
===== Dateline =====<br />
* a dateline element is identified by the class name <code>dateline</code>.<br />
* dateline represents the location where the news story was written or filed (see [http://en.wikipedia.org/wiki/Dateline dateline] for more details).<br />
* a dateline element {{may}} be encoded in an [[hCard]].<br />
* a news story {{should}} have a dateline element.<br />
* dateline sometimes also includes the publish date of the news story. In such cases, use the [[datetime-design-pattern]] to encode the date.<br />
<br />
===== Geo =====<br />
* a geo element is identified by the class name <code>geo</code><br />
* geo represents the geographic coordinates of relevant locations in the news story.<br />
* a geo element should be encoded in a [[geo]].<br />
* 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).<br />
<br />
===== License =====<br />
* a license element is identified by the class name <code>item-license</code>.<br />
* a license element {{must}} be encoded as described in this [http://microformats.org/wiki/licensing-brainstorming#item_as_container license brainstorm proposal].<br />
* a news story {{should}} include a license element.<br />
<br />
===== Principles =====<br />
* a principles element is identified by <code>rel-principles</code>.<br />
* principles represents the statement of principles and ethics used by the news organization that produced the news story.<br />
* a principles element {{must}} be encoded in [[principles-brainstorming#rel-principles_specification|rel-principles]].<br />
* a news story {{should}} include principles.<br />
* principles {{should}} be linked to using the icons http://labs.ap.org/principles-button-blue.png or http://labs.ap.org/principles-book-blue.png.<br />
<br />
=== XMDP Profile ===<br />
<pre><br />
<dl class="profile"><br />
<dt>class</dt><br />
<dd><p><br />
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class"><br />
HTML4 definition of the 'class' attribute.</a><br />
This meta data profile defines some 'class' attribute values (class names) <br />
and their meanings as suggested by a <br />
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile"><br />
draft of "Hypertext Links in HTML"</a>.<br />
<dl><br />
<br />
<dt>root</dt><br />
<dd><br />
Used to describe semantic information associated with news stories.<br />
</dd><br />
<br />
<dt>source-org</dt><br />
<dd><br />
The originating organization for the news story.<br />
</dd><br />
<br />
<dt>dateline</dt><br />
<dd><br />
Represents the location where the news story was filed.<br />
</dd><br />
<br />
<dt>geo</dt><br />
<dd><br />
Represents geographic coordinates of relevant locations in the story.<br />
</dd><br />
<br />
<dt>item-license</dt><br />
<dd><br />
Represents the license for the story.<br />
</dd><br />
<br />
<dt>principles</dt><br />
<dd><br />
Represents the statement of principles and ethics used by the news organization that produced the news story.<br />
</dd><br />
<br />
</dl><br />
</dd><br />
</dl><br />
</pre><br />
<br />
== Examples ==<br />
<br />
See [[hnews-examples]].<br />
<br />
=== Examples in the wild ===<br />
<br />
See [[hnews-examples-in-wild]].<br />
<br />
== Implementations ==<br />
<br />
== References ==<br />
<br />
=== Normative References ===<br />
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0]<br />
* [[hatom|hAtom]]<br />
* [[hcard|hCard]]<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [[rel-tag]]<br />
* [[geo]]<br />
* [[licensing-brainstorming#item_as_container_license|item-license brainstorm]]<br />
* [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles]<br />
* [http://www.ietf.org/rfc/rfc2119.txt RFC2119]<br />
* [http://www.ietf.org/rfc/rfc4287.txt RFC4287] (Atom 1.0)<br />
<br />
=== Informative References ===<br />
* Other news efforts: see [[news-formats]].<br />
<br />
== Work in progress ==<br />
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. <br />
<br />
=== Version 0.1 ===<br />
<br />
Version 0.1 was drafted August 2008.<br />
<br />
== Further Reading ==<br />
* See [http://www.technorati.com/cosmos/referer.html blogs discussing this page].<br />
<br />
== Related Pages ==<br />
* hnews<br />
* [[news-brainstorming]]: thoughts for improving hNews. <br />
* [[hnews-faq|hNews FAQ]]: if you have any questions about hNews, check here, and if you don't find answers, add your questions!<br />
* [[hnews-issues]]: please add any issues with the specification to the issues page.<br />
* [[news-formats]]: existing news and news management schemas.<br />
* [[news-examples]]: examples of news formats on the web.<br />
** [[hnews-examples]]: examples of how to implement hNews.<br />
<br />
[[Category:Draft Specifications]]<br />
[[Category:hNews]]</div>JonathanMalekhttp://microformats.org/wiki/index.php?title=hnews&diff=41060hnews2009-10-14T00:16:36Z<p>JonathanMalek: linking to the updated principles page</p>
<hr />
<div><entry-title>hNews 0.1</entry-title><br />
{{Template:DraftSpecification}}<br />
<br />
hNews is 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.<br />
__TOC__<br />
== Draft Specification ==<br />
<br />
;Editor/Author<br />
:[[:User:JonathanMalek|Jonathan Malek]] ([http://www.ap.org Associated Press])<br />
<br />
;Contributors<br />
:[[:User:Smyles|Stuart Myles]] ([http://www.ap.org Associated Press]) <br />
:[[:User:Martinjemoore|Martin Moore]] ([http://mediastandardstrust.org Media Standards Trust])<br />
:[[:User:MarkNg|Mark Ng]] ([http://mediastandardstrust.org Media Standards Trust])<br />
:[[:User:Tbmartinwiki|Todd B. Martin]] ([http://www.ap.org Associated Press])<br />
<br />
=== Copyright ===<br />
Per the public domain release on the authors' user pages ([[:User:JonathanMalek|Jonathan Malek]]) this specification is released into the public domain. <br />
<br />
{{MicroFormatPublicDomainContributionStatement}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Introduction ==<br />
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.<br />
<br />
{{rfc-2119-intro}}<br />
<br />
== Semantic XHTML Design Principles ==<br />
{{semantic-xhtml-design-principles}}<br />
<br />
== Format ==<br />
=== In General ===<br />
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.<br />
<br />
=== Schema ===<br />
The hNews schema consists of the following: <br />
<br />
* hNews ('''<code>hnews</code>''') and '''<code>hentry</code>'''. required. Using [[hAtom]].<br />
** '''<code>source-org</code>'''. required. Using [[hCard]].[*]<br />
** '''<code>dateline</code>'''. optional. Using text or [[hCard]].<br />
** '''<code>geo</code>'''. optional. Using [[geo]].[*]<br />
** '''<code>item-license</code>'''. recommended. Using a [[licensing-brainstorming#item_as_container license|brainstorm proposal]].<br />
** '''<code>principles</code>'''. recommended. Using the draft microformat [[principles-brainstorming#rel-principles_specification|rel-principles]].<br />
<br />
[*] Some required elements have defaults if missing, see below.<br />
<br />
=== Field and Element Details ===<br />
<br />
==== hAtom Fields ====<br />
<br />
===== Entry =====<br />
* an hNews story {{must}} be encoded as an [[hAtom]] <code>hentry</code>.<br />
* if an hNews story cannot be parsed as an [[hAtom]] <code>hentry</code>, it is invalid hNews.<br />
<br />
==== Additional Fields ====<br />
<br />
===== Source Organization =====<br />
* a Source Organization element is identified by the class name <code>source-org</code>.<br />
* Source Organization represents the originating organization for the news story.<br />
* a Source Organization {{must}} be encoded in an [[hCard]].<br />
* if the Source Organization is missing <br />
** find the [[algorithm-nearest-in-parent]] element(s) with class name <code>source-org</code> and that is/are a valid [[hCard]]<br />
** otherwise the entry is invalid hNews<br />
<br />
===== Dateline =====<br />
* a dateline element is identified by the class name <code>dateline</code>.<br />
* dateline represents the location where the news story was written or filed (see [http://en.wikipedia.org/wiki/Dateline dateline] for more details).<br />
* a dateline element {{may}} be encoded in an [[hCard]].<br />
* a news story {{should}} have a dateline element.<br />
* dateline sometimes also includes the publish date of the news story. In such cases, use the [[datetime-design-pattern]] to encode the date.<br />
<br />
===== Geo =====<br />
* a geo element is identified by the class name <code>geo</code><br />
* geo represents the geographic coordinates of relevant locations in the news story.<br />
* a geo element should be encoded in a [[geo]].<br />
* 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).<br />
<br />
===== License =====<br />
* a license element is identified by the class name <code>item-license</code>.<br />
* a license element {{must}} be encoded as described in this [http://microformats.org/wiki/licensing-brainstorming#item_as_container license brainstorm proposal].<br />
* a news story {{should}} include a license element.<br />
<br />
===== Principles =====<br />
* a principles element is identified by <code>rel-principles</code>.<br />
* principles represents the statement of principles and ethics used by the news organization that produced the news story.<br />
* a principles element {{must}} be encoded in [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles].<br />
* a news story {{should}} include principles.<br />
* principles {{should}} be linked to using the icons http://labs.ap.org/principles-button-blue.png or http://labs.ap.org/principles-book-blue.png.<br />
<br />
=== XMDP Profile ===<br />
<pre><br />
<dl class="profile"><br />
<dt>class</dt><br />
<dd><p><br />
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class"><br />
HTML4 definition of the 'class' attribute.</a><br />
This meta data profile defines some 'class' attribute values (class names) <br />
and their meanings as suggested by a <br />
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile"><br />
draft of "Hypertext Links in HTML"</a>.<br />
<dl><br />
<br />
<dt>root</dt><br />
<dd><br />
Used to describe semantic information associated with news stories.<br />
</dd><br />
<br />
<dt>source-org</dt><br />
<dd><br />
The originating organization for the news story.<br />
</dd><br />
<br />
<dt>dateline</dt><br />
<dd><br />
Represents the location where the news story was filed.<br />
</dd><br />
<br />
<dt>geo</dt><br />
<dd><br />
Represents geographic coordinates of relevant locations in the story.<br />
</dd><br />
<br />
<dt>item-license</dt><br />
<dd><br />
Represents the license for the story.<br />
</dd><br />
<br />
<dt>principles</dt><br />
<dd><br />
Represents the statement of principles and ethics used by the news organization that produced the news story.<br />
</dd><br />
<br />
</dl><br />
</dd><br />
</dl><br />
</pre><br />
<br />
== Examples ==<br />
<br />
See [[hnews-examples]].<br />
<br />
=== Examples in the wild ===<br />
<br />
See [[hnews-examples-in-wild]].<br />
<br />
== Implementations ==<br />
<br />
== References ==<br />
<br />
=== Normative References ===<br />
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0]<br />
* [[hatom|hAtom]]<br />
* [[hcard|hCard]]<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [[rel-tag]]<br />
* [[geo]]<br />
* [[licensing-brainstorming#item_as_container_license|item-license brainstorm]]<br />
* [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles]<br />
* [http://www.ietf.org/rfc/rfc2119.txt RFC2119]<br />
* [http://www.ietf.org/rfc/rfc4287.txt RFC4287] (Atom 1.0)<br />
<br />
=== Informative References ===<br />
* Other news efforts: see [[news-formats]].<br />
<br />
== Work in progress ==<br />
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. <br />
<br />
=== Version 0.1 ===<br />
<br />
Version 0.1 was drafted August 2008.<br />
<br />
== Further Reading ==<br />
* See [http://www.technorati.com/cosmos/referer.html blogs discussing this page].<br />
<br />
== Related Pages ==<br />
* hnews<br />
* [[news-brainstorming]]: thoughts for improving hNews. <br />
* [[hnews-faq|hNews FAQ]]: if you have any questions about hNews, check here, and if you don't find answers, add your questions!<br />
* [[hnews-issues]]: please add any issues with the specification to the issues page.<br />
* [[news-formats]]: existing news and news management schemas.<br />
* [[news-examples]]: examples of news formats on the web.<br />
** [[hnews-examples]]: examples of how to implement hNews.<br />
<br />
[[Category:Draft Specifications]]<br />
[[Category:hNews]]</div>JonathanMalekhttp://microformats.org/wiki/index.php?title=hnews&diff=41045hnews2009-10-13T00:36:00Z<p>JonathanMalek: clarifying root name.</p>
<hr />
<div><entry-title>hNews 0.1</entry-title><br />
{{Template:DraftSpecification}}<br />
<br />
hNews is 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.<br />
__TOC__<br />
== Draft Specification ==<br />
<br />
;Editor/Author<br />
:[[:User:JonathanMalek|Jonathan Malek]] ([http://www.ap.org Associated Press])<br />
<br />
;Contributors<br />
:[[:User:Smyles|Stuart Myles]] ([http://www.ap.org Associated Press]) <br />
:[[:User:Martinjemoore|Martin Moore]] ([http://mediastandardstrust.org Media Standards Trust])<br />
:[[:User:MarkNg|Mark Ng]] ([http://mediastandardstrust.org Media Standards Trust])<br />
:[[:User:Tbmartinwiki|Todd B. Martin]] ([http://www.ap.org Associated Press])<br />
<br />
=== Copyright ===<br />
Per the public domain release on the authors' user pages ([[:User:JonathanMalek|Jonathan Malek]]) this specification is released into the public domain. <br />
<br />
{{MicroFormatPublicDomainContributionStatement}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Introduction ==<br />
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.<br />
<br />
{{rfc-2119-intro}}<br />
<br />
== Semantic XHTML Design Principles ==<br />
{{semantic-xhtml-design-principles}}<br />
<br />
== Format ==<br />
=== In General ===<br />
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.<br />
<br />
=== Schema ===<br />
The hNews schema consists of the following: <br />
<br />
* hNews ('''<code>hnews</code>''') and '''<code>hentry</code>'''. required. Using [[hAtom]].<br />
** '''<code>source-org</code>'''. required. Using [[hCard]].[*]<br />
** '''<code>dateline</code>'''. optional. Using text or [[hCard]].<br />
** '''<code>geo</code>'''. optional. Using [[geo]].[*]<br />
** '''<code>item-license</code>'''. recommended. Using a [[licensing-brainstorming#item_as_container license|brainstorm proposal]].<br />
** '''<code>principles</code>'''. recommended. Using the draft microformat. [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles].<br />
<br />
[*] Some required elements have defaults if missing, see below.<br />
<br />
=== Field and Element Details ===<br />
<br />
==== hAtom Fields ====<br />
<br />
===== Entry =====<br />
* an hNews story {{must}} be encoded as an [[hAtom]] <code>hentry</code>.<br />
* if an hNews story cannot be parsed as an [[hAtom]] <code>hentry</code>, it is invalid hNews.<br />
<br />
==== Additional Fields ====<br />
<br />
===== Source Organization =====<br />
* a Source Organization element is identified by the class name <code>source-org</code>.<br />
* Source Organization represents the originating organization for the news story.<br />
* a Source Organization {{must}} be encoded in an [[hCard]].<br />
* if the Source Organization is missing <br />
** find the [[algorithm-nearest-in-parent]] element(s) with class name <code>source-org</code> and that is/are a valid [[hCard]]<br />
** otherwise the entry is invalid hNews<br />
<br />
===== Dateline =====<br />
* a dateline element is identified by the class name <code>dateline</code>.<br />
* dateline represents the location where the news story was written or filed (see [http://en.wikipedia.org/wiki/Dateline dateline] for more details).<br />
* a dateline element {{may}} be encoded in an [[hCard]].<br />
* a news story {{should}} have a dateline element.<br />
* dateline sometimes also includes the publish date of the news story. In such cases, use the [[datetime-design-pattern]] to encode the date.<br />
<br />
===== Geo =====<br />
* a geo element is identified by the class name <code>geo</code><br />
* geo represents the geographic coordinates of relevant locations in the news story.<br />
* a geo element should be encoded in a [[geo]].<br />
* 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).<br />
<br />
===== License =====<br />
* a license element is identified by the class name <code>item-license</code>.<br />
* a license element {{must}} be encoded as described in this [http://microformats.org/wiki/licensing-brainstorming#item_as_container license brainstorm proposal].<br />
* a news story {{should}} include a license element.<br />
<br />
===== Principles =====<br />
* a principles element is identified by <code>rel-principles</code>.<br />
* principles represents the statement of principles and ethics used by the news organization that produced the news story.<br />
* a principles element {{must}} be encoded in [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles].<br />
* a news story {{should}} include principles.<br />
* principles {{should}} be linked to using the icons http://labs.ap.org/principles-button-blue.png or http://labs.ap.org/principles-book-blue.png.<br />
<br />
=== XMDP Profile ===<br />
<pre><br />
<dl class="profile"><br />
<dt>class</dt><br />
<dd><p><br />
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class"><br />
HTML4 definition of the 'class' attribute.</a><br />
This meta data profile defines some 'class' attribute values (class names) <br />
and their meanings as suggested by a <br />
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile"><br />
draft of "Hypertext Links in HTML"</a>.<br />
<dl><br />
<br />
<dt>root</dt><br />
<dd><br />
Used to describe semantic information associated with news stories.<br />
</dd><br />
<br />
<dt>source-org</dt><br />
<dd><br />
The originating organization for the news story.<br />
</dd><br />
<br />
<dt>dateline</dt><br />
<dd><br />
Represents the location where the news story was filed.<br />
</dd><br />
<br />
<dt>geo</dt><br />
<dd><br />
Represents geographic coordinates of relevant locations in the story.<br />
</dd><br />
<br />
<dt>item-license</dt><br />
<dd><br />
Represents the license for the story.<br />
</dd><br />
<br />
<dt>principles</dt><br />
<dd><br />
Represents the statement of principles and ethics used by the news organization that produced the news story.<br />
</dd><br />
<br />
</dl><br />
</dd><br />
</dl><br />
</pre><br />
<br />
== Examples ==<br />
<br />
See [[hnews-examples]].<br />
<br />
=== Examples in the wild ===<br />
<br />
See [[hnews-examples-in-wild]].<br />
<br />
== Implementations ==<br />
<br />
== References ==<br />
<br />
=== Normative References ===<br />
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0]<br />
* [[hatom|hAtom]]<br />
* [[hcard|hCard]]<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [[rel-tag]]<br />
* [[geo]]<br />
* [[licensing-brainstorming#item_as_container_license|item-license brainstorm]]<br />
* [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles]<br />
* [http://www.ietf.org/rfc/rfc2119.txt RFC2119]<br />
* [http://www.ietf.org/rfc/rfc4287.txt RFC4287] (Atom 1.0)<br />
<br />
=== Informative References ===<br />
* Other news efforts: see [[news-formats]].<br />
<br />
== Work in progress ==<br />
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. <br />
<br />
=== Version 0.1 ===<br />
<br />
Version 0.1 was drafted August 2008.<br />
<br />
== Further Reading ==<br />
* See [http://www.technorati.com/cosmos/referer.html blogs discussing this page].<br />
<br />
== Related Pages ==<br />
* hnews<br />
* [[news-brainstorming]]: thoughts for improving hNews. <br />
* [[hnews-faq|hNews FAQ]]: if you have any questions about hNews, check here, and if you don't find answers, add your questions!<br />
* [[hnews-issues]]: please add any issues with the specification to the issues page.<br />
* [[news-formats]]: existing news and news management schemas.<br />
* [[news-examples]]: examples of news formats on the web.<br />
** [[hnews-examples]]: examples of how to implement hNews.<br />
<br />
[[Category:Draft Specifications]]<br />
[[Category:hNews]]</div>JonathanMalekhttp://microformats.org/wiki/index.php?title=hnews&diff=41044hnews2009-10-13T00:27:55Z<p>JonathanMalek: temporarily hosting images at labs.ap.org until we have someplace better.</p>
<hr />
<div><entry-title>hNews 0.1</entry-title><br />
{{Template:DraftSpecification}}<br />
<br />
hNews is 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.<br />
__TOC__<br />
== Draft Specification ==<br />
<br />
;Editor/Author<br />
:[[:User:JonathanMalek|Jonathan Malek]] ([http://www.ap.org Associated Press])<br />
<br />
;Contributors<br />
:[[:User:Smyles|Stuart Myles]] ([http://www.ap.org Associated Press]) <br />
:[[:User:Martinjemoore|Martin Moore]] ([http://mediastandardstrust.org Media Standards Trust])<br />
:[[:User:MarkNg|Mark Ng]] ([http://mediastandardstrust.org Media Standards Trust])<br />
:[[:User:Tbmartinwiki|Todd B. Martin]] ([http://www.ap.org Associated Press])<br />
<br />
=== Copyright ===<br />
Per the public domain release on the authors' user pages ([[:User:JonathanMalek|Jonathan Malek]]) this specification is released into the public domain. <br />
<br />
{{MicroFormatPublicDomainContributionStatement}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Introduction ==<br />
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.<br />
<br />
{{rfc-2119-intro}}<br />
<br />
== Semantic XHTML Design Principles ==<br />
{{semantic-xhtml-design-principles}}<br />
<br />
== Format ==<br />
=== In General ===<br />
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.<br />
<br />
=== Schema ===<br />
The hNews schema consists of the following: <br />
<br />
* (root) ('''<code>root</code>''') and '''<code>hentry</code>'''. required. Using [[hAtom]].<br />
** '''<code>source-org</code>'''. required. Using [[hCard]].[*]<br />
** '''<code>dateline</code>'''. optional. Using text or [[hCard]].<br />
** '''<code>geo</code>'''. optional. Using [[geo]].[*]<br />
** '''<code>item-license</code>'''. recommended. Using a [[licensing-brainstorming#item_as_container license|brainstorm proposal]].<br />
** '''<code>principles</code>'''. recommended. Using the draft microformat. [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles].<br />
<br />
[*] Some required elements have defaults if missing, see below.<br />
<br />
=== Field and Element Details ===<br />
<br />
==== hAtom Fields ====<br />
<br />
===== Entry =====<br />
* an hNews story {{must}} be encoded as an [[hAtom]] <code>hentry</code>.<br />
* if an hNews story cannot be parsed as an [[hAtom]] <code>hentry</code>, it is invalid hNews.<br />
<br />
==== Additional Fields ====<br />
<br />
===== Source Organization =====<br />
* a Source Organization element is identified by the class name <code>source-org</code>.<br />
* Source Organization represents the originating organization for the news story.<br />
* a Source Organization {{must}} be encoded in an [[hCard]].<br />
* if the Source Organization is missing <br />
** find the [[algorithm-nearest-in-parent]] element(s) with class name <code>source-org</code> and that is/are a valid [[hCard]]<br />
** otherwise the entry is invalid hNews<br />
<br />
===== Dateline =====<br />
* a dateline element is identified by the class name <code>dateline</code>.<br />
* dateline represents the location where the news story was written or filed (see [http://en.wikipedia.org/wiki/Dateline dateline] for more details).<br />
* a dateline element {{may}} be encoded in an [[hCard]].<br />
* a news story {{should}} have a dateline element.<br />
* dateline sometimes also includes the publish date of the news story. In such cases, use the [[datetime-design-pattern]] to encode the date.<br />
<br />
===== Geo =====<br />
* a geo element is identified by the class name <code>geo</code><br />
* geo represents the geographic coordinates of relevant locations in the news story.<br />
* a geo element should be encoded in a [[geo]].<br />
* 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).<br />
<br />
===== License =====<br />
* a license element is identified by the class name <code>item-license</code>.<br />
* a license element {{must}} be encoded as described in this [http://microformats.org/wiki/licensing-brainstorming#item_as_container license brainstorm proposal].<br />
* a news story {{should}} include a license element.<br />
<br />
===== Principles =====<br />
* a principles element is identified by <code>rel-principles</code>.<br />
* principles represents the statement of principles and ethics used by the news organization that produced the news story.<br />
* a principles element {{must}} be encoded in [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles].<br />
* a news story {{should}} include principles.<br />
* principles {{should}} be linked to using the icons http://labs.ap.org/principles-button-blue.png or http://labs.ap.org/principles-book-blue.png.<br />
<br />
=== XMDP Profile ===<br />
<pre><br />
<dl class="profile"><br />
<dt>class</dt><br />
<dd><p><br />
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class"><br />
HTML4 definition of the 'class' attribute.</a><br />
This meta data profile defines some 'class' attribute values (class names) <br />
and their meanings as suggested by a <br />
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile"><br />
draft of "Hypertext Links in HTML"</a>.<br />
<dl><br />
<br />
<dt>root</dt><br />
<dd><br />
Used to describe semantic information associated with news stories.<br />
</dd><br />
<br />
<dt>source-org</dt><br />
<dd><br />
The originating organization for the news story.<br />
</dd><br />
<br />
<dt>dateline</dt><br />
<dd><br />
Represents the location where the news story was filed.<br />
</dd><br />
<br />
<dt>geo</dt><br />
<dd><br />
Represents geographic coordinates of relevant locations in the story.<br />
</dd><br />
<br />
<dt>item-license</dt><br />
<dd><br />
Represents the license for the story.<br />
</dd><br />
<br />
<dt>principles</dt><br />
<dd><br />
Represents the statement of principles and ethics used by the news organization that produced the news story.<br />
</dd><br />
<br />
</dl><br />
</dd><br />
</dl><br />
</pre><br />
<br />
== Examples ==<br />
<br />
See [[hnews-examples]].<br />
<br />
=== Examples in the wild ===<br />
<br />
See [[hnews-examples-in-wild]].<br />
<br />
== Implementations ==<br />
<br />
== References ==<br />
<br />
=== Normative References ===<br />
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0]<br />
* [[hatom|hAtom]]<br />
* [[hcard|hCard]]<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [[rel-tag]]<br />
* [[geo]]<br />
* [[licensing-brainstorming#item_as_container_license|item-license brainstorm]]<br />
* [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles]<br />
* [http://www.ietf.org/rfc/rfc2119.txt RFC2119]<br />
* [http://www.ietf.org/rfc/rfc4287.txt RFC4287] (Atom 1.0)<br />
<br />
=== Informative References ===<br />
* Other news efforts: see [[news-formats]].<br />
<br />
== Work in progress ==<br />
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. <br />
<br />
=== Version 0.1 ===<br />
<br />
Version 0.1 was drafted August 2008.<br />
<br />
== Further Reading ==<br />
* See [http://www.technorati.com/cosmos/referer.html blogs discussing this page].<br />
<br />
== Related Pages ==<br />
* hnews<br />
* [[news-brainstorming]]: thoughts for improving hNews. <br />
* [[hnews-faq|hNews FAQ]]: if you have any questions about hNews, check here, and if you don't find answers, add your questions!<br />
* [[hnews-issues]]: please add any issues with the specification to the issues page.<br />
* [[news-formats]]: existing news and news management schemas.<br />
* [[news-examples]]: examples of news formats on the web.<br />
** [[hnews-examples]]: examples of how to implement hNews.<br />
<br />
[[Category:Draft Specifications]]<br />
[[Category:hNews]]</div>JonathanMalekhttp://microformats.org/wiki/index.php?title=hnews&diff=41043hnews2009-10-12T23:37:21Z<p>JonathanMalek: adding clarifying details on hatom dependency.</p>
<hr />
<div><entry-title>hNews 0.1</entry-title><br />
{{Template:DraftSpecification}}<br />
<br />
hNews is 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.<br />
__TOC__<br />
== Draft Specification ==<br />
<br />
;Editor/Author<br />
:[[:User:JonathanMalek|Jonathan Malek]] ([http://www.ap.org Associated Press])<br />
<br />
;Contributors<br />
:[[:User:Smyles|Stuart Myles]] ([http://www.ap.org Associated Press]) <br />
:[[:User:Martinjemoore|Martin Moore]] ([http://mediastandardstrust.org Media Standards Trust])<br />
:[[:User:MarkNg|Mark Ng]] ([http://mediastandardstrust.org Media Standards Trust])<br />
:[[:User:Tbmartinwiki|Todd B. Martin]] ([http://www.ap.org Associated Press])<br />
<br />
=== Copyright ===<br />
Per the public domain release on the authors' user pages ([[:User:JonathanMalek|Jonathan Malek]]) this specification is released into the public domain. <br />
<br />
{{MicroFormatPublicDomainContributionStatement}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Introduction ==<br />
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.<br />
<br />
{{rfc-2119-intro}}<br />
<br />
== Semantic XHTML Design Principles ==<br />
{{semantic-xhtml-design-principles}}<br />
<br />
== Format ==<br />
=== In General ===<br />
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.<br />
<br />
=== Schema ===<br />
The hNews schema consists of the following: <br />
<br />
* (root) ('''<code>root</code>''') and '''<code>hentry</code>'''. required. Using [[hAtom]].<br />
** '''<code>source-org</code>'''. required. Using [[hCard]].[*]<br />
** '''<code>dateline</code>'''. optional. Using text or [[hCard]].<br />
** '''<code>geo</code>'''. optional. Using [[geo]].[*]<br />
** '''<code>item-license</code>'''. recommended. Using a [[licensing-brainstorming#item_as_container license|brainstorm proposal]].<br />
** '''<code>principles</code>'''. recommended. Using the draft microformat. [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles].<br />
<br />
[*] Some required elements have defaults if missing, see below.<br />
<br />
=== Field and Element Details ===<br />
<br />
==== hAtom Fields ====<br />
<br />
===== Entry =====<br />
* an hNews story {{must}} be encoded as an [[hAtom]] <code>hentry</code>.<br />
* if an hNews story cannot be parsed as an [[hAtom]] <code>hentry</code>, it is invalid hNews.<br />
<br />
==== Additional Fields ====<br />
<br />
===== Source Organization =====<br />
* a Source Organization element is identified by the class name <code>source-org</code>.<br />
* Source Organization represents the originating organization for the news story.<br />
* a Source Organization {{must}} be encoded in an [[hCard]].<br />
* if the Source Organization is missing <br />
** find the [[algorithm-nearest-in-parent]] element(s) with class name <code>source-org</code> and that is/are a valid [[hCard]]<br />
** otherwise the entry is invalid hNews<br />
<br />
===== Dateline =====<br />
* a dateline element is identified by the class name <code>dateline</code>.<br />
* dateline represents the location where the news story was written or filed (see [http://en.wikipedia.org/wiki/Dateline dateline] for more details).<br />
* a dateline element {{may}} be encoded in an [[hCard]].<br />
* a news story {{should}} have a dateline element.<br />
* dateline sometimes also includes the publish date of the news story. In such cases, use the [[datetime-design-pattern]] to encode the date.<br />
<br />
===== Geo =====<br />
* a geo element is identified by the class name <code>geo</code><br />
* geo represents the geographic coordinates of relevant locations in the news story.<br />
* a geo element should be encoded in a [[geo]].<br />
* 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).<br />
<br />
===== License =====<br />
* a license element is identified by the class name <code>item-license</code>.<br />
* a license element {{must}} be encoded as described in this [http://microformats.org/wiki/licensing-brainstorming#item_as_container license brainstorm proposal].<br />
* a news story {{should}} include a license element.<br />
<br />
===== Principles =====<br />
* a principles element is identified by <code>rel-principles</code>.<br />
* principles represents the statement of principles and ethics used by the news organization that produced the news story.<br />
* a principles element {{must}} be encoded in [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles].<br />
* a news story {{should}} include principles.<br />
* principles {{should}} be linked to using the icons [[image:principles-button-blue.png]] or [[image:principles-book-blue.png]].<br />
<br />
=== XMDP Profile ===<br />
<pre><br />
<dl class="profile"><br />
<dt>class</dt><br />
<dd><p><br />
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class"><br />
HTML4 definition of the 'class' attribute.</a><br />
This meta data profile defines some 'class' attribute values (class names) <br />
and their meanings as suggested by a <br />
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile"><br />
draft of "Hypertext Links in HTML"</a>.<br />
<dl><br />
<br />
<dt>root</dt><br />
<dd><br />
Used to describe semantic information associated with news stories.<br />
</dd><br />
<br />
<dt>source-org</dt><br />
<dd><br />
The originating organization for the news story.<br />
</dd><br />
<br />
<dt>dateline</dt><br />
<dd><br />
Represents the location where the news story was filed.<br />
</dd><br />
<br />
<dt>geo</dt><br />
<dd><br />
Represents geographic coordinates of relevant locations in the story.<br />
</dd><br />
<br />
<dt>item-license</dt><br />
<dd><br />
Represents the license for the story.<br />
</dd><br />
<br />
<dt>principles</dt><br />
<dd><br />
Represents the statement of principles and ethics used by the news organization that produced the news story.<br />
</dd><br />
<br />
</dl><br />
</dd><br />
</dl><br />
</pre><br />
<br />
== Examples ==<br />
<br />
See [[hnews-examples]].<br />
<br />
=== Examples in the wild ===<br />
<br />
See [[hnews-examples-in-wild]].<br />
<br />
== Implementations ==<br />
<br />
== References ==<br />
<br />
=== Normative References ===<br />
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0]<br />
* [[hatom|hAtom]]<br />
* [[hcard|hCard]]<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [[rel-tag]]<br />
* [[geo]]<br />
* [[licensing-brainstorming#item_as_container_license|item-license brainstorm]]<br />
* [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles]<br />
* [http://www.ietf.org/rfc/rfc2119.txt RFC2119]<br />
* [http://www.ietf.org/rfc/rfc4287.txt RFC4287] (Atom 1.0)<br />
<br />
=== Informative References ===<br />
* Other news efforts: see [[news-formats]].<br />
<br />
== Work in progress ==<br />
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. <br />
<br />
=== Version 0.1 ===<br />
<br />
Version 0.1 was drafted August 2008.<br />
<br />
== Further Reading ==<br />
* See [http://www.technorati.com/cosmos/referer.html blogs discussing this page].<br />
<br />
== Related Pages ==<br />
* hnews<br />
* [[news-brainstorming]]: thoughts for improving hNews. <br />
* [[hnews-faq|hNews FAQ]]: if you have any questions about hNews, check here, and if you don't find answers, add your questions!<br />
* [[hnews-issues]]: please add any issues with the specification to the issues page.<br />
* [[news-formats]]: existing news and news management schemas.<br />
* [[news-examples]]: examples of news formats on the web.<br />
** [[hnews-examples]]: examples of how to implement hNews.<br />
<br />
[[Category:Draft Specifications]]<br />
[[Category:hNews]]</div>JonathanMalekhttp://microformats.org/wiki/index.php?title=hnews-faq&diff=41042hnews-faq2009-10-12T23:20:35Z<p>JonathanMalek: Moving pertinent discussion from labs.ap.org to FAQ.</p>
<hr />
<div>''(moved from the discussion page at http://labs.ap.org/wiki/Talk:hNews)''<br />
<br />
== Where can I read the current draft for hNews? ==<br />
It can be found [[hNews|here]].<br />
<br />
== Does hNews replace NewsML, NewsML-G2, ATOM or RSS? ==<br />
No. -- [[User:Smyles|Stuart Myles]]<br />
<br />
== OK, So How Does hNews relate to NewsML, NewsML-G2, ATOM and RSS? ==<br />
The idea with hNews is to add some machine-readable news-specific semantics to display-ready HTML. I see NewsML [http://www.iptc.org/cms/site/index.html?channel=CH0106], NewsML-G2 [http://www.iptc.org/cms/site/index.html?channel=CH0111], ATOM [http://tools.ietf.org/html/rfc4287] and RSS [http://en.wikipedia.org/wiki/RSS_(file_format)] as ways of enveloping content, to provide structure and metadata. (Each has its own merits and drawbacks). They can all be used to convey HTML and therefore any of them would be an ideal way to deliver hNews. There may be some overlap in the news metadata that is marked up (e.g. you can indicate a headline in NewsML and within hNews). -- [[User:Smyles|Stuart Myles]]<br />
<br />
== Does hNews Replace NITF? ==<br />
NITF (News Industry Text Format [http://www.nitf.org]) is an XML format for defining the content and structure of articles. Whereas hNews is ready-for-display, NITF needs to be translated into a display format (e.g. HTML, XHTML, WML, PDF, etc.). This is one of NITF's strengths - you can turn it into virtually any other display format (including print!). NITF also has a much richer set of metadata fields that can be expressed [http://www.iptc.org/std/NITF/3.4/documentation/nitf-documentation.html]. AP plans to continue to use NITF (alongside a number of other formats), even as we roll out hNews. -- [[User:Smyles|Stuart Myles]] (In the interests of full disclosure - I represent AP to the IPTC and am the chairman of the IPTC's NITF Working Group).<br />
<br />
== Why not RDFa? ==<br />
A couple of people have asked me whether the goals of hNews be met using RDFa [http://www.w3.org/TR/rdfa-syntax/] instead? RDFa is "a thin layer of markup you can add to your web pages that makes them understandable for machines as well as people... By adding it, browsers, search engines, and other software can understand more about the pages, and in so doing offer more services or better results for the user." (quote from [http://www.w3.org/MarkUp/2009/rdfa-for-html-authors]).<br />
<br />
I agree that RDFa would be another, equally valid way to add the hNews metadata into an (X)HTML page. I'm not an RDFa expert, but I wonder if it would be possible to use both hNews and RDFa at the same time? If anyone has done something similar to hNews with RDFa, then please let us know. -- [[User:Smyles|Stuart Myles]]<br />
<br />
Teams at the BBC are currently considering marking up their news content as RDF available as a seperate resource, rather than in the pages themselves. It might prove sensible to do some work with GRDDL to make it possible to exchange hNews content into whatever ontology they end up working with. -- [[User:MarkNg|Mark Ng]]<br />
<br />
== Why not use microdata ? ==<br />
The WHATWG is considering introducing a "microdata" syntax into HTML 5 [http://www.whatwg.org/specs/web-apps/current-work/multipage/microdata.html]. This would seem to be a valid way of achieving something similar to hNews - although not without controversy. See, for example the discussions at [http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2009Aug/thread.html]. We look forward to a bit more clarity around this, including whether microdata will only work in HTML 5 onwards or will it be possible to retrofit it into current web pages. -- [[User:Smyles|Stuart Myles]]<br />
<br />
== Where is the tracking piece in hNews? ==<br />
hNews is a way to add some machine-readable news semantics to HTML. If you want to follow the hNews spec, you are not required to - or prevented from - adding any kind of tracking device, such as a "web bug" [http://en.wikipedia.org/wiki/Web_bug]. -- [[User:Smyles|Stuart Myles]]<br />
<br />
== Is hNews a microformat? ==<br />
[[User:Adactio|Adactio]] proposed that this was erroneously asserted, and modified the draft. In fact, our intent is to submit this as a microformat draft on the microformat site (as should be evident from the use of microformat.org/wiki templates, to facilitate a quick move), assuming that it is acceptable to the community as such. If it is not, then at that time we will modify the language appropriately. -- [[User:JonathanMalek|Jonathan Malek]]<br />
<br />
But until a format has been through the microformats process, it is *not* a microformat. It does you no favours to mis-label a markup pattern as a microformat prematurely ...if anything, doing so will damage your standing with the microformats community who may view it as opportunistic coattail-grabbing. -- [[User:Adactio|Adactio]]<br />
<br />
I completely agree, Jeremy. I was happy to see the changes to the http://en.wikipedia.org/wiki/HNews that you made, and I think those make sense. I'd like to keep this draft intact in terms of intent, namely to submit this as a draft on the microformat site. -- [[User:JonathanMalek|Jonathan Malek]]<br />
<br />
But even if this were on the microformats wiki, you still wouldn't refer to hNews as a microformat until it has passed the microformats process. If this document is supposed to be a draft text for a page on the microformats wiki, then I don't understand why it has been published at a public URL. As long it *is* a public URL, it shouldn't contain any misleading falsehoods.<br />
<br />
I would encourage you to try the microformats process; namely to propose a format for syndicating news content, look at existing patterns and discussg what to do next. Creating an entire spec and *then* bringing it to the microformats community is putting the cart before the horse. State the problem case, not the solution. That way, others can help you in drafting a format. -- [[User:Adactio|Adactio]]<br />
<br />
Jeremy, I went through the process steps back in May of last year, and worked through what I could within the constraints I have. Be assured that we will faithfully pursue the microformats process, now that this effort has seen the light of day. I would point you to numerous other pages on the web that have done the same thing, and then let you consider whether you should revert your changes. For example: http://www.jodcast.net/avm/microformat.html, http://developer.iamalpha.com/profile, just to name a few. -- [[User:JonathanMalek|Jonathan Malek]]<br />
<br />
Yes, those examples you point to are examples of formats *incorrectly* labelling formats as microformats. There are some others out there as well. -- [[User:Adactio|Adactio]]<br />
<br />
I had a chance to speak with Tantek at the microformatsdevcamp about retrofitting some of the work from hnews into hatom and/or a specific news microformat. I'll be carrying that work out on the hatom-brainstorming page. I'm not sure how we best move the current work across to the microformats wiki wholesale. -- [[User:MarkNg|Mark Ng]]</div>JonathanMalekhttp://microformats.org/wiki/index.php?title=hNews&diff=41041hNews2009-10-12T22:20:20Z<p>JonathanMalek: fixing redirect</p>
<hr />
<div>#REDIRECT [[hnews]]</div>JonathanMalekhttp://microformats.org/wiki/index.php?title=User:JonathanMalek&diff=41040User:JonathanMalek2009-10-12T22:17:11Z<p>JonathanMalek: adding linked-in page</p>
<hr />
<div><div class="vcard"><br />
<span class="fn">Jonathan Malek</span><br />
* <span class="url">http://jonathanmalek.com/</span><br />
* <span class="url">http://www.linkedin.com/in/jonathanmalek</span><br />
</div><br />
----<br />
{{cc-public-domain-release}}</div>JonathanMalekhttp://microformats.org/wiki/index.php?title=hnews-examples&diff=41039hnews-examples2009-10-12T22:10:49Z<p>JonathanMalek: hNews with hMedia</p>
<hr />
<div><h1>hNews Examples</h1><br />
{{TOC-right}}<br />
<br />
Examples of [[hnews]] - '''Work in progress!'''<br />
<br />
= Contributors =<br />
* [[User:JonathanMalek|Jonathan Malek]] <br />
<br />
= Sample News Story = <br />
The following is a typically formatted news story:<br />
<br />
<div style="border: thin dashed black; padding: .5em 1em;"><br />
'''Renewing US ties with Latin America, Obama says he wants to lead, not lecture, on democracy'''<br />
<br />
by BEN FELLER, Associated Press - 19 April 2009 18:17 GMT <br />
<br />
PORT-OF-SPAIN, Trinidad (AP) -- Defending his brand of world politics, President Barack Obama said Sunday...<br />
<br />
Both Graham and McCaskill spoke on "Fox News Sunday." Ensign was interviewed on CNN's "State of the Union."<br />
<br />
Copyright 2009 The Associated Press. All rights reserved. This material may not be published, broadcast, rewritten or redistributed.<br />
</div><br />
<br />
Typically news organizations will have a significant amount of metadata behind this story, communicated in a variety of formats like [http://www.iptc.org/cms/site/ NewsML]. By the time they are presented to the reader, much of the metadata (amounting in some cases to hundreds of fields) has been stripped away. We can add a bit of that back in, and using hnews, create possibilities for some interesting semantic actions. Taking the above story, and formatting it as hnews:<br />
<br />
<pre><nowiki><br />
<div class="hnews hentry item"><br />
<h4><br />
<a class="url entry-title" href="http://example.org/article/us-latam-obama-democracy.html" rel="bookmark"><br />
Renewing US ties with Latin America, Obama says he wants to lead, not lecture, on democracy</a><br />
</h4><br />
<br />
<div><br />
<small> by <br />
<span class="author vcard"><a class="email fn" <br />
href="mailto:ben.feller@example.org">BEN FELLER</a></span>, <br />
<span class="source-org vcard"><a class="url org fn" <br />
href="http://www.ap.org">Associated Press</a></span>,<br />
<a href="http://www.ap.org/newsvalues/index.html" rel="principles"><img src="/wikidir/images/principles-button-blue.png" /></a> - <br />
<span class="updated dtstamp" <br />
title="2009-04-19T18:17:29Z">19 April 2009 18:17 GMT</span><br />
</small><br />
</div><br />
<br />
<div class="entry-content"><br />
<p><span class="dateline">PORT-OF-SPAIN, Trinidad</span> (AP) -- Defending his brand <br />
of world politics, President Barack Obama said Sunday...</p><br />
<p>Both Graham and McCaskill spoke on "Fox News Sunday." Ensign was interviewed on CNN's <br />
"State of the Union."</p><br />
</div><br />
<br />
<div><br />
<small><br />
News Topics:<br />
<a href="http://example.org/Summits" rel="tag">Summits</a>, ...,<br />
<a href="http://example.org/Government+policy" rel="tag">Government policy</a><br />
<br/><br />
People, Places and Companies: <br />
<a href="http://example.org/Barack+Obama" rel="tag">Barack Obama</a>, ..., <br />
<a href="http://example.org/Hugo+Chavez" rel="tag">Hugo Chavez</a> <br />
</small><br />
</div><br />
<br />
<br />
<div class="geo"><br />
<small><br />
Lat: <span class="latitude">10.65715</span> <br />
Long: <span class="longitude">-61.483582</span><br />
</small><br />
</div><br />
<br />
<div id="first-sample-license"><br />
<small><br />
Copyright 2009 The <a rel="item-license" href="#first-sample-license">Associated Press</a>. <br />
All rights reserved. This material may not be published, broadcast, rewritten or redistributed.<br />
</small><br />
</div><br />
</div><br />
</nowiki></pre><br />
<br />
We get a richly-formatted news story that enhances the reader's experience with news: <br />
<br />
<div style="border: thin dashed black; padding: .5em 1em;"><br />
<div class="hnews hentry item"><br />
<h4><br />
[http://example.org/article/us-latam-obama-democracy.html Renewing US ties with Latin America, Obama says he wants to lead, not lecture, on democracy]<br />
</h4><br />
<span><br />
<small> by [mailto:ben.feller@example.org BEN FELLER], <br />
[http://www.ap.org Associated Press]<br />
[http://www.ap.org/newsvalues/index.html principles] - <br />
<span class="updated dtstamp" <br />
title="2009-04-19T18:17:29Z">19 April 2009 18:17 GMT</span><br />
</small><br />
</span><br />
<br />
<span class="entry-content"><br />
<p><span class="dateline">PORT-OF-SPAIN, Trinidad</span> (AP) -- Defending his brand <br />
of world politics, President Barack Obama said Sunday...</p><br />
<p>Both Graham and McCaskill spoke on "Fox News Sunday." Ensign was interviewed on CNN's <br />
"State of the Union."</p><br />
</span><br />
<br />
<span><br />
<small><br />
News Topics:<br />
[http://example.org/Summits Summits], ...,<br />
[http://example.org/Government+policy Government policy]<br />
<br/><br />
People, Places and Companies: <br />
[http://example.org/Barack+Obama Barack Obama], ..., <br />
[http://example.org/Hugo+Chavez Hugo Chavez] <br />
</small><br />
</span><br />
<br/><br />
<span class="geo"><br />
<small><br />
Lat: <span class="latitude">10.65715</span> <br />
Long: <span class="longitude">-61.483582</span><br />
</small><br />
</span><br />
<br/><br />
<span><br />
<small><br />
Copyright 2009 The [http://www.ap.org Associated Press]. <br />
All rights reserved. This material may not be published, broadcast, rewritten or redistributed.<br />
</small><br />
</span><br />
</div><br />
</div><br />
<br />
== Geo Alternative ==<br />
There are a number of options with how this information is formatted. For instance, rather than adding in a separate [[geo]] line, we could chose to do something proposed as an improvement on [[geo-brainstorming#Geo_improvements|geo-brainstorming]]: <br />
<br />
<pre><nowiki><br />
<p><abbr title="10.65715,-61.483582" class="dateline geo">PORT-OF-SPAIN, Trinidad</abbr> (AP) -- Defending his brand <br />
of world politics, President Barack Obama said Sunday...</p><br />
</nowiki></pre><br />
<br />
Which renders as:<br />
<div style="border: thin dashed black; padding: .5em 1em;"><br />
<abbr title="10.65715,-61.483582" class="dateline geo">PORT-OF-SPAIN, Trinidad</abbr> (AP) -- Defending his brand of world politics, President Barack Obama said Sunday...<br />
</div><br />
<br />
Naturally, a valid option (as discussed [[assistive-technology-abbr-results#Markup_Possibilities|here]]) is to use the <code>&lt;span></code> element instead.<br />
<br />
= Sample News Story with Media (Photo) = <br />
<br />
Another example is combining this same story with a related photo by folding an [[hmedia]] item into the [[hnews]] entry:<br />
<br />
<pre><nowiki><br />
<div class="hnews hentry item"><br />
<div class="hmedia"><br />
<img class="photo" width="256" height="342" border="0" alt="President Barack Obama speaks on the South Lawn of the White House in Washington, Wednesday, Aug. 5, 2009, about the release of Laura Ling and Euna Lee, the two freed American journalists who were arrested in March after allegedly crossing into North Korea from China. (AP Photo/Ron Edmonds)" src="http://example.org/Obama_Mana.jpg"/><br />
<span class="fn">President Barack Obama</span><br />
</div><br />
<br />
<h4><br />
<a class="url entry-title" href="http://example.org/article/us-latam-obama-democracy.html" rel="bookmark"><br />
Renewing US ties with Latin America, Obama says he wants to lead, not lecture, on democracy</a><br />
</h4><br />
<br />
<div><br />
<small> by <br />
<span class="author vcard"><a class="email fn" <br />
href="mailto:ben.feller@example.org">BEN FELLER</a></span>, <br />
<span class="source-org vcard"><a class="url org fn" <br />
href="http://www.ap.org">Associated Press</a></span>,<br />
<a href="http://www.ap.org/newsvalues/index.html" rel="principles"><img src="/wikidir/images/principles-button-blue.png</a> - <br />
<span class="updated dtstamp" <br />
title="2009-04-19T18:17:29Z">19 April 2009 18:17 GMT</span><br />
</small><br />
</div><br />
<br />
<div class="entry-content"><br />
<p><span class="dateline">PORT-OF-SPAIN, Trinidad</span> (AP) -- Defending his brand <br />
of world politics, President Barack Obama said Sunday...</p><br />
<p>Both Graham and McCaskill spoke on "Fox News Sunday." Ensign was interviewed on CNN's <br />
"State of the Union."</p><br />
</div><br />
<br />
<div><br />
<small><br />
News Topics:<br />
<a href="http://example.org/Summits" rel="tag">Summits</a>, ...,<br />
<a href="http://example.org/Government+policy" rel="tag">Government policy</a><br />
<br/><br />
People, Places and Companies: <br />
<a href="http://example.org/Barack+Obama" rel="tag">Barack Obama</a>, ..., <br />
<a href="http://example.org/Hugo+Chavez" rel="tag">Hugo Chavez</a> <br />
</small><br />
</div><br />
<br />
<div class="geo"><br />
<small><br />
Lat: <span class="latitude">10.65715</span> <br />
Long: <span class="longitude">-61.483582</span><br />
</small><br />
</div><br />
<br />
<div><br />
<small><br />
Copyright 2009 The <a rel="item-license" href="http://www.ap.org">Associated Press</a>. <br />
All rights reserved. This material may not be published, broadcast, rewritten or redistributed.<br />
</small><br />
</div><br />
</div><br />
</nowiki></pre></div>JonathanMalekhttp://microformats.org/wiki/index.php?title=hnews-examples&diff=41038hnews-examples2009-10-12T22:03:44Z<p>JonathanMalek: Adding TOC, cleaning up layout</p>
<hr />
<div><h1>hNews Examples</h1><br />
{{TOC-right}}<br />
<br />
Examples of [[hnews]] - '''Work in progress!'''<br />
<br />
= Contributors =<br />
* [[User:JonathanMalek|Jonathan Malek]] <br />
<br />
= Sample News Story = <br />
The following is a typically formatted news story:<br />
<br />
<div style="border: thin dashed black; padding: .5em 1em;"><br />
'''Renewing US ties with Latin America, Obama says he wants to lead, not lecture, on democracy'''<br />
<br />
by BEN FELLER, Associated Press - 19 April 2009 18:17 GMT <br />
<br />
PORT-OF-SPAIN, Trinidad (AP) -- Defending his brand of world politics, President Barack Obama said Sunday...<br />
<br />
Both Graham and McCaskill spoke on "Fox News Sunday." Ensign was interviewed on CNN's "State of the Union."<br />
<br />
Copyright 2009 The Associated Press. All rights reserved. This material may not be published, broadcast, rewritten or redistributed.<br />
</div><br />
<br />
Typically news organizations will have a significant amount of metadata behind this story, communicated in a variety of formats like [http://www.iptc.org/cms/site/ NewsML]. By the time they are presented to the reader, much of the metadata (amounting in some cases to hundreds of fields) has been stripped away. We can add a bit of that back in, and using hnews, create possibilities for some interesting semantic actions. Taking the above story, and formatting it as hnews:<br />
<br />
<pre><nowiki><br />
<div class="hnews hentry item"><br />
<h4><br />
<a class="url entry-title" href="http://example.org/article/us-latam-obama-democracy.html" rel="bookmark"><br />
Renewing US ties with Latin America, Obama says he wants to lead, not lecture, on democracy</a><br />
</h4><br />
<br />
<div><br />
<small> by <br />
<span class="author vcard"><a class="email fn" <br />
href="mailto:ben.feller@example.org">BEN FELLER</a></span>, <br />
<span class="source-org vcard"><a class="url org fn" <br />
href="http://www.ap.org">Associated Press</a></span>,<br />
<a href="http://www.ap.org/newsvalues/index.html" rel="principles"><img src="/wikidir/images/principles-button-blue.png" /></a> - <br />
<span class="updated dtstamp" <br />
title="2009-04-19T18:17:29Z">19 April 2009 18:17 GMT</span><br />
</small><br />
</div><br />
<br />
<div class="entry-content"><br />
<p><span class="dateline">PORT-OF-SPAIN, Trinidad</span> (AP) -- Defending his brand <br />
of world politics, President Barack Obama said Sunday...</p><br />
<p>Both Graham and McCaskill spoke on "Fox News Sunday." Ensign was interviewed on CNN's <br />
"State of the Union."</p><br />
</div><br />
<br />
<div><br />
<small><br />
News Topics:<br />
<a href="http://example.org/Summits" rel="tag">Summits</a>, ...,<br />
<a href="http://example.org/Government+policy" rel="tag">Government policy</a><br />
<br/><br />
People, Places and Companies: <br />
<a href="http://example.org/Barack+Obama" rel="tag">Barack Obama</a>, ..., <br />
<a href="http://example.org/Hugo+Chavez" rel="tag">Hugo Chavez</a> <br />
</small><br />
</div><br />
<br />
<br />
<div class="geo"><br />
<small><br />
Lat: <span class="latitude">10.65715</span> <br />
Long: <span class="longitude">-61.483582</span><br />
</small><br />
</div><br />
<br />
<div id="first-sample-license"><br />
<small><br />
Copyright 2009 The <a rel="item-license" href="#first-sample-license">Associated Press</a>. <br />
All rights reserved. This material may not be published, broadcast, rewritten or redistributed.<br />
</small><br />
</div><br />
</div><br />
</nowiki></pre><br />
<br />
We get a richly-formatted news story that enhances the reader's experience with news: <br />
<br />
<div style="border: thin dashed black; padding: .5em 1em;"><br />
<div class="hnews hentry item"><br />
<h4><br />
[http://example.org/article/us-latam-obama-democracy.html Renewing US ties with Latin America, Obama says he wants to lead, not lecture, on democracy]<br />
</h4><br />
<span><br />
<small> by [mailto:ben.feller@example.org BEN FELLER], <br />
[http://www.ap.org Associated Press]<br />
[http://www.ap.org/newsvalues/index.html principles] - <br />
<span class="updated dtstamp" <br />
title="2009-04-19T18:17:29Z">19 April 2009 18:17 GMT</span><br />
</small><br />
</span><br />
<br />
<span class="entry-content"><br />
<p><span class="dateline">PORT-OF-SPAIN, Trinidad</span> (AP) -- Defending his brand <br />
of world politics, President Barack Obama said Sunday...</p><br />
<p>Both Graham and McCaskill spoke on "Fox News Sunday." Ensign was interviewed on CNN's <br />
"State of the Union."</p><br />
</span><br />
<br />
<span><br />
<small><br />
News Topics:<br />
[http://example.org/Summits Summits], ...,<br />
[http://example.org/Government+policy Government policy]<br />
<br/><br />
People, Places and Companies: <br />
[http://example.org/Barack+Obama Barack Obama], ..., <br />
[http://example.org/Hugo+Chavez Hugo Chavez] <br />
</small><br />
</span><br />
<br/><br />
<span class="geo"><br />
<small><br />
Lat: <span class="latitude">10.65715</span> <br />
Long: <span class="longitude">-61.483582</span><br />
</small><br />
</span><br />
<br/><br />
<span><br />
<small><br />
Copyright 2009 The [http://www.ap.org Associated Press]. <br />
All rights reserved. This material may not be published, broadcast, rewritten or redistributed.<br />
</small><br />
</span><br />
</div><br />
</div><br />
<br />
<br />
== Geo Alternative ==<br />
There are a number of options with how this information is formatted. For instance, rather than adding in a separate [[geo]] line, we could chose to do something proposed as an improvement on [[geo-brainstorming#Geo_improvements|geo-brainstorming]]: <br />
<br />
<pre><nowiki><br />
<p><abbr title="10.65715,-61.483582" class="dateline geo">PORT-OF-SPAIN, Trinidad</abbr> (AP) -- Defending his brand <br />
of world politics, President Barack Obama said Sunday...</p><br />
</nowiki></pre><br />
<br />
Which renders as:<br />
<div style="border: thin dashed black; padding: .5em 1em;"><br />
<abbr title="10.65715,-61.483582" class="dateline geo">PORT-OF-SPAIN, Trinidad</abbr> (AP) -- Defending his brand of world politics, President Barack Obama said Sunday...<br />
</div><br />
<br />
Naturally, a valid option (as discussed [[assistive-technology-abbr-results#Markup_Possibilities|here]]) is to use the <code>&lt;span></code> element instead.</div>JonathanMalekhttp://microformats.org/wiki/index.php?title=hnews-examples&diff=41037hnews-examples2009-10-12T22:00:59Z<p>JonathanMalek: Geo alternative sample</p>
<hr />
<div>Examples of [[hnews]] - '''Work in progress!'''<br />
<br />
= Contributors =<br />
* [[User:JonathanMalek|Jonathan Malek]] <br />
<br />
<br />
= Sample News Story = <br />
The following is a typically formatted news story:<br />
<br />
<div style="border: thin dashed black; padding: .5em 1em;"><br />
'''Renewing US ties with Latin America, Obama says he wants to lead, not lecture, on democracy'''<br />
<br />
by BEN FELLER, Associated Press - 19 April 2009 18:17 GMT <br />
<br />
PORT-OF-SPAIN, Trinidad (AP) -- Defending his brand of world politics, President Barack Obama said Sunday...<br />
<br />
Both Graham and McCaskill spoke on "Fox News Sunday." Ensign was interviewed on CNN's "State of the Union."<br />
<br />
Copyright 2009 The Associated Press. All rights reserved. This material may not be published, broadcast, rewritten or redistributed.<br />
</div><br />
<br />
Typically news organizations will have a significant amount of metadata behind this story, communicated in a variety of formats like [http://www.iptc.org/cms/site/ NewsML]. By the time they are presented to the reader, much of the metadata (amounting in some cases to hundreds of fields) has been stripped away. We can add a bit of that back in, and using hnews, create possibilities for some interesting semantic actions. Taking the above story, and formatting it as hnews:<br />
<br />
<pre><nowiki><br />
<div class="hnews hentry item"><br />
<h4><br />
<a class="url entry-title" href="http://example.org/article/us-latam-obama-democracy.html" rel="bookmark"><br />
Renewing US ties with Latin America, Obama says he wants to lead, not lecture, on democracy</a><br />
</h4><br />
<br />
<div><br />
<small> by <br />
<span class="author vcard"><a class="email fn" <br />
href="mailto:ben.feller@example.org">BEN FELLER</a></span>, <br />
<span class="source-org vcard"><a class="url org fn" <br />
href="http://www.ap.org">Associated Press</a></span>,<br />
<a href="http://www.ap.org/newsvalues/index.html" rel="principles"><img src="/wikidir/images/principles-button-blue.png" /></a> - <br />
<span class="updated dtstamp" <br />
title="2009-04-19T18:17:29Z">19 April 2009 18:17 GMT</span><br />
</small><br />
</div><br />
<br />
<div class="entry-content"><br />
<p><span class="dateline">PORT-OF-SPAIN, Trinidad</span> (AP) -- Defending his brand <br />
of world politics, President Barack Obama said Sunday...</p><br />
<p>Both Graham and McCaskill spoke on "Fox News Sunday." Ensign was interviewed on CNN's <br />
"State of the Union."</p><br />
</div><br />
<br />
<div><br />
<small><br />
News Topics:<br />
<a href="http://example.org/Summits" rel="tag">Summits</a>, ...,<br />
<a href="http://example.org/Government+policy" rel="tag">Government policy</a><br />
<br/><br />
People, Places and Companies: <br />
<a href="http://example.org/Barack+Obama" rel="tag">Barack Obama</a>, ..., <br />
<a href="http://example.org/Hugo+Chavez" rel="tag">Hugo Chavez</a> <br />
</small><br />
</div><br />
<br />
<br />
<div class="geo"><br />
<small><br />
Lat: <span class="latitude">10.65715</span> <br />
Long: <span class="longitude">-61.483582</span><br />
</small><br />
</div><br />
<br />
<div id="first-sample-license"><br />
<small><br />
Copyright 2009 The <a rel="item-license" href="#first-sample-license">Associated Press</a>. <br />
All rights reserved. This material may not be published, broadcast, rewritten or redistributed.<br />
</small><br />
</div><br />
</div><br />
</nowiki></pre><br />
<br />
We get a richly-formatted news story that enhances the reader's experience with news: <br />
<br />
<div style="border: thin dashed black; padding: .5em 1em;"><br />
<div class="hnews hentry item"><br />
<h4><br />
[http://example.org/article/us-latam-obama-democracy.html Renewing US ties with Latin America, Obama says he wants to lead, not lecture, on democracy]<br />
</h4><br />
<span><br />
<small> by [mailto:ben.feller@example.org BEN FELLER], <br />
[http://www.ap.org Associated Press]<br />
[http://www.ap.org/newsvalues/index.html principles] - <br />
<span class="updated dtstamp" <br />
title="2009-04-19T18:17:29Z">19 April 2009 18:17 GMT</span><br />
</small><br />
</span><br />
<br />
<span class="entry-content"><br />
<p><span class="dateline">PORT-OF-SPAIN, Trinidad</span> (AP) -- Defending his brand <br />
of world politics, President Barack Obama said Sunday...</p><br />
<p>Both Graham and McCaskill spoke on "Fox News Sunday." Ensign was interviewed on CNN's <br />
"State of the Union."</p><br />
</span><br />
<br />
<span><br />
<small><br />
News Topics:<br />
[http://example.org/Summits Summits], ...,<br />
[http://example.org/Government+policy Government policy]<br />
<br/><br />
People, Places and Companies: <br />
[http://example.org/Barack+Obama Barack Obama], ..., <br />
[http://example.org/Hugo+Chavez Hugo Chavez] <br />
</small><br />
</span><br />
<br/><br />
<span class="geo"><br />
<small><br />
Lat: <span class="latitude">10.65715</span> <br />
Long: <span class="longitude">-61.483582</span><br />
</small><br />
</span><br />
<br/><br />
<span><br />
<small><br />
Copyright 2009 The [http://www.ap.org Associated Press]. <br />
All rights reserved. This material may not be published, broadcast, rewritten or redistributed.<br />
</small><br />
</span><br />
</div><br />
</div><br />
<br />
<br />
== Geo Alternative ==<br />
There are a number of options with how this information is formatted. For instance, rather than adding in a separate [[geo]] line, we could chose to do something proposed as an improvement on [[geo-brainstorming#Geo_improvements|geo-brainstorming]]: <br />
<br />
<pre><nowiki><br />
<p><abbr title="10.65715,-61.483582" class="dateline geo">PORT-OF-SPAIN, Trinidad</abbr> (AP) -- Defending his brand <br />
of world politics, President Barack Obama said Sunday...</p><br />
</nowiki></pre><br />
<br />
Which renders as:<br />
<div style="border: thin dashed black; padding: .5em 1em;"><br />
<abbr title="10.65715,-61.483582" class="dateline geo">PORT-OF-SPAIN, Trinidad</abbr> (AP) -- Defending his brand of world politics, President Barack Obama said Sunday...<br />
</div><br />
<br />
Naturally, a valid option (as discussed [[assistive-technology-abbr-results#Markup_Possibilities|here]]) is to use the <code>&lt;span></code> element instead.</div>JonathanMalekhttp://microformats.org/wiki/index.php?title=hnews&diff=41036hnews2009-10-12T21:50:16Z<p>JonathanMalek: reorganizing related links (following hreview's lead)</p>
<hr />
<div><entry-title>hNews 0.1</entry-title><br />
{{Template:DraftSpecification}}<br />
<br />
hNews is 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.<br />
__TOC__<br />
== Draft Specification ==<br />
<br />
;Editor/Author<br />
:[[:User:JonathanMalek|Jonathan Malek]] ([http://www.ap.org Associated Press])<br />
<br />
;Contributors<br />
:[[:User:Smyles|Stuart Myles]] ([http://www.ap.org Associated Press]) <br />
:[[:User:Martinjemoore|Martin Moore]] ([http://mediastandardstrust.org Media Standards Trust])<br />
:[[:User:MarkNg|Mark Ng]] ([http://mediastandardstrust.org Media Standards Trust])<br />
:[[:User:Tbmartinwiki|Todd B. Martin]] ([http://www.ap.org Associated Press])<br />
<br />
=== Copyright ===<br />
Per the public domain release on the authors' user pages ([[:User:JonathanMalek|Jonathan Malek]]) this specification is released into the public domain. <br />
<br />
{{MicroFormatPublicDomainContributionStatement}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Introduction ==<br />
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.<br />
<br />
{{rfc-2119-intro}}<br />
<br />
== Semantic XHTML Design Principles ==<br />
{{semantic-xhtml-design-principles}}<br />
<br />
== Format ==<br />
=== In General ===<br />
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.<br />
<br />
=== Schema ===<br />
The hNews schema consists of the following: <br />
<br />
* (root) ('''<code>root</code>''') and '''<code>hentry</code>'''. required. Using [[hAtom]].<br />
** '''<code>source-org</code>'''. required. Using [[hCard]].[*]<br />
** '''<code>dateline</code>'''. optional. Using text or [[hCard]].<br />
** '''<code>geo</code>'''. optional. Using [[geo]].[*]<br />
** '''<code>item-license</code>'''. recommended. Using a [[licensing-brainstorming#item_as_container license|brainstorm proposal]].<br />
** '''<code>principles</code>'''. recommended. Using the draft microformat. [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles].<br />
<br />
[*] Some required elements have defaults if missing, see below.<br />
<br />
=== Field and Element Details ===<br />
<br />
===== Source Organization =====<br />
* a Source Organization element is identified by the class name <code>source-org</code>.<br />
* Source Organization represents the originating organization for the news story.<br />
* a Source Organization {{must}} be encoded in an [[hCard]].<br />
* if the Source Organization is missing <br />
** find the [[algorithm-nearest-in-parent]] element(s) with class name <code>source-org</code> and that is/are a valid [[hCard]]<br />
** otherwise the entry is invalid hNews<br />
<br />
===== Dateline =====<br />
* a dateline element is identified by the class name <code>dateline</code>.<br />
* dateline represents the location where the news story was written or filed (see [http://en.wikipedia.org/wiki/Dateline dateline] for more details).<br />
* a dateline element {{may}} be encoded in an [[hCard]].<br />
* a news story {{should}} have a dateline element.<br />
* dateline sometimes also includes the publish date of the news story. In such cases, use the [[datetime-design-pattern]] to encode the date.<br />
<br />
===== Geo =====<br />
* a geo element is identified by the class name <code>geo</code><br />
* geo represents the geographic coordinates of relevant locations in the news story.<br />
* a geo element should be encoded in a [[geo]].<br />
* 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).<br />
<br />
===== License =====<br />
* a license element is identified by the class name <code>item-license</code>.<br />
* a license element {{must}} be encoded as described in this [http://microformats.org/wiki/licensing-brainstorming#item_as_container license brainstorm proposal].<br />
* a news story {{should}} include a license element.<br />
<br />
===== Principles =====<br />
* a principles element is identified by <code>rel-principles</code>.<br />
* principles represents the statement of principles and ethics used by the news organization that produced the news story.<br />
* a principles element {{must}} be encoded in [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles].<br />
* a news story {{should}} include principles.<br />
* principles {{should}} be linked to using the icons [[image:principles-button-blue.png]] or [[image:principles-book-blue.png]].<br />
<br />
=== XMDP Profile ===<br />
<pre><br />
<dl class="profile"><br />
<dt>class</dt><br />
<dd><p><br />
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class"><br />
HTML4 definition of the 'class' attribute.</a><br />
This meta data profile defines some 'class' attribute values (class names) <br />
and their meanings as suggested by a <br />
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile"><br />
draft of "Hypertext Links in HTML"</a>.<br />
<dl><br />
<br />
<dt>root</dt><br />
<dd><br />
Used to describe semantic information associated with news stories.<br />
</dd><br />
<br />
<dt>source-org</dt><br />
<dd><br />
The originating organization for the news story.<br />
</dd><br />
<br />
<dt>dateline</dt><br />
<dd><br />
Represents the location where the news story was filed.<br />
</dd><br />
<br />
<dt>geo</dt><br />
<dd><br />
Represents geographic coordinates of relevant locations in the story.<br />
</dd><br />
<br />
<dt>item-license</dt><br />
<dd><br />
Represents the license for the story.<br />
</dd><br />
<br />
<dt>principles</dt><br />
<dd><br />
Represents the statement of principles and ethics used by the news organization that produced the news story.<br />
</dd><br />
<br />
</dl><br />
</dd><br />
</dl><br />
</pre><br />
<br />
== Examples ==<br />
<br />
See [[hnews-examples]].<br />
<br />
=== Examples in the wild ===<br />
<br />
See [[hnews-examples-in-wild]].<br />
<br />
== Implementations ==<br />
<br />
== References ==<br />
<br />
=== Normative References ===<br />
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0]<br />
* [[hatom|hAtom]]<br />
* [[hcard|hCard]]<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [[rel-tag]]<br />
* [[geo]]<br />
* [[licensing-brainstorming#item_as_container_license|item-license brainstorm]]<br />
* [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles]<br />
* [http://www.ietf.org/rfc/rfc2119.txt RFC2119]<br />
* [http://www.ietf.org/rfc/rfc4287.txt RFC4287] (Atom 1.0)<br />
<br />
=== Informative References ===<br />
* Other news efforts: see [[news-formats]].<br />
<br />
== Work in progress ==<br />
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. <br />
<br />
=== Version 0.1 ===<br />
<br />
Version 0.1 was drafted August 2008.<br />
<br />
== Further Reading ==<br />
* See [http://www.technorati.com/cosmos/referer.html blogs discussing this page].<br />
<br />
== Related Pages ==<br />
* hnews<br />
* [[news-brainstorming]]: thoughts for improving hNews. <br />
* [[hnews-faq|hNews FAQ]]: if you have any questions about hNews, check here, and if you don't find answers, add your questions!<br />
* [[hnews-issues]]: please add any issues with the specification to the issues page.<br />
* [[news-formats]]: existing news and news management schemas.<br />
* [[news-examples]]: examples of news formats on the web.<br />
** [[hnews-examples]]: examples of how to implement hNews.<br />
<br />
[[Category:Draft Specifications]]<br />
[[Category:hNews]]</div>JonathanMalekhttp://microformats.org/wiki/index.php?title=hnews&diff=41035hnews2009-10-12T21:36:41Z<p>JonathanMalek: informative references</p>
<hr />
<div><entry-title>hNews 0.1</entry-title><br />
{{Template:DraftSpecification}}<br />
<br />
hNews is 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.<br />
__TOC__<br />
== Draft Specification ==<br />
<br />
;Editor/Author<br />
:[[:User:JonathanMalek|Jonathan Malek]] ([http://www.ap.org Associated Press])<br />
<br />
;Contributors<br />
:[[:User:Smyles|Stuart Myles]] ([http://www.ap.org Associated Press]) <br />
:[[:User:Martinjemoore|Martin Moore]] ([http://mediastandardstrust.org Media Standards Trust])<br />
:[[:User:MarkNg|Mark Ng]] ([http://mediastandardstrust.org Media Standards Trust])<br />
:[[:User:Tbmartinwiki|Todd B. Martin]] ([http://www.ap.org Associated Press])<br />
<br />
=== Copyright ===<br />
Per the public domain release on the authors' user pages ([[:User:JonathanMalek|Jonathan Malek]]) this specification is released into the public domain. <br />
<br />
{{MicroFormatPublicDomainContributionStatement}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Introduction ==<br />
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.<br />
<br />
{{rfc-2119-intro}}<br />
<br />
== Semantic XHTML Design Principles ==<br />
{{semantic-xhtml-design-principles}}<br />
<br />
== Format ==<br />
=== In General ===<br />
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.<br />
<br />
=== Schema ===<br />
The hNews schema consists of the following: <br />
<br />
* (root) ('''<code>root</code>''') and '''<code>hentry</code>'''. required. Using [[hAtom]].<br />
** '''<code>source-org</code>'''. required. Using [[hCard]].[*]<br />
** '''<code>dateline</code>'''. optional. Using text or [[hCard]].<br />
** '''<code>geo</code>'''. optional. Using [[geo]].[*]<br />
** '''<code>item-license</code>'''. recommended. Using a [[licensing-brainstorming#item_as_container license|brainstorm proposal]].<br />
** '''<code>principles</code>'''. recommended. Using the draft microformat. [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles].<br />
<br />
[*] Some required elements have defaults if missing, see below.<br />
<br />
=== Field and Element Details ===<br />
<br />
===== Source Organization =====<br />
* a Source Organization element is identified by the class name <code>source-org</code>.<br />
* Source Organization represents the originating organization for the news story.<br />
* a Source Organization {{must}} be encoded in an [[hCard]].<br />
* if the Source Organization is missing <br />
** find the [[algorithm-nearest-in-parent]] element(s) with class name <code>source-org</code> and that is/are a valid [[hCard]]<br />
** otherwise the entry is invalid hNews<br />
<br />
===== Dateline =====<br />
* a dateline element is identified by the class name <code>dateline</code>.<br />
* dateline represents the location where the news story was written or filed (see [http://en.wikipedia.org/wiki/Dateline dateline] for more details).<br />
* a dateline element {{may}} be encoded in an [[hCard]].<br />
* a news story {{should}} have a dateline element.<br />
* dateline sometimes also includes the publish date of the news story. In such cases, use the [[datetime-design-pattern]] to encode the date.<br />
<br />
===== Geo =====<br />
* a geo element is identified by the class name <code>geo</code><br />
* geo represents the geographic coordinates of relevant locations in the news story.<br />
* a geo element should be encoded in a [[geo]].<br />
* 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).<br />
<br />
===== License =====<br />
* a license element is identified by the class name <code>item-license</code>.<br />
* a license element {{must}} be encoded as described in this [http://microformats.org/wiki/licensing-brainstorming#item_as_container license brainstorm proposal].<br />
* a news story {{should}} include a license element.<br />
<br />
===== Principles =====<br />
* a principles element is identified by <code>rel-principles</code>.<br />
* principles represents the statement of principles and ethics used by the news organization that produced the news story.<br />
* a principles element {{must}} be encoded in [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles].<br />
* a news story {{should}} include principles.<br />
* principles {{should}} be linked to using the icons [[image:principles-button-blue.png]] or [[image:principles-book-blue.png]].<br />
<br />
=== XMDP Profile ===<br />
<pre><br />
<dl class="profile"><br />
<dt>class</dt><br />
<dd><p><br />
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class"><br />
HTML4 definition of the 'class' attribute.</a><br />
This meta data profile defines some 'class' attribute values (class names) <br />
and their meanings as suggested by a <br />
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile"><br />
draft of "Hypertext Links in HTML"</a>.<br />
<dl><br />
<br />
<dt>root</dt><br />
<dd><br />
Used to describe semantic information associated with news stories.<br />
</dd><br />
<br />
<dt>source-org</dt><br />
<dd><br />
The originating organization for the news story.<br />
</dd><br />
<br />
<dt>dateline</dt><br />
<dd><br />
Represents the location where the news story was filed.<br />
</dd><br />
<br />
<dt>geo</dt><br />
<dd><br />
Represents geographic coordinates of relevant locations in the story.<br />
</dd><br />
<br />
<dt>item-license</dt><br />
<dd><br />
Represents the license for the story.<br />
</dd><br />
<br />
<dt>principles</dt><br />
<dd><br />
Represents the statement of principles and ethics used by the news organization that produced the news story.<br />
</dd><br />
<br />
</dl><br />
</dd><br />
</dl><br />
</pre><br />
<br />
== Examples ==<br />
<br />
See [[hnews-examples]].<br />
<br />
=== Examples in the wild ===<br />
<br />
See [[hnews-examples-in-wild]].<br />
<br />
== Implementations ==<br />
<br />
== References ==<br />
<br />
=== Normative References ===<br />
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0]<br />
* [[hatom|hAtom]]<br />
* [[hcard|hCard]]<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [[rel-tag]]<br />
* [[geo]]<br />
* [[licensing-brainstorming#item_as_container_license|item-license brainstorm]]<br />
* [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles]<br />
* [http://www.ietf.org/rfc/rfc2119.txt RFC2119]<br />
* [http://www.ietf.org/rfc/rfc4287.txt RFC4287] (Atom 1.0)<br />
<br />
=== Informative References ===<br />
* Other news efforts: see [[news-formats]].<br />
<br />
== Work in progress ==<br />
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 hNews: <br />
<br />
* [[news-brainstorming|hNews Brainstorming]]<br />
<br />
=== Version 0.1 ===<br />
<br />
Version 0.1 was drafted August 2008.<br />
<br />
== Discussions ==<br />
<br />
* See [http://www.technorati.com/cosmos/referer.html blogs discussing this page].<br />
<br />
=== Q&A ===<br />
* If you have any questions about hNews, check the [[hnews-faq|hNews FAQ]], and if you don't find answers, add your questions!<br />
<br />
=== Issues ===<br />
* Please add any issues with the specification to the separate [[hnews-issues|hNews issues]] document.<br />
<br />
[[Category:Draft Specifications]]<br />
[[Category:hNews]]</div>JonathanMalekhttp://microformats.org/wiki/index.php?title=hnews-examples&diff=41032hnews-examples2009-10-12T18:40:14Z<p>JonathanMalek: *draft* examples</p>
<hr />
<div>Examples of [[hnews]] - '''Work in progress!'''<br />
<br />
= Contributors =<br />
* [[User:JonathanMalek|Jonathan Malek]] <br />
<br />
<br />
= Sample News Story = <br />
The following is a typically formatted news story:<br />
<br />
<div style="border: thin dashed black; padding: .5em 1em;"><br />
'''Renewing US ties with Latin America, Obama says he wants to lead, not lecture, on democracy'''<br />
<br />
by BEN FELLER, Associated Press - 19 April 2009 18:17 GMT <br />
<br />
PORT-OF-SPAIN, Trinidad (AP) -- Defending his brand of world politics, President Barack Obama said Sunday...<br />
<br />
Both Graham and McCaskill spoke on "Fox News Sunday." Ensign was interviewed on CNN's "State of the Union."<br />
<br />
Copyright 2009 The Associated Press. All rights reserved. This material may not be published, broadcast, rewritten or redistributed.<br />
</div><br />
<br />
Typically news organizations will have a significant amount of metadata behind this story, communicated in a variety of formats like [http://www.iptc.org/cms/site/ NewsML]. By the time they are presented to the reader, much of the metadata (amounting in some cases to hundreds of fields) has been stripped away. We can add a bit of that back in, and using hnews, create possibilities for some interesting semantic actions. Taking the above story, and formatting it as hnews:<br />
<br />
<pre><nowiki><br />
<div class="hnews hentry item"><br />
<h4><br />
<a class="url entry-title" href="http://example.org/article/us-latam-obama-democracy.html" rel="bookmark"><br />
Renewing US ties with Latin America, Obama says he wants to lead, not lecture, on democracy</a><br />
</h4><br />
<br />
<div><br />
<small> by <br />
<span class="author vcard"><a class="email fn" <br />
href="mailto:ben.feller@example.org">BEN FELLER</a></span>, <br />
<span class="source-org vcard"><a class="url org fn" <br />
href="http://www.ap.org">Associated Press</a></span>,<br />
<a href="http://www.ap.org/newsvalues/index.html" rel="principles"><img src="/wikidir/images/principles-button-blue.png" /></a> - <br />
<span class="updated dtstamp" <br />
title="2009-04-19T18:17:29Z">19 April 2009 18:17 GMT</span><br />
</small><br />
</div><br />
<br />
<div class="entry-content"><br />
<p><span class="dateline">PORT-OF-SPAIN, Trinidad</span> (AP) -- Defending his brand <br />
of world politics, President Barack Obama said Sunday...</p><br />
<p>Both Graham and McCaskill spoke on "Fox News Sunday." Ensign was interviewed on CNN's <br />
"State of the Union."</p><br />
</div><br />
<br />
<div><br />
<small><br />
News Topics:<br />
<a href="http://example.org/Summits" rel="tag">Summits</a>, ...,<br />
<a href="http://example.org/Government+policy" rel="tag">Government policy</a><br />
<br/><br />
People, Places and Companies: <br />
<a href="http://example.org/Barack+Obama" rel="tag">Barack Obama</a>, ..., <br />
<a href="http://example.org/Hugo+Chavez" rel="tag">Hugo Chavez</a> <br />
</small><br />
</div><br />
<br />
<br />
<div class="geo"><br />
<small><br />
Lat: <span class="latitude">10.65715</span> <br />
Long: <span class="longitude">-61.483582</span><br />
</small><br />
</div><br />
<br />
<div id="first-sample-license"><br />
<small><br />
Copyright 2009 The <a rel="item-license" href="#first-sample-license">Associated Press</a>. <br />
All rights reserved. This material may not be published, broadcast, rewritten or redistributed.<br />
</small><br />
</div><br />
</div><br />
</nowiki></pre><br />
<br />
We get a richly-formatted news story that enhances the reader's experience with news: <br />
<br />
<div style="border: thin dashed black; padding: .5em 1em;"><br />
<div class="hnews hentry item"><br />
<h4><br />
[http://example.org/article/us-latam-obama-democracy.html Renewing US ties with Latin America, Obama says he wants to lead, not lecture, on democracy]<br />
</h4><br />
<span><br />
<small> by [mailto:ben.feller@example.org BEN FELLER], <br />
[http://www.ap.org Associated Press]<br />
[http://www.ap.org/newsvalues/index.html principles] - <br />
<span class="updated dtstamp" <br />
title="2009-04-19T18:17:29Z">19 April 2009 18:17 GMT</span><br />
</small><br />
</span><br />
<br />
<span class="entry-content"><br />
<p><span class="dateline">PORT-OF-SPAIN, Trinidad</span> (AP) -- Defending his brand <br />
of world politics, President Barack Obama said Sunday...</p><br />
<p>Both Graham and McCaskill spoke on "Fox News Sunday." Ensign was interviewed on CNN's <br />
"State of the Union."</p><br />
</span><br />
<br />
<span><br />
<small><br />
News Topics:<br />
[http://example.org/Summits Summits], ...,<br />
[http://example.org/Government+policy Government policy]<br />
<br/><br />
People, Places and Companies: <br />
[http://example.org/Barack+Obama Barack Obama], ..., <br />
[http://example.org/Hugo+Chavez Hugo Chavez] <br />
</small><br />
</span><br />
<br/><br />
<span class="geo"><br />
<small><br />
Lat: <span class="latitude">10.65715</span> <br />
Long: <span class="longitude">-61.483582</span><br />
</small><br />
</span><br />
<br/><br />
<span><br />
<small><br />
Copyright 2009 The [http://www.ap.org Associated Press]. <br />
All rights reserved. This material may not be published, broadcast, rewritten or redistributed.<br />
</small><br />
</span><br />
</div><br />
</div></div>JonathanMalekhttp://microformats.org/wiki/index.php?title=hNews&diff=41030hNews2009-10-12T17:36:34Z<p>JonathanMalek: redirect for casing</p>
<hr />
<div>REDIRECT:[[hnews]]</div>JonathanMalekhttp://microformats.org/wiki/index.php?title=hnews&diff=41029hnews2009-10-12T17:22:15Z<p>JonathanMalek: Normative references</p>
<hr />
<div><entry-title>hNews 0.1</entry-title><br />
{{Template:DraftSpecification}}<br />
<br />
hNews is 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.<br />
__TOC__<br />
== Draft Specification ==<br />
<br />
;Editor/Author<br />
:[[:User:JonathanMalek|Jonathan Malek]] ([http://www.ap.org Associated Press])<br />
<br />
;Contributors<br />
:[[:User:Smyles|Stuart Myles]] ([http://www.ap.org Associated Press]) <br />
:[[:User:Martinjemoore|Martin Moore]] ([http://mediastandardstrust.org Media Standards Trust])<br />
:[[:User:MarkNg|Mark Ng]] ([http://mediastandardstrust.org Media Standards Trust])<br />
:[[:User:Tbmartinwiki|Todd B. Martin]] ([http://www.ap.org Associated Press])<br />
<br />
=== Copyright ===<br />
Per the public domain release on the authors' user pages ([[:User:JonathanMalek|Jonathan Malek]]) this specification is released into the public domain. <br />
<br />
{{MicroFormatPublicDomainContributionStatement}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Introduction ==<br />
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.<br />
<br />
{{rfc-2119-intro}}<br />
<br />
== Semantic XHTML Design Principles ==<br />
{{semantic-xhtml-design-principles}}<br />
<br />
== Format ==<br />
=== In General ===<br />
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.<br />
<br />
=== Schema ===<br />
The hNews schema consists of the following: <br />
<br />
* (root) ('''<code>root</code>''') and '''<code>hentry</code>'''. required. Using [[hAtom]].<br />
** '''<code>source-org</code>'''. required. Using [[hCard]].[*]<br />
** '''<code>dateline</code>'''. optional. Using text or [[hCard]].<br />
** '''<code>geo</code>'''. optional. Using [[geo]].[*]<br />
** '''<code>item-license</code>'''. recommended. Using a [[licensing-brainstorming#item_as_container license|brainstorm proposal]].<br />
** '''<code>principles</code>'''. recommended. Using the draft microformat. [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles].<br />
<br />
[*] Some required elements have defaults if missing, see below.<br />
<br />
=== Field and Element Details ===<br />
<br />
===== Source Organization =====<br />
* a Source Organization element is identified by the class name <code>source-org</code>.<br />
* Source Organization represents the originating organization for the news story.<br />
* a Source Organization {{must}} be encoded in an [[hCard]].<br />
* if the Source Organization is missing <br />
** find the [[algorithm-nearest-in-parent]] element(s) with class name <code>source-org</code> and that is/are a valid [[hCard]]<br />
** otherwise the entry is invalid hNews<br />
<br />
===== Dateline =====<br />
* a dateline element is identified by the class name <code>dateline</code>.<br />
* dateline represents the location where the news story was written or filed (see [http://en.wikipedia.org/wiki/Dateline dateline] for more details).<br />
* a dateline element {{may}} be encoded in an [[hCard]].<br />
* a news story {{should}} have a dateline element.<br />
* dateline sometimes also includes the publish date of the news story. In such cases, use the [[datetime-design-pattern]] to encode the date.<br />
<br />
===== Geo =====<br />
* a geo element is identified by the class name <code>geo</code><br />
* geo represents the geographic coordinates of relevant locations in the news story.<br />
* a geo element should be encoded in a [[geo]].<br />
* 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).<br />
<br />
===== License =====<br />
* a license element is identified by the class name <code>item-license</code>.<br />
* a license element {{must}} be encoded as described in this [http://microformats.org/wiki/licensing-brainstorming#item_as_container license brainstorm proposal].<br />
* a news story {{should}} include a license element.<br />
<br />
===== Principles =====<br />
* a principles element is identified by <code>rel-principles</code>.<br />
* principles represents the statement of principles and ethics used by the news organization that produced the news story.<br />
* a principles element {{must}} be encoded in [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles].<br />
* a news story {{should}} include principles.<br />
* principles {{should}} be linked to using the icons [[image:principles-button-blue.png]] or [[image:principles-book-blue.png]].<br />
<br />
=== XMDP Profile ===<br />
<pre><br />
<dl class="profile"><br />
<dt>class</dt><br />
<dd><p><br />
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class"><br />
HTML4 definition of the 'class' attribute.</a><br />
This meta data profile defines some 'class' attribute values (class names) <br />
and their meanings as suggested by a <br />
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile"><br />
draft of "Hypertext Links in HTML"</a>.<br />
<dl><br />
<br />
<dt>root</dt><br />
<dd><br />
Used to describe semantic information associated with news stories.<br />
</dd><br />
<br />
<dt>source-org</dt><br />
<dd><br />
The originating organization for the news story.<br />
</dd><br />
<br />
<dt>dateline</dt><br />
<dd><br />
Represents the location where the news story was filed.<br />
</dd><br />
<br />
<dt>geo</dt><br />
<dd><br />
Represents geographic coordinates of relevant locations in the story.<br />
</dd><br />
<br />
<dt>item-license</dt><br />
<dd><br />
Represents the license for the story.<br />
</dd><br />
<br />
<dt>principles</dt><br />
<dd><br />
Represents the statement of principles and ethics used by the news organization that produced the news story.<br />
</dd><br />
<br />
</dl><br />
</dd><br />
</dl><br />
</pre><br />
<br />
== Examples ==<br />
<br />
See [[hnews-examples]].<br />
<br />
=== Examples in the wild ===<br />
<br />
See [[hnews-examples-in-wild]].<br />
<br />
== Implementations ==<br />
<br />
== References ==<br />
<br />
=== Normative References ===<br />
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0]<br />
* [[hatom|hAtom]]<br />
* [[hcard|hCard]]<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [[rel-tag]]<br />
* [[geo]]<br />
* [[licensing-brainstorming#item_as_container_license|item-license brainstorm]]<br />
* [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles]<br />
* [http://www.ietf.org/rfc/rfc2119.txt RFC2119]<br />
* [http://www.ietf.org/rfc/rfc4287.txt RFC4287] (Atom 1.0)<br />
<br />
== Work in progress ==<br />
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 hNews: <br />
<br />
* [[news-brainstorming|hNews Brainstorming]]<br />
<br />
=== Version 0.1 ===<br />
<br />
Version 0.1 was drafted August 2008.<br />
<br />
== Discussions ==<br />
<br />
* See [http://www.technorati.com/cosmos/referer.html blogs discussing this page].<br />
<br />
=== Q&A ===<br />
* If you have any questions about hNews, check the [[hnews-faq|hNews FAQ]], and if you don't find answers, add your questions!<br />
<br />
=== Issues ===<br />
* Please add any issues with the specification to the separate [[hnews-issues|hNews issues]] document.<br />
<br />
[[Category:Draft Specifications]]<br />
[[Category:hNews]]</div>JonathanMalekhttp://microformats.org/wiki/index.php?title=hnews&diff=41028hnews2009-10-12T16:48:42Z<p>JonathanMalek: making item-license *should*, vs. *must*</p>
<hr />
<div><entry-title>hNews 0.1</entry-title><br />
{{Template:DraftSpecification}}<br />
<br />
hNews is 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.<br />
__TOC__<br />
== Draft Specification ==<br />
<br />
;Editor/Author<br />
:[[:User:JonathanMalek|Jonathan Malek]] ([http://www.ap.org Associated Press])<br />
<br />
;Contributors<br />
:[[:User:Smyles|Stuart Myles]] ([http://www.ap.org Associated Press]) <br />
:[[:User:Martinjemoore|Martin Moore]] ([http://mediastandardstrust.org Media Standards Trust])<br />
:[[:User:MarkNg|Mark Ng]] ([http://mediastandardstrust.org Media Standards Trust])<br />
:[[:User:Tbmartinwiki|Todd B. Martin]] ([http://www.ap.org Associated Press])<br />
<br />
=== Copyright ===<br />
Per the public domain release on the authors' user pages ([[:User:JonathanMalek|Jonathan Malek]]) this specification is released into the public domain. <br />
<br />
{{MicroFormatPublicDomainContributionStatement}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Introduction ==<br />
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.<br />
<br />
{{rfc-2119-intro}}<br />
<br />
== Semantic XHTML Design Principles ==<br />
{{semantic-xhtml-design-principles}}<br />
<br />
== Format ==<br />
=== In General ===<br />
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.<br />
<br />
=== Schema ===<br />
The hNews schema consists of the following: <br />
<br />
* (root) ('''<code>root</code>''') and '''<code>hentry</code>'''. required. Using [[hAtom]].<br />
** '''<code>source-org</code>'''. required. Using [[hCard]].[*]<br />
** '''<code>dateline</code>'''. optional. Using text or [[hCard]].<br />
** '''<code>geo</code>'''. optional. Using [[geo]].[*]<br />
** '''<code>item-license</code>'''. recommended. Using a [[licensing-brainstorming#item_as_container license|brainstorm proposal]].<br />
** '''<code>principles</code>'''. recommended. Using the draft microformat. [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles].<br />
<br />
[*] Some required elements have defaults if missing, see below.<br />
<br />
=== Field and Element Details ===<br />
<br />
===== Source Organization =====<br />
* a Source Organization element is identified by the class name <code>source-org</code>.<br />
* Source Organization represents the originating organization for the news story.<br />
* a Source Organization {{must}} be encoded in an [[hCard]].<br />
* if the Source Organization is missing <br />
** find the [[algorithm-nearest-in-parent]] element(s) with class name <code>source-org</code> and that is/are a valid [[hCard]]<br />
** otherwise the entry is invalid hNews<br />
<br />
===== Dateline =====<br />
* a dateline element is identified by the class name <code>dateline</code>.<br />
* dateline represents the location where the news story was written or filed (see [http://en.wikipedia.org/wiki/Dateline dateline] for more details).<br />
* a dateline element {{may}} be encoded in an [[hCard]].<br />
* a news story {{should}} have a dateline element.<br />
* dateline sometimes also includes the publish date of the news story. In such cases, use the [[datetime-design-pattern]] to encode the date.<br />
<br />
===== Geo =====<br />
* a geo element is identified by the class name <code>geo</code><br />
* geo represents the geographic coordinates of relevant locations in the news story.<br />
* a geo element should be encoded in a [[geo]].<br />
* 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).<br />
<br />
===== License =====<br />
* a license element is identified by the class name <code>item-license</code>.<br />
* a license element {{must}} be encoded as described in this [http://microformats.org/wiki/licensing-brainstorming#item_as_container license brainstorm proposal].<br />
* a news story {{should}} include a license element.<br />
<br />
===== Principles =====<br />
* a principles element is identified by <code>rel-principles</code>.<br />
* principles represents the statement of principles and ethics used by the news organization that produced the news story.<br />
* a principles element {{must}} be encoded in [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles].<br />
* a news story {{should}} include principles.<br />
* principles {{should}} be linked to using the icons [[image:principles-button-blue.png]] or [[image:principles-book-blue.png]].<br />
<br />
=== XMDP Profile ===<br />
<pre><br />
<dl class="profile"><br />
<dt>class</dt><br />
<dd><p><br />
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class"><br />
HTML4 definition of the 'class' attribute.</a><br />
This meta data profile defines some 'class' attribute values (class names) <br />
and their meanings as suggested by a <br />
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile"><br />
draft of "Hypertext Links in HTML"</a>.<br />
<dl><br />
<br />
<dt>root</dt><br />
<dd><br />
Used to describe semantic information associated with news stories.<br />
</dd><br />
<br />
<dt>source-org</dt><br />
<dd><br />
The originating organization for the news story.<br />
</dd><br />
<br />
<dt>dateline</dt><br />
<dd><br />
Represents the location where the news story was filed.<br />
</dd><br />
<br />
<dt>geo</dt><br />
<dd><br />
Represents geographic coordinates of relevant locations in the story.<br />
</dd><br />
<br />
<dt>item-license</dt><br />
<dd><br />
Represents the license for the story.<br />
</dd><br />
<br />
<dt>principles</dt><br />
<dd><br />
Represents the statement of principles and ethics used by the news organization that produced the news story.<br />
</dd><br />
<br />
</dl><br />
</dd><br />
</dl><br />
</pre><br />
<br />
== Examples ==<br />
<br />
See [[hnews-examples]].<br />
<br />
=== Examples in the wild ===<br />
<br />
See [[hnews-examples-in-wild]].<br />
<br />
== Implementations ==<br />
<br />
== References ==<br />
<br />
== Work in progress ==<br />
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 hNews: <br />
<br />
* [[news-brainstorming|hNews Brainstorming]]<br />
<br />
=== Version 0.1 ===<br />
<br />
Version 0.1 was drafted August 2008.<br />
<br />
== Discussions ==<br />
<br />
* See [http://www.technorati.com/cosmos/referer.html blogs discussing this page].<br />
<br />
=== Q&A ===<br />
* If you have any questions about hNews, check the [[hnews-faq|hNews FAQ]], and if you don't find answers, add your questions!<br />
<br />
=== Issues ===<br />
* Please add any issues with the specification to the separate [[hnews-issues|hNews issues]] document.<br />
<br />
[[Category:Draft Specifications]]<br />
[[Category:hNews]]</div>JonathanMalekhttp://microformats.org/wiki/index.php?title=hnews&diff=41025hnews2009-10-12T16:42:40Z<p>JonathanMalek: changing external to internal link</p>
<hr />
<div><entry-title>hNews 0.1</entry-title><br />
{{Template:DraftSpecification}}<br />
<br />
hNews is 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.<br />
__TOC__<br />
== Draft Specification ==<br />
<br />
;Editor/Author<br />
:[[:User:JonathanMalek|Jonathan Malek]] ([http://www.ap.org Associated Press])<br />
<br />
;Contributors<br />
:[[:User:Smyles|Stuart Myles]] ([http://www.ap.org Associated Press]) <br />
:[[:User:Martinjemoore|Martin Moore]] ([http://mediastandardstrust.org Media Standards Trust])<br />
:[[:User:MarkNg|Mark Ng]] ([http://mediastandardstrust.org Media Standards Trust])<br />
:[[:User:Tbmartinwiki|Todd B. Martin]] ([http://www.ap.org Associated Press])<br />
<br />
=== Copyright ===<br />
Per the public domain release on the authors' user pages ([[:User:JonathanMalek|Jonathan Malek]]) this specification is released into the public domain. <br />
<br />
{{MicroFormatPublicDomainContributionStatement}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Introduction ==<br />
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.<br />
<br />
{{rfc-2119-intro}}<br />
<br />
== Semantic XHTML Design Principles ==<br />
{{semantic-xhtml-design-principles}}<br />
<br />
== Format ==<br />
=== In General ===<br />
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.<br />
<br />
=== Schema ===<br />
The hNews schema consists of the following: <br />
<br />
* (root) ('''<code>root</code>''') and '''<code>hentry</code>'''. required. Using [[hAtom]].<br />
** '''<code>source-org</code>'''. required. Using [[hCard]].[*]<br />
** '''<code>dateline</code>'''. optional. Using text or [[hCard]].<br />
** '''<code>geo</code>'''. optional. Using [[geo]].[*]<br />
** '''<code>item-license</code>'''. required. Using a [[licensing-brainstorming#item_as_container license|brainstorm proposal]].<br />
** '''<code>principles</code>'''. recommended. Using the draft microformat. [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles].<br />
<br />
[*] Some required elements have defaults if missing, see below.<br />
<br />
=== Field and Element Details ===<br />
<br />
===== Source Organization =====<br />
* a Source Organization element is identified by the class name <code>source-org</code>.<br />
* Source Organization represents the originating organization for the news story.<br />
* a Source Organization {{must}} be encoded in an [[hCard]].<br />
* if the Source Organization is missing <br />
** find the [[algorithm-nearest-in-parent]] element(s) with class name <code>source-org</code> and that is/are a valid [[hCard]]<br />
** otherwise the entry is invalid hNews<br />
<br />
===== Dateline =====<br />
* a dateline element is identified by the class name <code>dateline</code>.<br />
* dateline represents the location where the news story was written or filed (see [http://en.wikipedia.org/wiki/Dateline dateline] for more details).<br />
* a dateline element {{may}} be encoded in an [[hCard]].<br />
* a news story {{should}} have a dateline element.<br />
* dateline sometimes also includes the publish date of the news story. In such cases, use the [[datetime-design-pattern]] to encode the date.<br />
<br />
===== Geo =====<br />
* a geo element is identified by the class name <code>geo</code><br />
* geo represents the geographic coordinates of relevant locations in the news story.<br />
* a geo element should be encoded in a [[geo]].<br />
* 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).<br />
<br />
===== License =====<br />
* a license element is identified by the class name <code>item-license</code>.<br />
* a license element {{must}} be encoded as described in this [http://microformats.org/wiki/licensing-brainstorming#item_as_container license brainstorm proposal].<br />
<br />
===== Principles =====<br />
* a principles element is identified by <code>rel-principles</code>.<br />
* principles represents the statement of principles and ethics used by the news organization that produced the news story.<br />
* a principles element {{must}} be encoded in [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles].<br />
* a news story {{should}} include principles.<br />
* principles {{should}} be linked to using the icons [[image:principles-button-blue.png]] or [[image:principles-book-blue.png]].<br />
<br />
=== XMDP Profile ===<br />
<pre><br />
<dl class="profile"><br />
<dt>class</dt><br />
<dd><p><br />
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class"><br />
HTML4 definition of the 'class' attribute.</a><br />
This meta data profile defines some 'class' attribute values (class names) <br />
and their meanings as suggested by a <br />
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile"><br />
draft of "Hypertext Links in HTML"</a>.<br />
<dl><br />
<br />
<dt>root</dt><br />
<dd><br />
Used to describe semantic information associated with news stories.<br />
</dd><br />
<br />
<dt>source-org</dt><br />
<dd><br />
The originating organization for the news story.<br />
</dd><br />
<br />
<dt>dateline</dt><br />
<dd><br />
Represents the location where the news story was filed.<br />
</dd><br />
<br />
<dt>geo</dt><br />
<dd><br />
Represents geographic coordinates of relevant locations in the story.<br />
</dd><br />
<br />
<dt>item-license</dt><br />
<dd><br />
Represents the license for the story.<br />
</dd><br />
<br />
<dt>principles</dt><br />
<dd><br />
Represents the statement of principles and ethics used by the news organization that produced the news story.<br />
</dd><br />
<br />
</dl><br />
</dd><br />
</dl><br />
</pre><br />
<br />
== Examples ==<br />
<br />
See [[hnews-examples]].<br />
<br />
=== Examples in the wild ===<br />
<br />
See [[hnews-examples-in-wild]].<br />
<br />
== Implementations ==<br />
<br />
== References ==<br />
<br />
== Work in progress ==<br />
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 hNews: <br />
<br />
* [[news-brainstorming|hNews Brainstorming]]<br />
<br />
=== Version 0.1 ===<br />
<br />
Version 0.1 was drafted August 2008.<br />
<br />
== Discussions ==<br />
<br />
* See [http://www.technorati.com/cosmos/referer.html blogs discussing this page].<br />
<br />
=== Q&A ===<br />
* If you have any questions about hNews, check the [[hnews-faq|hNews FAQ]], and if you don't find answers, add your questions!<br />
<br />
=== Issues ===<br />
* Please add any issues with the specification to the separate [[hnews-issues|hNews issues]] document.<br />
<br />
[[Category:Draft Specifications]]<br />
[[Category:hNews]]</div>JonathanMalekhttp://microformats.org/wiki/index.php?title=hnews&diff=41024hnews2009-10-12T16:38:47Z<p>JonathanMalek: fixing link for Martin's page.</p>
<hr />
<div><entry-title>hNews 0.1</entry-title><br />
{{Template:DraftSpecification}}<br />
<br />
hNews is 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.<br />
__TOC__<br />
== Draft Specification ==<br />
<br />
;Editor/Author<br />
:[[:User:JonathanMalek|Jonathan Malek]] ([http://www.ap.org Associated Press])<br />
<br />
;Contributors<br />
:[[:User:Smyles|Stuart Myles]] ([http://www.ap.org Associated Press]) <br />
:[[:User:Martinjemoore|Martin Moore]] ([http://mediastandardstrust.org Media Standards Trust])<br />
:[[:User:MarkNg|Mark Ng]] ([http://mediastandardstrust.org Media Standards Trust])<br />
:[[:User:Tbmartinwiki|Todd B. Martin]] ([http://www.ap.org Associated Press])<br />
<br />
=== Copyright ===<br />
Per the public domain release on the authors' user pages ([[:User:JonathanMalek|Jonathan Malek]]) this specification is released into the public domain. <br />
<br />
{{MicroFormatPublicDomainContributionStatement}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Introduction ==<br />
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.<br />
<br />
{{rfc-2119-intro}}<br />
<br />
== Semantic XHTML Design Principles ==<br />
{{semantic-xhtml-design-principles}}<br />
<br />
== Format ==<br />
=== In General ===<br />
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.<br />
<br />
=== Schema ===<br />
The hNews schema consists of the following: <br />
<br />
* (root) ('''<code>root</code>''') and '''<code>hentry</code>'''. required. Using [[hAtom]].<br />
** '''<code>source-org</code>'''. required. Using [[hCard]].[*]<br />
** '''<code>dateline</code>'''. optional. Using text or [[hCard]].<br />
** '''<code>geo</code>'''. optional. Using [[geo]].[*]<br />
** '''<code>item-license</code>'''. required. Using a [http://microformats.org/wiki/licensing-brainstorming#item_as_container license brainstorm proposal].<br />
** '''<code>principles</code>'''. recommended. Using the draft microformat. [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles].<br />
<br />
[*] Some required elements have defaults if missing, see below.<br />
<br />
=== Field and Element Details ===<br />
<br />
===== Source Organization =====<br />
* a Source Organization element is identified by the class name <code>source-org</code>.<br />
* Source Organization represents the originating organization for the news story.<br />
* a Source Organization {{must}} be encoded in an [[hCard]].<br />
* if the Source Organization is missing <br />
** find the [[algorithm-nearest-in-parent]] element(s) with class name <code>source-org</code> and that is/are a valid [[hCard]]<br />
** otherwise the entry is invalid hNews<br />
<br />
===== Dateline =====<br />
* a dateline element is identified by the class name <code>dateline</code>.<br />
* dateline represents the location where the news story was written or filed (see [http://en.wikipedia.org/wiki/Dateline dateline] for more details).<br />
* a dateline element {{may}} be encoded in an [[hCard]].<br />
* a news story {{should}} have a dateline element.<br />
* dateline sometimes also includes the publish date of the news story. In such cases, use the [[datetime-design-pattern]] to encode the date.<br />
<br />
===== Geo =====<br />
* a geo element is identified by the class name <code>geo</code><br />
* geo represents the geographic coordinates of relevant locations in the news story.<br />
* a geo element should be encoded in a [[geo]].<br />
* 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).<br />
<br />
===== License =====<br />
* a license element is identified by the class name <code>item-license</code>.<br />
* a license element {{must}} be encoded as described in this [http://microformats.org/wiki/licensing-brainstorming#item_as_container license brainstorm proposal].<br />
<br />
===== Principles =====<br />
* a principles element is identified by <code>rel-principles</code>.<br />
* principles represents the statement of principles and ethics used by the news organization that produced the news story.<br />
* a principles element {{must}} be encoded in [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles].<br />
* a news story {{should}} include principles.<br />
* principles {{should}} be linked to using the icons [[image:principles-button-blue.png]] or [[image:principles-book-blue.png]].<br />
<br />
=== XMDP Profile ===<br />
<pre><br />
<dl class="profile"><br />
<dt>class</dt><br />
<dd><p><br />
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class"><br />
HTML4 definition of the 'class' attribute.</a><br />
This meta data profile defines some 'class' attribute values (class names) <br />
and their meanings as suggested by a <br />
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile"><br />
draft of "Hypertext Links in HTML"</a>.<br />
<dl><br />
<br />
<dt>root</dt><br />
<dd><br />
Used to describe semantic information associated with news stories.<br />
</dd><br />
<br />
<dt>source-org</dt><br />
<dd><br />
The originating organization for the news story.<br />
</dd><br />
<br />
<dt>dateline</dt><br />
<dd><br />
Represents the location where the news story was filed.<br />
</dd><br />
<br />
<dt>geo</dt><br />
<dd><br />
Represents geographic coordinates of relevant locations in the story.<br />
</dd><br />
<br />
<dt>item-license</dt><br />
<dd><br />
Represents the license for the story.<br />
</dd><br />
<br />
<dt>principles</dt><br />
<dd><br />
Represents the statement of principles and ethics used by the news organization that produced the news story.<br />
</dd><br />
<br />
</dl><br />
</dd><br />
</dl><br />
</pre><br />
<br />
== Examples ==<br />
<br />
See [[hnews-examples]].<br />
<br />
=== Examples in the wild ===<br />
<br />
See [[hnews-examples-in-wild]].<br />
<br />
== Implementations ==<br />
<br />
== References ==<br />
<br />
== Work in progress ==<br />
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 hNews: <br />
<br />
* [[news-brainstorming|hNews Brainstorming]]<br />
<br />
=== Version 0.1 ===<br />
<br />
Version 0.1 was drafted August 2008.<br />
<br />
== Discussions ==<br />
<br />
* See [http://www.technorati.com/cosmos/referer.html blogs discussing this page].<br />
<br />
=== Q&A ===<br />
* If you have any questions about hNews, check the [[hnews-faq|hNews FAQ]], and if you don't find answers, add your questions!<br />
<br />
=== Issues ===<br />
* Please add any issues with the specification to the separate [[hnews-issues|hNews issues]] document.<br />
<br />
[[Category:Draft Specifications]]<br />
[[Category:hNews]]</div>JonathanMalekhttp://microformats.org/wiki/index.php?title=hnews&diff=41023hnews2009-10-12T16:37:39Z<p>JonathanMalek: fixing link to brainstorming.</p>
<hr />
<div><entry-title>hNews 0.1</entry-title><br />
{{Template:DraftSpecification}}<br />
<br />
hNews is 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.<br />
__TOC__<br />
== Draft Specification ==<br />
<br />
;Editor/Author<br />
:[[:User:JonathanMalek|Jonathan Malek]] ([http://www.ap.org Associated Press])<br />
<br />
;Contributors<br />
:[[:User:Smyles|Stuart Myles]] ([http://www.ap.org Associated Press]) <br />
:[[:User:martinjemoore|Martin Moore]] ([http://mediastandardstrust.org Media Standards Trust])<br />
:[[:User:MarkNg|Mark Ng]] ([http://mediastandardstrust.org Media Standards Trust])<br />
:[[:User:Tbmartinwiki|Todd B. Martin]] ([http://www.ap.org Associated Press])<br />
<br />
=== Copyright ===<br />
Per the public domain release on the authors' user pages ([[:User:JonathanMalek|Jonathan Malek]]) this specification is released into the public domain. <br />
<br />
{{MicroFormatPublicDomainContributionStatement}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Introduction ==<br />
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.<br />
<br />
{{rfc-2119-intro}}<br />
<br />
== Semantic XHTML Design Principles ==<br />
{{semantic-xhtml-design-principles}}<br />
<br />
== Format ==<br />
=== In General ===<br />
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.<br />
<br />
=== Schema ===<br />
The hNews schema consists of the following: <br />
<br />
* (root) ('''<code>root</code>''') and '''<code>hentry</code>'''. required. Using [[hAtom]].<br />
** '''<code>source-org</code>'''. required. Using [[hCard]].[*]<br />
** '''<code>dateline</code>'''. optional. Using text or [[hCard]].<br />
** '''<code>geo</code>'''. optional. Using [[geo]].[*]<br />
** '''<code>item-license</code>'''. required. Using a [http://microformats.org/wiki/licensing-brainstorming#item_as_container license brainstorm proposal].<br />
** '''<code>principles</code>'''. recommended. Using the draft microformat. [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles].<br />
<br />
[*] Some required elements have defaults if missing, see below.<br />
<br />
=== Field and Element Details ===<br />
<br />
===== Source Organization =====<br />
* a Source Organization element is identified by the class name <code>source-org</code>.<br />
* Source Organization represents the originating organization for the news story.<br />
* a Source Organization {{must}} be encoded in an [[hCard]].<br />
* if the Source Organization is missing <br />
** find the [[algorithm-nearest-in-parent]] element(s) with class name <code>source-org</code> and that is/are a valid [[hCard]]<br />
** otherwise the entry is invalid hNews<br />
<br />
===== Dateline =====<br />
* a dateline element is identified by the class name <code>dateline</code>.<br />
* dateline represents the location where the news story was written or filed (see [http://en.wikipedia.org/wiki/Dateline dateline] for more details).<br />
* a dateline element {{may}} be encoded in an [[hCard]].<br />
* a news story {{should}} have a dateline element.<br />
* dateline sometimes also includes the publish date of the news story. In such cases, use the [[datetime-design-pattern]] to encode the date.<br />
<br />
===== Geo =====<br />
* a geo element is identified by the class name <code>geo</code><br />
* geo represents the geographic coordinates of relevant locations in the news story.<br />
* a geo element should be encoded in a [[geo]].<br />
* 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).<br />
<br />
===== License =====<br />
* a license element is identified by the class name <code>item-license</code>.<br />
* a license element {{must}} be encoded as described in this [http://microformats.org/wiki/licensing-brainstorming#item_as_container license brainstorm proposal].<br />
<br />
===== Principles =====<br />
* a principles element is identified by <code>rel-principles</code>.<br />
* principles represents the statement of principles and ethics used by the news organization that produced the news story.<br />
* a principles element {{must}} be encoded in [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles].<br />
* a news story {{should}} include principles.<br />
* principles {{should}} be linked to using the icons [[image:principles-button-blue.png]] or [[image:principles-book-blue.png]].<br />
<br />
=== XMDP Profile ===<br />
<pre><br />
<dl class="profile"><br />
<dt>class</dt><br />
<dd><p><br />
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class"><br />
HTML4 definition of the 'class' attribute.</a><br />
This meta data profile defines some 'class' attribute values (class names) <br />
and their meanings as suggested by a <br />
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile"><br />
draft of "Hypertext Links in HTML"</a>.<br />
<dl><br />
<br />
<dt>root</dt><br />
<dd><br />
Used to describe semantic information associated with news stories.<br />
</dd><br />
<br />
<dt>source-org</dt><br />
<dd><br />
The originating organization for the news story.<br />
</dd><br />
<br />
<dt>dateline</dt><br />
<dd><br />
Represents the location where the news story was filed.<br />
</dd><br />
<br />
<dt>geo</dt><br />
<dd><br />
Represents geographic coordinates of relevant locations in the story.<br />
</dd><br />
<br />
<dt>item-license</dt><br />
<dd><br />
Represents the license for the story.<br />
</dd><br />
<br />
<dt>principles</dt><br />
<dd><br />
Represents the statement of principles and ethics used by the news organization that produced the news story.<br />
</dd><br />
<br />
</dl><br />
</dd><br />
</dl><br />
</pre><br />
<br />
== Examples ==<br />
<br />
See [[hnews-examples]].<br />
<br />
=== Examples in the wild ===<br />
<br />
See [[hnews-examples-in-wild]].<br />
<br />
== Implementations ==<br />
<br />
== References ==<br />
<br />
== Work in progress ==<br />
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 hNews: <br />
<br />
* [[news-brainstorming|hNews Brainstorming]]<br />
<br />
=== Version 0.1 ===<br />
<br />
Version 0.1 was drafted August 2008.<br />
<br />
== Discussions ==<br />
<br />
* See [http://www.technorati.com/cosmos/referer.html blogs discussing this page].<br />
<br />
=== Q&A ===<br />
* If you have any questions about hNews, check the [[hnews-faq|hNews FAQ]], and if you don't find answers, add your questions!<br />
<br />
=== Issues ===<br />
* Please add any issues with the specification to the separate [[hnews-issues|hNews issues]] document.<br />
<br />
[[Category:Draft Specifications]]<br />
[[Category:hNews]]</div>JonathanMalekhttp://microformats.org/wiki/index.php?title=hnews&diff=41020hnews2009-10-12T16:36:34Z<p>JonathanMalek: fixing link for Todd's page.</p>
<hr />
<div><entry-title>hNews 0.1</entry-title><br />
{{Template:DraftSpecification}}<br />
<br />
hNews is 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.<br />
__TOC__<br />
== Draft Specification ==<br />
<br />
;Editor/Author<br />
:[[:User:JonathanMalek|Jonathan Malek]] ([http://www.ap.org Associated Press])<br />
<br />
;Contributors<br />
:[[:User:Smyles|Stuart Myles]] ([http://www.ap.org Associated Press]) <br />
:[[:User:martinjemoore|Martin Moore]] ([http://mediastandardstrust.org Media Standards Trust])<br />
:[[:User:MarkNg|Mark Ng]] ([http://mediastandardstrust.org Media Standards Trust])<br />
:[[:User:Tbmartinwiki|Todd B. Martin]] ([http://www.ap.org Associated Press])<br />
<br />
=== Copyright ===<br />
Per the public domain release on the authors' user pages ([[:User:JonathanMalek|Jonathan Malek]]) this specification is released into the public domain. <br />
<br />
{{MicroFormatPublicDomainContributionStatement}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Introduction ==<br />
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.<br />
<br />
{{rfc-2119-intro}}<br />
<br />
== Semantic XHTML Design Principles ==<br />
{{semantic-xhtml-design-principles}}<br />
<br />
== Format ==<br />
=== In General ===<br />
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.<br />
<br />
=== Schema ===<br />
The hNews schema consists of the following: <br />
<br />
* (root) ('''<code>root</code>''') and '''<code>hentry</code>'''. required. Using [[hAtom]].<br />
** '''<code>source-org</code>'''. required. Using [[hCard]].[*]<br />
** '''<code>dateline</code>'''. optional. Using text or [[hCard]].<br />
** '''<code>geo</code>'''. optional. Using [[geo]].[*]<br />
** '''<code>item-license</code>'''. required. Using a [http://microformats.org/wiki/licensing-brainstorming#item_as_container license brainstorm proposal].<br />
** '''<code>principles</code>'''. recommended. Using the draft microformat. [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles].<br />
<br />
[*] Some required elements have defaults if missing, see below.<br />
<br />
=== Field and Element Details ===<br />
<br />
===== Source Organization =====<br />
* a Source Organization element is identified by the class name <code>source-org</code>.<br />
* Source Organization represents the originating organization for the news story.<br />
* a Source Organization {{must}} be encoded in an [[hCard]].<br />
* if the Source Organization is missing <br />
** find the [[algorithm-nearest-in-parent]] element(s) with class name <code>source-org</code> and that is/are a valid [[hCard]]<br />
** otherwise the entry is invalid hNews<br />
<br />
===== Dateline =====<br />
* a dateline element is identified by the class name <code>dateline</code>.<br />
* dateline represents the location where the news story was written or filed (see [http://en.wikipedia.org/wiki/Dateline dateline] for more details).<br />
* a dateline element {{may}} be encoded in an [[hCard]].<br />
* a news story {{should}} have a dateline element.<br />
* dateline sometimes also includes the publish date of the news story. In such cases, use the [[datetime-design-pattern]] to encode the date.<br />
<br />
===== Geo =====<br />
* a geo element is identified by the class name <code>geo</code><br />
* geo represents the geographic coordinates of relevant locations in the news story.<br />
* a geo element should be encoded in a [[geo]].<br />
* 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).<br />
<br />
===== License =====<br />
* a license element is identified by the class name <code>item-license</code>.<br />
* a license element {{must}} be encoded as described in this [http://microformats.org/wiki/licensing-brainstorming#item_as_container license brainstorm proposal].<br />
<br />
===== Principles =====<br />
* a principles element is identified by <code>rel-principles</code>.<br />
* principles represents the statement of principles and ethics used by the news organization that produced the news story.<br />
* a principles element {{must}} be encoded in [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles].<br />
* a news story {{should}} include principles.<br />
* principles {{should}} be linked to using the icons [[image:principles-button-blue.png]] or [[image:principles-book-blue.png]].<br />
<br />
=== XMDP Profile ===<br />
<pre><br />
<dl class="profile"><br />
<dt>class</dt><br />
<dd><p><br />
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class"><br />
HTML4 definition of the 'class' attribute.</a><br />
This meta data profile defines some 'class' attribute values (class names) <br />
and their meanings as suggested by a <br />
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile"><br />
draft of "Hypertext Links in HTML"</a>.<br />
<dl><br />
<br />
<dt>root</dt><br />
<dd><br />
Used to describe semantic information associated with news stories.<br />
</dd><br />
<br />
<dt>source-org</dt><br />
<dd><br />
The originating organization for the news story.<br />
</dd><br />
<br />
<dt>dateline</dt><br />
<dd><br />
Represents the location where the news story was filed.<br />
</dd><br />
<br />
<dt>geo</dt><br />
<dd><br />
Represents geographic coordinates of relevant locations in the story.<br />
</dd><br />
<br />
<dt>item-license</dt><br />
<dd><br />
Represents the license for the story.<br />
</dd><br />
<br />
<dt>principles</dt><br />
<dd><br />
Represents the statement of principles and ethics used by the news organization that produced the news story.<br />
</dd><br />
<br />
</dl><br />
</dd><br />
</dl><br />
</pre><br />
<br />
== Examples ==<br />
<br />
See [[hnews-examples]].<br />
<br />
=== Examples in the wild ===<br />
<br />
See [[hnews-examples-in-wild]].<br />
<br />
== Implementations ==<br />
<br />
== References ==<br />
<br />
== Work in progress ==<br />
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 hNews: <br />
<br />
* [[hnews-brainstorming|hNews Brainstorming]]<br />
<br />
=== Version 0.1 ===<br />
<br />
Version 0.1 was drafted August 2008.<br />
<br />
== Discussions ==<br />
<br />
* See [http://www.technorati.com/cosmos/referer.html blogs discussing this page].<br />
<br />
=== Q&A ===<br />
* If you have any questions about hNews, check the [[hnews-faq|hNews FAQ]], and if you don't find answers, add your questions!<br />
<br />
=== Issues ===<br />
* Please add any issues with the specification to the separate [[hnews-issues|hNews issues]] document.<br />
<br />
[[Category:Draft Specifications]]<br />
[[Category:hNews]]</div>JonathanMalekhttp://microformats.org/wiki/index.php?title=news-brainstorming&diff=41019news-brainstorming2009-10-12T16:25:56Z<p>JonathanMalek: Response to third class name "item" in news.</p>
<hr />
<div>= News Brainstorming =<br />
<br />
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.<br />
<br />
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]]. - [[User:JonathanMalek|Jonathan Malek]] <br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* Jonathan Malek<br />
* Stuart Myles<br />
* Martin Moore<br />
* Mark Ng<br />
* Todd Martin<br />
<br />
== See Also ==<br />
<br />
* [[news-examples]]<br />
* [[news-formats]]<br />
<br />
== The Problem ==<br />
<br />
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 ''[http://www.wired.com/threatlevel/2008/09/six-year-old-st/ Wired.com], 2008'').<br />
<br />
== Thoughts on a Microformat for News ==<br />
<br />
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 [http://www.atomenabled.org/ 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]].<br />
<br />
In much the same way that one extends [http://www.atomenabled.org/ Atom], we are looking to extend [[hAtom]] with the most vital news-specific fields.<br />
<br />
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'''.<br />
<br />
=== Common News Fields ===<br />
<br />
* [[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.<br />
* '''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.<br />
* '''dateline''': using text or [[hCard]], not to be confused with date (see [http://en.wikipedia.org/wiki/Dateline dateline] for more information).<br />
* '''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.<br />
* '''item-license''': to express licensing around the item<br />
* '''principles''': using the draft format [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles]<br />
<br />
== Issues ==<br />
<br />
<br />
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.<br />
<br />
See also [[hatom-issues|hAtom Issues]] for questions about [[hAtom]].<br />
<br />
=== Issues Template ===<br />
<br />
{{issues-format}}<br />
<br />
=== Open Issues ===<br />
<div class="hentry"><br />
{{OpenIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-09</span> raised by <span class="fn">Miles De Feyter</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Implementation of item-license as it relates to hNews</strong>. Reading through the item-license brainstorm it seems to indicate that "item-license" would need to be nested within something with the class of "item". So as this relates to hNews is the suggestion to then have an articles containing div have the three class names of "hnews hentry item"?<br />
** At this point, Miles, that is correct (following the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] concept and guidance). I expect we'll see changes around item-license (it's still just brainstorming), but for the time being, the third class name "item" is needed. --[[User:JonathanMalek|JonathanMalek]] 16:25, 12 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
=== Closed Issues ===<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">2009-09-28</span> raised by <span class="fn">[[User:MilesD|Miles De Feyter]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Principles as a requirement</strong>. Working for a publishing company that owns and operates a large number of different organizations I'd love to incorporate hNews within our publishing system. The hNews requirement for a principles statement could pose a problem though or at least make rolling out hNews a more involved process then it would be otherwise. The issue is, I would now have to go to each product owner and ask then to provide this principles statement to link to. So my concern is now rather then just making a change to the publishing system to support hNews there is this requirement for some supporting content. And due to the nature of the content I can only assume our legal dep. would need to sign off as well, further complicating the adoption of hNews.<br />
** +1 I agree that the "principles" property (and probably all other others) should be optional. [[User:Tantek|Tantek]] 18:29, 29 September 2009 (UTC)<br />
*** I think it's important to explain why principles is a requirement. hnews is essentially a specialization of hAtom. Its purpose is to distinguish news on the web. Hence the description of source organisation, license and principles. Of these, principles is the only one which consistently distinguishes news on the web from other content (eg. commercial, government). In the future it should be distinguished further by making the principles themselves machine readable (but that is for a later date). Most professional news organisations adhere to a Statement of Principles (e.g. see http://en.wikipedia.org/wiki/Journalism_ethics_and_standards and http://www.journalism.org/resources/ethics_codes). If a site wants to mark up its content but does not want to distinguish it as news, then wouldn't it be easiest to use hAtom? [[User:martinjemoore|Martin Moore]] 9:00, 20 September 2009 (UTC)<br />
*** Having discussed this issue at length outside this brainstorming, we understand some of the concerns of the microformat community regarding 'must', but are still convinced of the criticality of principles to hNews - therefore recommend downgrading from 'must' to 'should'. [[User:martinjemoore|Martin Moore]] 14:00, 7 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">hCalendar instead of dateline?</strong> Would an [[hCalendar]] event (which can contain an hCard location) make sense for a dateline, or is the 'date' part more often omitted?<br />
** Confusingly, the journalistic term "dateline" isn't anything to do with a date or time. It is the location from which a report is filed and is generally the main location associated with a story. Generally, a dateline consists of a city (e.g. "Rome") but could be the name of a ship at sea or even a space station. [[User:Stuart Myles|Stuart Myles]] 21:12, 24 August 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">hCard instead of geo?</strong> Is geo really in use here, or would using an hCard (that can contain geo) be a better way of representing locations referred to in the story, as more human readable?<br />
** The reason for geo being highlighted (as an optional field) is to promote at least one location identifier in the story--preferably the most appropriate single location on a map for that particular story. Geo does not have to be related to dateline, but in some [http://labs.ap.org/wiki/hNews examples] we've worked on, we show the two collapsed into a single field. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)<br />
** For locations referred to in the story, I agree--publishers should be using [[hCard]] with the contained geo to markup the locations themselves. One of the concepts I've struggled with is drawing an admittedly arbitrary line between the metadata ''about'' a story from the metadata ''within'' a story. For the former, we've focused on simplicity and minimalism, primarily as a means to encourage adoption. That has meant preferring [[rel-tag]] over in-line entity extraction and markup using compound microformats. For the latter, we feel that the field is open: use whatever microformat fits your purpose, however you can--the more, the better. This lets publishers with minimal technology capabilities at least get started by tweaking a few templates in their CMS, while those more technically inclined aren't limited by the simplicity of the format to a paucity of data. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)<br />
** Also, dateline can be text or [[hCard]], as noted in the [[news-brainstorming#Common_News_Fields|Common News Fields]] section. --[[User:JonathanMalek|JonathanMalek]] 18:17, 24 September 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">What is item-license?</strong> Using [[rel-license]] presumably?<br />
** We're working off the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] discussions for this. Our concern with [[rel-license]] was its definition as applying to an entire page, rather than an item within a page. The current discussions around licensing definitely address that. --[[User:JonathanMalek|JonathanMalek]] 00:02, 25 August 2009 (UTC)<br />
*** +1 using item-license for news-brainstorming makes sense. [[User:Tantek|Tantek]] 22:32, 27 August 2009 (UTC)<br />
</div><br />
</div><br />
<br />
== Naming ==<br />
<br />
Here are candidate names for a news microformat:<br />
<br />
* hNews<br />
<br />
= Proposal = <br />
See the [[hnews]] draft.</div>JonathanMalekhttp://microformats.org/wiki/index.php?title=news-brainstorming&diff=41018news-brainstorming2009-10-12T15:50:23Z<p>JonathanMalek: /* Issues */ cleaner description on hAtom</p>
<hr />
<div>= News Brainstorming =<br />
<br />
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.<br />
<br />
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]]. - [[User:JonathanMalek|Jonathan Malek]] <br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* Jonathan Malek<br />
* Stuart Myles<br />
* Martin Moore<br />
* Mark Ng<br />
* Todd Martin<br />
<br />
== See Also ==<br />
<br />
* [[news-examples]]<br />
* [[news-formats]]<br />
<br />
== The Problem ==<br />
<br />
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 ''[http://www.wired.com/threatlevel/2008/09/six-year-old-st/ Wired.com], 2008'').<br />
<br />
== Thoughts on a Microformat for News ==<br />
<br />
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 [http://www.atomenabled.org/ 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]].<br />
<br />
In much the same way that one extends [http://www.atomenabled.org/ Atom], we are looking to extend [[hAtom]] with the most vital news-specific fields.<br />
<br />
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'''.<br />
<br />
=== Common News Fields ===<br />
<br />
* [[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.<br />
* '''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.<br />
* '''dateline''': using text or [[hCard]], not to be confused with date (see [http://en.wikipedia.org/wiki/Dateline dateline] for more information).<br />
* '''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.<br />
* '''item-license''': to express licensing around the item<br />
* '''principles''': using the draft format [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles]<br />
<br />
== Issues ==<br />
<br />
<br />
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.<br />
<br />
See also [[hatom-issues|hAtom Issues]] for questions about [[hAtom]].<br />
<br />
=== Issues Template ===<br />
<br />
{{issues-format}}<br />
<br />
=== Open Issues ===<br />
<div class="hentry"><br />
{{OpenIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-09</span> raised by <span class="fn">Miles De Feyter</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Implementation of item-license as it relates to hNews</strong>. Reading through the item-license brainstorm it seems to indicate that "item-license" would need to be nested within something with the class of "item". So as this relates to hNews is the suggestion to then have an articles containing div have the three class names of "hnews hentry item"? <br />
</div><br />
</div><br />
<br />
=== Closed Issues ===<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">2009-09-28</span> raised by <span class="fn">[[User:MilesD|Miles De Feyter]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Principles as a requirement</strong>. Working for a publishing company that owns and operates a large number of different organizations I'd love to incorporate hNews within our publishing system. The hNews requirement for a principles statement could pose a problem though or at least make rolling out hNews a more involved process then it would be otherwise. The issue is, I would now have to go to each product owner and ask then to provide this principles statement to link to. So my concern is now rather then just making a change to the publishing system to support hNews there is this requirement for some supporting content. And due to the nature of the content I can only assume our legal dep. would need to sign off as well, further complicating the adoption of hNews.<br />
** +1 I agree that the "principles" property (and probably all other others) should be optional. [[User:Tantek|Tantek]] 18:29, 29 September 2009 (UTC)<br />
*** I think it's important to explain why principles is a requirement. hnews is essentially a specialization of hAtom. Its purpose is to distinguish news on the web. Hence the description of source organisation, license and principles. Of these, principles is the only one which consistently distinguishes news on the web from other content (eg. commercial, government). In the future it should be distinguished further by making the principles themselves machine readable (but that is for a later date). Most professional news organisations adhere to a Statement of Principles (e.g. see http://en.wikipedia.org/wiki/Journalism_ethics_and_standards and http://www.journalism.org/resources/ethics_codes). If a site wants to mark up its content but does not want to distinguish it as news, then wouldn't it be easiest to use hAtom? [[User:martinjemoore|Martin Moore]] 9:00, 20 September 2009 (UTC)<br />
*** Having discussed this issue at length outside this brainstorming, we understand some of the concerns of the microformat community regarding 'must', but are still convinced of the criticality of principles to hNews - therefore recommend downgrading from 'must' to 'should'. [[User:martinjemoore|Martin Moore]] 14:00, 7 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">hCalendar instead of dateline?</strong> Would an [[hCalendar]] event (which can contain an hCard location) make sense for a dateline, or is the 'date' part more often omitted?<br />
** Confusingly, the journalistic term "dateline" isn't anything to do with a date or time. It is the location from which a report is filed and is generally the main location associated with a story. Generally, a dateline consists of a city (e.g. "Rome") but could be the name of a ship at sea or even a space station. [[User:Stuart Myles|Stuart Myles]] 21:12, 24 August 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">hCard instead of geo?</strong> Is geo really in use here, or would using an hCard (that can contain geo) be a better way of representing locations referred to in the story, as more human readable?<br />
** The reason for geo being highlighted (as an optional field) is to promote at least one location identifier in the story--preferably the most appropriate single location on a map for that particular story. Geo does not have to be related to dateline, but in some [http://labs.ap.org/wiki/hNews examples] we've worked on, we show the two collapsed into a single field. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)<br />
** For locations referred to in the story, I agree--publishers should be using [[hCard]] with the contained geo to markup the locations themselves. One of the concepts I've struggled with is drawing an admittedly arbitrary line between the metadata ''about'' a story from the metadata ''within'' a story. For the former, we've focused on simplicity and minimalism, primarily as a means to encourage adoption. That has meant preferring [[rel-tag]] over in-line entity extraction and markup using compound microformats. For the latter, we feel that the field is open: use whatever microformat fits your purpose, however you can--the more, the better. This lets publishers with minimal technology capabilities at least get started by tweaking a few templates in their CMS, while those more technically inclined aren't limited by the simplicity of the format to a paucity of data. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)<br />
** Also, dateline can be text or [[hCard]], as noted in the [[news-brainstorming#Common_News_Fields|Common News Fields]] section. --[[User:JonathanMalek|JonathanMalek]] 18:17, 24 September 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">What is item-license?</strong> Using [[rel-license]] presumably?<br />
** We're working off the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] discussions for this. Our concern with [[rel-license]] was its definition as applying to an entire page, rather than an item within a page. The current discussions around licensing definitely address that. --[[User:JonathanMalek|JonathanMalek]] 00:02, 25 August 2009 (UTC)<br />
*** +1 using item-license for news-brainstorming makes sense. [[User:Tantek|Tantek]] 22:32, 27 August 2009 (UTC)<br />
</div><br />
</div><br />
<br />
== Naming ==<br />
<br />
Here are candidate names for a news microformat:<br />
<br />
* hNews<br />
<br />
= Proposal = <br />
See the [[hnews]] draft.</div>JonathanMalekhttp://microformats.org/wiki/index.php?title=news-brainstorming&diff=41017news-brainstorming2009-10-12T15:44:06Z<p>JonathanMalek: moving the draft proposal to its own page.</p>
<hr />
<div>= News Brainstorming =<br />
<br />
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.<br />
<br />
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]]. - [[User:JonathanMalek|Jonathan Malek]] <br />
<br />
__TOC__<br />
<br />
== Contributors ==<br />
<br />
* Jonathan Malek<br />
* Stuart Myles<br />
* Martin Moore<br />
* Mark Ng<br />
* Todd Martin<br />
<br />
== See Also ==<br />
<br />
* [[news-examples]]<br />
* [[news-formats]]<br />
<br />
== The Problem ==<br />
<br />
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 ''[http://www.wired.com/threatlevel/2008/09/six-year-old-st/ Wired.com], 2008'').<br />
<br />
== Thoughts on a Microformat for News ==<br />
<br />
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 [http://www.atomenabled.org/ 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]].<br />
<br />
In much the same way that one extends [http://www.atomenabled.org/ Atom], we are looking to extend [[hAtom]] with the most vital news-specific fields.<br />
<br />
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'''.<br />
<br />
=== Common News Fields ===<br />
<br />
* [[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.<br />
* '''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.<br />
* '''dateline''': using text or [[hCard]], not to be confused with date (see [http://en.wikipedia.org/wiki/Dateline dateline] for more information).<br />
* '''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.<br />
* '''item-license''': to express licensing around the item<br />
* '''principles''': using the draft format [http://newscredit.org/development/newscredit-specification/rel-principles-specification/ rel-principles]<br />
<br />
== Issues ==<br />
<br />
<br />
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.<br />
<br />
See also [[hatom-issues|hAtom Issues]]<br />
<br />
=== Issues Template ===<br />
<br />
{{issues-format}}<br />
<br />
=== Open Issues ===<br />
<div class="hentry"><br />
{{OpenIssue}} <span class="entry-summary author vcard"><span class="published">2009-10-09</span> raised by <span class="fn">Miles De Feyter</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Implementation of item-license as it relates to hNews</strong>. Reading through the item-license brainstorm it seems to indicate that "item-license" would need to be nested within something with the class of "item". So as this relates to hNews is the suggestion to then have an articles containing div have the three class names of "hnews hentry item"? <br />
</div><br />
</div><br />
<br />
=== Closed Issues ===<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">2009-09-28</span> raised by <span class="fn">[[User:MilesD|Miles De Feyter]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">Principles as a requirement</strong>. Working for a publishing company that owns and operates a large number of different organizations I'd love to incorporate hNews within our publishing system. The hNews requirement for a principles statement could pose a problem though or at least make rolling out hNews a more involved process then it would be otherwise. The issue is, I would now have to go to each product owner and ask then to provide this principles statement to link to. So my concern is now rather then just making a change to the publishing system to support hNews there is this requirement for some supporting content. And due to the nature of the content I can only assume our legal dep. would need to sign off as well, further complicating the adoption of hNews.<br />
** +1 I agree that the "principles" property (and probably all other others) should be optional. [[User:Tantek|Tantek]] 18:29, 29 September 2009 (UTC)<br />
*** I think it's important to explain why principles is a requirement. hnews is essentially a specialization of hAtom. Its purpose is to distinguish news on the web. Hence the description of source organisation, license and principles. Of these, principles is the only one which consistently distinguishes news on the web from other content (eg. commercial, government). In the future it should be distinguished further by making the principles themselves machine readable (but that is for a later date). Most professional news organisations adhere to a Statement of Principles (e.g. see http://en.wikipedia.org/wiki/Journalism_ethics_and_standards and http://www.journalism.org/resources/ethics_codes). If a site wants to mark up its content but does not want to distinguish it as news, then wouldn't it be easiest to use hAtom? [[User:martinjemoore|Martin Moore]] 9:00, 20 September 2009 (UTC)<br />
*** Having discussed this issue at length outside this brainstorming, we understand some of the concerns of the microformat community regarding 'must', but are still convinced of the criticality of principles to hNews - therefore recommend downgrading from 'must' to 'should'. [[User:martinjemoore|Martin Moore]] 14:00, 7 October 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">hCalendar instead of dateline?</strong> Would an [[hCalendar]] event (which can contain an hCard location) make sense for a dateline, or is the 'date' part more often omitted?<br />
** Confusingly, the journalistic term "dateline" isn't anything to do with a date or time. It is the location from which a report is filed and is generally the main location associated with a story. Generally, a dateline consists of a city (e.g. "Rome") but could be the name of a ship at sea or even a space station. [[User:Stuart Myles|Stuart Myles]] 21:12, 24 August 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">hCard instead of geo?</strong> Is geo really in use here, or would using an hCard (that can contain geo) be a better way of representing locations referred to in the story, as more human readable?<br />
** The reason for geo being highlighted (as an optional field) is to promote at least one location identifier in the story--preferably the most appropriate single location on a map for that particular story. Geo does not have to be related to dateline, but in some [http://labs.ap.org/wiki/hNews examples] we've worked on, we show the two collapsed into a single field. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)<br />
** For locations referred to in the story, I agree--publishers should be using [[hCard]] with the contained geo to markup the locations themselves. One of the concepts I've struggled with is drawing an admittedly arbitrary line between the metadata ''about'' a story from the metadata ''within'' a story. For the former, we've focused on simplicity and minimalism, primarily as a means to encourage adoption. That has meant preferring [[rel-tag]] over in-line entity extraction and markup using compound microformats. For the latter, we feel that the field is open: use whatever microformat fits your purpose, however you can--the more, the better. This lets publishers with minimal technology capabilities at least get started by tweaking a few templates in their CMS, while those more technically inclined aren't limited by the simplicity of the format to a paucity of data. --[[User:JonathanMalek|JonathanMalek]] 23:53, 24 August 2009 (UTC)<br />
** Also, dateline can be text or [[hCard]], as noted in the [[news-brainstorming#Common_News_Fields|Common News Fields]] section. --[[User:JonathanMalek|JonathanMalek]] 18:17, 24 September 2009 (UTC)<br />
</div><br />
</div><br />
<br />
<div class="hentry"><br />
{{ClosedIssue}} <span class="entry-summary author vcard"><span class="published">18:32, 24 August 2009 (UTC)</span> raised by <span class="fn">[[User:Kevin Marks|Kevin Marks]]</span></span><br />
<div class="entry-content discussion issues"><br />
* <strong class="entry-title">What is item-license?</strong> Using [[rel-license]] presumably?<br />
** We're working off the [[licensing-brainstorming#item_as_container|licensing-brainstorming]] discussions for this. Our concern with [[rel-license]] was its definition as applying to an entire page, rather than an item within a page. The current discussions around licensing definitely address that. --[[User:JonathanMalek|JonathanMalek]] 00:02, 25 August 2009 (UTC)<br />
*** +1 using item-license for news-brainstorming makes sense. [[User:Tantek|Tantek]] 22:32, 27 August 2009 (UTC)<br />
</div><br />
</div><br />
<br />
== Naming ==<br />
<br />
Here are candidate names for a news microformat:<br />
<br />
* hNews<br />
<br />
= Proposal = <br />
See the [[hnews]] draft.</div>JonathanMalek