faq - Revision history

GRegorLove: s///

2024-06-20T23:00:40Z

s/<source>/<syntaxhighlight>/

← Older revision		Revision as of 23:00, 20 June 2024
Line 47:		Line 47:
	E.g. using an h-card for the location of an h-event		E.g. using an h-card for the location of an h-event

	<~~source~~ lang=~~html4strict~~>		<syntaxhighlight lang="html">
	<span class="h-event">		<span class="h-event">
	<span class="p-name">HTML5 Developer Conference</span>,		<span class="p-name">HTML5 Developer Conference</span>,
Line 56:		Line 56:
	</span>		</span>
	</span>		</span>
	</~~source~~>		</syntaxhighlight>


Line 289:		Line 289:

	A. <code class="element"><span></code> and <code class="element"><div></code> are generic elements in HTML. When you use microformats, you should pick the most specific semantic element available for the semantics you are trying to express. You might, for example, apply <code>class="vevent"</code> to a <code><nowiki><tr></nowiki></code>, or <code>class="vcard"</code> to a <code><nowiki><p></nowiki></code>. Here is an example using more [[semantic HTML]] with a definition list to mark-up an hCard:		A. <code class="element"><span></code> and <code class="element"><div></code> are generic elements in HTML. When you use microformats, you should pick the most specific semantic element available for the semantics you are trying to express. You might, for example, apply <code>class="vevent"</code> to a <code><nowiki><tr></nowiki></code>, or <code>class="vcard"</code> to a <code><nowiki><p></nowiki></code>. Here is an example using more [[semantic HTML]] with a definition list to mark-up an hCard:
	<~~source~~ lang=~~html4strict~~>		<syntaxhighlight lang="html">
	<dl class="vcard">		<dl class="vcard">
	<dt class="category">Restaurant</dt>		<dt class="category">Restaurant</dt>
Line 306:		Line 306:
	<dd class="tel">+1.707.428.2210</dd>		<dd class="tel">+1.707.428.2210</dd>
	</dl>		</dl>
	</~~source~~>		</syntaxhighlight>

	== Class semantics ==		== Class semantics ==
Line 324:		Line 324:
	===Q. ''Does the order of class names matter?'' ===		===Q. ''Does the order of class names matter?'' ===
	A. No. The HTML class attribute is an unordered space separated set of class names. The order of classes in an class attribute do affect their meaning or use. E.g. these two divs' class names are equivalent:		A. No. The HTML class attribute is an unordered space separated set of class names. The order of classes in an class attribute do affect their meaning or use. E.g. these two divs' class names are equivalent:
	<~~source~~ lang=~~html4strict~~>		<syntaxhighlight lang="html">
	<div class="a b">...</div>		<div class="a b">...</div>
	<div class="b a">...</div>		<div class="b a">...</div>
	</~~source~~>		</syntaxhighlight>

	===Q. ''Do (X)HTML class names have semantics?''===		===Q. ''Do (X)HTML class names have semantics?''===
