396
results for "microformats hard"
-
↩️ not sure if you ran into it yet but i think a lot of the folks that stuck around are all hanging out doing work with ActivityPub (unless you are looking for hard ontological rdf microformats folks who seem to all be at google)
Loqi
at
2021-06-30 18:25
-
it's going to be a hard one to "get right", as the way timezones work in vcard/ical is very weird, and timezones as a whole are an iffy thing to denote (quite the disconnect between complexity, automated processing ability, actually representing what a user would want to show/display or already does on their homepage, and actually representing something useful to parse and do something with)
[tantek]
at
2021-06-22 20:15
-
one of the reasons for this was that a lot of the classic microformats parsers were necessarily based on hard-coded classnames, and they were a lot of work to maintain and went out of date quickly
barnaby
at
2021-06-12 21:04
-
if you’re using php-mf2, then you already have a DOMDocument available, which has done a lot of the hard work of resolving URLs, dealing with encodings, etc
barnabywalters
at
2021-05-25 19:32
-
I think part of that problem is that consuming HTML is hard. The mf2 parser makes it easier by narrowing down what HTML you have to deal with, but as soon as e-* properties are involved, consumers have to worry about potentially non-trivial transformations if they want to work with it
barnabywalters
at
2021-05-25 19:14
-
yeah this is hard to read :)
aaronpk
at
2021-04-23 23:39
-
Whether that's due to microformats h-card classed, or just Google using that text, is hard to say.
btrem
at
2021-04-08 02:19
-
I'm also hard pressed to think of a way to use MathML in microformats. Nothing comes to mind at the moment.
btrem
at
2021-04-08 01:28
-
But then, I'm hard-pressed to think of a reason for using anything other than the `<time>` element for a dt property.
btrem
at
2021-04-08 01:27
-
btrem: that could be done by doing a hard specification though
jacky
at
2021-02-20 03:28