microformats2-implied-properties - Revision history

Aaronpk: Replace with {{DISPLAYTITLE:}}

2020-07-18T16:29:47Z

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

← Older revision		Revision as of 16:29, 18 July 2020
Line 1:		Line 1:
	~~<entry-title>~~microformats2 implied properties~~</entry-title>~~		{{DISPLAYTITLE:microformats2 implied properties}}
	== summary ==		== summary ==
	As part of the further simplifications in [[microformats-2]], the following generic properties are automatically implied by microformats with only a root class name with certain common semantic markup patterns.		As part of the further simplifications in [[microformats-2]], the following generic properties are automatically implied by microformats with only a root class name with certain common semantic markup patterns.

TomMorris: /* see also */ adding experimental properties link

2015-07-11T14:50:13Z

see also: adding experimental properties link

← Older revision		Revision as of 14:50, 11 July 2015
Line 194:		Line 194:
	* [[microformats2]]		* [[microformats2]]
	* [[microformats2-brainstorming]]		* [[microformats2-brainstorming]]
			* [[microformats2-experimental-properties]]
	* [[microformats2-prefixes]]		* [[microformats2-prefixes]]
	* [[microformats2-implied-properties]]		* [[microformats2-implied-properties]]
	* [[microformats2-parsing]]		* [[microformats2-parsing]]
	* [[microformats2-faq]]		* [[microformats2-faq]]

Barnabywalters: /* hyperlinked image and name photo url properties */ Clarified implied .h-card > img parsing

2013-06-03T17:11:31Z

hyperlinked image and name photo url properties: Clarified implied .h-card > img parsing

← Older revision		Revision as of 17:11, 3 June 2013
Line 110:		Line 110:
	Often proper noun references on web pages are a representative image of the proper noun that is hyperlinked to a page about that proper noun.		Often proper noun references on web pages are a representative image of the proper noun that is hyperlinked to a page about that proper noun.

	Thus if a microformat is on a hyperlink element with only a root class name and no properties, and that element has ~~but one~~ child element that is an image, then in addition to implying the the URL from its <code>href</code>, the <code>src</code> of the child image element is parsed as the '''<code>u-photo</code>''' property of the microformat, and if present, its <code>alt</code> attribute is parsed as the '''<code>p-name</code> property of the microformat.		Thus if a microformat is on a hyperlink element with only a root class name and no properties, and that element has a single child element and that element is an image, then in addition to implying the the URL from its <code>href</code>, the <code>src</code> of the child image element is parsed as the '''<code>u-photo</code>''' property of the microformat, and if present, its <code>alt</code> attribute is parsed as the '''<code>p-name</code> property of the microformat.

	Markup example:		Markup example:

Tantek: /* root class on one element */ add example/use-case for abbr implying 'name' property

2012-11-07T19:15:19Z

root class on one element: add example/use-case for abbr implying 'name' property

@@ Line 163: / Line 163: @@
 === root class on one element ===
 Let's consider root class only on:
-* '''<code>&lt;abbr class="h-card" title&gt;</code>''' - imply '''<code>p-name</code>''' from <code>title</code>
+* '''<code>&lt;abbr class="h-card" title&gt;</code>''' - imply '''<code>p-name</code>''' from <code>title</code>. Example(s)/use-case(s):
 * '''<code>&lt;object class="h-card" type="image/..." data="..."></code>''' - imply '''<code>u-photo</code>''' from <code>data</code> and '''<code>p-name</code>''' from text contents as with elements in general.
 * ...

Tantek: object[data] works wherever img[src] does.

2012-10-25T00:27:06Z

object[data] works wherever img[src] does.

← Older revision		Revision as of 00:27, 25 October 2012
Line 98:		Line 98:
	}		}
	</source>		</source>

			An object element with a data attribute works the same way as the img element with its src attribute.

	to-do:		to-do:
