microformats2-prefixes - Revision history

Kevin Marks: /* naming conventions for generic parsing */

2021-08-17T15:32:39Z

naming conventions for generic parsing

← Older revision		Revision as of 15:32, 17 August 2021
Line 13:		Line 13:
	* '''"h-*" for root class names''', e.g. "h-card", "h-event", "h-entry"		* '''"h-*" for root class names''', e.g. "h-card", "h-event", "h-entry"
	* '''"p-*" for plain (text) properties''', e.g. "p-name", "p-summary"		* '''"p-*" for plain (text) properties''', e.g. "p-name", "p-summary"
	** generic ~~plan~~ text parsing, element text in general, certain HTML elements use special attributes first, e.g. img/alt, abbr/title.		** generic plain text parsing, element text in general, certain HTML elements use special attributes first, e.g. img/alt, abbr/title.
	* '''"u-*" for URL properties''', e.g. "u-url", "u-photo", "u-logo"		* '''"u-*" for URL properties''', e.g. "u-url", "u-photo", "u-logo"
	** special parsing required: prefer a/href, img/src, object/data etc. attributes to element contents.		** special parsing required: prefer a/href, img/src, object/data etc. attributes to element contents.

Tantek: /* see also */ rm link which was a self-redirect

2021-03-31T01:00:17Z

see also: rm link which was a self-redirect

← Older revision		Revision as of 01:00, 31 March 2021
Line 308:		Line 308:
	* [[microformats-2]]		* [[microformats-2]]
	* [[microformats-2-brainstorming]]		* [[microformats-2-brainstorming]]
	* [[microformats-2-prefixes]]
	* [[microformats-2-faq]]		* [[microformats-2-faq]]

Aaronpk: Replace with {{DISPLAYTITLE:}}

2020-07-18T16:30:28Z

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

← Older revision		Revision as of 16:30, 18 July 2020
Line 1:		Line 1:
	~~<entry-title>~~microformats2 prefix conventions~~</entry-title>~~		{{DISPLAYTITLE:microformats2 prefix conventions}}

	[[microformats2]] uses a small number of prefixes to distinguish microformats2 class names from other class names.		[[microformats2]] uses a small number of prefixes to distinguish microformats2 class names from other class names.

Tantek: editorial improvements without changing meaning

2018-11-19T05:43:07Z

editorial improvements without changing meaning

← Older revision		Revision as of 05:43, 19 November 2018
Line 1:		Line 1:
	<entry-title>~~microformats 2~~ prefix conventions</entry-title>		<entry-title>microformats2 prefix conventions</entry-title>

	[[~~microformats 2~~]] uses a small number of prefixes to distinguish ~~microformats 2~~ class names from other class names.		[[microformats2]] uses a small number of prefixes to distinguish microformats2 class names from other class names.

	== ~~microformats 2~~ prefixes ==		== microformats2 prefixes ==
	=== naming conventions for generic parsing ===		=== naming conventions for generic parsing ===
	The naming conventions for microformats class names make it obvious when:'''		The naming conventions for microformats class names make it obvious when:'''
	* a class name represents a microformat '''root class name'''		* a class name represents a microformat '''root class name'''
	* a class name represents a microformat '''property name'''		* a class name represents a microformat '''property name'''
	* a class name represents a microformat '''property that needs special parsing''' ~~(specific type of property).~~		* a class name represents a microformat '''property that needs special parsing'''

	In particular ~~- derived from the real world examples of existing proven microformats~~:		In particular:
	* '''"h-*" for root class names''', e.g. "h-card", "h-event", "h-entry"		* '''"h-*" for root class names''', e.g. "h-card", "h-event", "h-entry"
	* '''"p-*" for plain (text) properties''', e.g. "p-fn", "p-summary"		* '''"p-*" for plain (text) properties''', e.g. "p-name", "p-summary"
	** generic plan text parsing, element text in general, certain HTML elements use special attributes first, e.g. img/alt, abbr/title.		** generic plan text parsing, element text in general, certain HTML elements use special attributes first, e.g. img/alt, abbr/title.
	* '''"u-*" for URL properties''', e.g. "u-url", "u-photo", "u-logo"		* '''"u-*" for URL properties''', e.g. "u-url", "u-photo", "u-logo"
Line 49:		Line 49:
	</source>		</source>

	=== ~~COMPATIBILITY~~ ===		=== backwards compatibility ===

	microformats2 is backwards ~~compatible in that it permits~~ content authors to markup with both old and new class names for compatibility with old tools.		microformats2 provides backwards compatibility by enabling content authors to markup with both old and new class names for compatibility with old tools.

	Here is a simple backcompat example:		Here is a simple backcompat example:
Line 87:		Line 87:
	etc.		etc.

	Note that these are merely string '''prefixes''', not bound to any URL, and thus not namespaces in any practical sense of the word. This is quite an important distinction, as avoiding the need to bind to a URL has made them easier to support and use.		Note that these are merely string '''prefixes''', not bound to any URL, and thus not namespaces in any practical sense of the word. This is quite an important distinction, as avoiding the need to bind to a URL has made them easier to support and use.

	This use of vendor specific CSS properties has in recent years allowed the larger web design/development/~~implementor~~ communities to experiment and iterate on new CSS features while the features were being developed and standardized.		This use of vendor specific CSS properties has in recent years allowed the larger web design/development/implementer communities to experiment and iterate on new CSS features while the features were being developed and standardized.

	The benefits have been two-fold:		The benefits have been two-fold:

