#microformats 2017-03-19

2017-03-19 UTC
[kevinmarks], tantek, KartikPrabhu, gRegorLove and jkphl joined the channel
#
jkphl hi all! can you recommend any resources or best practice on how to markup session that are part of an h-event (basically subevents)?
#
tantek jkphl, it's something that's been brainstormed but nothing concrete yet
#
tantek so for now, just child h-events
tantek joined the channel
#
jkphl tantek: thanks! (interesting use case for my micrometa parser btw)
#
tantek jkphl interesting! are you looking to consume multipel h-events per page? or building some kind of event / calendar program or?
#
jkphl tantek: yes, exactly (the programme schedule for the nuremberg web week, ~100 events with potentially multiple sessions each)
#
tantek wow
#
jkphl one more question (tricky one i guess): if an event has it's own social media profiles, contact details (b/c it has its own website) plus several event profiles (on facebook, g+ etc.), how would you cram that into the h-event?
#
tantek those are all URLs
#
jkphl (it's not the details to the organizer which would go into p-organizer obviously)
#
jkphl ah, ok. what about phone links? u-url / p-tel (which doesn't seem to exist for h-event, officially at least)
#
tantek I think it's ok to just put all the URLs (whether social media profile, website) as u-url
#
tantek a phone just for the event? I've never seen that
#
tantek a phone for the organizer of the event yes
#
tantek pretty sure phone companies require a person or company to be assigned the phone number
#
tantek thus that's a p-organizer h-card
#
tantek or part of
#
tantek p-tel on h-event makes no sense
#
jkphl i'm not sure if people really use it, but our event management interface has an option for it at least. a use case could be a ticket hotline somewhere (but we don't have any details about the people behind, so it's hard to make an h-card of it, isn't it?)
#
jkphl it's not necessarily the phone number of the organizer (who has his own phone number option btw, but in this case it's clearly a part of p-organizer)
#
tantek my point is to get a phone number, you have to fill out a form with the phone company with the name of a person or organization entity
#
jkphl it's similar with email addresses: as an event can have its own domain, it might also have its own email address, which isn't necessarily the same as the organizer's one. u-url on h-event?
#
tantek not at all, you can create email addreses on a whim
#
tantek but not phone numbers
#
tantek and yes, you could use a u-url mailto: on an h-event for that
#
Zegnat If u-url mailto is fine, then u-url tel would work for phones
#
jkphl great, thanks. i guess i'll simply move the event phone number to the organizer and replace his one in case both are given.
#
Zegnat i.e. what makes mailto and tel different?
#
jkphl good point, Zegnat. is u-tel officially specced somewhere? would be much more appropriate b/c we link the phone numbers anyway ...
#
Zegnat u-tel works with most parsers I have tested, I use u-tel on http://vanderven.se/martijn/
#
Loqi Martijn van der Ven h
#
Zegnat u- and p- are specced by the mf2 format spec, and -tel by the h-card spec. You should always be able to use any prefix with any property. No need for separate specs.
#
jkphl sounds like a plan then ;)
#
Zegnat My comment was mostly about why there would be a difference between .u-url[href^="mailto:"] and .u-url[href^="tel:"]. If -tel isn't available in the spec but -url is, you can still sneak a phone number in there.
#
tantek there is no u-tel
#
tantek there can be u-url with tel:
#
tantek (in h-event)
#
jkphl tantek: the combination of "u-url p-tel" should be possible though, right?
#
jkphl (well, besides the point that there's no p-tel for h-event)
#
jkphl (say, for h-card then at least)
#
Zegnat That wouldn't make a lot of sense, jkphl. You would get a url and a tel property with the same value.
#
Zegnat That's interesting to me, tantek :) Basically it means any format that accepts *-url can have a phone number associated with it through the tel-protocol.
#
jkphl Zegnat: sure. but i do see a point in both considering it a URL *and* a phone number. both are valid observations that go beyond just taking it as a string.
#
tantek Zegnat, sure it can, however, don't expect any consuming code to do anything special with it, since it won't be expected outside of an h-card
#
tantek that's the point of the vocabularies, to document what consuming code for those use-cases is likely to pay attention to
#
Zegnat tantek, agreed.
#
Zegnat Though I find microformats are mostly governed by how it is being used in the wild. So I feel completely fine using u-tel :D
#
jkphl as i seem to have to decide between u-url and p-tel, i think i go with p-tel as i consider it more specific in terms of content classification
davidmead and [kevinmarks] joined the channel
#
[kevinmarks] The difference is whether you want the href or the text contents to be parsed from that element
#
Loqi [kevinmarks]: martymcguire[m] left you a message 4 days, 12 hours ago: i finally created that .u-* to .util-* pull request for Skeleton: https://github.com/dhg/Skeleton/pull/348
tantek joined the channel
#
tantek martymcguire++ great work with https://github.com/dhg/Skeleton/pull/348
#
Loqi martymcguire has 1 karma in this channel (11 overall)
[kevinmarks], [eddie], davidmead, tantek, KartikPrabhu, KevinMarks and gRegorLove joined the channel