hlisting-issues - Revision history

Aaronpk: Replace with {{DISPLAYTITLE:}}

2020-07-18T16:26:58Z

Replace <entry-title> with {{DISPLAYTITLE:}}

← Older revision		Revision as of 16:26, 18 July 2020
Line 1:		Line 1:
	~~<entry-title>~~ hListing Issues ~~</entry-title>~~		{{DISPLAYTITLE: hListing Issues }}

	These are externally raised issues about [[hlisting\|hListing]] 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 spec.		These are externally raised issues about [[hlisting\|hListing]] 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 spec.

TomMorris: all were raised today - correct date

2014-11-17T17:12:02Z

all were raised today - correct date

ChiefRA: /* issues */ - added more inconsistencies to bring hListing to a definitive form

2014-11-17T16:55:29Z

issues: - added more inconsistencies to bring hListing to a definitive form

← Older revision		Revision as of 16:55, 17 November 2014
Line 35:		Line 35:

	=== 2014 ===		=== 2014 ===

			{{OpenIssue}}
			* 2014-11-14 raised by [[User:ChiefRA\|Arthur Rădulescu]]
			*# We should create Directives for hListing consumers (and also for Google?): directives on how hListing should be interpreted and consumed, rules which CAN be applied to hListing validators too.

			{{OpenIssue}}
			* 2014-11-13 raised by [[User:ChiefRA\|Arthur Rădulescu]]
			*# There is an ambiguity regarding [http://microformats.org/wiki/hlisting#Property_Details hListing Property Details]: on the second line, named '''Listing type::''' it sais: "This required field" but it is not mentioned in the main Properties and there is no field on the above main [http://microformats.org/wiki/hlisting#Properties hListing Properties]. However, there is a mix of properties on the second listed property called: "''listing action.'' optional."
			# Tried to fix all of these in the [http://microformats.org/wiki/hlisting-duplicated-for-discussions hlisting duplicated draft page] - read it by comparison 1-on-1 with the [http://microformats.org/wiki/hlisting default hListing page]. These 2 fields should now be understandable from implementation POV.

			{{OpenIssue}}
			* 2014-11-12 raised by [[User:ChiefRA\|Arthur Rădulescu]]
			*# I presume this mandatory field called '''Item type''' should be added next to the other properties of the hListing next to the [http://microformats.org/wiki/hlisting#Properties hListing Properties].
			# Tried to fix this in the [http://microformats.org/wiki/hlisting-duplicated-for-discussions hlisting duplicated draft page] - read it by comparison 1-on-1 with the [http://microformats.org/wiki/hlisting default hListing page]. This field should now be understandable from implementation POV.

	{{OpenIssue}}		{{OpenIssue}}
	* 2014-11-17 raised by [[User:ChiefRA\|Arthur]]		* 2014-11-11 raised by [[User:ChiefRA\|Arthur Rădulescu]]
	*# One of the main obstacles for hListing usage is the lack of implementation examples on our end (real in-code implementation) for the 2-words properties. ex. "item info": tag which should encapsulate all the details like hCard \| (fn \|\| url \|\| photo \|\| geo \|\| adr)? Should it be exactly class="item info" OR class="item-info"? This needs to be defined as it has to keep encapsulated within all the details of the item.		*# One of the main obstacles for hListing usage is the lack of implementation examples on our end (real in-code implementation) for the 2-words properties. ex. "item info": tag which should encapsulate all the details like hCard \| (fn \|\| url \|\| photo \|\| geo \|\| adr)? Should it be exactly class="item info" OR class="item-info"? This needs to be defined as it has to keep encapsulated within all the details of the item.

	{{OpenIssue}}		{{OpenIssue}}
	* 2014-11-17 raised by [[User:TomMorris\|Tom Morris]]		* 2014-11-10 raised by [[User:TomMorris\|Tom Morris]]
	*# The '''version''' property should be deprecated. No other Microformat (classic or [[microformats-2\|new]]) has used explicit versioning and it seems out of sync with the way we have thus far built microformats specifications. It also seems incompatible with the [http://www.w3.org/TR/html-design-principles/#compatibility Compatibility section of the HTML Design Principles] which we ought to attempt to follow where possible.		*# The '''version''' property should be deprecated. No other Microformat (classic or [[microformats-2\|new]]) has used explicit versioning and it seems out of sync with the way we have thus far built microformats specifications. It also seems incompatible with the [http://www.w3.org/TR/html-design-principles/#compatibility Compatibility section of the HTML Design Principles] which we ought to attempt to follow where possible.

