microformats2-brainstorming

(Difference between revisions)

Jump to: navigation, search
(move further simplifications to microformats-2-implied-properties)
(adopt itemref: Note hAtom shared author use case for itemref left open by loss of <address> optimisation.)
Line 10: Line 10:
There many existing real-world use-cases where either:
There many existing real-world use-cases where either:
-
* several microformats in a page want to share some common data without repeating it, e.g. a page about a product with multiple reviews of that product (very common, products sites, Amazon/CNET et al, review aggregators, Yelp et al)
+
* several microformats in a page want to share some common data without repeating it.
 +
** e.g. a page about a product with multiple reviews of that product (very common, products sites, Amazon/CNET et al, review aggregators, Yelp et al)
 +
** e.g. representing the author of multiple hAtom entries on a page. Currently this is possible with the <code>&lt;address class="hcard"></code> optimisation, which would be rendered obsolete by the proposed new generic parsing rules.
* a microformat in a page needs to incorporate information spread across different parts of a page, without assigning the entire page to that microformat
* a microformat in a page needs to incorporate information spread across different parts of a page, without assigning the entire page to that microformat

Revision as of 06:36, 5 October 2011

Brainstorming experimental / undeveloped / rejected ideas for microformats-2.

Contents

further simplifications

more on allow root class name only

This has been stable for a while, see:

adopt itemref

There many existing real-world use-cases where either:

The include-pattern provides the necessary functionality for existing microformats (1.0).

For 2.0 it may be reasonable to simply re-use the nice itemref attribute from microdata, with identical/analogous functionality.

That is, when present on the root element of a microformat, the itemref attribute provides a space separated list of ids of elements in the document which are then incorporated as children of the microformat, before its actual children in the document. This is a simple coarse summary of course, and the actual itemref inclusion algorithm should be followed.

One might say that this raises the issue of requiring HTML5 with the ability to accepted extended attributes like "itemref", but I think that might be ok for the set of use-cases that need "itemref". That is, they *are* a minority of actual use-cases, and thus making them use HTML5 is probably ok.

rejected ideas

n prefix for multiple numbers

Idea:

Rejected because while this *might* work for some properties in *English* it will NOT localize/internationalize well (orders of numbers in phrases change in different languages), and it will also limit the human expressivity of the plain text. Thanks to Ben Ward for this feedback at the 2011-06-02 microformats dinner. Tantek 14:25, 9 June 2011 (UTC)

see also

microformats2-brainstorming was last modified: Wednesday, December 31st, 1969

Views