Microformat definitions

[gareth rushgrove]

Something I pondered a while back but only started delving into.

hkit uses definition files for each microformat, with the hcard
example included for reference. Their are a number of other parsers
around, some of which also use a definition format (Sumo) and others I
don't know about (Operator, Mofo, etc. *) but may well do.

I was wondering if it would be a good idea to standardise on a cross
parser definition format? Or at least to move the definitions out of
PHP and into something else (perhaps YAML?)

Any thoughts? Just floating the idea at this stage.

G

* A list of parsers; http://microformats.org/wiki/parsers

--
Gareth Rushgrove
garethrushgrove.com
morethanseven.net
getjobsin.com
isitbirthday.com

[Drew McLellan]

On Jan 17, 2:04 pm, "gareth rushgrove" <gareth.rushgr...@gmail.com>
wrote:

> I was wondering if it would be a good idea to standardise on a cross
> parser definition format? Or at least to move the definitions out of
> PHP and into something else (perhaps YAML?)

Yes, I've been thinking about this too. The nice thing about the hkit
profiles being just PHP is that it enables us to include any
additional post-processing routines in the profile itself. (see the
implied n-optimisation in the hCard profile, for instance).

It'd be interesting to see a proof of concept.

drew.

[Steve Ivy]

Many (most?) of the microformats have XMDP[1] definitions. Perhaps
this (admittedly verbose) format could be used? See hcard[2],
hresume[3], hcalendar[4].

Thoughts?

--Steve

[1] http://gmpg.org/xmdp/
[2] http://microformats.org/wiki/hcard-profile
[3] http://dannyayers.com/micromodels/profiles/hreview
[4] http://microformats.org/wiki/hcalendar-profile

--
Steve Ivy
http://redmonk.net // http://diso-project.org
This email is: [ ] bloggable [x] ask first [ ] private