#microformats 2016-07-19

2016-07-19 UTC
#
tantek
edited /microformats2-parsing-brainstorming (+475) "/* Parse img alt */ nested h-image, is workable, but requires author use of that structure"
(view diff)
#
tantek
I wonder if it is ok for microformats to require the author to use a nested h-image if they want the alt text to propagate with the u-photo
#
tantek
btw this also works for <object> instead of <img>!
#
aaronpk
edited /microformats2-parsing-brainstorming (+803) "/* Parse img alt */ split into sections, add code examples"
(view diff)
#
tantek
drat what
#
aaronpk
edited /microformats2-parsing-brainstorming (+0) "/* Make photo property an object */ oops just realized it's h-image"
(view diff)
#
aaronpk
sorry were you editing too?
#
tantek
aborts his edit
#
aaronpk
heh, the challenges of in-place editing
#
tantek
edited /microformats2-parsing-brainstorming (+504) "/* Make photo property an object */ object works like img, use source tags, use "featured" to reduce confusion of what "photo" applies to"
(view diff)
#
aaronpk
oh nice forgot about <source> tags
#
tantek
aaronpk, I kind of see the raw ability to extract and use URLs, e.g. u-photo or whatever as similar to HTTP requesting a .jpg URL
#
tantek
when a browser requests a .jpg, it's not like HTTP provdes an "ALT: here's a text alternative" in the return header
#
tantek
so it should be OK to have the ability to *just* upload images
#
tantek
or any other random binary
#
aaronpk
interesting
#
tantek
however what's missing is *a* way to provide alt-text pairing with that image if that's what you want to upload
#
tantek
and that's what an h-image would provide
#
tantek
micropub media endpoint in that sense is like HTTP, it just provides a raw place to upload a binary resource
#
aaronpk
that makes sense
#
aaronpk
so the media endpoint doesn't know about alt text, the alt text would be added when the image is used in a post
#
tantek
edited /microformats2-parsing-brainstorming (+842) "/* Make photo property an object */ have u-* on an img automatically create an object if there is a non-empty 'alt' attribute"
(view diff)
#
tantek
aaronpk, yes that is one possible approach
#
tantek
also I just captured what I think you were suggesting, maybe from voxpelli earlier about only creating an object if there is a non-empty alt
#
tantek
I honestly don't know which approach will be better
#
tantek
this deserves broader discussion
#
tantek
The "2." approach would have the side-effect of being scalable to "lang" or "id" or potentially any other attribute we wanted to "pass through"
#
tantek
aaronpk, can you try writing up the object structures in either case so we can compare?
#
tantek
and then I'd like to get feedback from folks using mf2 JSON
#
aaronpk
edited /microformats2-parsing-brainstorming (+319) "/* Make photo property an object */ add html/json example"
(view diff)
#
aaronpk
like that?
#
tantek
looks good
#
KevinMarks_
Would u-featured be an image that is purely presentational?
#
tantek
purely presentational is like little decorative doo-dads for the corners etc.
#
tantek
u-featured means a featured photo
#
tantek
representative of an article the way news articles have a featured photo
#
tantek
that's definitely a specific meaning that is being conveyed
#
tantek
aaronpk: I'm leaning toward "2." because it causes more "automatic accessibility"
#
tantek
in terms of the "alt" information getting passed through
#
tantek
edited /microformats2-parsing-brainstorming (+522) "/* Parse img alt */ discussion section, leaning towards "Make photo property an object" brainstorm "2.""
(view diff)
#
tantek
edited /microformats2-parsing-brainstorming (+8) "/* img alt discussion */ /div"
(view diff)
#
aaronpk
now that's where the github thread becomes more useful :)
davidmead joined the channel
#
tantek
aaronpk - maybe? I'd rather keep a summary of current preferences somehow
#
tantek
rather than back/forth discussion that's hard to figure out what people actually want
#
aaronpk
heh interesting
#
tantek
like I don't feel like a "debate" framing is helpful here
#
tantek
because I don't want to feel like defening a particular proposal / position
#
tantek
s/defening/defending
#
aaronpk
so you would update that discussion item if you revise your opinion?
#
tantek
like I did with my opinions on indieweb.org options
#
tantek
maybe "discussion" is the wrong term there
#
tantek
I'm not sure what to call it
#
tantek
"current opinion"
#
aaronpk
yeah that'd be better
#
tantek
maybe thoughts
#
aaronpk
edited /microformats2-parsing-brainstorming (+578) "/* img alt discussion */ my thoughts"
(view diff)
#
tantek
oops I did it again
#
tantek
edited /microformats2-parsing-brainstorming (+181) "/* img alt discussion */ more thoughts than discussion."
(view diff)
#
tantek
edited /microformats2-parsing-brainstorming (+249) "/* img alt thoughts */ emergence convergence -> go back to github to discuss that specific proposal to see if we can get consensus"
(view diff)
#
tantek
edited /microformats2-parsing-brainstorming (-1) "/* img alt thoughts */"
(view diff)
#
kevin marks
edited /microformats2-parsing-brainstorming (+390) "/* img alt thoughts */ specific alt makes sense"
(view diff)
#
KevinMarks_
The web version of the Log says loqi edited
KevinMarks, KevinMarks_, tantek, gRegorLove, iwaim_, dogada, nitot, adactio and Garbee joined the channel
#
@gary_schroeder
Whatever happened to #microformats? Remember those?
(twitter.com/_/status/755363029538201600)
TallTed joined the channel
#
@boatempire1
Microformats: Empowering Your Markup for Web 2.0 by John Allsopp http://www.amazon.com/dp/1590598148/?tag=4432-20
(twitter.com/_/status/755413657668890625)
nitot, nitot_, gRegorLove, KevinMarks, tantek, ben_thatmustbeme, iwaim_, sagerdearia and miklb joined the channel
#
aaronpk
lol wat
tantek joined the channel
#
tantek
aaronpk: wat indeed. there are no microformats on that site!
KevinMarks, KevinMarks_ and gRegorLove joined the channel