Line 404:		Line 404:

	Instead, you can use the <code>abbr</code> element and its <code>title</code> attribute to provide an expanded form of the information in cases where substituting the expanded form when reading the text in context reads correctly, e.g. inside an [[hCard]]:		Instead, you can use the <code>abbr</code> element and its <code>title</code> attribute to provide an expanded form of the information in cases where substituting the expanded form when reading the text in context reads correctly, e.g. inside an [[hCard]]:
	<~~source~~ lang=~~html4strict~~>		<syntaxhighlight lang="html">
	<abbr class="region" title="Connecticut">CT</abbr>		<abbr class="region" title="Connecticut">CT</abbr>
	</~~source~~>		</syntaxhighlight>

	[http://twitter.com/microformats/status/112556548877844481]		[http://twitter.com/microformats/status/112556548877844481]

Tantek: /* Can you mix properties and the root class name */ add a bit more explanation to the example

2023-10-09T05:18:31Z

Can you mix properties and the root class name: add a bit more explanation to the example

← Older revision		Revision as of 05:18, 9 October 2023
Line 59:		Line 59:


	Note the <code><span class="p-location h-card"></code> which specifies that the location of the ~~outer~~ [[h-event] is an entire [[h-card~~]] nested inside.~~		Note the <code><span class="p-location h-card"></code> which specifies that:
			* the <code>p-location</code> is a property of the surrounding <code>[[h-event]]</code>
			* the <em>value</em> of that h-event’s <code>p-location</code> is an entire embedded <code>h-card</code>

	Another example, inside an [[h-entry]], specifying the author as an h-card: <code><span class="p-author h-card"></code>		Another example, inside an [[h-entry]], specifying the author as an h-card: <code><span class="p-author h-card"></code>

GRegorLove: /* Usage/Verbiage */ close italics

2022-09-14T18:13:33Z

Usage/Verbiage: close italics

← Older revision		Revision as of 18:13, 14 September 2022
Line 418:		Line 418:
	A. Since the term "microformat" was established, it has been written in lowercase. This is a nod to its roots in the term "lowercase semantic web", in contrast to the uppercase "Semantic Web" which has long been tied to RDF and other technologies often viewed as impractical for the open web. In a few cases in the wild(citation needed), the term has been capitalized as "Microformat", perhaps due to proper noun capitalization conventions.		A. Since the term "microformat" was established, it has been written in lowercase. This is a nod to its roots in the term "lowercase semantic web", in contrast to the uppercase "Semantic Web" which has long been tied to RDF and other technologies often viewed as impractical for the open web. In a few cases in the wild(citation needed), the term has been capitalized as "Microformat", perhaps due to proper noun capitalization conventions.

	=== Q. ''Can you use microformat as an adjective or verb, as in "microformatted content" or "can you please microformat that page with an hCard?"===		=== Q. ''Can you use microformat as an adjective or verb, as in "microformatted content" or "can you please microformat that page with an hCard?"'' ===

	A. Because the word ''microformat'' is derived from the word '''format''', it makes logical sense that one can use the term as an adjective or verb, just as one would use the word '''format'''.		A. Because the word ''microformat'' is derived from the word '''format''', it makes logical sense that one can use the term as an adjective or verb, just as one would use the word '''format'''.

Tantek: /* Q. How does the use of class values for semantics interact with the use of class values for attaching CSS styles? */ update per experience, add link to not using the phrase "CSS class"

2022-09-12T17:37:08Z

Q. How does the use of class values for semantics interact with the use of class values for attaching CSS styles?: update per experience, add link to not using the phrase "CSS class"

← Older revision		Revision as of 17:37, 12 September 2022
Line 256:		Line 256:
	===Q. ''How does the use of class values for semantics interact with the use of class values for attaching CSS styles?''===		===Q. ''How does the use of class values for semantics interact with the use of class values for attaching CSS styles?''===

	A. The class attribute takes a space separated set of class names [http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.2 HTML4 reference]. Thus both author and microformat defined class names may be used in the same class attribute. ~~In addition, microformat~~ class names ~~provide the author with a consistent set of~~ class names ~~to use~~ for ~~styling~~. If the author is already using using specific class names, they can continue to do so~~, and include microformat class names~~. If the author is already using a class name that happens to also be a ~~microformat~~ class name, then the author may want to consider using contextual CSS class selectors to make sure ~~that avoid~~ any unintentional styling effects.		A. The class attribute takes a space separated set of class names [http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.2 HTML4 reference]. Thus both author and microformat defined class names may be used in the same class attribute. Experience has shown that the best practice is for authors to use their own class names for styling, and only use microformats class names for expressing microformats semantics. If the author is already using using specific class names, they can continue to do so. If the author is already using a class name that happens to also be a microformats class name, then the author may want to consider using contextual CSS class selectors to make sure to reduce any unintentional styling effects, or ideally use their own site-specific class names that are not microformats class names.

	See also:		See also:
Line 263:		Line 263:
	* [http://www.meyerweb.com/eric/thoughts/2004/07/18/competent-classing Competant Classing], by Eric Meyer for discussion of choosing class names in (X)HTML		* [http://www.meyerweb.com/eric/thoughts/2004/07/18/competent-classing Competant Classing], by Eric Meyer for discussion of choosing class names in (X)HTML
	* [http://www.microformats.org/blog/2005/10/19/more-than-styling/ Class attributes are about more than styling] - Ryan King dispells common misconceptions about the ''HTML'' class attribute.		* [http://www.microformats.org/blog/2005/10/19/more-than-styling/ Class attributes are about more than styling] - Ryan King dispells common misconceptions about the ''HTML'' class attribute.
			* [https://tantek.com/2012/353/b1/why-html-classes-css-class-selectors Why you should say HTML classes, CSS class selectors, or CSS pseudo-classes, but not CSS classes]

	===Q. ''Are class names case sensitive?'' ===		===Q. ''Are class names case sensitive?'' ===

Aaronpk: Replace with {{DISPLAYTITLE:}}

2020-07-18T16:22:34Z

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

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

	This page document frequently asked questions about microformats. For frequently asked questions from the [[press]], see [[press-faq]].		This page document frequently asked questions about microformats. For frequently asked questions from the [[press]], see [[press-faq]].

Tantek: improve wording a little for mf2 or mf1, and a few others

2019-01-25T19:50:45Z

improve wording a little for mf2 or mf1, and a few others

Tantek: /* Q. 'How do I find an answer to a question not mentioned here? */ Other

2018-05-24T01:48:15Z

Q. 'How do I find an answer to a question not mentioned here?: Other

← Older revision		Revision as of 01:48, 24 May 2018
Line 421:		Line 421:
	A. Because the word ''microformat'' is derived from the word '''format''', it makes logical sense that one can use the term as an adjective or verb, just as one would use the word '''format'''.		A. Because the word ''microformat'' is derived from the word '''format''', it makes logical sense that one can use the term as an adjective or verb, just as one would use the word '''format'''.

			== Other ==
	=== Q. '''How do I find an answer to a question not mentioned here?'' ===		=== Q. '''How do I find an answer to a question not mentioned here?'' ===

Tantek: How do I find an answer to a question not mentioned here? ask in irc

2018-05-24T01:47:44Z

How do I find an answer to a question not mentioned here? ask in irc

← Older revision		Revision as of 01:47, 24 May 2018
Line 420:		Line 420:

	A. Because the word ''microformat'' is derived from the word '''format''', it makes logical sense that one can use the term as an adjective or verb, just as one would use the word '''format'''.		A. Because the word ''microformat'' is derived from the word '''format''', it makes logical sense that one can use the term as an adjective or verb, just as one would use the word '''format'''.

			=== Q. '''How do I find an answer to a question not mentioned here?'' ===

			A. Join [[irc]] and ask!

	== See Also ==		== See Also ==
	* [[misconceptions]]		* [[misconceptions]]

Tantek: /* Wiki specific questions */ how do I pass a reCAPTCHA - do you feel ...

2018-05-24T01:46:27Z

Wiki specific questions: how do I pass a reCAPTCHA - do you feel ...

← Older revision		Revision as of 01:46, 24 May 2018
Line 69:		Line 69:

	A: First, read this: http://en.wikipedia.org/wiki/Wikipedia:Username . Second, real names are preferred to pseudonyms/handles etc. Real names encourage better transparency and accountability. Third, the most common problem creating a user name is forgetting to capitalize the first letter of the user name. Try using a WikiCase version of your full name as username, e.g. RyanKing.		A: First, read this: http://en.wikipedia.org/wiki/Wikipedia:Username . Second, real names are preferred to pseudonyms/handles etc. Real names encourage better transparency and accountability. Third, the most common problem creating a user name is forgetting to capitalize the first letter of the user name. Try using a WikiCase version of your full name as username, e.g. RyanKing.

			===Q: ''How do I pass a reCAPTCHA V1'' ===

			A: Do you feel that there's a part of you that's missing?

	== Email list ==		== Email list ==

Kevin Marks: /* Q. Why don't microformats use the HTML5 data- attributes to embed data? */ update refs; typo

2017-08-01T14:52:00Z

Q. Why don't microformats use the HTML5 data- attributes to embed data?: update refs; typo

← Older revision		Revision as of 14:52, 1 August 2017
Line 353:		Line 353:

	<abbr title='Answer'>A</abbr>:		<abbr title='Answer'>A</abbr>:
	# <a href='http://www.w3.org/TR/html5/'>HTML5</a> is a draft specification, and microformats are built to work with the web ''as it exists today''. The rules for processing <code>data-</code> could change.		# The HTML5 <code>data-</code> attribute specification expressly forbids the microformats use-case:<blockquote cite='https://www.w3.org/TR/html5/dom.html#embedding-custom-non-visible-data-with-the-data-*-attributes'>Custom data attributes are intended to store custom data private to the page or application, for which there are no more appropriate attributes or elements. These attributes are not intended for use by software that is independent of the site that uses the attributes. [...] It would be inappropriate, however, for the user to use generic software not associated with that music site to search for tracks of a certain length by looking at this data. This is because these attributes are intended for use by the site's own scripts, and are not a generic extension mechanism for publicly-usable metadata.</blockquote>— <cite>[http://www.w3.org/TR/html5/semantics.html#embedding HTML5 · Embedding custom-non-visible data]</cite>
	# The HTML5 <code>data-</code> attribute specification expressly forbids the microformats use-case:<blockquote cite='~~http~~://www.w3.org/TR/html5/~~semantics~~.html#embedding'>~~User agents must not derive any implementation behavior from these~~ attributes or ~~values~~. ~~Specifications~~ intended for user ~~agents must~~ not ~~define~~ these attributes ~~to have any meaningful values~~.</blockquote>— <cite>[http://www.w3.org/TR/html5/semantics.html#embedding HTML5 · Embedding custom-non-visible data]</cite>		# Microformats are designed around the principle that non-visible data is undesirable, harder to maintain, more prone to inaccuracy (as no-one will see the data on the page to notice errors). The <code>data-</code> attribute is explicitly designed for non-visible data.
	# Microformats are designed around the ~~principal~~ that non-visible data is undesirable, harder to maintain, more prone to inaccuracy (as no-one will see the data on the page to notice errors). The <code>data-</code> attribute is explicitly designed for non-visible data.

	== Hidden Content ==		== Hidden Content ==

← Older revision		Revision as of 19:50, 25 January 2019
Line 15:		Line 15:
	From: http://indiewebcamp.com/faq#How_should_I_markup_my_blog		From: http://indiewebcamp.com/faq#How_should_I_markup_my_blog

	=== When should I use microformats2 ~~over~~ microformats1 ===		=== When should I use microformats2 or microformats1 ===
	''On sites that don't currently have microformats, should microformats2 be utilized in ~~favor over v1~~? E.g. for a rather large site.''		<span id="When_should_I_use_microformats2_over_microformats1">''On sites that don't currently have microformats, should microformats2 be utilized in or classic microformats? E.g. for a rather large site.''</span>

	A: [[microformats2]] use less markup (are even simpler) than ~~microformats1~~, so in general ~~it's~~ preferred for adding to sites.		A: [[microformats2]] use less markup (are even simpler) than classic (v1) microformats, so in general microformats2 is preferred for adding to sites.

	~~However, you~~ may want to add one v1 microformat for each page that describes the primary subject of the page.		You may also want to add one v1 microformat for each page that describes the primary subject of the page.

	You can easily use both:		You can easily use both:
	* if a page is about a '''person''' or '''company''', add an '''[[hCard]]''' (and '''[[h-card]]''') to markup the info about the person/company.		* if a page is about a '''person''' or '''company''', add an '''[[hCard]]''' (and '''[[h-card]]''') to markup the info about the person/company.
	* Or if the page is for an '''event''', add an '''[[hCalendar]]''' (and '''[[h-event]]''') about the event info.		* Or if the page is for an '''event''', add an '''[[hCalendar]]''' <code>vevent</code> (and '''[[h-event]]''') about the event info.
	* Similarly with a page that is a '''[[hReview\|review]], [[hProduct\|product]], [[hAtom\|blog post]], or [[hRecipe\|recipe]]'''.		* Similarly with a page that is a '''[[hReview\|review]], [[hProduct\|product]], [[hAtom\|blog post]], or [[hRecipe\|recipe]]'''.
	See the [[Main_Page#Specifications\|list of specs and drafts]] for more recommended top level microformats.		See the [[Main_Page#Specifications\|list of specs and drafts]] for more recommended top level microformats.

	For all other references to things on the page, links to or mentions of [[h-card\|people]]/[[h-event\|events]]/[[h-cite\|citations]]/products, etc. use microformats2.		For all other references to things on the page, links to or mentions of [[h-card\|people]]/[[h-event\|events]]/[[h-cite\|citations]]/products, etc. use [[microformats2]].

	=== What microformats should I use for backward compatibility ===		=== What microformats should I use for backward compatibility ===
	For backwards compatibility, e.g. with some [[search-engines]], it's sufficient to include one v1 microformat for each page that best describes what that page is about. See above '''When should I use microformats2 ~~over~~ microformats1''' for more details.		For backwards compatibility, e.g. with some [[search-engines]], it's sufficient to include one v1 microformat for each page that best describes what that page is about. See above '''When should I use microformats2 or microformats1''' for more details.


Line 37:		Line 37:
	=== Can you mix properties and the root class name ===		=== Can you mix properties and the root class name ===
	''<span id="nesting-properties">Can you put properties on the same element as the root class for a microformat? E.g. span class="h-card p-org"?</span>''		''<span id="nesting-properties">Can you put properties on the same element as the root class for a microformat? E.g. span class="h-card p-org"?</span>''
	* No, ~~because~~ property elements must be inside the root class name element.		* No, property elements must be inside the root class name element.

	It will result in more confusion for parsers which may be parsing nested microformats. In this case in the question, you need two elements:		Mixing will result in more confusion for parsers which may be parsing nested microformats. In this case in the question, you need two elements:
	* WRONG: <code><span class="h-card p-org"></code>		* WRONG: <code><span class="h-card p-org"></code>
	* RIGHT: <code><span class="h-card"><span class="p-org"></code>		* RIGHT: <code><span class="h-card"><span class="p-org"></code>
Line 110:		Line 110:
	If you're looking for minimal markup addition, just use microformats.		If you're looking for minimal markup addition, just use microformats.

	If you want to use both ~~to cover all your bases~~, you ~~can~~ do so because they don't interfere.		If you want to use both, you may do so because they don't interfere.

	===Q: ''Are microformats dependent upon (X)HTML?''===		===Q: ''Are microformats dependent upon (X)HTML?''===

	A: Microformats ~~are made to be embeddable~~. ~~They~~ can be embedded in (~~X)HTML, RSS,~~ Atom or ~~anywhere (X~~)~~HTML is allowed~~.		A: No. Microformats work with the class attribute in HTML5, SVG etc., and can also be embedded in any XML (like Atom or RSS), as embedded XHTML.