#microformats 2017-05-31

2017-05-31 UTC
gRegorLove, [kevinmarks], AngeloGladding, nitot, gRegorLove_ and ben_thatmustbeme joined the channel
#
Zegnat Just pinging sknebel on this one: https://github.com/indieweb/php-mf2/issues/129
#
Loqi [Zegnat] #129 Partially matching date pattern is accepted for dt.
[colinwalker], nitot_, gRegorLove, voxpelli_, sknebel__, adactio and Calli joined the channel
#
Zegnat growls at vcp
#
Zegnat sknebel_ / sknebel__ if you have a moment: gRegorLove and I seem to have different readings of vcp, what’s your take? https://github.com/indieweb/php-mf2/issues/129
#
Loqi [Zegnat] #129 Partially matching date pattern is accepted for dt.
#
gRegorLove Which part?
nitot joined the channel
#
Zegnat I just commented on the issue, gRegorLove
sknebel, AngeloGladding, Garbee and TallTed joined the channel
#
Zegnat Hmm, is there some way we can generalise a vcp-to-string algo for dt-* and then generalise a string-to-valid-timestamp algo that works on the string value of the dt-*, then it no longer matters if that string value was obtained through regular parsing or through vcp.
#
@bloggermin Blogger SEO: Microformats http://www.bloggermin.cashmore.com.br/2012/07/seo-blogger-microformats.html https://twitter.com/bloggermin/status/869931548317032449/photo/1 (twitter.com/_/status/869931548317032449)
[cleverdevil], tantek, adactio, [barryf], [kevinmarks], [javery], gRegorLove, [eddie] and uf-wiki-visitor joined the channel
#
sourcerer Hi!
#
gRegorLove o/ sourcerer
#
sourcerer I am currently searching/developing a concept to provide information about electronic components and their packaging to the various machines in an electronic factory.
#
sourcerer My current idea is to put QR codes on the component reels, which would point to a web-page with detailled information about it, with embedded information to datasheets, rules and photos for optical inspection, ...
#
sourcerer The currently available microformats seem to be concentrating on the publishing industry and perhaps web-shops.
#
sourcerer Should I try to use the existing product microformats and extend them for the needs of electronic factories, or should I create different standards?
#
tantek sourcerer, re-using the closest most generic microformat for your use-case is a good start
#
tantek and then document what's missing for your use-cases
#
tantek (on the wiki preferably)
sourcerer_ joined the channel
#
gRegorLove Hey tantek. Would appreciate your input on https://github.com/indieweb/php-mf2/issues/129
#
Loqi [Zegnat] #129 Partially matching date pattern is accepted for dt.
#
Zegnat Lot of overlap with https://github.com/microformats/microformats2-parsing/issues/8 really, it is just general vcp issues I think :/
#
Loqi [sknebel] #8 imply dates also outside vcp?
#
tantek gRegorLove: all kinds of problems with that issue, examples etc. commented
#
gRegorLove The value=title is superfluous there. I don't think Zegnat is expecting it to be parsed from there.
tantek joined the channel
#
gRegorLove Er, I mean title= is superfluous there
#
tantek better to reduce example to minimum necessary to illustrate point, otherwise lots of copy/pasta errors / misinterpretations
#
gRegorLove Zegnat: Is this a real example of markup?
#
tantek indeed, the other thing is, reject any feature/complexity requests without real world examples
#
tantek with citations to public URLs on the web for analysis
#
gRegorLove tantek: Aside from that, comment on the seeming contradiction I mention here: https://github.com/indieweb/php-mf2/issues/129#issuecomment-305133685
#
Loqi [gRegorLove] Lots of good date-parsing catches lately. :) The regex used for this appears to be too lenient. It's checking the YYYY-MM-DD format but doesn't care about extra characters around it. I don't think it should be parsing the date value due to the chi...
#
gRegorLove Sorry, meant that as a question, not a direction. :)
[cleverdevil] joined the channel
#
Zegnat !tell gRegorLove I do not know if it is a real example of markup, it is your example of markup with added chicken to illustrate the parsing problem. Your markup from https://github.com/microformats/microformats2-parsing/issues/8#issuecomment-304957737
#
Loqi Ok, I'll tell them that when I see them next
#
Loqi [gRegorLove] Below is an example of php-mf2 doing this. Pending any drawbacks to be raised, I'm in favor of updating the spec to make it match this behavior. `<span class="h-event vevent"><strong><span class="dt-start"><span class="value" title="May 31, 201...
Garbee, [barryf], AngeloGladding, [kevinmarks] and gRegorLove joined the channel
#
gRegorLove Zegnat: Gotcha. That's not considered a real world example then (the one with chicken added)
#
Loqi gRegorLove: Zegnat left you a message 1 hour, 15 minutes ago: I do not know if it is a real example of markup, it is your example of markup with added chicken to illustrate the parsing problem. Your markup from https://github.com/microformats/microformats2-parsing/issues/8#issuecomment-304957737
ben_thatmustbeme joined the channel
#
gRegorLove It raises interesting questions to be clarified about VCP though
#
gRegorLove I'm going to PR the implied timezone stuff for VCP that's clear, though, then I think we'll get a 0.4.0 release out.
#
KartikPrabhu is this still the imply dtend timezone issue?
#
gRegorLove KartikPrabhu: No, this one: https://github.com/indieweb/php-mf2/issues/129
#
Loqi [Zegnat] #129 Partially matching date pattern is accepted for dt.
#
gRegorLove implied tz for any dt-* in an h-* is working in my local updates and will be in a PR for php-mf2
#
gRegorLove Implying for the dt-end is a common case, but the spec indicates it can go the other way, too -- if the dt-start doesn't have a tz but the dt-end does.
#
KartikPrabhu mf2py ignores the chicken line completely
#
KartikPrabhu http://www.unmung.com/?html=%3Cspan+class%3D%22h-event%22%3E%0D%0A++%3Cspan+class%3D%22dt-start%22%3E%0D%0A++++%3Cspan+class%3D%22value%22+title%3D%22May+31%2C+2017%22%3E%F0%9F%90%94+2017-05-31%3C%2Fspan%3E%0D%0A++++%3Cspan+class%3D%22value%22+title%3D%2217%3A30%22%3E17%3A30%3C%2Fspan%3E%0D%0A++%3C%2Fspan%3E%0D%0A++%E2%80%93%0D%0A++%3Cspan+class%3D%22dt-end%22%3E19%3A30%3C%2Fspan%3E%0D%0A%3C%2Fspan%3E&pretty=on
#
gRegorLove That's good. I think that's correct behavior.
#
KartikPrabhu oh ok
#
KartikPrabhu it doesnot match Zegnat's expected output in that bug report
#
gRegorLove I forgot to check other parsers, but glad I reached the same conclusion: https://github.com/indieweb/php-mf2/issues/129#issuecomment-305133685
#
Loqi [gRegorLove] Lots of good date-parsing catches lately. :) The regex used for this appears to be too lenient. It's checking the YYYY-MM-DD format but doesn't care about extra characters around it. I don't think it should be parsing the date value due to the chi...
#
KartikPrabhu yes, it does match your expected output
#
Zegnat Yeah, KartikPrabhu, I was reading it differently. But I do feer towards gRegorLove’s and sknebel’s reading now.
#
Zegnat Because no valid date part, I was expecting vcp to default away from dt rules and just concat and return the total value string for start. And as a direct follow-up to that happening, I expected no date part to be implied for the end date. But on re-reading the quoted text I agree that dropping the invalid string because a valid time part exists is
#
Zegnat correct.
#
Zegnat Still believe there is a deeper issue here, both with the complex vcp rules and the fact that dt sanitation is only applied during vcp and not at all for non-vcp values. Hope to get my thoughts on that cleared up after a good night’s sleep
#
Zegnat taps out
#
sknebel good night Zegnat!
#
Loqi sleep tight!
AngeloGladding, tantek and [chrisaldrich] joined the channel