The fact that I’m considering splitting #microformats examples lists into “publishing” and “consuming” is testament to the progress which has been made in the past month
The fact that I’m considering splitting #microformats examples lists into “publishing” and “consuming” is testament to the progress which has been made in the past month
Thank you @spreadly @pfefferle for rolling out #microformats 2 support, hoping to see even more in the future! To other companies: there’s still time to catch up!
#microformats2 wild examples list growing quickly, will your site be the next? microformats.org/wiki/microformats2#Examples_in_the_wild
php-mf2 alert: v0.1.15 just released with rel+alternate parsing and an HTML-safe option to deal with the p-* e-* ambiguity. Just in time for everyone implementing #indiecomments at IndieWebCamp :)
@schofeld microformats2 drafts are ready to use, many examples of h-card and h-entry in the wild and applications making real use of them microformats.org/wiki/microformats2
RSS enthusiasts are HTML enthusiasts who haven’t met #microformats 2 yet. microformats.org/wiki/microformats2
Battle for the planet of the APIs by Jeremy Keith — nice piece of writing, it’s worth pointing out that Twitter still includes rel=me links back to homepages, but is increasingly wrapping them with t.co, making them fairly useless.
Whilst I admire RSS as a rallying cry for the openness of data on the web, I don’t like it much, mainly due to it’s DRY violation. microformats2 is the better solution.
Just pushed latest #taproot changes: using htmlpurifier.org to remove any nasties in reply contexts and comments, hopefully with upcoming php-mf2 changes that’ll allow limited HTML comments!
Also using brand new php-mf2-cleaner to parse said reply contexts and comments, find authors, etc. Check it out if you deal with #microformats 2 at all in PHP.
@benwerd loving your work on idno! Just had a look at the source, great that you’re using #microformats 2, I have some suggestions/corrections:
.h-entry
is better off where you’ve got .idno-entry
so then the author .h-card
can be scoped into the entry.p-author
to the .h-card
for each .h-entry
to explicitly declare authorship.h-as-*
on the same element as .h-entry .idno-entry
.u-url
where you currently have .dt-published
, move .dt-published
to the time
elementThanks to Aaron Parecki you can see how a page is parsed here, or use my php-mf2 demo sandbox for experimentation by hand.
Jeremy Keith I know Aaron Parecki currently has a script to convert twitter pages into microformats 2 canonical JSON, I think it should be here but he hasn’t pushed it yet :)
@thatEmil anything here: microformats.org/wiki/microformats-2
“People in the garage door industry have been busy designing and manufacturing doors that are handsome as well as functional.”
A TOAST, I SAY, TO THE GALLANT FOLKS OF THE GARAGE DOOR INDUSTRY
The spam on the #microformats wiki just gets weirder and weirder. This one is masterfully surreal in all its mundane glory:
“How about a garage door you can see through? Well almost”
“The neat thing is that these are overhead sectional garage doors just like any other.”
“Can you acquire a bucket of paint?”
“you'll amaze yourself”
“Now that you understand how financially important your garage door really is to you, it is time to get to work.”
sophiedennis ooh shiny! Any chance of some microformats 2 and other similar goodness on the new theme? Ping me or hop into #microformats on freenode if you need a hand, currently the documentation needs lots of tidying up
Aral Balkan h-event with hCalendar fallback microformats.org/wiki/microformats-2#h-event
cssquirrel not separating machine–readable data from human–readable data might be a good start #microformats
Hopefully h-card entities should get expanded in the reply context for this note (crosses fingers)
Turns out the #microformats 2 JSON structures enable safe entity expansion just like twitter entities.
In my reply contexts I am not wanting to embed 3rd party HTML in my site, so I take the p-summary and strip tags. But, I want embedded h-cards to be expanded just like at-mentions on twitter. Pseudocode:
let h-card = canonical JSON structure for a note, with .summary as a plaintext representation of the content;
for item in h-card.children:
if not in_array('h-card', item.type) continue;
let html = HTML representation of the child from properties.url, name, etc;
replace item.value in h-card.summary with html
Example here.
Aaron Parecki testing reply context microformat entity expansion, please ignore :)