#microformats 2015-07-12

2015-07-12 UTC
KartikPrabhu joined the channel
#
@ProjectPeachUK We've #played with #microformats. Love the #idea of #marking up our #business data to #machines as well as #humans! #pickupaRT #DBFY (twitter.com/_/status/620058789170008064)
KartikPrabhu, fuzzyhorns, tantek, eschnou and csarven joined the channel
#
@neogeografen De DK Mapillary frivillige har fotog. ca. 12500 km - samlet er der ca 207000 km veje/stier i DK - så afsted med dig http://www.microformats.dk/2015/03/04/ideforslag-det-rullende-brugerpanel-kunne-skabe-faelles-billeder-og-geodata/ (twitter.com/_/status/620153921173065728)
adactio, tantek and barnabywalters joined the channel
#
barnabywalters good morning!
#
barnabywalters tantek, I’d appreciate your thoughts on my comments on https://github.com/indieweb/php-mf2/issues/64
#
barnabywalters Having spent a long time away from the parsing spec, I’m not sure if the confusion I’m having is due to unfamiliarity, or actual problems exposed by looking at it with a fresh eye
#
tommorris tantek, barnabywalters: is it affecting other implementations?
#
barnabywalters tommorris: not sure, I’ve been fixing some bugs in php-mf2 and have found potentially confusing language in the parsing spec
#
barnabywalters specifically, the behaviour I was fixing was not clearly specified anywhere, and in reading it I found language which seems to imply that parsing a property-nested microformat should result in two items in the parent microformat’s property array
#
tantek barnabywalters: looking at it
#
tantek barnabywalters: looks like you resolved https://github.com/indieweb/php-mf2/issues/64 ?
#
tantek what’s the specific question? I thought I was reporting a really obvious bug
#
barnabywalters tantek: yep, thanks for reporting it! The issue itself is resolved, the problem (as I pointed out in comments on that issue) is that the mf2 parsing spec does not clearly specify the correct behaviour
#
barnabywalters and then, reading it more closely, it seems to imply that parsing a property-nested microformat should result in two items in the parent’s corresponding property list, one for the bare property (a string) and a nested microformat structure in addition to that
#
tantek by property list is that the { } structure?
#
barnabywalters by property list I am referring to the list of values associated with a property name in a microformat structure
#
tantek array then?
#
barnabywalters e.g. "name": ["value 1", "value 2" •••]
#
tantek [ ]
#
barnabywalters yep
#
tantek I always call the [ ] things arrays because that’s well established naming in CS for the [ ] structure
#
barnabywalters fair enough, I’m always flipping between python and PHP, which have very different naming and overlapping use-cases :)
#
barnabywalters so I tend to use python terminology as it’s more precise
#
barnabywalters than PHP’s, that is
#
barnabywalters but that is not very relevant
#
tantek the value vs. html things go into the { } structure, not [ ]
#
barnabywalters yep, that is not what I am confused about
#
tantek edited /microformats2-linting (-21) "created published updated" (view diff)
#
tantek edited /microformats2-linting (+393) "-1 linting any <article>" (view diff)
#
barnabywalters the fact that property parsing and nested microformat parsing are separate steps in the spec makes it sound like a parsing a property-nested microformat should result in two items in the parent’s array for the property the microformat is nested under
#
tantek tommorris: ok updated http://microformats.org/wiki/microformats2-linting
#
tantek barnabywalters: huh that is weird and no one else seems to have had that interpretation. regardless I’d like to clarify the spec if I can.
#
barnabywalters e.g. <div class="h-entry"><span class="p-author h-card">Author</span></div> would result in a h-entry mf with 'author': ['Author', { nested mf value }]
#
tantek also - it makes no sense for there to be two values in an array for the same source of data
#
tommorris tantek: thanks
#
tantek since every thing in a [ ] is a different piece of data from the author
#
tantek so to have two things show up in a [ ] that come from *one* thing the author wrote is only confusing
#
tantek not sure how that could be interepeted as valid in any interpretation
#
barnabywalters tantek: agreed that it makes no sense and is likely not a big problem, but looking at the spec with fresh eyes that is how I’m reading it
#
barnabywalters it’s quite obvious from examples how property nested microformats should work, but there’s nothing in the spec which explains that, having parsed a tree for properties, when parsing for child microformats, their values should replace the previously parsed property values
#
barnabywalters tommorris: I just checked mf2py, if the version on kartikprabhu.com is up to date then it has a similar nested e- html problem as php-mf2 did. Raising issue now.
#
tommorris thanks
#
tantek barnabywalters: it does? huh I thought I checked the latest of the other parsers
#
tantek I think kylewm’s is newer (deployment of mf2py)
#
barnabywalters tantek: mf2py gets it more correct than php-mf2 did, but still wrong as per kartikprabhu.com — the value of value is a nested dictionary with value and html keys, rather than the html key being added to the root of the nested structure
#
barnabywalters is there a mf2py testing field on kylewm’s site?
#
tantek I thought there was yes
#
tommorris I should update the heroku instance
#
tantek I think it’s on the wiki
#
Loqi +1
#
tommorris but not right now. ;-)
#
barnabywalters tantek: I can’t see it, http://microformats.org/wiki/mf2py only links to a version on heroku for URLs, and raw text entry on kartikprabhu.com
#
tommorris opens https://github.com/tommorris/mf2py/issues/49
#
tantek barnabywalters: we have our own DRY violation problem :)
#
tantek try the /microformats2#Parsers
#
barnabywalters tantek: ha ha ha, indeed
#
barnabywalters yep, we have a threefold DRY violation issue, because there’s also http://microformats.org/wiki/parsers
#
tantek yeah I minimized there a bit and linked from there to /microformats2#Parsers
#
tantek that was the first violation I found
#
tantek the key is making the info accessible
#
tantek rather than having to click through 3 pages or something to find it
#
tantek hence the flatter list of all the implementations on /microformats2 made more sense to update
#
barnabywalters agreed, however I would expect the most detailed information to be on the project page
#
barnabywalters I’ll at least copy the full list there
#
barnabywalters edited /mf2py (+137) "Added list of live implementations" (view diff)
#
barnabywalters added it and moved kylewm’s to the top as it offers both textentry and URL, and is apparently up to date
#
tantek agreed on “would expect the most detailed information to be on the project page” yet that’s in contrast with the “don’t have to click too much to find the info"
#
tantek so we end up with a DRY content problem
#
barnabywalters yeah, in theory this is what transclusion should solve. Does mediawiki do transclusion, other than templates? E.g. “embed the examples section from [[mf2py]] on [[microformats2]]”
#
barnabywalters nope, looks like (without extensions) templates are the only way to do this
#
tantek yeah
#
tommorris barnabywalters: nope, only templates
adactio joined the channel
#
KevinMarks unmung.com has a linkable type-in html field (it makes the worlds ugliest URLs though)
#
KevinMarks eg http://www.unmung.com/?html=%3Cdiv+class%3D%22h-entry%22%3E%3Cdiv+class%3D%22e-content%22%3E%3Cp%3EHello%3C%2Fp%3E%3C%2Fdiv%3E%3C%2Fdiv%3E%0D%0A%3Cdiv+class%3D%22h-entry%22%3E%3Cdiv+class%3D%22h-card+e-content%22%3E%3Cp%3EHello+hcard%3C%2Fp%3E%3C%2Fdiv%3E%3C%2Fdiv%3E&pretty=on
#
KevinMarks (that uses mf2py)
barnabywalters joined the channel
#
kylewm thank you for filing that issue barnabywalters, I thought for sure I had already done that :embarrassed:
#
barnabywalters kylewm: no problem! My embarrassment should be far greater for not having dealt with the issue for such a long time :)
#
barnabywalters and mf2py was much less wrong than php-mf2 ;)
csarven, Zegnat, Zegnat_, fuzzyhorns, gRegorLove, emmak_, tantek, gRegorLove_, adactio and rawtext joined the channel
#
@scriptzteam IP.Blog 2.6: SEO Improvements and Microformats - http://newz.scriptz-team.info/IPS-News-And-Updates/078819-IP-Blog-2-6-SEO-Improvements-and-Microformats.html (twitter.com/_/status/620309926167097345)
#
tantek edited /comment-brainstorming (+149) "/* Use case for same page u-in-reply-to */ note use-case currently theoretical" (view diff)
adactio, KartikPrabhu and gRegorLove_ joined the channel
#
csarven edited /comment-brainstorming (+116) "Asked for clarification/relevancy on "indieweb"" (view diff)
#
tantek yeah no need for indieweb specific reference there
#
tantek not sure when that got added
#
tantek will fix
adactio and fuzzyhorns joined the channel
#
tantek edited /comment-brainstorming (+450) "remove reference to "indieweb" from issue / idea - was not relevant to the idea. clarify comment on its own page, vs in a list, vs both." (view diff)
csarven_ and rawtext joined the channel
#
@scriptzteam IP.Blog 2.6: SEO Improvements and Microformats - http://newz.scriptz-team.info/IPS-News-And-Updates/078819-IP-Blog-2-6-SEO-Improvements-and-Microformats.html (twitter.com/_/status/620348440476819456)
fuzzyhorns and rawtext joined the channel
#
@scriptzteam IP.Blog 2.6: SEO Improvements and Microformats - http://newz.scriptz-team.info/IPS-News-And-Updates/078819-IP-Blog-2-6-SEO-Improvements-and-Microformats.html (twitter.com/_/status/620350317658550272)
#
@scriptzteam IP.Blog 2.6: SEO Improvements and Microformats - http://newz.scriptz-team.info/IPS-News-And-Updates/078819-IP-Blog-2-6-SEO-Improvements-and-Microformats.html (twitter.com/_/status/620350431005421568)
#
@scriptzteam IP.Blog 2.6: SEO Improvements and Microformats - http://newz.scriptz-team.info/IPS-News-And-Updates/078819-IP-Blog-2-6-SEO-Improvements-and-Microformats.html (twitter.com/_/status/620352242806325248)
csarven_, fuzzyhorns and tantek joined the channel
#
@chason70 Microformats2 http://microformats.org/wiki/microformats-2 #microformats (twitter.com/_/status/620364748434051072)
KartikPrabhu joined the channel