freenode :: #microformats

19 Mar 2017
06:59jkphlhi all! can you recommend any resources or best practice on how to markup session that are part of an h-event (basically subevents)?
07:40tantekjkphl, it's something that's been brainstormed but nothing concrete yet
07:40tantekso for now, just child h-events
08:29jkphltantek: thanks! (interesting use case for my micrometa parser btw)
08:31tantekjkphl interesting! are you looking to consume multipel h-events per page? or building some kind of event / calendar program or?
08:33jkphltantek: yes, exactly (the programme schedule for the nuremberg web week, ~100 events with potentially multiple sessions each)
08:33tantekwow
08:34jkphlone 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?
08:34tantekthose are all URLs
08:34jkphl(it's not the details to the organizer which would go into p-organizer obviously)
08:35jkphlah, ok. what about phone links? u-url / p-tel (which doesn't seem to exist for h-event, officially at least)
08:35tantekI think it's ok to just put all the URLs (whether social media profile, website) as u-url
08:35tanteka phone just for the event? I've never seen that
08:35tanteka phone for the organizer of the event yes
08:36tantekpretty sure phone companies require a person or company to be assigned the phone number
08:36tantekthus that's a p-organizer h-card
08:36tantekor part of
08:36tantekp-tel on h-event makes no sense
08:37jkphli'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?)
08:38jkphlit'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)
08:39jkphlit'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?
08:39tantekmy 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
08:40tanteknot at all, you can create email addreses on a whim
08:40tantekbut not phone numbers
08:40tantekand yes, you could use a u-url mailto: on an h-event for that
08:41ZegnatIf u-url mailto is fine, then u-url tel would work for phones
08:41jkphlgreat, thanks. i guess i'll simply move the event phone number to the organizer and replace his one in case both are given.
08:42Zegnati.e. what makes mailto and tel different?
08:42jkphlgood point, Zegnat. is u-tel officially specced somewhere? would be much more appropriate b/c we link the phone numbers anyway ...
08:43Zegnatu-tel works with most parsers I have tested, I use u-tel on http://vanderven.se/martijn/
08:43LoqiMartijn van der Ven h
08:44Zegnatu- 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.
08:44jkphlsounds like a plan then ;)
08:46ZegnatMy 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.
08:46tantekthere is no u-tel
08:46tantekthere can be u-url with tel:
08:46tantek(in h-event)
08:47jkphltantek: the combination of "u-url p-tel" should be possible though, right?
08:48jkphl(well, besides the point that there's no p-tel for h-event)
08:48jkphl(say, for h-card then at least)
08:48ZegnatThat wouldn't make a lot of sense, jkphl. You would get a url and a tel property with the same value.
08:49ZegnatThat'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.
08:49jkphlZegnat: 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.
08:51tantekZegnat, 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
08:51tantekthat's the point of the vocabularies, to document what consuming code for those use-cases is likely to pay attention to
08:51Zegnattantek, agreed.
08:52ZegnatThough I find microformats are mostly governed by how it is being used in the wild. So I feel completely fine using u-tel :D
08:54jkphlas 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
15:06[kevinmarks]The difference is whether you want the href or the text contents to be parsed from that element
15:06Loqi[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
15:23tantekmartymcguire++ great work with https://github.com/dhg/Skeleton/pull/348
15:23Loqimartymcguire has 1 karma in this channel (11 overall)
20 Mar 2017
No messages
   
Last message: 97 days and 22 hours ago