microformats2-brainstorming

(Difference between revisions)

Jump to: navigation, search
(adopt itemref: Noting that lovely as itemref is, it's not HTML5, nor is it stable, and we've rejected useful invalid attributes in the past.)
m (adopt itemref: fix code typo)
Line 23: Line 23:
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.
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.
-
* More problematic is the fact that <code>itemref</code> is not part of the HTML5 specification, nor is it documented as a stable draft. In the past, we resisted cribbing attributes from RDFa, which was a ''stable'' augmentation of HTML, and creating an ugly empty-element hack rather than reusing <code>content</content>. We build atop HTML, and it would be dangerous to adopt features of separate technologies that are unstable, may change, or may disappear. --[[User:BenWard|BenWard]] 06:46, 5 October 2011 (UTC)
+
* More problematic is the fact that <code>itemref</code> is not part of the HTML5 specification, nor is it documented as a stable draft. In the past, we resisted cribbing attributes from RDFa, which was a ''stable'' augmentation of HTML, and creating an ugly empty-element hack rather than reusing <code>content</code>. We build atop HTML, and it would be dangerous to adopt features of separate technologies that are unstable, may change, or may disappear. --[[User:BenWard|BenWard]] 06:46, 5 October 2011 (UTC)
== rejected ideas ==
== rejected ideas ==

Revision as of 06:46, 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