#microformats 2017-09-12

2017-09-12 UTC
[kevinmarks], rodolfojcj, tantek and vivus joined the channel
#
vivus
Hello all.
#
vivus
Zegnat: what OS do you use?
barpthewire joined the channel
#
@gRegorLove
@kimadactl Not sure about crawling. Calagator can import events from hCalendar (microformats1) and there's a request to support h-event (microformats2)
(twitter.com/_/status/907488538303893506)
#
Zegnat
vivus: I am on macOS
[pfefferle] and nitot joined the channel
#
Zegnat
Did you ever get h2vx running, vivus?
nitot joined the channel
#
vivus
Zegnat: I re-cloned the repo, did not make any modifications to the code, except for the sharing.js you did. The result I got was: no tidy :(No hCards found
#
Zegnat
Yeah, there is no installation guide for h2vx. It requires HTML Tidy available to PHP.
#
Zegnat
I have some projects where I modify HTML through DOMDocument and run it through Tidy, so I already had that set-up
nitot and [kevinmarks] joined the channel
#
vivus
HTML Tidy? Zegnat
#
vivus
Zegnat: finally, it works!
#
vivus
I was missing tidy
#
Zegnat
Sorry for slow replies, I am in class.
#
Zegnat
Yeah, Tidy is a PHP extension. But I guess you figured that out :)
#
vivus
took a while to get it working. Zegnat , how do I add instructions to make the setup easier for others?
#
vivus
are there any h-card generators in the wild?
#
Zegnat
I think veganstraightedge used to have a tool where people could create hcards. Don't have a link ready though.
#
Zegnat
vivus pull requests are always welcomed, just work on the README if you want to improve documentation.
#
vivus
Zegnat: there is no readme for the h2vx site
#
vivus
I could create a CLI-tool for it. Zegnat do you have a link to the full list of properties for h-cards?
nitot joined the channel
#
Zegnat
vivus: http://microformats.org/wiki/h-card#Properties is a list of the common ones.
#
Loqi
h-card
#
Zegnat
But microformats are very flexible and extendable. See e.g. http://vanderven.se/martijn/ for a big h-card.
#
Loqi
Martijn van der Ven
#
Zegnat
If you want to build vcards, it might be better to work back from vcard properties and finding out what microformats people are using to describe them.
rodolfojcj joined the channel
#
vivus
Zegnat: for now, I am targeting building a mf2 generator for h-cards
#
vivus
what programming languages are you familiar with? Zegnat
nitot, [pfefferle] and barpthewire joined the channel
#
@cat_and_cat3
どーもワードプレスでマークアップをしようとすると、 microformatsがじゃましてschemaの効果が効かない、、、 どうやったらmicroformatsの息の根を止められるかな。
(twitter.com/_/status/907593705443401729)
#
Zegnat
vivus, I work with the web, mainly JavaScript and PHP. Though I have worked a little with Ruby and C++.
#
vivus
Zegnat: did you compose your h-card manually?
#
Zegnat
I would look for a mf2 parser in whatever language you are using, and skip writing the parser yourself. If that is an option for you.
#
Zegnat
Yes, my homepage is all manual HTML
#
vivus
Zegnat: maybe my language was unclear. I want to build an app that allows people to generate h-cards. None exist (from what I know)
#
vivus
Unless you know of a strategy where I can hack a generator via a parser
#
Loqi
[veganstraightedge] h-card-as-a-service
#
Zegnat
That’s the project I was referring to earlier today. Just got home, so I was only now able to dig it up.
#
vivus
awesome. you may have saved me enormous amounts of time :)
[kevinmarks] joined the channel
#
[kevinmarks]
Also, remember indiewebify.me will check them
#
vivus
[kevinmarks]: are you chatting on a slack group?
#
sebsel
vivus The IndieWeb Slack's channel #microformats (see http://indieweb.org/discuss) is bridged to this channel.
#
vivus
wait, that doesn't make sense. why would an indieweb use a slack group?
adactio joined the channel
#
sebsel
I'm afraid this is not the right channel to discuss that, but it's just one way to join the discussion :)
#
vivus
where should I discuss it? sebsel
#
sebsel
#indieweb-meta?
#
vivus
that channel is empty :)
#
sebsel
without the question mark certainly not. I'm in it.
#
[kevinmarks]
I use slack on my phone more because I don't have an irc bouncer set up.
TallTed, KevinMarks, Kevinmarks1 and tantek joined the channel
#
@m4rseo
https://jsonld.com Des exemples super complets pour vos microformats en JSON
(twitter.com/_/status/907639217060270081)
KartikPrabhu, KevinMarks, rodolfojcj and gRegorLove joined the channel
#
tantek
Would it be helpful to have a navigable set of actual microformats in JSON like that?
#
aaronpk
like what?
#
aaronpk
jsonld . com is blocked according to my list of blocked domains (malware)
#
tantek
but not blocked by Twitter then
#
tantek
it's a WordPress site - so if there's malware it was likely planted externally
#
tantek
I mean, that's from 2017-08-31 so who knows if that is out of date, but curious if you can find evidence of mal. I did a quick view source scan and didn't see anything (beyond WordPress 4.8.1 - which is the latest)
[kevinmarks] joined the channel
#
tantek
ok so here's the weird thing - they have no actual JSONLD example in their example pages, e.g. https://jsonld.com/article/
#
aaronpk
ok i'll whitelist it
#
tantek
nor in the source! so they're not using JSONLD themselves
#
tantek
dogfoodfail
#
tantek
oh weird, they're including it remotely via JS from github
#
tantek
to display on the page visibly
#
tantek
but they don't have any "application/ld+json" in the source of their own pages which is quite ironic.
rodolfojcj joined the channel
#
[kevinmarks]
They have mf2 though
#
tantek
wait what
#
tantek
on what page? I didn't see any on /article
#
tantek
I'm guessing compat mf1 seen by your parser
#
[kevinmarks]
Ah, mf1 yes
#
[kevinmarks]
With my wp compatiblity extensions
#
tantek
oh? are those documented somewhere? like as a backcompat proposal?
#
tantek
(for parsers)
#
tantek
yeah it's hAtom from their WP theme
#
[kevinmarks]
I think I did.
#
[kevinmarks]
See the h-feed mapping
#
tantek
hey there's no backcompat section in the h-feed spec!
#
tantek
not sure how I missed that
#
[kevinmarks]
Hm, I should fix that.
barpthewire joined the channel
#
tantek
I'll get to it eventually, but if you want to take a crack at it, start by cloning the structure of http://microformats.org/wiki/h-entry#Backward_Compatibility
#
[kevinmarks]
The top level stuff in hAtom was pretty sparse
#
tantek
it's ok to start backcompat as minimal / sparse
#
tantek
that's a good way to start it,
#
tantek
and then add "Proposed" for the stuff you've discovered
#
tantek
similar to how http://microformats.org/wiki/h-entry#Backward_Compatibility has a couple of "Proposed" items
KevinMarks_ joined the channel
#
Loqi
[Tantek Çelik] h-entry is a simple, open format for episodic or datestamped content on the web. h-entry is often used with content intended to be syndicated, e.g. blog posts. h-entry is one of several open microformat standards suitable for embedding data in HTML. ...
#
tantek
well that was odd Loqi - why show a link preview the second time and not the first?
#
tantek
hmm - there shouldn't be a separate "Parsing" section there on h-feed
#
tantek
that's an error. those kinds of extension should only be for backward compat
#
tantek
fixing
#
tantek
that I can't leave be
KevinMarks joined the channel
#
tantek
edited /h-feed (+472) "replace misleading "Parsing" section with "Backward Compatibility" stub sections"
(view diff)
#
tantek
ok KevinMarks, backcompat section stubbed very minimally with the content that was there - stub warnings etc.
#
Loqi
h-feed
#
[kevinmarks]
Partly hAtom didn't specify anything at the hfeed level, which was a bit of an omission. Part of that is that Atom has the slightly odd inheritance model between feed and entry
KevinMarks_ joined the channel
#
tantek
and we didn't manage to verify any of that odd inheritance with real world examples so we should ditch it by default
#
tantek
until we find actual examples we can't solve any other way
#
[kevinmarks]
Author inheritance was used
#
[kevinmarks]
But author discovery covers that I think
#
tantek
right, we separated it out to a specific algorithm, instead of making the format more complicate
#
[kevinmarks]
Omitting title and subtitle at the feed level was a bit odd though. I don't remember how we got there
#
tantek
conceptually or backcompat? we have p-name and p-summary
#
[kevinmarks]
Backcompat. We fixed it in h-feed but hAtom had nothing top level except category
KevinMarks joined the channel
#
gregorlove
edited /h-feed (+3) "/* Parser Compatibility */ fix </span>"
(view diff)
#
gregorlove
edited /h-feed (-3) "/* Parser Compatibility */ https indieweb url"
(view diff)
#
tantek
? that first edit. Good sign I should get/make (late) lunch.
#
tantek
gRegorLove++ thanks for promptly noticing/fixing :)
#
Loqi
gregorlove has 14 karma in this channel (181 overall)
KevinMarks_ and KevinMarks joined the channel
#
kevin marks
edited /h-feed (+238) "/* Parser Compatibility */ wordpress suggestions"
(view diff)
[cleverdevil], KartikPrabhu1 and globbot joined the channel