Line 129:		Line 131:
	}		}
	</source>		</source>

			An object element with a data attribute works the same way as the img element with its src attribute. E.g. '''<code><a class="h-card" href><object type="image/..." data="..."></code>''' in addition to implying '''<code>u-url</code>''' from the <code>href</code>, implies '''<code>u-photo</code>''' from the object element's <code>data</code>, as well as '''<code>p-name</code>''' from the text contents of the object as with elements in general.

	use-cases:		use-cases:
Line 171:		Line 175:

	=== root element and one child ===		=== root element and one child ===
	* '''<code><a class="h-card" href><object type="image/..." data="..."></code>''' - imply '''<code>u-url</code>''' from <code>href</code> and imply '''<code>u-photo</code>''' from the object element's <code>data</code> and '''<code>p-name</code>''' from text contents as with elements in general.		* '''<code><a class="h-card" href><abbr title></code>''' - imply '''<code>u-url</code>''' from <code>href</code> and imply '''<code>p-name</code>''' from the abbr element's <code>title</code>. Similar to the abbr root element case above (if that's allowed, we should strongly consider allowing this too).
	* '''<code><a class="h-card" href><abbr title></code>''' - imply '''<code>u-url</code>''' from <code>href</code> and imply '''<code>p-name</code>''' from the abbr element's <code>title</code>

	== see also ==		== see also ==

Tantek: /* root class only and name property */ replace issue with a link to the FAQ and a short inline answer.

2012-10-23T20:37:56Z

root class only and name property: replace issue with a link to the FAQ and a short inline answer.

← Older revision		Revision as of 20:37, 23 October 2012
Line 36:		Line 36:
	* every single proper noun on any web page.		* every single proper noun on any web page.

	~~issues~~:		related FAQ:
	* ~~may not work for all microformats, e.g. how would~~ [[adr~~]] or [[~~geo]] ~~work with this~~?		* [[microformats2-faq#how_do_h-adr_and_h-geo_work_with_an_implied_name_property\|how do instances of h-adr and h-geo work with implied names]]? short answer: (implied) names are useful for labeling them when in lists.

	=== aside name vs fn ===		=== aside name vs fn ===

Tantek: parsing

2012-10-16T01:38:50Z

parsing

← Older revision		Revision as of 01:38, 16 October 2012
Line 1:		Line 1:
	<entry-title>~~microformats 2~~ implied properties</entry-title>		<entry-title>microformats2 implied properties</entry-title>
	== summary ==		== summary ==
	As part of the further simplifications in [[microformats-2]], the following generic properties are automatically implied by microformats with only a root class name with certain common semantic markup patterns.		As part of the further simplifications in [[microformats-2]], the following generic properties are automatically implied by microformats with only a root class name with certain common semantic markup patterns.
Line 144:		Line 144:
	** minimal markup example with real values: http://krijnhoetmer.nl/irc-logs/microformats/20120901#l-150 from aaronpk		** minimal markup example with real values: http://krijnhoetmer.nl/irc-logs/microformats/20120901#l-150 from aaronpk
	*** similar: https://gist.github.com/3585643 - has an explicit span around the text after the image, but is otherwise similar. If there is an actual use case for having the second child span around the visible text, then we should consider expanding to allow implied properties for that too (general pattern of image and then something else which has the name, e.g. span/b etc.).		*** similar: https://gist.github.com/3585643 - has an explicit span around the text after the image, but is otherwise similar. If there is an actual use case for having the second child span around the visible text, then we should consider expanding to allow implied properties for that too (general pattern of image and then something else which has the name, e.g. span/b etc.).

			== parsing ==
			See: http://microformats.org/wiki/microformats2-parsing#parsing_for_implied_properties

	== to do ==		== to do ==

Tantek: microformats-2-implied-properties moved to microformats2-implied-properties

2012-10-16T01:11:25Z

microformats-2-implied-properties moved to microformats2-implied-properties

← Older revision	Revision as of 01:11, 16 October 2012
(No difference)

Tantek: parsing

2012-10-16T01:11:10Z

parsing

← Older revision		Revision as of 01:11, 16 October 2012
Line 172:		Line 172:

	== see also ==		== see also ==
	* [[~~microformats-2~~]]		* [[microformats2]]
	* [[~~microformats-2~~-brainstorming]]		* [[microformats2-brainstorming]]
	* [[~~microformats-2~~-prefixes]]		* [[microformats2-prefixes]]
	* [[~~microformats-2~~-implied-properties]]		* [[microformats2-implied-properties]]
	* [[~~microformats~~-2-faq]]		* [[microformats2-parsing]]
			* [[microformats2-faq]]

Tantek: promote a few more root class with one child element markup patterns from consideration to inclusion based on real-world uses

2012-09-21T03:06:53Z

promote a few more root class with one child element markup patterns from consideration to inclusion based on real-world uses

@@ Line 129: / Line 129: @@
+}
 </source>
 use-cases:
 * nearly every social networking site that shows a grid of people without text already does so with hyperlinked img tags and their names in the alt attribute.
 == additional markup patterns to consider ==
@@ Line 158: / Line 170: @@
 * '''<code>&lt;a class="h-card" href>&lt;object type="image/..." data="..."></code>''' - imply '''<code>u-url</code>''' from <code>href</code> and imply '''<code>u-photo</code>''' from the object element's <code>data</code> and '''<code>p-name</code>''' from text contents as with elements in general.
 * '''<code>&lt;a class="h-card" href>&lt;abbr title&gt;</code>''' - imply '''<code>u-url</code>''' from <code>href</code> and imply '''<code>p-name</code>''' from the abbr element's <code>title</code>
 == see also ==