This is exactly where XML is the only right choice. JSON is much simpler than XML, thats why lots of people like it. However for documents XML markup is more appropriate. The reasons:
- Allows extensibility with other xml standards (such as SVG and MathML in your resume, which might makes sense)
- Allows linking to other stuff with XLink
- Allows styling it with lots of xml styling technologies.
- Better versioning support
JSON is not bad however, so if you just want to have simple plaint text cv's, json is good enough.
I do agree that with XML comes bloatness, complexity, and more crap. However from a pure technical point of view, its a better option for doing resumes.
That project seems dead now, and recent updates to my systems have resulted in me being able to build HTMLTXT but not PDF.
In the future, when looking for a job, I'll be looking at JSON instead. It might not be the best tool, but it seems to be what several _live_ and active projects are using.
- Allows extensibility with other xml standards (such as SVG and MathML in your resume, which might makes sense) - Allows linking to other stuff with XLink - Allows styling it with lots of xml styling technologies. - Better versioning support
JSON is not bad however, so if you just want to have simple plaint text cv's, json is good enough. I do agree that with XML comes bloatness, complexity, and more crap. However from a pure technical point of view, its a better option for doing resumes.