Difference between revisions of "representative-object-brainstorming"
m (→Methods of Prioritisation: Fixed source snippet)
(Added related page links)
|Line 72:||Line 72:|
Revision as of 06:45, 25 June 2009
<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.
- 1 Examples of Problems
- 2 Methods of Prioritisation
- 2.1 Deprioritize Compound Objects
- 2.2 Deprioritize Objects Contained in hAtom Entries
- 2.3 Prioritize hCards with rel=me or any object with a uid property on the same domain
- 2.4 Prioritize hCards nested inside or containing address elements
- 2.5 Create a new microformat for authors to explicitly publish the representative object for their page
- 3 Related Pages
Examples of Problems
Note that the similarity of some of these problems highlights how subtle
- A personal blog homepage contains an hCard 1.0 for the author and hAtom 0.1 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:
===Summary of Technique=== Detailed description. Provide some indication of the weight of this technique. --~~~~ <div class="discussion"> * … </div>
Deprioritize Compound Objects
Many microformats including hCalendar 1.0, hAtom 0.1, hReview 0.4 (in progress) include sub-properties which are themselves microformats (
agent etc.) Although parsable as standalone microformats as well, when used directly as a component of another microformat, they should be deprioritized. --BenWard 06:39, 25 June 2009 (UTC)
Deprioritize Objects Contained in hAtom Entries
Since hAtom entries represent articles, the content of each
hentry 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. --BenWard 06:39, 25 June 2009 (UTC)
Prioritize hCards with
rel=me or any object with a
uid 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
uid pointing to the same domain as the current page, and/or making a
rel=me 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
url property. --BenWard 06:39, 25 June 2009 (UTC)
Prioritize hCards nested inside or containing
address 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. --BenWard 06:39, 25 June 2009 (UTC)
If authors could add a
representative 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. --BenWard 06:39, 25 June 2009 (UTC)