#microformats 2015-11-28

2015-11-28 UTC
fuzzyhorns and davidized joined the channel
# 05:43 
@JustinAHammonds Author Hreview Review - #Increase #Search #Traffic With Eye Catching SERPS http://www.matthewwoodward.co.uk/reviews/author-hreview-review-increase-search-traffic-with-eye-catching-serps/ (twitter.com/_/status/670478180000604161)
# 05:43 
@JustinAHammonds Author Hreview Review - #Increase #Search #Traffic With Eye Catching SERPS http://linkis.com/co.uk/TFOCr (twitter.com/_/status/670478205111951360)
KartikPrabhu, krijnhoetmer, fuzzyhorns, tantek and nitot joined the channel
# 13:21 
@hasanvirus4 Felicity Keith&rsquo;s Language Of Desire Review &ndash; Dirty Words, Dirtier Phrases, And A Whole Lot Of Verbal Viagra hreview-d (twitter.com/_/status/670593481266569217)
fuzzyhorns, nitot, davidized, nitot_ and Calli joined the channel
# 16:46 
Calli If I follow
# 16:48 
Calli The Microformats-2 parsing spec for a property that is also a root, I find it hard not to produce both the value for the property *and* the structure for the item. But other parsers end up with only the structure for the item.
# 16:51 
Calli Seems like the spec is missing some wording about what to do in this case? Or I'm just not seeing where it is.
# 16:52 
Calli Spec says "add properties found to current microformat's properties: { } structure"
# 16:53 
Calli Then spec says "if that child element itself has a microformat ("h-*" or backcompat roots) and is a property element, add it into the array of values for that property"
# 16:54 
Calli And these seem to be separate steps in a sequence
# 16:55 
Calli So I end up with two values in an array: for example, the inner text when following the property parsing rules and the structure when following the item parsing rules
Calli_, davidized, nitot, tantek, fuzzyhorns, davidmead, gRegorLove, KevinMarks_, KevinMarks__ and KartikPrabhu joined the channel