issues - Revision history

Aaronpk: Replace with {{DISPLAYTITLE:}}

2020-07-18T16:28:33Z

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

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

	These are externally raised issues about microformats in general.		These are externally raised issues about microformats in general.

Tantek: rel-values-issues is what it means here

2013-05-02T18:44:26Z

rel-values-issues is what it means here

← Older revision		Revision as of 18:44, 2 May 2013
Line 81:		Line 81:
	* [[hresume-issues]]		* [[hresume-issues]]
	* [[hreview-issues]]		* [[hreview-issues]]
	* [[rel-issues]]		* [[rel-values-issues]]
	** [[rel-home-issues]]		** [[rel-home-issues]]
	** [[rel-license-issues]]		** [[rel-license-issues]]

Tantek: Reverted edits by ABIDEEN10 (Talk) to last version by Tantek

2013-04-07T04:51:36Z

Reverted edits by ABIDEEN10 (Talk) to last version by Tantek

Show changes

ABIDEEN10 at 04:02, 7 April 2013

2013-04-07T04:02:52Z

Show changes

Tantek: /* opened 2010 */ issue was also noted on Google rich snippets knol

2011-12-17T00:25:09Z

opened 2010: issue was also noted on Google rich snippets knol

← Older revision		Revision as of 00:25, 17 December 2011
Line 58:		Line 58:
	** [https://twitter.com/richardtvaughan/status/129236380873261057 and follow-up same day also]:		** [https://twitter.com/richardtvaughan/status/129236380873261057 and follow-up same day also]:
	*** "microformats are the easiest as it's just CSS classes, but may be a pain to implement if those class names are already used."		*** "microformats are the easiest as it's just CSS classes, but may be a pain to implement if those class names are already used."
			** See also '''Beware of microformats/CSS naming collisions''' section in http://knol.google.com/k/google-rich-snippets-tips-and-tricks (no edit history, date unknown, found 2011-350)
	** '''ACCEPTED. PROPOSED RESOLUTION.''' We are fixing this with [[microformats-2]], all property names have prefixes to avoid such collisions. E.g. 'url' becomes 'u-url' and 'region' becomes 'p-region'. See [[microformats-2#h-card\|microformats 2: h-card properties]] for more. - [[User:Tantek\|Tantek]]		** '''ACCEPTED. PROPOSED RESOLUTION.''' We are fixing this with [[microformats-2]], all property names have prefixes to avoid such collisions. E.g. 'url' becomes 'u-url' and 'region' becomes 'p-region'. See [[microformats-2#h-card\|microformats 2: h-card properties]] for more. - [[User:Tantek\|Tantek]]
	</div>		</div>

Tantek: /* Issues */ cognitive dissonance in naming of root microformats class names slightly differently than the microformats themselves hCard/vcard, hCalendar/vevent, hReview/hreview, add ids

2011-10-28T15:21:46Z

Issues: cognitive dissonance in naming of root microformats class names slightly differently than the microformats themselves hCard/vcard, hCalendar/vevent, hReview/hreview, add ids

← Older revision		Revision as of 15:21, 28 October 2011
Line 20:		Line 20:

	== Issues ==		== Issues ==
			=== opened 2006 ===

			<div class="hentry" id="hcard-vs-vcard-name">
			{{OpenIssue}}
			<span class="entry-summary author vcard">
			<span class="published">2006-05-11</span>
			[http://microformats.org/wiki/index.php?title=hcard-faq&diff=6324&oldid=6323 FAQ by <span class="fn">Brian Suda</span>], expanded/reraised by [[User:Tantek\|Tantek]]
			</span>
			<div class="entry-content discussion issues">
			* <strong class="entry-title">why does hCard use "vcard" as the root class or hCalendar use "vevent"?</strong>
			** Originally partly [[hcard-faq#Why_does_hCard_use_vcard_as_the_root_class_name\|an FAQ written by Brian Suda]], this slight inconsistency between the name of the format and the name of the root class name consistently causes confusion in a large percentage of newcomers to microformats. - [[User:Tantek\|Tantek]]
			*** Looks like a typo (just one letter difference)
			*** Cognitive dissonance: saying "use hCard" but implying use "vcard" class name, or the implication causing one to just say "use vcard", e.g. [https://twitter.com/cssquirrel/status/129602573635289088 Kyle Weems]: <blockquote>I always end up saying "vcard" instead of "hcard" because I never write "hcard" in the code. It's weird having "two" formats that are 1:1.</blockquote>
			*** Ambiguity in discussions, e.g. put "vcard" in your HTML - meaning, class name, or a link to a .vcf file?
			*** Cognitive load: extra bit of information to remember when marking up a microformat
			*** in contrast to [[hReview]], [[hListing]], [[hRecipe]], etc. which all have root class name same as name of microformat (albeit lowercased, however some publishers have used the 2nd-letter-uppercase version as the root class name, e.g. class="hReview", enough for Google's rich snippet parsers to liberally accept it, so those could be improved as well.).
			** Though in microformats we believe very strongly in the [[principle]] of [[reuse]], we have to admit that in this case experience/evidence has shown that this may be a case where we re-used something too far beyond it's original meaning. Or perhaps we errantly called two slightly different things by the same name.
			*** '''ACCEPTED PROPOSED RESOLUTION.''' In [[microformats-2]], all vocabularies are named the same as their root class names, e.g. "h-card", "h-event", "h-entry" etc. - [[User:Tantek\|Tantek]]
			</div>
			</div>

	=== opened 2010 ===		=== opened 2010 ===
	Issues opened/raised in 2010.		Issues opened/raised in 2010.

	<div class="hentry">		<div class="hentry" id="class-collisions">
	{{OpenIssue}}		{{OpenIssue}}
	<span class="entry-summary author vcard">		<span class="entry-summary author vcard">
	<span class="published">2010-08-24</span>		<span class="published">2010-08-24</span>
	[http://html5doctor.com/microformats/#comment-10241 raised by <span class="fn">Wim</span>]		[http://html5doctor.com/microformats/#comment-10241 raised by <span class="fn">Wim</span>], expanded by [[User:Tantek\|Tantek]]
	</span>		</span>
	<div class="entry-content discussion issues">		<div class="entry-content discussion issues">
	* <strong class="entry-title">microformats classes like 'url' or 'region' already in use</strong>. "Using class for the microformat markup is clearly a problem, in part because it’s so easy to overlap with other markup. Authors use classes like “url” or “region” all the time, and might not be aware of the hCard format. All sorts of markup might look like a microformat."		* <strong class="entry-title">microformats classes like 'url' or 'region' already in use</strong>. "Using class for the microformat markup is clearly a problem, in part because it’s so easy to overlap with other markup. Authors use classes like “url” or “region” all the time, and might not be aware of the hCard format. All sorts of markup might look like a microformat."
			** There has also been an anecdotal report of a design firm who was not (yet) familiar with microformats seeing the "extra" classes that "that don't seem to be used" (without corresponding CSS rules) and asking if they "can remove them". By making microformats class names different from generic words, authors unfamiliar with microformats may at least notice such distinction and infer special functionality accordingly. - [[User:Tantek\|Tantek]]
	** ACCEPTED. Pretty sure this was raised before, in IRC/lists elsewhere, but this URL was the earliest one I could find to capture it. - [[User:Tantek\|Tantek]]		** ACCEPTED. Pretty sure this was raised before, in IRC/lists elsewhere, but this URL was the earliest one I could find to capture it. - [[User:Tantek\|Tantek]]
	** 2011-10-26 [https://twitter.com/richardtvaughan/status/129235473414631424 confirmed by Richard Vaughan]:		** 2011-10-26 [https://twitter.com/richardtvaughan/status/129235473414631424 confirmed by Richard Vaughan]:
Line 36:		Line 58:
	** [https://twitter.com/richardtvaughan/status/129236380873261057 and follow-up same day also]:		** [https://twitter.com/richardtvaughan/status/129236380873261057 and follow-up same day also]:
	*** "microformats are the easiest as it's just CSS classes, but may be a pain to implement if those class names are already used."		*** "microformats are the easiest as it's just CSS classes, but may be a pain to implement if those class names are already used."
	** ACCEPTED. PROPOSED RESOLUTION ~~- we~~ are fixing this with [[microformats-2]], all property names have prefixes to avoid such collisions. E.g. 'url' becomes 'u-url' and 'region' becomes 'p-region'. See [[microformats-2#h-card\|microformats 2: h-card properties]] for more. - [[User:Tantek\|Tantek]]		** '''ACCEPTED. PROPOSED RESOLUTION.''' We are fixing this with [[microformats-2]], all property names have prefixes to avoid such collisions. E.g. 'url' becomes 'u-url' and 'region' becomes 'p-region'. See [[microformats-2#h-card\|microformats 2: h-card properties]] for more. - [[User:Tantek\|Tantek]]
	</div>		</div>
	</div>		</div>

Tantek: /* opened 2010 */ grammar

2011-10-27T21:55:14Z

opened 2010: grammar

← Older revision		Revision as of 21:55, 27 October 2011
Line 31:		Line 31:
	<div class="entry-content discussion issues">		<div class="entry-content discussion issues">
	* <strong class="entry-title">microformats classes like 'url' or 'region' already in use</strong>. "Using class for the microformat markup is clearly a problem, in part because it’s so easy to overlap with other markup. Authors use classes like “url” or “region” all the time, and might not be aware of the hCard format. All sorts of markup might look like a microformat."		* <strong class="entry-title">microformats classes like 'url' or 'region' already in use</strong>. "Using class for the microformat markup is clearly a problem, in part because it’s so easy to overlap with other markup. Authors use classes like “url” or “region” all the time, and might not be aware of the hCard format. All sorts of markup might look like a microformat."
	** ACCEPTED. ~~I this~~ this was raised before, in IRC/lists elsewhere, but this URL was the earliest one I could find to capture it. - [[User:Tantek\|Tantek]]		** ACCEPTED. Pretty sure this was raised before, in IRC/lists elsewhere, but this URL was the earliest one I could find to capture it. - [[User:Tantek\|Tantek]]
	** 2011-10-26 [https://twitter.com/richardtvaughan/status/129235473414631424 confirmed by Richard Vaughan]:		** 2011-10-26 [https://twitter.com/richardtvaughan/status/129235473414631424 confirmed by Richard Vaughan]:
	*** "... Microformats can screw with existing CSS rules. ..."		*** "... Microformats can screw with existing CSS rules. ..."

Tantek: microformats-issues moved to issues: move to shorter and less redundant URL

2011-10-27T05:33:07Z

microformats-issues moved to issues: move to shorter and less redundant URL

← Older revision	Revision as of 05:33, 27 October 2011
(No difference)

Tantek: /* opened 2010 */ add Richard Vaughan confirmation of 2010 issue, and proposed resolution with fixing it in microformats-2

2011-10-27T04:34:49Z

opened 2010: add Richard Vaughan confirmation of 2010 issue, and proposed resolution with fixing it in microformats-2

← Older revision		Revision as of 04:34, 27 October 2011
Line 32:		Line 32:
	* <strong class="entry-title">microformats classes like 'url' or 'region' already in use</strong>. "Using class for the microformat markup is clearly a problem, in part because it’s so easy to overlap with other markup. Authors use classes like “url” or “region” all the time, and might not be aware of the hCard format. All sorts of markup might look like a microformat."		* <strong class="entry-title">microformats classes like 'url' or 'region' already in use</strong>. "Using class for the microformat markup is clearly a problem, in part because it’s so easy to overlap with other markup. Authors use classes like “url” or “region” all the time, and might not be aware of the hCard format. All sorts of markup might look like a microformat."
	** ACCEPTED. I this this was raised before, in IRC/lists elsewhere, but this URL was the earliest one I could find to capture it. - [[User:Tantek\|Tantek]]		** ACCEPTED. I this this was raised before, in IRC/lists elsewhere, but this URL was the earliest one I could find to capture it. - [[User:Tantek\|Tantek]]
	** ...		** 2011-10-26 [https://twitter.com/richardtvaughan/status/129235473414631424 confirmed by Richard Vaughan]:
			*** "... Microformats can screw with existing CSS rules. ..."
			** [https://twitter.com/richardtvaughan/status/129236380873261057 and follow-up same day also]:
			*** "microformats are the easiest as it's just CSS classes, but may be a pain to implement if those class names are already used."
			** ACCEPTED. PROPOSED RESOLUTION - we are fixing this with [[microformats-2]], all property names have prefixes to avoid such collisions. E.g. 'url' becomes 'u-url' and 'region' becomes 'p-region'. See [[microformats-2#h-card\|microformats 2: h-card properties]] for more. - [[User:Tantek\|Tantek]]
	</div>		</div>
	</div>		</div>

Tantek: /* Issues */ collect issue from 2010 on microformats classes like 'url' or 'region' already in use

2011-10-27T04:01:33Z

Issues: collect issue from 2010 on microformats classes like 'url' or 'region' already in use

@@ Line 20: / Line 20: @@
 == Issues ==
 === opened 2011 ===
-Issues opened in 2011.
+Issues opened/raised in 2011.
 * ...