While this seems like a nice exercise, I wonder how much things would break when the JSON is slightly "off" in terms of the schema, which seems to be very ad-hoc.
And with so many standards for resume schemas going around, I fear this will end up in a http://xkcd.com/927/ situation.
Perhaps this exercise could've been more interesting if it were some nifty XSLT that took HR-XML and made HTML (preferably with tags that followed the hResume format) and LaTeX? The "XML Résumé library" http://xmlresume.sourceforge.net/ seems to be abandoned, but it is still worth to take a look.
I kind of thought JSON is [essentially] HR-XML. lol. But then again, I have not heard of Human Readable XML, and sort of chuckled at the thought of “HR” meaning human readable (until I googled it — __face–palm__).
Comments
While this seems like a nice exercise, I wonder how much things would break when the JSON is slightly "off" in terms of the schema, which seems to be very ad-hoc.
And with so many standards for resume schemas going around, I fear this will end up in a http://xkcd.com/927/ situation.
Perhaps this exercise could've been more interesting if it were some nifty XSLT that took HR-XML and made HTML (preferably with tags that followed the hResume format) and LaTeX? The "XML Résumé library" http://xmlresume.sourceforge.net/ seems to be abandoned, but it is still worth to take a look.
I really like OP's suggestion.
“Interesting” ≠ Better right?
I kind of thought JSON is [essentially] HR-XML. lol. But then again, I have not heard of Human Readable XML, and sort of chuckled at the thought of “HR” meaning human readable (until I googled it — __face–palm__).
Anyways, this is begging to feel a little like; http://xkcd.com/378/