representative-object-brainstorming - Revision history

Aaronpk: Replace with {{DISPLAYTITLE:}}

2020-07-18T16:32:44Z

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

← Older revision		Revision as of 16:32, 18 July 2020
Line 1:		Line 1:
	~~<entry-title>~~Microformat Objects Representing an Entire Page~~</entry-title>~~		{{DISPLAYTITLE:Microformat Objects Representing an Entire Page}}
	Pages may (and often do) contain multiple microformats; objects of different vocabularies, multiple objects from the same vocabulary, and objects from other sources of structure data. There are use cases (such as Search Engine Results) that want to use microformats in the page to better represent the page, but must work out which object is the most important, the one that really represents ''the page'', as opposed to being an incidental piece of data.		Pages may (and often do) contain multiple microformats; objects of different vocabularies, multiple objects from the same vocabulary, and objects from other sources of structure data. There are use cases (such as Search Engine Results) that want to use microformats in the page to better represent the page, but must work out which object is the most important, the one that really represents ''the page'', as opposed to being an incidental piece of data.

BenWard: /* Methods of Prioritisation */ Notes/call for examples

2009-06-25T07:26:39Z

Methods of Prioritisation: Notes/call for examples

← Older revision		Revision as of 07:26, 25 June 2009
Line 30:		Line 30:

	Many microformats including [[hCalendar]], [[hAtom]], [[hReview]] include sub-properties which are themselves microformats (<code>author</code>, <code>organizer</code>, <code>agent</code> etc.) Although parsable as standalone microformats as well, when used directly as a component of another microformat, they should be deprioritized. --[[User:BenWard\|BenWard]] 06:39, 25 June 2009 (UTC)		Many microformats including [[hCalendar]], [[hAtom]], [[hReview]] include sub-properties which are themselves microformats (<code>author</code>, <code>organizer</code>, <code>agent</code> etc.) Although parsable as standalone microformats as well, when used directly as a component of another microformat, they should be deprioritized. --[[User:BenWard\|BenWard]] 06:39, 25 June 2009 (UTC)

			'''This needs to be supported by real-world examples. Please add some!'''

	<div class="discussion">		<div class="discussion">
Line 40:		Line 42:

	In a blogging context these entries are chronological content, their content is passing through the page as more content is written. As such, microformats nested inside entries could be deprioritized. --[[User:BenWard\|BenWard]] 06:39, 25 June 2009 (UTC)		In a blogging context these entries are chronological content, their content is passing through the page as more content is written. As such, microformats nested inside entries could be deprioritized. --[[User:BenWard\|BenWard]] 06:39, 25 June 2009 (UTC)

			'''This needs to be supported by real-world examples. Please add some!'''

	<div class="discussion">		<div class="discussion">
Line 52:		Line 56:

	Some weight could be given to any object that links identifies the same domain in its <code>url</code> property. --[[User:BenWard\|BenWard]] 06:39, 25 June 2009 (UTC)		Some weight could be given to any object that links identifies the same domain in its <code>url</code> property. --[[User:BenWard\|BenWard]] 06:39, 25 June 2009 (UTC)

			'''This needs to be supported by real-world examples. Please add some!'''

	<div class="discussion">		<div class="discussion">
Line 60:		Line 66:

	Since the <code>address</code> element may only be used by a person or organisation that is responsible for the page, the present of this on or within an hCard should add weight to that hCard. --[[User:BenWard\|BenWard]] 06:39, 25 June 2009 (UTC)		Since the <code>address</code> element may only be used by a person or organisation that is responsible for the page, the present of this on or within an hCard should add weight to that hCard. --[[User:BenWard\|BenWard]] 06:39, 25 June 2009 (UTC)

			'''This needs to be supported by real-world examples. Please add some!'''

	<div class="discussion">		<div class="discussion">
Line 68:		Line 76:

	If authors could add a <code>representative</code> classname (or functional equivalent) to any microformat on a page, it could indicate to the parser that the object described is the definitive object over all others, and bypass heuristics. --[[User:BenWard\|BenWard]] 06:39, 25 June 2009 (UTC)		If authors could add a <code>representative</code> classname (or functional equivalent) to any microformat on a page, it could indicate to the parser that the object described is the definitive object over all others, and bypass heuristics. --[[User:BenWard\|BenWard]] 06:39, 25 June 2009 (UTC)

			'''This needs to be supported by real-world examples. Please add some!'''

	<div class="discussion">		<div class="discussion">

BenWard: Added related page links

2009-06-25T06:45:31Z

