#microformats 2016-05-18

2016-05-18 UTC
miklb and laughinghan joined the channel
#
@lidyacota
that it is possible to express meaning on the web in HTML in a simple way far simpler than the complex alternatives http://microformats.org/
(twitter.com/_/status/732768012348985345)
tantek, M-RyanRix, laughinghan and dogada joined the channel
#
@strongerhead
One of the longest testimonial that can be termed as essay by Lifang. http://strongerhead.com/testimonial/?wpcrp=1#hreview-313
(twitter.com/_/status/732818818771374080)
laughinghan, tantek, voxpelli_, reidab_, ivc, myfreeweb, M-RyanRix, KevinMarks, Phae, twisted` and JonathanNeal joined the channel
#
@dylanbeattie
@RehanSaeedUK JSON+HAL is kinda like HTML+microformats - it's still the same language, but offers rich semantics to clients that support it.
(twitter.com/_/status/732891355077304320)
ben_thatmustbeme, nitot_, tantek, TallTed, willnorris and KevinMarks joined the channel
#
willnorris
I seem to recall reading somewhere that microformats2 references a section of an HTML spec for how it formats dates. Specifically, that is uses a space between the date and time rather than a "T" like is sometimes common. But now I can't find that reference anywhere. Does anyone know where that is specified?
#
willnorris
http://microformats.org/wiki/value-class-pattern#Date_and_time_parsing talks about using the "T" separator, but I think that's targetted at microformats1?
#
willnorris
(by the way, is anyone at OSCON this week by chance?)
tantek joined the channel
#
kylewm
tantek^^ did you see will's question?
#
tantek
checks logs
#
tantek
darn willnorris left the channel
#
tantek
!tell willnorris yes microformats2 prefers space between date and time, there's an outstanding resolved issue on this to make this more clear: http://microformats.org/wiki/microformats2-parsing-issues#parsing_a_dt-_property
#
Loqi
Ok, I'll tell them that when I see them next
willnorris, KevinMarks and benward__ joined the channel
#
willnorris
(I'm at OSCON, so dropping in and out of IRC as I move between sessions... working on getting znc setup. Checking logs though)
#
Loqi
willnorris: tantek left you a message 1 hour, 5 minutes ago: yes microformats2 prefers space between date and time, there's an outstanding resolved issue on this to make this more clear: http://microformats.org/wiki/microformats2-parsing-issues#parsing_a_dt-_property
#
willnorris
tantek, at https://indiewebcamp.com/irc/2016-04-25#t1461606553653 you mention "Date and time keeps the authored level of specificity". Where is that quoted from?
#
tantek
hopefully the microformats2 spec :)
#
willnorris
can't find it
#
tantek
parsing spec
#
tantek
now I'm having trouble finding it
#
willnorris
part of the problem (I think) is that the parsing spec links to the value-class-pattern page for dt-* values. And I think that page is trying to cover both mf1 and mf2. that's mostly fine, but there are a few small changes I think
#
willnorris
I've been knee deep in writing dt-* parsing code the last couple of days, and running into a handful of discrepencies between how I'm interpreting the parsing spec and what the microformats/tests repo (and other implementations) say
#
willnorris
I'll try and get them captured on the issues page
#
tantek
then this is a good time for me to update vcp per the issue resolutions
#
willnorris
yeah, I think that'd be great
#
aaronpk
Oh fun
#
willnorris
also, I found the "Authored level of specificity should always be kept in dates." quote. It was a comment from Glenn on the parsing-issues pages
#
tantek
interestingly, while avoiding that overspecificity for seconds, it makes sense for minutes
#
tantek
e.g. when humans communicate times in whole hours (of the clock), they are strongly implying :00 minutes
#
tantek
that is they are still implying that precision. they are not implying "sometime during that hour"
#
tantek
whereas that's not true with seconds.
#
tantek
it's an interesting case where the human behavior is different, so the spec should match that
#
tantek
edited /value-class-pattern (+177) "per http://microformats.org/wiki/microformats2-parsing-issues#parsing_a_dt-_property, do not imply 00 seconds, ok for minutes though because common use"
(view diff)
#
tantek
edited /microformats2-parsing-issues (+328) "/* parsing a dt- property */ Consensus resolutions: Drop value-class-pattern implying 00 seconds"
(view diff)
gRegorLove joined the channel
#
willnorris
tantek: those parsed values still show the use of "T" rather than a space separator. Is that still the recommendation, or should that be updated? Not sure if you feel like there was consensus on that
#
tantek
working on that update now
#
tantek
like code changes, sometimes I prefer atomic spec updates, especially to older more stable specs
miklb joined the channel
#
tantek
edited /value-class-pattern (+369) "more updates for do not imply 00 seconds (except artificial precision needed by iCalendar and Atom), use " " char for separator if needed"
(view diff)
#
tantek
edited /microformats2-parsing-issues (+144) "/* parsing a dt- property */ Value-class-pattern parsing should instruct to use a single space as the separator"
(view diff)
#
tantek
!tell willnorris like code changes, sometimes I prefer atomic spec updates, especially to older more stable specs. Regardless, vcp parsed values now use " " (space char) separator rather than "T" when combining separate date and time. No consensus on *replacing* *author* use of "T" as separator (leave as is seems to be the sentiment)
#
Loqi
Ok, I'll tell them that when I see them next
#
tantek
edited /microformats2-parsing-issues (+200) "/* parsing a dt- property */ dropped: replace a "T" separator (when authored that way) with a single space"
(view diff)
#
tantek
edited /microformats2-parsing-issues (+36) "resolved "parsing a dt- property" issue"
(view diff)
#
tantek
!tell willnorris all those dt-* parsing issues should be resolved now: http://microformats.org/wiki/microformats2-parsing-issues#parsing_a_dt-_property let me know if you have any more questions!
#
Loqi
Ok, I'll tell them that when I see them next
#
tantek
!tell willnorris also, would love to see you at the IndieWeb Summit! http://2016.indieweb.org/
#
Loqi
Ok, I'll tell them that when I see them next
willnorris joined the channel
#
Loqi
willnorris: tantek left you a message 1 hour, 3 minutes ago: like code changes, sometimes I prefer atomic spec updates, especially to older more stable specs. Regardless, vcp parsed values now use " " (space char) separator rather than "T" when combining separate date and time. No consensus on *replacing* *author* use of "T" as separator (leave as is seems to be the sentiment)
#
Loqi
willnorris: tantek left you a message 42 minutes ago: all those dt-* parsing issues should be resolved now: http://microformats.org/wiki/microformats2-parsing-issues#parsing_a_dt-_property let me know if you have any more questions!
#
Loqi
willnorris: tantek left you a message 40 minutes ago: also, would love to see you at the IndieWeb Summit! http://2016.indieweb.org/
#
tantek
tlksio is a place for finding talks
#
tantek
I feel like this is a pattern. People are frustrated by not being able to find something (web search fail / Google / Yahoo etc.), so they build a silo to collect all the stuff which is then horribly incomplete and eventually likely dies of neglect, or acquishutdown.
elux, KevinMarks, willnorris, laughinghan, sagerdearia, tantek and omarhuanca joined the channel
#
omarhuanca
hi everyone
willnorris joined the channel
#
omarhuanca
I have a question about image about structure hentry
#
tantek
hello omarhuanca what is your use-case you're trying to use h-entry for?
#
omarhuanca
I use h-entry for my project, current I need document about this
#
tantek
great!
#
tantek
Reminder US West Coast folks! HWC tonight in LA, SF, PDX!
#
omarhuanca
maybe a image about structure?
#
tantek
I don't understand what that means - could you give an example?
#
omarhuanca
I have a example, I need a image represent items
willnorris, KartikPrabhu and miklb joined the channel