#microformats 2013-11-12

2013-11-12 UTC
tantek, tswicegood and bret joined the channel
#
@divproject hCard Creator http://microformats.org/code/hcard/creator (twitter.com/_/status/400179930308542465)
KevinMarks, tobyink, barnabywalters, pfefferle, tobyink1 and adactio joined the channel
#
@Sanremouk @Cocoa_Cabana thank you for your thoughts on your Zoe coffee machine, http://www.sanremouk.com/portfolio/zoe/?wpcrp=1#hreview-47 @Sanremomacchine (twitter.com/_/status/400255433530540032)
TallTed joined the channel
#
@Casa_Espresso RT @Sanremouk: @Cocoa_Cabana thank you for your thoughts on your Zoe coffee machine, http://www.sanremouk.com/portfolio/zoe/?wpcrp=1#hreview-47 @Sanremomacchine (twitter.com/_/status/400256334668759040)
tobyink joined the channel
#
@Sanremomacchine RT @Sanremouk: @Cocoa_Cabana thank you for your thoughts on your Zoe coffee machine, http://www.sanremouk.com/portfolio/zoe/?wpcrp=1#hreview-47 @Sanremomacchine (twitter.com/_/status/400262740708978688)
tantek and jgay joined the channel
#
@SMIDIT @ThE_ED Precies en wellicht een opvallende opmaak? http://www.smid-it.nl/author-hreview-zoekverkeer-verbeteren-door-opvallende-opmaak-in-de-serps/ (twitter.com/_/status/400278944328716288)
#
@SMIDIT @Mediaonderhoud Helemaal mee eens hoor. En dan de #conversie beter door gebruik van #Rich #Snippets http://www.smid-it.nl/author-hreview-zoekverkeer-verbeteren-door-opvallende-opmaak-in-de-serps/ (twitter.com/_/status/400278713121910784)
brianloveswords joined the channel
#
@Mediaonderhoud RT @SMIDIT: @Mediaonderhoud Helemaal mee eens hoor. En dan de #conversie beter door gebruik van #Rich #Snippets http://www.smid-it.nl/author-hreview-zoekverkeer-verbeteren-door-opvallende-opmaak-in-de-serps/ (twitter.com/_/status/400287724831518720)
#
tantek barnabywalters I've been thinking of resolving the <input> element parsing issue per http://microformats.org/wiki/hcard-parsing-brainstorming#input_element_handling - any objection? (cc: tommorris)
#
tantek this issue: http://microformats.org/wiki/microformats2-parsing-issues#How_to_interpret_mf2_classnames_on_form_inputs
#
barnabywalters tantek: looks fine to me
#
barnabywalters should we worry about <select> and checkbox/radio button @checked now or leave it until someone’s actually publishing that data?
#
tantek for <select> I think we should wait for real world publishing examples that make sense to parse
#
barnabywalters agreed
#
barnabywalters so, just <input>s which result in a text-like control, and <textarea>
#
tantek I'm thinking any <input> with a value attribute uses the value attribute, independent of "type"
#
tantek to simplify the model for publishers and parsers
#
tantek rather than special casing checkbox or text-like control
#
barnabywalters yeah, worry about what happens to checkboxes and radio buttons when someone actually publishes them
#
tantek textarea I don't think needs to be explicitly specified until we find a use-case. the use-case for input is https://brennannovak.com/notes/338 as pointed out in the issue.
#
tantek barnabywalters - I mean, if someone puts a p-* class on a checkbox and it has a value attribute - we should still use the value attribute
#
barnabywalters so just input[value]
#
tantek regardless of its checkboxness
#
tantek yeah that's what I'm writing up now
#
barnabywalters makes sense, is simple and solves current use case. doesn’t get much better than that
#
tantek I'm doing it for p- u- and dt- since there are inputs for all three
#
tantek as of HTML5
#
tantek e.g. input type=url or type=date
#
tantek edited /microformats2-parsing (+61) "add input[value] handling per [[microformats2-parsing-issues#How_to_interpret_mf2_classnames_on_form_inputs]]" (view diff)
#
tantek edited /microformats2-parsing-issues (+357) "resolved How to interpret mf2 classnames on form inputs, separate other minor issue about form element itself and select element - awaiting real world publishing experience on those and/or use cases" (view diff)
#
tantek barnabywalters - how does that look? http://microformats.org/wiki/microformats2-parsing#parse_an_element_for_properties
#
tantek and I've now added an input with URL of my permalink to my notes to test this parsing. E.g. http://tantek.com/2013/314/t1/run-to-beach-happy-pi-day - try it out when you've added input[value] handling to phpmf2
#
barnabywalters looks good!
#
barnabywalters should be easy to implement too. I’ll roll this in with a bunch of other small fixes
#
tantek nice
#
tantek and then I think that will fix a bug that aaronpk found with my note h-entry markup (missing u-url)
#
tantek two birds (input[parsing], note url), three stones (uf2 parsing spec, phpmf2, input.u-url[type=url][value])
#
tantek s/input[parsing]/input[value] parsing
#
tantek Loqi?
#
tantek (or did I fail to escape something)
#
aaronpk square brackets are magic regex characters
#
tantek s/input\[parsing\]/input\[value\] parsing
#
tantek and now I'm too late to make it work
#
tantek retry just to test Loqi
#
Loqi woot!
#
tantek two birds (input[parsing], note url), three stones (uf2 parsing spec, phpmf2, input.u-url[type=url][value])
#
tantek s/input\[parsing\]/input\[value\] parsing
#
Loqi tantek meant to say: two birds (input\[value\] parsing, note url), three stones (uf2 parsing spec, phpmf2, input.u-url[type=url][value])
#
barnabywalters Loqi, learn to escape regexes
#
tantek s/input\[parsing\]/input[value] parsing
#
aaronpk lol
#
tantek so only escape the first part then?
#
aaronpk no I think loqi is just wrong
KevinMarks joined the channel
#
tantek ok looks like I should say "textContent" not "innertext"
#
tantek to preserve whitespace in parsing
#
tantek edited /microformats2-parsing (+10) "use textContent instead of innertext because the goal was always to preserve whitespace at parsing time and leave that to the consuming/displaying application (e.g. with CSS)" (view diff)
KevinMarks and tobyink joined the channel
#
tantek edited /microformats2-parsing (+161) "make e-x value consistent with p-x (e.g. for e-content vs p-content vs p-name)" (view diff)
#
tantek edited /microformats2-parsing-issues (+192) "resolved: When to collapse whitespace in properties - no more than what HTML5 parsing does." (view diff)
#
tantek barnabywalters - also resolved for you: http://microformats.org/wiki/microformats2-parsing-issues#When_to_collapse_whitespace_in_properties
#
tantek that should help with p-content vs e-content value type stuff
jgay and KevinMarks3 joined the channel
#
@istiaak Author hReview: Show Google Rich Snippet Star Rating in Search Results http://roadtoblogging.com/show-star-rating-in-google-search/ (twitter.com/_/status/400361718754189312)
jgay and barnabywalters joined the channel
#
barnabywalters parsing for implied name says drop trailing/leading whitespace from implied name but not p-* properties: http://microformats.org/wiki/microformats2-parsing
#
barnabywalters not sure if inconsistency or if there’s thought behind it
#
barnabywalters earlier tantek was saying implied name should be consistent with p-* properties so I’m going with trimming everything but leaving whitespace within, for the moment
#
barnabywalters easy enough to change later on
#
barnabywalters php-mf2 v0.2.3 released, fixes a bunch of bugs https://github.com/indieweb/php-mf2
#
aaronpk hooray!
#
aaronpk have you seen the newr eleases feature in github?
#
aaronpk https://github.com/indieweb/php-mf2/releases/tag/v0.2.3
#
aaronpk you can add descriptions and changelogs and such
#
barnabywalters aaronpk: pretty sure that protocol-relative bug is actually fine
#
barnabywalters I’ll have to refind the example which was going wrong, I wrote a test and it passed
#
aaronpk oh weird
#
barnabywalters hm, releases look nice — basically a way of easily downloading a zip of tagged commits?
#
aaronpk yeah, but also to provide a place for release notes
#
aaronpk i mean a blog post is the same thing if you're into that sort of thing :)
#
barnabywalters that or more POSSE to github :)
#
aaronpk could even posse a blog post about the release from your site to that page
#
barnabywalters JINX
#
aaronpk whoa
#
aaronpk oh you know what... the fail case in your comment is different from the case in the test
#
aaronpk because in your comment the base URL was http://example.com/page.html , not http://example.com
#
barnabywalters oh good point, maybe it fails if there’s a path but passes if there isn’t
#
aaronpk yeah that's my guess
#
barnabywalters adds to issue
#
aaronpk there's a lot of weird logic in there for hadling all the possible combinations of base URLs
#
barnabywalters I’ll check it out some other time — battery dying now
#
aaronpk cool
#
barnabywalters goodnight!
#
Loqi sleep tight!
tantek joined the channel