TomMorris: /* 2014 */ HTML design principles

2014-11-17T12:46:12Z

2014: HTML design principles

← Older revision		Revision as of 12:46, 17 November 2014
Line 41:		Line 41:
	{{OpenIssue}}		{{OpenIssue}}
	* 2014-11-17 raised by [[User:TomMorris\|Tom Morris]]		* 2014-11-17 raised by [[User:TomMorris\|Tom Morris]]
	*# The '''version''' property should be deprecated. No other Microformat (classic or [[microformats-2\|new]]) has used explicit versioning and it seems out of sync with the way we have thus far built microformats specifications.		*# The '''version''' property should be deprecated. No other Microformat (classic or [[microformats-2\|new]]) has used explicit versioning and it seems out of sync with the way we have thus far built microformats specifications. It also seems incompatible with the [http://www.w3.org/TR/html-design-principles/#compatibility Compatibility section of the HTML Design Principles] which we ought to attempt to follow where possible.

	<div class="hentry">		<div class="hentry">

TomMorris: /* issues */ deprecate version

2014-11-17T11:41:20Z

issues: deprecate version

← Older revision		Revision as of 11:41, 17 November 2014
Line 39:		Line 39:
	*# One of the main obstacles for hListing usage is the lack of implementation examples on our end (real in-code implementation) for the 2-words properties. ex. "item info": tag which should encapsulate all the details like hCard \| (fn \|\| url \|\| photo \|\| geo \|\| adr)? Should it be exactly class="item info" OR class="item-info"? This needs to be defined as it has to keep encapsulated within all the details of the item.		*# One of the main obstacles for hListing usage is the lack of implementation examples on our end (real in-code implementation) for the 2-words properties. ex. "item info": tag which should encapsulate all the details like hCard \| (fn \|\| url \|\| photo \|\| geo \|\| adr)? Should it be exactly class="item info" OR class="item-info"? This needs to be defined as it has to keep encapsulated within all the details of the item.

			{{OpenIssue}}
			* 2014-11-17 raised by [[User:TomMorris\|Tom Morris]]
			*# The '''version''' property should be deprecated. No other Microformat (classic or [[microformats-2\|new]]) has used explicit versioning and it seems out of sync with the way we have thus far built microformats specifications.

	<div class="hentry">		<div class="hentry">

ChiefRA: /* issues */ adding all the recent issues I've found

2014-11-17T11:09:17Z

issues: adding all the recent issues I've found

← Older revision		Revision as of 11:09, 17 November 2014
Line 33:		Line 33:

	== issues ==		== issues ==

			=== 2014 ===
			{{OpenIssue}}
			* 2014-11-17 raised by [[User:ChiefRA\|Arthur]]
			*# One of the main obstacles for hListing usage is the lack of implementation examples on our end (real in-code implementation) for the 2-words properties. ex. "item info": tag which should encapsulate all the details like hCard \| (fn \|\| url \|\| photo \|\| geo \|\| adr)? Should it be exactly class="item info" OR class="item-info"? This needs to be defined as it has to keep encapsulated within all the details of the item.


	<div class="hentry">		<div class="hentry">
	~~{{OpenIssue}}~~
	<span class="entry-summary author vcard">		<span class="entry-summary author vcard">
	<span class="published">2010-09-19</span>		<span class="published">2010-09-19</span>

JulienChaumond: /* issues */

2010-09-19T13:03:15Z

issues

@@ Line 33: / Line 33: @@
 == issues ==
-* no current open issues.
 == Template ==

Tantek: resolve all outstanding issues

2009-08-05T10:18:10Z

resolve all outstanding issues

