2024-07-30 UTC
# 
Zegnat I would personally not merge it into a single parser implementation. I would leave the file type detection to the consumer, who can then pick the correct mf2 parser. (Ie. either an HTML or XML based parser.) So rather than expanding every mf2 parser, I would see (if the usecase exists) which steps need to be taken to go from XML->mf2 json