#microformats 2017-02-22

2017-02-22 UTC
[cleverdevil], nitot, KartikPrabhu, [keithjgrant], [acegiak_net], davidmead, KevinMarks, KevinMarks_, [scottgruber], uf-wiki-visitor and AndySky21 joined the channel
#
AndySky21
Added proposal to h-event: http://microformats.org/wiki/h-event#Properties . Feedback is appreciated.
#
Loqi
h-event
AndySky21_, bigbluehat, TallTed, KartikPrabhu and uf-wiki-visitor joined the channel
#
uf-wiki-visitor
hello, I'm looking at the possibility of a new microformat for spoilers. Is there anything you currently have that might cover it? I've spent quite a while looking through the other proposals here: http://microformats.org/wiki/exploratory-discussions . But I haven't found anything that looks close.
#
Loqi
Exploratory Discussions
#
Zegnat
Hi! No, I do not think there is such a thing as a spoiler mf yet. In what context would you use it?
#
AndySky21
I suppose you mean a post talking about an extensive work whose reading would spoil the suspense effect? Well then there should be a property on h-entry
#
uf-wiki-visitor
I was thinking more of things that the internet often spoills such as sporting event outcomes. Or TV/Movie endings & twists. If authors could mark up potential information that could ruin a users experience, the browsers (or extensions) could hook in to this and hide info based on the users desires.
#
uf-wiki-visitor
e.g.
#
uf-wiki-visitor
<div class="spoiler"> <div class="sport"> <p class="F1"><span class="individual">Lewis Hamilton</span> <span class="outcome">wins</span> the <time class="event" datetime="2017-01-14">UK Silverstone Grand Prix.</time></p> </div> </div>
#
Zegnat
that feels like a lot of hidden metadata there.
#
AndySky21
well we're talking about post however, so it should be added to entry.
#
Zegnat
AndySky21, I am not sure about that. Would an entire post classify as spoiler in its entirety? The spoiler might only be part of a book h-review.
#
Zegnat
Though if an entire h-entry can be marked as being a spoiler, applications could hide it based on the h-entry's tags. Which would be a nice way to get rid of things like the hidden sport/F1 classes from the example above.
#
uf-wiki-visitor
While wrestling with this problem I've also noticed that. It could be a partial part of a post. Or the entire thing could be a spoiler. It feels like it should be an extension to something existing, rather than a whole new thing though
#
uf-wiki-visitor
reading through the h-entry docs. This seems like a natural area for a spoiler context to exist.
#
AndySky21
like e-spoiler : part of content giving potentially unwanted information about the original subject, not to be shown unless allowed by the user
#
Zegnat
How would that work as part of the post? e-spoiler nested within e-content?
#
AndySky21
that'd be the idea I suppose
#
KartikPrabhu
all of this would be useless unless we have examples of something that would consume such data
#
KartikPrabhu
browsers themselves do not look for any microformats AFAIK
#
uf-wiki-visitor
Its a fair point. But also its, a Chicken and egg scenario. If you don't have something in a standardised way. Why would you build anything for it?
#
AndySky21
this could work for search engines. Spoiler sections are not to be shown by SE widget/preview
#
KartikPrabhu
no, I mean does anyone consume anything like that on a page?
#
uf-wiki-visitor
I was coming at it more from a user need point of view. The internet spoils many things and we may be able to provide a way to fix that.
#
AndySky21
for sure this won't be implemented at UA level, like most extended semantics. It could work for content reposting/embedding/lookup
#
uf-wiki-visitor
News articles frequently publish results to big sporting events in their headlines as a way to get more users reading them. But also spoil the result for others who haven't had time to watch on catch-up TV.
#
KartikPrabhu
uf-wiki-visitor: individual sites can provide that themselves. The use of microformats would be to have it cross-site
#
KartikPrabhu
I haven't seen any such publisher use mf2 in the first place
#
uf-wiki-visitor
fair point, I hadn't considered syndication, my bad.
#
KartikPrabhu
uf-wiki-visitor: one good practice would be to implement such a proposal yourself
#
KartikPrabhu
on some thing you publish
#
AndySky21
as far as half mf2 are marked as draft while being defined as stable, nobody wants to rely upon that
#
AndySky21
On a side note: does anybody know who to ask about changing username on the wiki? sorry for the OT
#
Zegnat
Not sure who manages the wiki. aaronpk (ping) would know
#
uf-wiki-visitor
thanks for the feedback all, I'll see what I can think of and try perhaps implementing something as a proof of concept.
#
KartikPrabhu
uf-wiki-visitor: yes that would be a good thing. :)
#
AndySky21
Zegnat, how can I contact aaronpk about that?
ben_thatmustbeme joined the channel
#
aaronpk
Not me, I'm not a wiki admin. Ask Tantek.
#
AndySky21
I'm not sure such an issue is worth that..
#
KartikPrabhu
AndySky21: AFAIK there was no way to change username, one had to make a new account
#
AndySky21
i'll stick with current nn then. Thanks
tantek_ and [kevinmarks] joined the channel
#
[kevinmarks]
Hi uf-wiki-visitor - do read the process page and gather examples of how people publish spoiler warnings already
#
@refschool
est ce que vous pensez que les microformats sont utiles pour un site de ecommerce?lequels? je vois pas grand chose
(twitter.com/_/status/834446390365401090)
AndySky21 and [kevinmarks] joined the channel
#
[kevinmarks]
Tvtropes.org would be a good one to check
#
AndySky21
What can be a good way to use p-rsvp in conjunction with h-event?
#
aaronpk
there's some good examples here https://indieweb.org/rsvp
#
AndySky21
what if I wanted to list participants in an event page marked up as h-event, maybe using p-attendee? how wrong would that be?
#
aaronpk
i think that's been prototyped too
#
Loqi
h-event
#
AndySky21
h-event p-attendee is meant for h-card as of now. Which does not allow for anything but personal info
#
aaronpk
what do you mean?
#
AndySky21
p-attendee - a person attending the event, optionally embed h-card (from h-event)
#
aaronpk
you asked about listing participants
#
AndySky21
listing participants usually involves a participating status - that's why i hoped to use p-attendee in conjunction with h-entry instead of h-card
#
aaronpk
in general, mf2 parsing doesn't care about the types of things, the parsers will all produce a result still. it's only the consumers of the data that care about whether e.g. the p-attendee value is an h-card vs a plain string or some other things
#
aaronpk
ah yeah, i think that's the note on the indieweb wiki about "not sure how to indicate RSVP status for each" https://indieweb.org/event#Markup_design
#
aaronpk
there is definitely room for experimentation here. there aren't a lot of examples of pages with mf2 that list attendees
#
aaronpk
following http://microformats.org/wiki/process the thing to do would be to analyze how existing event websites list attendees and people who said they can't come, etc
#
AndySky21
I also quickly read the page about defining rsvp, when it was decided it could be a property of h-entry
#
Loqi
The microformats process
KartikPrabhu joined the channel
#
AndySky21
aaronpk, what if existing sites don't implement a microdata rsvp structure?
#
AndySky21
microformat*
#
aaronpk
it's more about finding what *content* they are publishing and in what structure the content is
#
aaronpk
which is why you'll find examples of things like facebook here https://indieweb.org/event#Silo_Attendees
#
AndySky21
I will try and search something. as a baseline I put a suggestion on h-event to list p-attendee as standard rather than experimental and maybe use it for rsvp.
#
AndySky21
for what i know event always list participants along with participation status (e.g. by groups)
#
aaronpk
!tell tantek h-event needs the change control section that h-entry has
#
Loqi
Ok, I'll tell them that when I see them next
AndySky21, gRegorLove, KevinMarks, tantek_, nitot_ and KartikPrabhu joined the channel
KevinMarks, AndySky21 and tantek_ joined the channel