Added related page links

← Older revision		Revision as of 06:45, 25 June 2009
Line 72:		Line 72:
	* …		* …
	</div>		</div>

			==Related Pages==

			* [[hcards-and-pages]]
			* [[representative-hcard]]

BenWard: /* Methods of Prioritisation */ Fixed source snippet

2009-06-25T06:40:48Z

Methods of Prioritisation: Fixed source snippet

← Older revision		Revision as of 06:40, 25 June 2009
Line 17:		Line 17:
	When you document a possible technique for analyzing/prioritizing each object, please give it a new heading. Follow this template for each new idea:		When you document a possible technique for analyzing/prioritizing each object, please give it a new heading. Follow this template for each new idea:

	<source ~~class~~="html4strict">		<source lang="html4strict">
	===Summary of Technique===		===Summary of Technique===

BenWard: Initial representative-object page, brainstorming how to get the more representative microformat objects from a page.

2009-06-25T06:39:49Z

Initial representative-object page, brainstorming how to get the more representative microformat objects from a page.

New page

<entry-title>Microformat Objects Representing an Entire Page</entry-title>
Pages may (and often do) contain multiple microformats; objects of different vocabularies, multiple objects from the same vocabulary, and objects from other sources of structure data. There are use cases (such as Search Engine Results) that want to use microformats in the page to better represent the page, but must work out which object is the most important, the one that really represents ''the page'', as opposed to being an incidental piece of data.

This page is for brainstorming methods of ranking all the structured data objects in a page, prioritizing and de-prioritizing them according to conditions, such that a consumer tool could pick the item ranked highest to confidently represent the page.

==Examples of Problems==

Note that the similarity of some of these problems highlights how subtle

# A ''personal'' blog homepage contains an [[hCard]] for the author and [[hAtom]] blog entries. You would represent the page using the hCard.
# A ''group'' blog contains hCards for the authors and hAtom entries. You would represent the page with information about the feed.

''Please add more''

==Methods of Prioritisation==

When you document a possible technique for analyzing/prioritizing each object, please give it a new heading. Follow this template for each new idea:

<source class="html4strict">
===Summary of Technique===

Detailed description. Provide some indication of the weight of this technique. --~~~~

<div class="discussion">
* …
</div>
</source>

===Deprioritize Compound Objects===

Many microformats including [[hCalendar]], [[hAtom]], [[hReview]] include sub-properties which are themselves microformats (<code>author</code>, <code>organizer</code>, <code>agent</code> etc.) Although parsable as standalone microformats as well, when used directly as a component of another microformat, they should be deprioritized. --[[User:BenWard|BenWard]] 06:39, 25 June 2009 (UTC)

<div class="discussion">
* …
</div>

===Deprioritize Objects Contained in hAtom Entries===

Since hAtom entries represent articles, the content of each <code>hentry</code> may contain other microformat objects — blog posts about an event or another person for example may contain hCalendar and hCard microformats.

In a blogging context these entries are chronological content, their content is passing through the page as more content is written. As such, microformats nested inside entries could be deprioritized. --[[User:BenWard|BenWard]] 06:39, 25 June 2009 (UTC)

<div class="discussion">
* …
</div>

===Prioritize hCards with <code>rel=me</code> or any object with a <code>uid</code> property on the same domain===

See also, [[representative-hcard]] for ways of working out which hCard is representative of a page, when compared to others (such as a blog author hcard in relation to hcards of article commentors)

Where an object is in a page with a property <code>uid</code> pointing to the same domain as the current page, and/or making a <code>rel=me</code> link to the same domain (hCards only), that object should be weighted in favour.

Some weight could be given to any object that links identifies the same domain in its <code>url</code> property. --[[User:BenWard|BenWard]] 06:39, 25 June 2009 (UTC)

<div class="discussion">
* …
</div>

===Prioritize hCards nested inside or containing <code>address</code> elements===

Since the <code>address</code> element may only be used by a person or organisation that is responsible for the page, the present of this on or within an hCard should add weight to that hCard. --[[User:BenWard|BenWard]] 06:39, 25 June 2009 (UTC)

<div class="discussion">
* …
</div>

===Create a new microformat for authors to explicitly publish the representative object for their page===

If authors could add a <code>representative</code> classname (or functional equivalent) to any microformat on a page, it could indicate to the parser that the object described is the definitive object over all others, and bypass heuristics. --[[User:BenWard|BenWard]] 06:39, 25 June 2009 (UTC)

<div class="discussion">
* …
</div>