hcard-implied-brainstorming

(Difference between revisions)

Jump to: navigation, search
Line 34: Line 34:
* Extraordinarily simple markup
* Extraordinarily simple markup
* Provides a smaller barrier-to-entry for microformats that require hCard
* Provides a smaller barrier-to-entry for microformats that require hCard
 +
 +
Additionally, the @href could map to different properties based on protocol:
 +
 +
* <nowiki>[href^='http']</nowiki> would map to <code>url</code>
 +
* <nowiki>[href^='mailto']</nowiki> would map to <code>email</code>
 +
* <nowiki>[href^='data']</nowiki> would map to <code>photo</code>
--[[User:RCanine|Ryan Cannon]]
--[[User:RCanine|Ryan Cannon]]

Revision as of 21:09, 8 December 2006

Implied hCard Brainstorming

These are ideas for solutions to implied-hcards. See implied-hcard-examples for use cases.

Initial ideas

The rule could be similar to:

If a an element with class=vcard does not have any hCard class names, imply the entire content as an fn field, and attempt to apply the implied "n" optimization.

Optionally, if the root element has @href, imply a class="url".

For example:

<a class="vcard" href="http://ryancannon.com/">Ryan Cannon</a>

becomes

BEGIN:VCARD
N:Cannon;Ryan;;;
FN:Ryan Cannon
URL:http\://ryancannon.com/
END:VCARD

All this is possible because it requires an hCard without hCard markup inside.

This is fairly powerful for a few reasons:

Additionally, the @href could map to different properties based on protocol:

--Ryan Cannon

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

Views