microformats2-brainstorming - Revision history

Btrem: /* adopt itemref */ Adds quote about itemref from whatwg html5 spec.

2020-12-14T23:41:26Z

adopt itemref: Adds quote about itemref from whatwg html5 spec.

← Older revision		Revision as of 23:41, 14 December 2020
Line 34:		Line 34:
	* Wasn't RDFa a ''stable'' augmentation of HTML, and yet we resisted incorporated attributes from it?		* Wasn't RDFa a ''stable'' augmentation of HTML, and yet we resisted incorporated attributes from it?
	** In practice, no, RDFa has continued to change evolve (which is good) in response to market feedback about its complexity. There was very little real world use (and thus exercising) of RDFa until Google provided it as a Rich Snippets alternative syntax in 2009. At this point, it may be reasonable to also consider attributes from RDFa (e.g. 'vocab' instead of 'profile'), however for this particular purpose (providing inclusion functionality), the 'itemref' attribute/feature makes the most sense.		** In practice, no, RDFa has continued to change evolve (which is good) in response to market feedback about its complexity. There was very little real world use (and thus exercising) of RDFa until Google provided it as a Rich Snippets alternative syntax in 2009. At this point, it may be reasonable to also consider attributes from RDFa (e.g. 'vocab' instead of 'profile'), however for this particular purpose (providing inclusion functionality), the 'itemref' attribute/feature makes the most sense.

			Note that itemref is only sort of part of microdata. According to the [https://html.spec.whatwg.org/multipage/microdata.html#attr-itemref whatwg html spec]:
			<blockquote cite="https://html.spec.whatwg.org/multipage/microdata.html#attr-itemref">
			The itemref attribute is not part of the microdata data model. It is merely a syntactic construct to aid authors in adding annotations to pages where the data to be annotated does not follow a convenient tree structure. For example, it allows authors to mark up data in a table so that each column defines a separate item, while keeping the properties in the cells.
			</blockquote>
	</div>		</div>

Tantek: original brainstorming see * microformats2-origins, note long ago accepted/rejected brainstorms, update doc url idea,

2018-04-03T16:25:42Z

original brainstorming see * microformats2-origins, note long ago accepted/rejected brainstorms, update doc url idea,

Show changes

Tantek: Reverted edits by Videosxxxde (Talk) to last version by TomMorris

2016-02-23T18:46:52Z

Reverted edits by Videosxxxde (Talk) to last version by TomMorris

← Older revision		Revision as of 18:46, 23 February 2016
Line 157:		Line 157:
	* [[microformats2-faq]]		* [[microformats2-faq]]
	* [[html-stripping-examples]]		* [[html-stripping-examples]]
	~~[http://http://videosxxx.portfolik.com/ perfil title]~~

Videosxxxde at 13:17, 23 February 2016

2016-02-23T13:17:20Z

← Older revision		Revision as of 13:17, 23 February 2016
Line 157:		Line 157:
	* [[microformats2-faq]]		* [[microformats2-faq]]
	* [[html-stripping-examples]]		* [[html-stripping-examples]]
			[http://http://videosxxx.portfolik.com/ perfil title]

TomMorris: /* see also */ linking to experimental properties

2015-07-11T14:49:28Z

see also: linking to experimental properties

← Older revision		Revision as of 14:49, 11 July 2015
Line 150:		Line 150:

	== see also ==		== see also ==
	* [[~~microformats~~-2]]		* [[microformats2]]
	* [[~~microformats~~-2-~~brainstorming~~]]		* [[microformats2-brainstorming]]
	* [[~~microformats-2~~-prefixes]]		* [[microformats2-experimental-properties]]
	* [[~~microformats-2~~-implied-properties]]		* [[microformats2-prefixes]]
	* [[~~microformats-2~~-faq]]		* [[microformats2-implied-properties]]
			* [[microformats2-faq]]
	* [[html-stripping-examples]]		* [[html-stripping-examples]]

TomMorris: adding microformats2-mime-type

2015-04-13T20:19:11Z

adding microformats2-mime-type

← Older revision		Revision as of 20:19, 13 April 2015
Line 136:		Line 136:

	Note: we should analyze [[hreview-examples-in-wild]] to see if there are any that actually depend on parsing for "item", or if simply looking for "fn", "photo", and "url" directly inside a root class name of "hreview" is sufficient. If so, we should '''DROP''' the backward-compat parsing for the class name "item" as it may otherwise produce too many false positives ("item" is a fairly common term).		Note: we should analyze [[hreview-examples-in-wild]] to see if there are any that actually depend on parsing for "item", or if simply looking for "fn", "photo", and "url" directly inside a root class name of "hreview" is sufficient. If so, we should '''DROP''' the backward-compat parsing for the class name "item" as it may otherwise produce too many false positives ("item" is a fairly common term).

			=== register a mime type? ===
			See [[microformats2-mime-type]].

	== rejected ideas ==		== rejected ideas ==

TomMorris: /* see also */ linking to html-stripping-examples

2013-09-14T10:57:32Z

see also: linking to html-stripping-examples

← Older revision		Revision as of 10:57, 14 September 2013
Line 152:		Line 152:
	* [[microformats-2-implied-properties]]		* [[microformats-2-implied-properties]]
	* [[microformats-2-faq]]		* [[microformats-2-faq]]
			* [[html-stripping-examples]]

Tantek: add items hash wrappers to JSON examples that should have been there ages ago

2013-05-09T21:19:28Z

add items hash wrappers to JSON examples that should have been there ages ago

← Older revision		Revision as of 21:19, 9 May 2013
Line 31:		Line 31:
	Parsed JSON per microformats2 properties:		Parsed JSON per microformats2 properties:
	<source lang=javascript>		<source lang=javascript>
	[{		{
	"type": ["h-card"],		"items": [{
	"properties": {		"type": ["h-card"],
	"name": ["Tantek Çelik"],		"properties": {
	"url": ["https://twitter.com/t",		"name": ["Tantek Çelik"],
	"http://github.com/tantek"]		"url": ["https://twitter.com/t",
	}		"http://github.com/tantek"]
	}]		}
			}]
			}
	</source>		</source>

	We could incorporate rel property parsing either as just another property (like a 'u-' property) scoped to the microformat:		We could incorporate rel property parsing either as just another property (like a 'u-' property) scoped to the microformat:
	<source lang=javascript>		<source lang=javascript>
	[{		{
	"type": ["h-card"],		"items": [{
	"properties": {		"type": ["h-card"],
	"name": ["Tantek Çelik"],		"properties": {
	"url": ["https://twitter.com/t",		"name": ["Tantek Çelik"],
	"http://github.com/tantek"],		"url": ["https://twitter.com/t",
	"rel-me": ["https://twitter.com/t",		"http://github.com/tantek"],
	"http://github.com/tantek"]		"rel-me": ["https://twitter.com/t",
	}		"http://github.com/tantek"]
	}]		}
			}]
			}

	</source>		</source>

	Or as always within global scope (closer to HTML5's currently defined scoping for 'rel' attributed links in a document):		Or as always within global scope (closer to HTML5's currently defined scoping for 'rel' attributed links in a document):
	<source lang=javascript>		<source lang=javascript>
	[{"url": "http://tantek.com/",		{
	"rel-stylesheet": ["...", "..."],		"items": [{
	"rel-me": ["https://twitter.com/t",		"url": "http://tantek.com/",
	"http://github.com/tantek"]		"rel-stylesheet": ["...", "..."],
	},		"rel-me": ["https://twitter.com/t",
	{		"http://github.com/tantek"]
	"type": ["h-card"],		},
	"properties": {		{
	"name": ["Tantek Çelik"],		"type": ["h-card"],
	"url": ["https://twitter.com/t",		"properties": {
	"http://github.com/tantek"],		"name": ["Tantek Çelik"],
	}		"url": ["https://twitter.com/t",
	}]		"http://github.com/tantek"],
			}
			}]
			}
	</source>		</source>

Tantek: move back-compat parsing of "item" class name to brainstorming to capture it until we can determine whether it is necessary.

2013-01-16T16:03:08Z

move back-compat parsing of "item" class name to brainstorming to capture it until we can determine whether it is necessary.

@@ Line 105: / Line 105: @@
 ** In practice, no, RDFa has continued to change evolve (which is good) in response to market feedback about its complexity. There was very little real world use (and thus exercising) of RDFa until Google provided it as a Rich Snippets alternative syntax in 2009. At this point, it may be reasonable to also consider attributes from RDFa (e.g. 'vocab' instead of 'profile'), however for this particular purpose (providing inclusion functionality), the 'itemref' attribute/feature makes the most sense.
 </div>
 == rejected ideas ==

Tantek: microformats-2-brainstorming moved to microformats2-brainstorming

2012-10-16T01:12:13Z

microformats-2-brainstorming moved to microformats2-brainstorming

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