← Older revision		Revision as of 10:18, 5 August 2009
Line 11:		Line 11:
	== closed issues ==		== closed issues ==
	When this section gets too big, it can be moved to [[hlisting-issues-closed]].		When this section gets too big, it can be moved to [[hlisting-issues-closed]].
			Issues that are resolved, with accepted resolutions (in some cases simply accepting the entire noted issue), and with completion of respective edits to the draft or related documents.

	== resolved issues ==		== resolved issues ==
			Issues that have been resolved but may have outstanding to-do items.
	When this section gets too big, it can be moved to [[hlisting-issues-resolved]].		When this section gets too big, it can be moved to [[hlisting-issues-resolved]].
	=== 2007 ===		=== 2007 ===
	* 2007-07-21 raised by [[User:RobManson]]		* 2007-07-21 raised by [[User:RobManson]]
	*# The only discussion I could find relating to payment method for hListing was in the tag section. Wouldn't [[rel-payment]] be a natural fit with hListing?		*# The only discussion I could find relating to payment method for hListing was in the tag section. Wouldn't [[rel-payment]] be a natural fit with hListing?
	# ACCEPTED BRAINSTORMING. Consider using [[rel-payment]] or something similar for an iteration of hListing, suggestion added to [[hlisting-brainstorming]]. [[User:Tantek\|Tantek]] 09:40, 5 August 2009 (UTC)		# ACCEPTED BRAINSTORMING. Consider using [[rel-payment]] or something similar for an iteration of hListing, suggestion added to [[hlisting-brainstorming]]. [[User:Tantek\|Tantek]] 10:18, 5 August 2009 (UTC)
	=== 2008 ===		=== 2008 ===
	* 2008-04-07 raised by [[User:Eazytiger]]		* 2008-04-07 raised by [[User:Eazytiger]]
	*# When hListing is used for eCommerce products, is there any provision for product variations (eg. sizes) that will affect the price? I'm not aware of a precedent for variations in another microformat.		*# When hListing is used for eCommerce products, is there any provision for product variations (eg. sizes) that will affect the price? I'm not aware of a precedent for variations in another microformat.
	# ACCEPTED FAQ. A variation that affects the price should be included in the description of ~~them~~, and perhaps as a tag on the item as well. [[User:Tantek\|Tantek]] 09:40, 5 August 2009 (UTC)		# ACCEPTED FAQ. A product variation that affects the price should be included in the description of the item, and perhaps as a tag on the item as well. This should be added to [[hlisting-faq]] [[User:Tantek\|Tantek]] 10:18, 5 August 2009 (UTC)
	* 2008-08-26 raised by [[User:TobyInk\|TobyInk]]		* 2008-08-26 raised by [[User:TobyInk\|TobyInk]]
	*# The example given in the spec includes an invalid [[hCard]]. (Missing '''fn'''.)		*# The example given in the spec includes an invalid [[hCard]]. (Missing '''fn'''.)
	# ACCEPTED. The example has been fixed to reference the "adr" directly for the location, which was the intent of the example. [[User:Tantek\|Tantek]] 09:40, 5 August 2009 (UTC)		# ACCEPTED. The example has been fixed to reference the "adr" directly for the location, which was the intent of the example. [[User:Tantek\|Tantek]] 10:18, 5 August 2009 (UTC)
	=== 2009 ===		=== 2009 ===
	*2009-03-10 raised by [[User:JayMyers\|JayMyers]]		*2009-03-10 raised by [[User:JayMyers\|JayMyers]]
	*# Per the discussions raised in the [[hproduct-issues\|hProduct issues list]], are there any provisions for providing transactional details like "shipping" or "buy/payment" attributes?		*# Per the discussions raised in the [[hproduct-issues\|hProduct issues list]], are there any provisions for providing transactional details like "shipping" or "buy/payment" attributes?
	# ACCEPTED BRAINSTORMING. Consider adding transactional details like "shipping" or "buy/payment" attributes or something similar for an iteration of hListing, request added to [[hlisting-brainstorming]]. [[User:Tantek\|Tantek]] 09:40, 5 August 2009 (UTC)		# ACCEPTED BRAINSTORMING. Consider adding transactional details like "shipping" or "buy/payment" attributes or something similar for an iteration of hListing, request added to [[hlisting-brainstorming]]. [[User:Tantek\|Tantek]] 10:18, 5 August 2009 (UTC)

	== issues ==		== issues ==
Line 40:		Line 42:
	* [[hlisting-feedback]]		* [[hlisting-feedback]]
	* [[hlisting-brainstorming]]		* [[hlisting-brainstorming]]
			* [[hlisting-faq]]

Tantek: resolve all outstanding issues

2009-08-05T09:40:09Z

resolve all outstanding issues

← Older revision		Revision as of 09:40, 5 August 2009
Line 1:		Line 1:
	<h1> hListing Issues </h1>		<entry-title> hListing Issues </entry-title>

	These are externally raised issues about [[hlisting\|hListing]] 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 spec.		These are externally raised issues about [[hlisting\|hListing]] 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 spec.
