karlpro I shouldn’t really have to sign up in order to leave a comment, but in the interests of promoting #microformats I will :)
karlpro I shouldn’t really have to sign up in order to leave a comment, but in the interests of promoting #microformats I will :)
@karlpro wrt your opera dev article, check out microformats 2 h-geo, Ben Ward’s hparse-js for parsing and my own php-mf2 online syntax checker :) #microformats
lkdto how about rel=me
on all your links?
thepastrybox rolled out the µf2 I added. Suggestions for other similar websites which accept pull requests? #microformats
Current status: sending pull requests to thepastrybox to include #microformats and microformats-2 on their wonderful site
Pushed out SFW-inspired article edit histories. Thinking we could do with a document edit history #microformat
@zeldman by which you mean µf2? It would be fab to see you roll them out as well!
Brennan Novak hey, you did better than @zeldman. There’s nary an hcard on his personal site :/ http://identengine.com/api/identities/http%3A%2F%2Ftwitter.com%2Fzeldman/profiles/
Updates to #php-mf2: vastly improved handling of combined microformats. http://waterpigs.co.uk/php-mf2
I updated the #php-mf2 web demo again, now you can try out the classic microformats compatibility. http://waterpigs.co.uk/php-mf2/
Updated php-mf2 with improved handling of children keys, updated the demo to output JSON and time taken;
Just put in a few solid hours working on https://github.com/indieweb/php-mf2/ — it’s now at v0.1.6 and has preliminary support for the microformats-2 canonical JSON representation. As always it is installable via composer via "mf2/mf2": "0.1.*"
Reduced test cases are my friends tonight #microformats
HA! value-class pattern, I have beaten you.
For at least one test case. But still.
The value–class pattern for datetimes was made to torture parser developers, right? #microformats
@sandeepshetty yep. At the moment it’s a couple of functions, by tomorrow it’ll be a PHP5 namespaced composer package.
My #microformats-2 parser will allow for generic parsing (i.e. won’t have to be updated for each new µf) and I’ll do my best to handle nested µf well
Increasingly, my #indieweb activities are moving from “Publishing my own content” to “Intelligently parsing other people’s content”. As such, I am writing a PHP #microformats-2 parser
The vcard syntax is bloody hideous. We should replace it with #hcard #microformats
Implemented #microformats 2 on my site. Conflicted about redundant classnames, but mf2 likely to have greater longevity