news-issues - Revision history

JonathanMalek: redirecting to news-brainstorming#Issues

2009-08-27T17:14:44Z

redirecting to news-brainstorming#Issues

← Older revision		Revision as of 17:14, 27 August 2009
Line 1:		Line 1:
	~~This page reflects externally raised issues about [[news]] microformat effort in development.~~		#REDIRECT:[[news-brainstorming#Issues]]

	~~= Issues =~~

	~~Please add new issues to the bottom of the [[news-issues~~#~~Open_Issues\|Open Issues]] section by copy and pasting the~~ [[news~~-issues#Issues_Template\|Template]]. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.~~

	~~== Issues Template ==~~

	~~{{issues-format}}~~

	~~= Open Issues =~~

	~~<div class="hentry">~~
	~~{{OpenIssue}} <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>~~
	~~<div class="entry-content discussion issues">~~
	* <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?
	** 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)
	~~</div>~~
	~~</div>~~

	~~<div class="hentry">~~
	~~{{OpenIssue}} <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>~~
	~~<div class="entry-content discussion issues">~~
	* <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?
	** 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)
	** 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)
	~~</div>~~
	~~</div>~~

	~~<div class="hentry">~~
	~~{{OpenIssue}} <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>~~
	~~<div class="entry-content discussion issues">~~
	* <strong class="entry-title">What is item-license?</strong> Using [[rel-license]] presumably?
	** 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)
	~~</div>~~
	~~</div>~~

	~~= Closed~~ Issues =

	~~= Related Pages =~~

	* [[news\|news description]]
	* [[news-examples]]
	* [[news-formats]]
	* [[news-brainstorming]]

Tantek: fix link vs linktext

2009-08-25T00:13:25Z

fix link vs linktext

← Older revision		Revision as of 00:13, 25 August 2009
Line 32:		Line 32:
	<div class="entry-content discussion issues">		<div class="entry-content discussion issues">
	* <strong class="entry-title">What is item-license?</strong> Using [[rel-license]] presumably?		* <strong class="entry-title">What is item-license?</strong> Using [[rel-license]] presumably?
	** 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)		** 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)
	</div>		</div>
	</div>		</div>

Tantek: typos fix intrawiki link

2009-08-25T00:11:30Z

typos fix intrawiki link

← Older revision		Revision as of 00:11, 25 August 2009
Line 32:		Line 32:
	<div class="entry-content discussion issues">		<div class="entry-content discussion issues">
	* <strong class="entry-title">What is item-license?</strong> Using [[rel-license]] presumably?		* <strong class="entry-title">What is item-license?</strong> Using [[rel-license]] presumably?
	** 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)		** 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)
	</div>		</div>
	</div>		</div>

JonathanMalek: item-license or rel-license

2009-08-25T00:02:14Z

item-license or rel-license

← Older revision		Revision as of 00:02, 25 August 2009
Line 32:		Line 32:
	<div class="entry-content discussion issues">		<div class="entry-content discussion issues">
	* <strong class="entry-title">What is item-license?</strong> Using [[rel-license]] presumably?		* <strong class="entry-title">What is item-license?</strong> Using [[rel-license]] presumably?
			** 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)
	</div>		</div>
	</div>		</div>

JonathanMalek: hCard instead of geo?

2009-08-24T23:53:39Z

hCard instead of geo?

← Older revision		Revision as of 23:53, 24 August 2009
Line 23:		Line 23:
	<div class="entry-content discussion issues">		<div class="entry-content discussion issues">
	* <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?		* <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?
			** 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)
			** 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)
	</div>		</div>
	</div>		</div>

JonathanMalek: moving Kevin Marks' issues over

2009-08-24T22:40:03Z

moving Kevin Marks' issues over

← Older revision		Revision as of 22:40, 24 August 2009
Line 10:		Line 10:

	= Open Issues =		= Open Issues =

			<div class="hentry">
			{{OpenIssue}} <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>
			<div class="entry-content discussion issues">
			* <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?
			** 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)
			</div>
			</div>

			<div class="hentry">
			{{OpenIssue}} <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>
			<div class="entry-content discussion issues">
			* <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?
			</div>
			</div>

			<div class="hentry">
			{{OpenIssue}} <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>
			<div class="entry-content discussion issues">
			* <strong class="entry-title">What is item-license?</strong> Using [[rel-license]] presumably?
			</div>
			</div>

	= Closed Issues =		= Closed Issues =

JonathanMalek: Creating a news-issues page idea from Kevin Marks http://twitter.com/kevinmarks/status/3519426860

2009-08-24T20:48:29Z

Creating a news-issues page idea from Kevin Marks http://twitter.com/kevinmarks/status/3519426860

New page

This page reflects externally raised issues about [[news]] microformat effort in development.

= Issues =

Please add new issues to the bottom of the [[news-issues#Open_Issues|Open Issues]] section by copy and pasting the [[news-issues#Issues_Template|Template]]. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.

== Issues Template ==

{{issues-format}}

= Open Issues =

= Closed Issues =

= Related Pages =

* [[news|news description]]
* [[news-examples]]
* [[news-formats]]
* [[news-brainstorming]]