Line 9:		Line 9:
	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.		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.

	~~__TOC__~~		== closed issues ==
			When this section gets too big, it can be moved to [[hlisting-issues-closed]].

	== ~~Issues~~ ==		== resolved issues ==
	*~~{{OpenIssue}}~~ 2007-07-21 raised by [[User:RobManson]]		When this section gets too big, it can be moved to [[hlisting-issues-resolved]].
			=== 2007 ===
			* 2007-07-21 raised by [[User:RobManson]]
	*# The only discussion I could find relating to payment method for hListing was in the tag section. Wouldn't [[rel-payment]] be a natural fit with hListing?		*# The only discussion I could find relating to payment method for hListing was in the tag section. Wouldn't [[rel-payment]] be a natural fit with hListing?
			# ACCEPTED BRAINSTORMING. Consider using [[rel-payment]] or something similar for an iteration of hListing, suggestion added to [[hlisting-brainstorming]]. [[User:Tantek\|Tantek]] 09:40, 5 August 2009 (UTC)
	*~~{{OpenIssue}}~~ 2008-04-07 raised by [[User:Eazytiger]]		=== 2008 ===
			* 2008-04-07 raised by [[User:Eazytiger]]
	*# When hListing is used for eCommerce products, is there any provision for product variations (eg. sizes) that will affect the price? I'm not aware of a precedent for variations in another microformat.		*# When hListing is used for eCommerce products, is there any provision for product variations (eg. sizes) that will affect the price? I'm not aware of a precedent for variations in another microformat.
			# ACCEPTED FAQ. A variation that affects the price should be included in the description of them, and perhaps as a tag on the item as well. [[User:Tantek\|Tantek]] 09:40, 5 August 2009 (UTC)
	*~~{{OpenIssue}}~~ 2008-08-26 raised by [[User:TobyInk\|TobyInk]]		* 2008-08-26 raised by [[User:TobyInk\|TobyInk]]
	*# The example given in the spec includes an invalid [[hCard]]. (Missing '''fn'''.)		*# The example given in the spec includes an invalid [[hCard]]. (Missing '''fn'''.)
			# ACCEPTED. The example has been fixed to reference the "adr" directly for the location, which was the intent of the example. [[User:Tantek\|Tantek]] 09:40, 5 August 2009 (UTC)
			=== 2009 ===
			*2009-03-10 raised by [[User:JayMyers\|JayMyers]]
			*# Per the discussions raised in the [[hproduct-issues\|hProduct issues list]], are there any provisions for providing transactional details like "shipping" or "buy/payment" attributes?
			# ACCEPTED BRAINSTORMING. Consider adding transactional details like "shipping" or "buy/payment" attributes or something similar for an iteration of hListing, request added to [[hlisting-brainstorming]]. [[User:Tantek\|Tantek]] 09:40, 5 August 2009 (UTC)

	*{{OpenIssue}} 2009-03-10 raised by [[User:JayMyers\|JayMyers]]		== issues ==
	*~~# Per the discussions raised in the [[hproduct-issues\|hProduct~~ issues ~~list]], are there any provisions for providing transactional details like "shipping" or "buy/payment" attributes?~~		* no current open issues.

	== Template ==		== Template ==
	{{issues-format}}		{{issues-format}}

	== ~~Resolved Issues~~ ==		== see also ==
			* [[hListing]]
	~~== Closed Issues ==~~		* [[hlisting-feedback]]
			* [[hlisting-brainstorming]]
	~~== Related Pages ==~~

JayMyers: editing comment

2009-03-10T20:13:46Z

editing comment

← Older revision		Revision as of 20:13, 10 March 2009
Line 22:		Line 22:

	*{{OpenIssue}} 2009-03-10 raised by [[User:JayMyers\|JayMyers]]		*{{OpenIssue}} 2009-03-10 raised by [[User:JayMyers\|JayMyers]]
	*# Per the discussions raised in the [[hproduct-issues\|hProduct issues list]], are there any provisions for providing transactional details like shipping ~~details~~ or buy/payment attributes?		*# Per the discussions raised in the [[hproduct-issues\|hProduct issues list]], are there any provisions for providing transactional details like "shipping" or "buy/payment" attributes?

	== Template ==		== Template ==

