#microformats 2016-05-12

2016-05-12 UTC
willnorris, tantek, laughinghan, trevor_b and dogada joined the channel
#
@AllTheTwits +Lachlan: It worked in 0.6 Weird. Try to change “actions” to “microformats”. (twitter.com/_/status/730637395377434624)
laughinghan, trevor-b, trevor_b, KevinMarks and petermolnar joined the channel
#
petermolnar morning; question: in a h-card, the u-key entry for pgp should contain the actual key or can it be a url to the key?
adactio joined the channel
#
Zegnat petermolnar: without checking anything, but, the fact that the property is called u-key means that the URL is its value. So URL to key should be exactly what that takes
#
Zegnat If you wanted to put the key in text on the page that would be class="p-key"
#
Zegnat It might be worth updating http://microformats.org/wiki/h-card#Properties as u-key could have a p-key equivalent, and p-tel can also have a u-tel equivalent (as I am using on my site)
#
petermolnar thanks Zegnat
#
Zegnat E.g. https://gist.github.com/Zegnat/2c2a2cb52013a6ab4c3bfe609c5e1895
#
Zegnat !tell tantek Is there any reason /h-card is specifying prefixes for properties like u-key and p-tel? Some people might include their key on page (thus needing p-key) or link to their phone number (thus needing u-tel).
#
Loqi Ok, I'll tell him that when I see him next
Garbee, miklb, KevinMarks and adactio_ joined the channel
#
@JustOpenSourced willnorris just open sourced a repository: https://github.com/willnorris/microformats (twitter.com/_/status/730789099901231106)
dogada, adactio_, adactio, gRegorLove and pabs3 joined the channel
#
pabs3 I'd like to add this to the existing-rel-values wiki page, which section should I add it in? https://joeyh.name/rfc/rel-vcs/
#
kylewm pabs3: http://microformats.org/wiki/existing-rel-values#proposals I think
#
pabs3 thanks, adding
#
pabs3 gah, recaptcha
#
pabs3 and no ssl...
#
paulwise edited /existing-rel-values (+196) "add rel=vcs-*" (view diff)
#
pabs3 thanks again kylewm, hope I did it correctly
MeanderingCode, laughinghan, TallTed, nitot_ and tantek joined the channel
#
tantek I'm in the CSS Houdini meeting and noticed that for custom author published properties, they're using a --author- prefix and I think it may be better for us to adopt that too for custom author published properties
#
Loqi tantek: Zegnat left you a message 7 hours, 15 minutes ago: Is there any reason /h-card is specifying prefixes for properties like u-key and p-tel? Some people might include their key on page (thus needing p-key) or link to their phone number (thus needing u-tel).
#
tantek that is, rather than h-cassis-username, instead we encourage h--cassis-username
#
tantek while it's unlikely we'll have a root class name that starts with h-cassis-, we may have other h-something-name hyphenated root class names or properties, and the double -- avoids any possible collision
#
tantek and secondarily (perhaps more importantly) the "--" after the prefix really helps identify it as a custom root class name or property for folks reading/writing HTML + microformats
#
tantek thoughts?
#
tantek (given the very low usage of author custom root / property names I'm thinking of just going ahead and changing this in the microformats2 spec)
#
tantek Zegnat - the prefixes are there to provide the expected defaults, but of course as you observer any of the parsing prefixes are syntax-valid on any property
#
tantek Zegnat: it may also help to provide examples in the spec with alternative prefixes like that to give authors specific examples of when they may want/need to use different prefixes
#
Zegnat I will write up my telephone number u-tel usecase as soon as I have time again, thanks for confirming what I already thought tantek
#
tantek what is h-card-examples?
KartikPrabhu and laughinghan joined the channel
#
kylewm tantek: would p--p3k-food and p-p3k-food parse as the same property?
#
KartikPrabhu that is most likely a typo
#
kylewm ?
#
KartikPrabhu kylewm: I meant the double hyphen
#
KartikPrabhu is that intentional?
#
kylewm oh, see scrollback
#
kylewm tantek suggested --author- instead of -author- based on similar recommendation in CSS
#
KartikPrabhu oh sorry, this double hyphen is new to me
laughinghan joined the channel
#
aaronpk Is that different from -x somehow?
#
tantek aaronpk, yes, that's already distinguished in the existing /wiki/microformats2 : -x- is for experimental, i.e. conveys an intent toward a common / cross-site standard, whereas --author- is for things the author has no immeidate intention to see work cross-site etc.
#
tantek kylewm: would not parse as same property. rather, p--p3k-food would still obey the p- parsing, and parse as "-p3k-food", which also has the advantage of continuing to look like non-standard, and not expected to be.
gRegorLove joined the channel
#
@wpulsarblog Author hReview Plugin Review http://www.wpulsar.com/author-hreview-plugin/ (twitter.com/_/status/730894019685814272)
sagerdearia, laughinghan, KevinMarks and KartikPrabhu joined the channel