jkingwebAfter three years I'm finally adding h-feed processing to my generic newsfeed parser. It's been a long time coming, but thankfully so far the IndieWeb wiki is being very helpful.
jkingwebI can see why there's interest in a simpler representation (viz. jf2) for Microformats, because working with the standard structure gets convoluted quickly.
[snarfed]yup. I like the schema itself a lot, and a lot of the lower level design decisions, eg that everything is multiply valued. but the flexibility and minimal high level structure, ie where h-entries vs h-feeds vs [representative] h-cards are, do make those parts more complicated to handle
jkingwebDefinitely. One's head spins a bit at how complex (in code) a simple four-step algorithm actually is. But it's clear, I must say. I'm not confused about what I need to do, just wondering how best to write it down so I have a hope of being able to understand it when I look at the code in future.
ulhar4409i'm in a funny spot where i "want to" have an MF2 parser in my codebase (maybe even a proper library that makes it easier to work with in code) but the algorithm behind it is so daunting to me :P
jkingwebThe mf2 parsing algorithm is pretty complex, yeah, not to mention ambiguous in some spots. I was able to write a generic parser in a week, though I then spend months off and on supplementing the test suite, because much of what is specified was not actually tested.
jkingweb Definitely. One's head spins a bit at how complex (in code) a simple four-step algorithm actually is. But it's clear, I must say. I'm not confused about what I need to do, just wondering how best to write it down so I have a hope of being able to understand it when I look at the code in future.