← Older revision		Revision as of 17:12, 17 November 2014
Line 37:		Line 37:

	{{OpenIssue}}		{{OpenIssue}}
	* 2014-11-14 raised by [[User:ChiefRA\|Arthur Rădulescu]]		* 2014-11-17 raised by [[User:ChiefRA\|Arthur Rădulescu]]
	*# We should create Directives for hListing consumers (and also for Google?): directives on how hListing should be interpreted and consumed, rules which CAN be applied to hListing validators too.		*# We should create Directives for hListing consumers (and also for Google?): directives on how hListing should be interpreted and consumed, rules which CAN be applied to hListing validators too.

	{{OpenIssue}}		{{OpenIssue}}
	* 2014-11-13 raised by [[User:ChiefRA\|Arthur Rădulescu]]		* 2014-11-17 raised by [[User:ChiefRA\|Arthur Rădulescu]]
	*# There is an ambiguity regarding [http://microformats.org/wiki/hlisting#Property_Details hListing Property Details]: on the second line, named '''Listing type::''' it sais: "This required field" but it is not mentioned in the main Properties and there is no field on the above main [http://microformats.org/wiki/hlisting#Properties hListing Properties]. However, there is a mix of properties on the second listed property called: "''listing action.'' optional."		*# There is an ambiguity regarding [http://microformats.org/wiki/hlisting#Property_Details hListing Property Details]: on the second line, named '''Listing type::''' it sais: "This required field" but it is not mentioned in the main Properties and there is no field on the above main [http://microformats.org/wiki/hlisting#Properties hListing Properties]. However, there is a mix of properties on the second listed property called: "''listing action.'' optional."
	# Tried to fix all of these in the [http://microformats.org/wiki/hlisting-duplicated-for-discussions hlisting duplicated draft page] - read it by comparison 1-on-1 with the [http://microformats.org/wiki/hlisting default hListing page]. These 2 fields should now be understandable from implementation POV.		# Tried to fix all of these in the [http://microformats.org/wiki/hlisting-duplicated-for-discussions hlisting duplicated draft page] - read it by comparison 1-on-1 with the [http://microformats.org/wiki/hlisting default hListing page]. These 2 fields should now be understandable from implementation POV.

	{{OpenIssue}}		{{OpenIssue}}
	* 2014-11-12 raised by [[User:ChiefRA\|Arthur Rădulescu]]		* 2014-11-17 raised by [[User:ChiefRA\|Arthur Rădulescu]]
	*# I presume this mandatory field called '''Item type''' should be added next to the other properties of the hListing next to the [http://microformats.org/wiki/hlisting#Properties hListing Properties].		*# I presume this mandatory field called '''Item type''' should be added next to the other properties of the hListing next to the [http://microformats.org/wiki/hlisting#Properties hListing Properties].
	# Tried to fix this in the [http://microformats.org/wiki/hlisting-duplicated-for-discussions hlisting duplicated draft page] - read it by comparison 1-on-1 with the [http://microformats.org/wiki/hlisting default hListing page]. This field should now be understandable from implementation POV.		# Tried to fix this in the [http://microformats.org/wiki/hlisting-duplicated-for-discussions hlisting duplicated draft page] - read it by comparison 1-on-1 with the [http://microformats.org/wiki/hlisting default hListing page]. This field should now be understandable from implementation POV.

	{{OpenIssue}}		{{OpenIssue}}
	* 2014-11-11 raised by [[User:ChiefRA\|Arthur Rădulescu]]		* 2014-11-17 raised by [[User:ChiefRA\|Arthur Rădulescu]]
	*# One of the main obstacles for hListing usage is the lack of implementation examples on our end (real in-code implementation) for the 2-words properties. ex. "item info": tag which should encapsulate all the details like hCard \| (fn \|\| url \|\| photo \|\| geo \|\| adr)? Should it be exactly class="item info" OR class="item-info"? This needs to be defined as it has to keep encapsulated within all the details of the item.		*# One of the main obstacles for hListing usage is the lack of implementation examples on our end (real in-code implementation) for the 2-words properties. ex. "item info": tag which should encapsulate all the details like hCard \| (fn \|\| url \|\| photo \|\| geo \|\| adr)? Should it be exactly class="item info" OR class="item-info"? This needs to be defined as it has to keep encapsulated within all the details of the item.

	{{OpenIssue}}		{{OpenIssue}}
	* 2014-11-10 raised by [[User:TomMorris\|Tom Morris]]		* 2014-11-17 raised by [[User:TomMorris\|Tom Morris]]
	*# The '''version''' property should be deprecated. No other Microformat (classic or [[microformats-2\|new]]) has used explicit versioning and it seems out of sync with the way we have thus far built microformats specifications. It also seems incompatible with the [http://www.w3.org/TR/html-design-principles/#compatibility Compatibility section of the HTML Design Principles] which we ought to attempt to follow where possible.		*# The '''version''' property should be deprecated. No other Microformat (classic or [[microformats-2\|new]]) has used explicit versioning and it seems out of sync with the way we have thus far built microformats specifications. It also seems incompatible with the [http://www.w3.org/TR/html-design-principles/#compatibility Compatibility section of the HTML Design Principles] which we ought to attempt to follow where possible.