GRegorLove: /* microformats2 examples */ no p-fn

2017-07-13T00:09:52Z

microformats2 examples: no p-fn

← Older revision		Revision as of 00:09, 13 July 2017
Line 67:		Line 67:
	<source lang=html4strict>		<source lang=html4strict>
	<h1 class="h-card vcard">		<h1 class="h-card vcard">
	<a class="~~p-fn~~ u-url n fn url" href="http://factoryjoe.com/">		<a class="u-url n fn url" href="http://factoryjoe.com/">
	<span class="p-given-name given-name">Chris</span>		<span class="p-given-name given-name">Chris</span>
	<abbr class="p-additional-name additional-name">R.</abbr>		<abbr class="p-additional-name additional-name">R.</abbr>

GRegorLove: /* microformats2 examples */ add back "n" - not a typo :)

2017-07-13T00:04:55Z

microformats2 examples: add back "n" - not a typo :)

← Older revision		Revision as of 00:04, 13 July 2017
Line 67:		Line 67:
	<source lang=html4strict>		<source lang=html4strict>
	<h1 class="h-card vcard">		<h1 class="h-card vcard">
	<a class="p-fn u-url fn url" href="http://factoryjoe.com/">		<a class="p-fn u-url n fn url" href="http://factoryjoe.com/">
	<span class="p-given-name given-name">Chris</span>		<span class="p-given-name given-name">Chris</span>
	<abbr class="p-additional-name additional-name">R.</abbr>		<abbr class="p-additional-name additional-name">R.</abbr>

GRegorLove: /* microformats2 examples */ fixes

2017-07-13T00:00:35Z

microformats2 examples: fixes

← Older revision		Revision as of 00:00, 13 July 2017
Line 31:		Line 31:
	<source lang=html4strict>		<source lang=html4strict>
	<h1 class="h-card">		<h1 class="h-card">
	~~<span class="p-fn">~~		<span class="p-given-name">Chris</span>
	<span class="p-given-name">Chris</span>		<abbr class="p-additional-name">R.</abbr>
	<abbr class="p-additional-name">R.</abbr>		<span class="p-family-name">Messina</span>
	<span class="p-family-name">Messina~~</span>~~
	</span>
	</h1>		</h1>
	</source>		</source>
Line 43:		Line 41:
	<source lang=html4strict>		<source lang=html4strict>
	<h1 class="h-card">		<h1 class="h-card">
	<a class="~~p-fn~~ u-url" href="http://factoryjoe.com/">		<a class="u-url" href="http://factoryjoe.com/">
	<span class="p-given-name">Chris</span>		<span class="p-given-name">Chris</span>
	<abbr class="p-additional-name">R.</abbr>		<abbr class="p-additional-name">R.</abbr>
Line 69:		Line 67:
	<source lang=html4strict>		<source lang=html4strict>
	<h1 class="h-card vcard">		<h1 class="h-card vcard">
	<a class="p-fn u-url n fn url" href="http://factoryjoe.com/">		<a class="p-fn u-url fn url" href="http://factoryjoe.com/">
	<span class="p-given-name given-name">Chris</span>		<span class="p-given-name given-name">Chris</span>
	<abbr class="p-additional-name additional-name">R.</abbr>		<abbr class="p-additional-name additional-name">R.</abbr>

Tantek: 2

2017-06-25T17:39:05Z

← Older revision		Revision as of 17:39, 25 June 2017
Line 53:		Line 53:
	=== COMPATIBILITY ===		=== COMPATIBILITY ===

	~~microformats 2.0~~ is backwards compatible in that it permits content authors to markup with both old and new class names for compatibility with old tools.		microformats2 is backwards compatible in that it permits content authors to markup with both old and new class names for compatibility with old tools.

	Here is a simple backcompat example:		Here is a simple backcompat example:

Tantek: simplify top of page for microformats2 prefix summaries, examples, clean up a bit

2017-06-25T17:37:06Z

simplify top of page for microformats2 prefix summaries, examples, clean up a bit

Show changes

Andy sky: /* COMPATIBILITY */ typo

2017-01-30T00:27:54Z

COMPATIBILITY: typo

← Older revision		Revision as of 00:27, 30 January 2017
Line 159:		Line 159:
	=== COMPATIBILITY ===		=== COMPATIBILITY ===

	microformats 2.0 is backwards compatible in that in permits content authors to markup with both old and new class names for compatibility with old tools.		microformats 2.0 is backwards compatible in that it permits content authors to markup with both old and new class names for compatibility with old tools.

	Here is a simple example:		Here is a simple example:
Line 182:		Line 182:
	</h1>		</h1>
	</source>		</source>


	== vendor extensions ==		== vendor extensions ==